Reference
What an order
management system decides
Four kinds of vendor sell something called an order management system, and they don't mean the same thing by it. A storefront's own order screen, a middleware router, a warehouse system's order module and an ERP's sales-order module all carry the name. The job is working out which of the four you're missing.
Start from the decision rather than the category. An order management system is the layer that decides which stock, from which location, fulfils which order — and holds that order's state from placed to settled. Everything else it does follows from owning that decision.
Four systems, and the one that owns the promise
These overlap in the brochures and not in the building. What matters is which of the four makes the allocation decision on your orders today. Often none of them does, and it happens by accident of sequence.
The storefront
Takes the order and knows everything about it except where it'll be fulfilled from. Shopify holds locations and can route, and for one channel and one location that's a complete answer. It can't see an order that arrived somewhere else.
The warehouse system
Runs the building: bins, picking paths, packing, dispatch. It's expert on what happens after an order is assigned to it, and deliberately incurious about how it got there. Asking a WMS to arbitrate between channels is asking the wrong floor.
The ledger
Values what happened after it has happened, in a form an accountant will accept. It sits downstream of every decision on this page. Where that line falls, and the four reconciliations that break across it, are covered in accounting and stock.
The order layer
Sits above all three and owns the promise: this unit, from this location, to this customer, in this priority. It's the only one of the four with a reason to know that a trade order and a website order want the same box.
Four things that break when nothing owns allocation
None of these arrives as an error. Each one arrives as a person doing a job by hand that nobody costed, and the job stays invisible until that person takes a holiday.
Two channels sell the same unit
A unit is only committed when something writes the commitment down, and a stock feed publishing an availability number isn't a commitment. Whichever channel is asked first wins, and during a promotion both are asked in the same second.
The split decision is made by the picker
An order with two lines in two locations either ships as two parcels or waits for a transfer. That's a cost decision, two shipping labels against a delayed delivery date, and with no rule it's taken by whoever reaches the order first, differently every time.
Trade and retail compete blind
A wholesale order for forty and six website orders for one arrive against the same stock. There's a right answer, and it depends on the margin, the customer and the replenishment date. Without a priority rule, the answer is whichever was keyed first.
Where is my order takes three systems
The sign that order state lives nowhere. Someone opens the storefront, the courier portal and a spreadsheet to answer one question, several times a day. That time is the running cost of having no order layer, and it never appears on a quote.
The four routes, compared on what they cost you later
Licence cost is the smallest and most published number in the decision. The figures that decide it (implementation, the mapping work when a SKU convention changes, the person who owns the integration) are specific to your catalogue and channel mix. What holds across all of them is where each route puts the logic, and so what it costs to change later.
| Storefront native | Middleware routing | Dedicated OMS | ERP sales-order module | |
|---|---|---|---|---|
| Where allocation logic lives | In the platform's own rules | In flows somebody authored | In the product, configurable | In the ERP, with the finance model |
| Adding a fifth channel | Only if the platform supports it | Another flow, and another to maintain | Usually configuration | A project, and often a partner |
| When a SKU convention changes | Contained | Every mapping is touched by hand | One mapping layer | Contained, but change-controlled |
| Where it breaks first | The second sales channel | The author leaving | A process the product didn't anticipate | Speed of change, not capability |
| When it's the wrong choice | More than one place holds stock | Nobody in-house will own the flows | One channel, one location | The finance model isn't the constraint |
Stok.ly, Brightpearl, Linnworks and Veeqo sit in the dedicated-OMS column; NetSuite and Khaos Control in the ERP column. How each physically connects to Shopify Plus, and where each connection type breaks, is the systems reference.
StoreBuilder Ltd earns referral commission from Shopify and holds an affiliate account with Stok.ly. No other vendor named on this page pays us. Commercial relationships
When the storefront is enough
One sales channel, one place stock sits, and orders in the low hundreds a month: the storefront's order screen is an order management system, and a good one.
The threshold is the moment a second place holds stock, or a second channel sells it. That's when allocation becomes a decision somebody has to own, so name the owner before the decision starts being taken by accident.
Where stock truth should live in the first place, multi-location inventory and the WMS-versus-3PL decision are the operations side of the same question.
Stock and fulfilmentChoosing where allocation lives
Which product should make the allocation decision depends on how partial orders are handled, whether a trade channel runs alongside retail, and what order volume the connectors have to carry.
We decide where allocation lives first, then choose the system that can hold it, so the commitment to the customer is written down somewhere. The systems that can hold it are set out, as their vendors publish them, on the stock control page.
The systems review starts there: which system makes the allocation decision today, whether anything writes the commitment down, and which of the four failures above a person is already handling by hand.
Start the systems reviewTell us what you need
What the systems are doing now, and what you need them to do. We'll tell you whether it's a platform problem or something cheaper.