Part of mPorts OMS
Ship every order from the right place.
Fulfillment in mPorts OMS is the capability that decides where an order is fulfilled from and what happens when that plan fails. It covers fulfillment planning, warehouse and source selection, and fulfillment recovery.
Choosing where an order ships from is a cost decision made hundreds of times a day, usually by whichever rule was easiest to implement. Distance, available stock, warehouse cost and the promised date rarely agree, and the cheapest plan is not always the one that keeps the promise.
Recovery matters more than planning, because plans fail routinely. A warehouse cannot complete all lines; a location is short; a carrier misses a pickup. Treating that as the normal case rather than the exception is the difference between a procedure and an investigation.
What this looks like in the product
An interface diagram using the product’s real navigation and field names — no customer data.
Fulfillment planning
Where this order ships from, and why
- Candidate locationsstock · cost · distance
- Selected sourceagainst promised date
- Lines shortrecovery required
- Plan statusstate
-
Fulfillment planning
Deciding where an order is fulfilled from, before the pick.
-
Source selection
Which location or supplier, against stock, cost and the promised date.
-
Fulfillment recovery
What happens when the plan cannot be met — designed for, not improvised.
-
Warehouse cost
Cost analysis attached to the decision rather than reported after it.
Questions buyers ask
- Can it split an order across warehouses?
- Splitting is a fulfillment planning decision. What a given configuration does depends on the policy set for it, which is the point — it is a decision you make rather than a behaviour you discover.
- What happens when a warehouse cannot fulfill?
- That is what fulfillment recovery is for. The order stops at a named stage rather than silently stalling, which is what makes the next step a procedure.