WMS Selection
Part of Fulfilment technology implementation
Preparing clean product and location data
Check product identifiers, units, barcodes, warehouse locations and proposed opening-stock records before a fulfilment system launch.
Prepare product and location data so every sellable item, handling unit and recorded storage position matches the intended goods and physical place. The launch deliverable is an approved record set and a visible decision for each exception that could affect warehouse work.
Establish identifiers and owners
List every system that holds a product reference: storefront, purchasing and warehouse. For each product and variant, record each system's identifier, the barcode workers read, the unit it represents and who may change it. Keep a cross-reference where systems legitimately use different numbers. Matching descriptions alone does not prove two records are the same variant.
Check codes against the physical pack. A single item and a carton may have different codes and quantities. Record the approved conversion before quantities are imported or work rules use them.
In Dynamics 365 Supply Chain Management, an item number cannot uniquely identify a product variant; it must be combined with all product dimensions defined on the product master.
Product identifier consistency across systems
- System
- Storefront
- Unit of Measure
- Each
- Owner
- Marketing Team
- System
- Purchasing
- Owner
- Procurement Team
- Unit of Measure
- Each
- Owner
- Warehouse Operations
Validate the fields used in work
| Record | Data check | Physical check |
|---|---|---|
| Product or variant | Intended identity, active status and usable code | Does the code on the goods resolve to the right variant? |
| Unit | Stock, purchase and pick units with approved conversions | Is a carton quantity being mistaken for individual pieces? |
| Location | Distinct ID, type, allowed use and active status | Is the ID fixed to the intended position? |
| Proposed opening stock | Item, quantity, unit, location and status; tracked identity where needed | Are the goods there and in that condition? |
Add dimensions, weight, batch or serial fields when the planned workflow needs them. Leave an unknown value for investigation; do not fill it with a plausible default. A made-up quantity or location can enter live work unnoticed.
Location IDs must also fit the proposed warehouse rules. Microsoft's WMS-enabled warehouse setup uses location formats, types and profiles, and Microsoft describes location directives as rules that help identify pick and put locations. Review equivalent dependencies in the system being implemented; do not approve a file solely because its IDs are distinct.
Resolve exceptions against physical evidence
Check for duplicate product codes, retired variants referenced by open orders, duplicate location IDs, missing or invalid conversions, and stock assigned to closed or unsuitable positions. Give each exception a source row, owner and proposed correction. Verify ambiguous products against product and purchasing evidence before merging records.
Walk the warehouse with a sample of the proposed location list, including pick faces, reserve and any receiving, returns or hold positions that will carry recorded stock. Compare the printed ID with its physical position and the data row. When they disagree, correct the label and record together.
For proposed opening stock, agree the item, location, unit and status detail needed for the later count and transfer. Check that the chosen import route accepts the records and exposes rejected rows. The live observation time, final quantity load and reconciliation belong in the cutover plan, after the underlying product and location records are approved.
Hand over the approved records, cross-references and exception log. Hold any unresolved item that could cause a worker to pick or move the wrong stock.
