Omnichannel: align inventory, promise and customer experience
Customer promise depends on interpretable availability, allocation rules and shared status through returns.
The decision thread
This dossier follows 5 control points, from “Unify the order” to “Orchestrate returns”.
Systems to align: EMS Commerce · ERP · PROTECH WMS · POS · E-commerce · TMS.
Unify the order
Keep one order and line identity when the channel, fulfilment site or handover method changes.
- Which data establishes “Unify the order”?
- Who decides when “Unify the order” reveals a variance?
- Which record confirms the outcome of “Unify the order”?
Define availability
Separate physical, reserved, blocked, in-transit and promiseable stock with known horizon and freshness.
- Which data establishes “Define availability”?
- Who decides when “Define availability” reveals a variance?
- Which record confirms the outcome of “Define availability”?
Allocate by context
Make customer priority, channel, margin, proximity, capacity and stock-protection rules explicit.
- Which data establishes “Allocate by context”?
- Who decides when “Allocate by context” reveals a variance?
- Which record confirms the outcome of “Allocate by context”?
Execute without breaks
Connect acceptance, fulfilment, carrier handover, collection, delivery and incident without rebuilding the journey afterwards.
- Which data establishes “Execute without breaks”?
- Who decides when “Execute without breaks” reveals a variance?
- Which record confirms the outcome of “Execute without breaks”?
Orchestrate returns
Connect reason, product, condition, refund, restocking and ownership through to actual closure.
- Which data establishes “Orchestrate returns”?
- Who decides when “Orchestrate returns” reveals a variance?
- Which record confirms the outcome of “Orchestrate returns”?
Associated solutions
Turn these questions into a scoping grid.
Questions, ownership, evidence and comparison criteria for workshops.
- Scoping questions
- Points to watch
- Comparison criteria
Sources & reference framework
The scope must be tested against the definitions, events and responsibilities of each system below.
Omnichannel works when the displayed promise stays connected to real capacity and every execution confirmation.
Frequently asked questions
How should these insights be used?
Each insight structures the discussion. Scope, data and ownership still need to be contextualised with your teams.
How can a topic be connected to my IT landscape?
Each insight structures the discussion. Scope, data and ownership still need to be contextualised with your teams.
Do these resources replace scoping?
Each insight structures the discussion. Scope, data and ownership still need to be contextualised with your teams.
Recommended insights
WMS · INVENTORYInventory optimisation: seven questions to ask before choosing a WMS
A high-performing WMS is more than a feature list. It must align with operational priorities, data, processes and responsibilities.
12 min
TMS · TRANSPORTNext-generation TMS: five levers to reduce cost and emissions
Transport performance starts before departure: demand quality, scenario choice, allocation, evidenced execution and financial reconciliation.
11 min
INDUSTRY · PLANNINGIndustrial planning: align demand, capacity and disruption
Useful planning connects demand, materials, resources and field events without hiding assumptions or trade-offs.
10 min
MAINTENANCE · ASSETSPredictive maintenance: move from alert to decision
A signal becomes useful when connected to an asset, criticality, history, work capacity and a documented decision.
9 min