- Feature
- Source-system inventory status mapping
- Availability
- Generally available in Supply Chain Management 10.0.49, enabled by default
- Industry focus
- Retailers using Dynamics 365 warehouse management with a different ERP
Not every retailer wants to replace its ERP to modernize its warehouses. Many keep a merchandising or finance system they trust and add Dynamics 365 warehouse management in WMS-only mode to run their distribution centres. That approach can deliver warehouse improvements quickly, but it depends on the two systems agreeing about the state of stock.
The industry challenge
Inventory status describes the condition of stock: available, damaged, on quality hold, reserved for returns processing and so on. The retailer's ERP has its own list of statuses, built around how merchandising and finance think about stock. Dynamics 365 warehouse management has its own, built around warehouse operations.
When the two lists do not match, integration teams build custom translation logic. Every new status, or every change in how a status is used, means changing code on one side or both. Mistakes lead to stock appearing available in the ERP when the warehouse has it on hold, or the reverse, with consequences for store replenishment, online availability and financial reporting.
What Microsoft delivered in Supply Chain Management 10.0.49
Supply Chain Management 10.0.49 adds source-system inventory status mapping for WMS-only mode, enabled by default. Inventory statuses used by the external source system can be mapped to statuses in Dynamics 365 warehouse management.
Translation between the two systems becomes configuration rather than custom integration code.
Where the value shows up
| Business area | Impact |
|---|---|
| Integration | Status translation handled through configuration, not bespoke code |
| Stock accuracy | ERP and warehouse agree on which stock is available, held or damaged |
| Omnichannel availability | Fewer cases of selling stock that is actually on hold |
| Change management | New statuses can be added through mapping updates |
| Project speed | Faster WMS-only rollouts with less integration build |
A worked scenario
(An illustrative example.) A department store group keeps its long-standing merchandising and finance ERP but implements Dynamics 365 warehouse management in WMS-only mode at its main DC. The ERP uses statuses such as sellable, faulty, return to vendor and quarantine; the warehouse uses its own set.
Instead of building translation logic into the integration, the project team configures the status mapping. When a quality inspector puts a batch of returned items on hold in the warehouse, the mapped status reaches the ERP correctly, so the items are not shown as available online. Later, when the merchandising team introduces a new status for clearance stock, the change is handled by updating the mapping.
Adoption considerations
- Agree a status model. Business teams on both sides should agree what each status means before mapping begins.
- Keep mappings simple. Avoid many-to-many mappings that make behaviour hard to predict.
- Assign ownership. Decide who maintains mappings when statuses change.
- Test round trips. Check that status changes in each system arrive correctly in the other.
- Review existing integrations. If custom translation code exists, plan how to retire it safely.
The bottom line
For retailers running Dynamics 365 warehousing beside another ERP, agreeing on inventory status is essential and often fragile. Built-in source-system status mapping turns that agreement into configuration, which cuts integration effort and reduces errors in stock availability. It makes the WMS-only approach more practical to run. An experienced Dynamics 365 warehouse adviser can help you design the status model and mappings.
Source: Microsoft: What's new or changed in Dynamics 365 Supply Chain Management 10.0.49