Route Order
POST /orders/{id}/route action bearer
Executes routing logic to assign the optimal fulfillment node for each order line and creates Fulfillment Orders.
Overview
|
|
| ID |
route-order-api |
| Method |
POST |
| Path |
/orders/{id}/route |
| Classification |
action |
| Domain |
order |
| Capability |
order-orchestration |
| Service |
route-order |
| Application |
oms — OMS |
| Auth |
bearer |
Response
|
|
| Business Object |
fulfillment-order |
| Description |
Fulfillment-oriented grouping derived from an order for execution. |
| Lifecycle |
created → allocated → picking → packed → dispatched → delivered → failed-delivery → returned-to-sender → cancelled |
Events Emitted
| Event |
Classification |
Object |
Description |
fulfillment-order-created |
created |
fulfillment-order |
A Fulfillment Order has been created for a confirmed Order by the routing engine. |
Scenarios using order-orchestration
| Scenario |
Description |
Buy Online, Pick Up In Store |
Customer browses and purchases online, then collects the order from a physical store. The canonical |
Endless Aisle |
Store associate helps a customer order an item that is not physically stocked in the current store b |
Exchange Anywhere |
Customer exchanges an item purchased in any channel at any supported touchpoint. The original item i |
Ship From Store |
An online order is fulfilled by shipping the goods directly from a physical store rather than a cent |
Ship To Store |
Customer places an online order for collection at a chosen store while stock is sourced from a wareh |
Unified Return |
Customer returns an item regardless of the original purchase channel. The return may be initiated on |
Related APIs — order domain