Migration & integrations
OMS
Order Management System
An OMS, or order management system, is the layer that decides how each order is routed, fulfilled, and tracked across warehouses, stores, and 3PLs. It is what makes ship-from-store, split shipments, and partial returns work as one coherent process. Merchants selling through several channels usually need one; a single-warehouse store typically does not.
Why it matters
An OMS becomes necessary at the point where "which warehouse should ship this" stops having an obvious answer. One warehouse and one channel needs no routing logic. Three locations, a 3PL, retail stock, and orders arriving from a website and two marketplaces needs a system making that decision consistently.
Without one, the decision gets made by a person, using judgement, differently each time. The results are the familiar ones: orders shipped from the wrong location, split shipments that should have been consolidated, and stock that appears available in aggregate while being in the wrong place.
The cost sits in shipping spend and delivery times, both of which are visible to the customer, and in the staff time spent resolving exceptions that a rule would have handled.
How it works on Shopify
Shopify's own fulfillment model — locations, fulfillment orders, and routing rules — covers a meaningful range of cases, and many merchants who think they need an OMS need to configure that properly first.
A dedicated OMS earns its place when routing has to weigh several factors at once: proximity to the customer, stock availability, shipping cost, warehouse capacity, and whether splitting an order is cheaper than shipping from further away. It also handles the reverse flow, which Shopify models more simply — returns arriving at a different location from the one that shipped.
The ownership question is the same as every integration. Shopify usually stays the system of record for the order and the customer; the OMS owns routing, fulfilment state, and inventory allocation. Both writing fulfilment status is how orders end up in contradictory states.
Where an ERP is present, the boundary needs deciding explicitly, since ERPs frequently claim some of the same responsibilities.
Common mistakes
- Buying one instead of configuring locations. Shopify's native routing handles more than most merchants have tried.
- Unclear ownership of fulfilment state. Two systems marking orders fulfilled produces reconciliation work forever.
- Routing on stock alone. Ignoring shipping cost and delivery time optimises the wrong thing.
- No exception handling. Every routing system produces orders it cannot resolve. Someone needs a queue and a process.
- Ignoring returns. Reverse logistics is where the OMS case is often strongest and least examined.
- Adding it during peak. Routing changes need a quiet period to stabilise.
When you need help
The assessment is the valuable part, and it frequently concludes that Shopify's native capabilities plus a properly designed location model would solve the problem at a fraction of the cost.
Where an OMS is warranted, the work is the boundary design: which system owns the order, which owns routing, which owns inventory allocation, and how they reconcile when they disagree. Multi-system fulfilment setups fail at those seams rather than inside any one system, and the seams are decided during planning.
Related terms
- FulfillmentFulfillment is everything that happens after the order is placed: picking, packing, shipping, tracking, and handling returns. It is where most of a store's post-purchase customer experience actually lives, and where margin quietly leaks. Shopify models it through fulfillment orders and locations, which is what lets a store split one order across warehouses.
- 3PLA 3PL, or third-party logistics provider, is an outsourced warehouse that stores your inventory and ships orders on your behalf. It removes the fixed cost of running a warehouse and usually improves delivery times through multiple locations. The integration matters as much as the rates: inventory and fulfillment status must sync back to Shopify reliably, or oversells follow.
- ERP integrationERP integration connects Shopify to the system a business runs its operations on — NetSuite, SAP, Business Central — so products, inventory, orders, and invoices stay in sync. The ERP is normally the system of record for stock and pricing, and Shopify the sales channel that reflects it. Getting the sync direction and cadence right is what prevents overselling.