Order Management System for eCommerce: What It Really Solves
An order management system for eCommerce is the layer that pools your stock and routes every order across Shopify, Amazon, eBay and Etsy from one live figure. This guide shows UK multichannel sellers what an OMS really solves, and how to buy one sized to your operation — because most sellers are outgrowing spreadsheets and disconnected tools.
An order management system for ecommerce is the software layer that receives orders from every sales channel, decides where and how each one is fulfilled, and keeps stock, shipments, cancellations, returns and customer messages tied to the same order record. It is less about storing orders and more about making the same decisions consistently, hundreds of times a day.
The practical problem is that those decisions are usually made by people under time pressure. Which warehouse ships this order? Who gets the last unit when two channels sell it in the same minute? Should a three-line order go in one parcel or two? What happens to stock when a customer cancels after picking? When the rules live in someone’s head, the answers change from shift to shift, and the cost shows up as split parcels nobody planned, refunds that miss their deadline and customers asking where their order is.

An OMS decides which stock serves which order before anyone walks to the rack. Illustrative photograph, not an OpsMavix project.
Image credit: CHUTTERSNAP, Unsplash License. Resized only.
Key Takeaways
- An ecommerce OMS is a set of written decision rules: capture, routing, allocation, splitting, cancellation, returns and customer updates.
- Routing chooses the location; allocation chooses which order gets the stock. Keep the two rules separate.
- Split shipments are a cost and service decision, so compare parcel, transfer and waiting costs before splitting.
- Cancellations need different handling before allocation, after allocation and after picking.
- UK consumer refunds have legal deadlines, so returns status must drive the refund clock.
- Test any system against one awkward week of real orders before choosing configuration, packaged software or a custom build.
In this guide:
- 1. Understand What an Ecommerce OMS Decides
- 2. Capture Orders From Every Channel Once
- 3. Route Each Order to the Right Location
- 4. Allocate Stock When Supply Is Short
- 5. Decide When to Split a Shipment
- 6. Handle Cancellations at Every Stage
- 7. Bring Returns Back Into Stock and Refunds
- 8. Keep Customers Updated and Choose the System
- Frequently Asked Questions
- How OpsMavix Can Help
1. Understand What an Ecommerce OMS Decides
Think in decisions rather than screens
Most descriptions of an order management system list features: order list, inventory sync, label printing. A more useful way to evaluate one is to list the decisions it makes on your behalf and the information each decision needs.
| Decision | Question the OMS answers | Information it needs |
|---|---|---|
| Capture | Is this a valid, new order we can act on? | Channel order, SKU mapping, address, service, payment status |
| Routing | Which location should fulfil it? | Stock by location, destination, location capacity, courier cut-offs |
| Allocation | Which orders get the stock when there is not enough? | Available stock, order age, service level, channel priority |
| Splitting | One parcel later, or several parcels now? | Line availability, parcel costs, promised delivery date |
| Cancellation | What happens to stock, pick lists and payment? | Order stage, allocation, pick status, channel rules |
| Returns | Where does the item go and what is refunded? | Inspection result, original payment, legal deadlines |
| Customer updates | Who tells the customer what, and when? | Channel messaging rules, tracking events, exceptions |
Know where this guide fits
This guide covers the decision rules inside an ecommerce OMS. For the step-by-step order journey, see the ecommerce order management process flow. For a UK buyer’s view of software options, see order management software UK. For the general definition, see what an order management system is.
2. Capture Orders From Every Channel Once
Normalise without losing the original
Each channel sends orders in its own format, with its own order number, status names and address fields. The OMS should convert every order into one internal structure while keeping the channel’s original reference. That reference is what lets tracking, cancellations and refunds flow back to the right place later.
Capture checklist
- Every channel SKU maps to one internal product, bundle or kit.
- Bundles expand into their component lines so stock is reserved correctly.
- The delivery service requested exists in your courier set-up.
- Duplicate orders from a repeated feed or a retried connection are rejected.
- Orders with missing data go to a named exception status with an owner.
- The original channel, order number and order time are stored unchanged.
Hypothetical bundle example
Assume a gift set is sold as one listing but made from 2 candles and 1 holder. An order for 3 gift sets must reserve 3 × 2 = 6 candles and 3 × 1 = 3 holders. If the OMS only reserves 3 “gift sets”, the candle stock shown to other channels is overstated by 6 units. Bundle expansion belongs at capture, not at the packing bench.
3. Route Each Order to the Right Location
Separate routing from allocation
Routing chooses which location fulfils an order: a main warehouse, a shop, a third-party logistics provider or a supplier that ships direct. It matters as soon as stock sits in more than one place. Packaged platforms often provide configurable rules for this. For example, Shopify’s order routing documentation describes default rules to minimise split fulfilments, stay within the destination market and ship from the closest location, applied in sequence with each rule filtering the result of the previous one.
Whatever tool you use, write the rules down in the order they apply, because the sequence changes the outcome.
Common routing rules
| Rule | What it does | Watch out for |
|---|---|---|
| Complete order first | Prefers a location that holds every line | Can send orders far away to avoid one extra parcel |
| Closest location | Prefers the location nearest the customer | Distance is not always cost; courier contracts differ by site |
| Ranked locations | Uses a fixed priority list, such as warehouse before shop | Shops may need stock protected for walk-in customers |
| Capacity check | Skips a location that has reached its daily limit | Needs an accurate, maintained capacity figure |
| Channel restriction | Sends certain channel orders only to set locations | Marketplace or third-party fulfilment stock may be ring-fenced |
| Cut-off time | Prefers a site that can still meet today’s collection | Requires live knowledge of courier collection times |
Record why an order was routed
Store the rule that decided each route. When a customer asks why their order came from the other end of the country, or a shop manager asks why their stock went to web orders, the answer should be in the order history rather than in someone’s memory.
4. Allocate Stock When Supply Is Short
Allocation is a priority rule
Allocation reserves units at a location against specific order lines. When there is enough stock, it barely matters which order is served first. When there is not, the allocation rule decides who waits. The calculation behind sellable stock is covered in available to promise, and channel overselling in how to prevent overselling.
Hypothetical shortfall example
Assume a warehouse holds 10 units of a SKU after a delayed delivery. Released orders ask for 14 units: 6 from the website, 5 from a marketplace and 3 from a trade customer.
| Rule | Website (6) | Marketplace (5) | Trade (3) | Units short |
|---|---|---|---|---|
| Oldest order first (marketplace, then trade, then website) | 2 | 5 | 3 | 4 |
| Service level first (marketplace promise, then website, then trade) | 5 | 5 | 0 | 4 |
| Proportional share, rounded down then topped up | 4 | 4 | 2 | 4 |
Every rule leaves 14 - 10 = 4 units short; the rules only change who carries the shortage. In the proportional row, 10 ÷ 14 of each demand gives 4.29, 3.57 and 2.14, which round down to 4, 3 and 2 (9 units); the tenth unit goes to the largest remainder, the marketplace at 0.57, making 4, 4 and 2. Whichever rule you choose, apply it the same way every time and show the short lines as a named exception.
Keep unsellable stock out of the pool
Returns awaiting inspection, damaged units and stock already promised to another location should not appear as available. If they do, the allocation rule is working from the wrong number. For running one stock figure across channels, see multi-channel inventory management.

Every extra parcel in a split shipment is another label, collection and tracking event to manage. Illustrative photograph, not an OpsMavix project.
Image credit: Claudio Schwarz, Unsplash License. Resized only.
5. Decide When to Split a Shipment
Three ways to handle an incomplete order
When no single location can complete an order, the OMS has three options: ship what is available now and the rest later, move stock between locations and ship once, or hold the whole order until it is complete. Each has a different cost and a different effect on the customer’s delivery date.
Hypothetical split shipment example
Assume a customer orders three items. The main warehouse has two of them; the third is in a shop 60 miles away. The figures below are hypothetical and exclude VAT.
| Option | Calculation | Cost | Delivery effect |
|---|---|---|---|
| Split: two parcels now | £4.20 warehouse parcel + £3.90 shop parcel | £8.10 | All items arrive in 1 to 2 days, in two deliveries |
| Transfer, then one parcel | £2.50 share of a stock transfer + £4.80 single parcel | £7.30 | One delivery, about 2 days later |
| Hold until restock | £4.80 single parcel, no transfer | £4.80 | One delivery, depends on supplier date |
Splitting costs £8.10 - £7.30 = £0.80 more than transferring, and £8.10 - £4.80 = £3.30 more than holding. At 200 such orders a month, always splitting instead of transferring costs 200 × £0.80 = £160 a month, or £1,920 a year. The decision is whether two extra days, or an uncertain restock date, is worth more or less than that to your customers. There is no universal answer, but there should be a written one.
Split shipment rules to agree
- Maximum number of parcels per order before a manager reviews it.
- Which products are never split, such as sets or matched items.
- Whether delivery charges change when you split for your own convenience.
- How each parcel’s tracking number is attached to the order and sent to the channel.
- What the customer is told when the first parcel leaves without the rest.
Respect delivery commitments
For UK consumer sales, the Consumer Rights Act 2015, section 28 provides that, unless a time is agreed, goods must be delivered without undue delay and in any event within 30 days of the contract. Holding an order for a restock is therefore not open-ended. Set the OMS to flag held orders well before the date you promised or the legal default.
6. Handle Cancellations at Every Stage
The stage decides the work
A cancellation is cheap before stock is reserved and expensive after a parcel is packed. The OMS should recognise the order’s stage and trigger the right steps automatically.
| Order stage | Stock action | Warehouse action | Payment and channel action |
|---|---|---|---|
| Captured, not allocated | None needed | None | Cancel on the channel and void or refund payment |
| Allocated, not picked | Release the reservation | Remove from the next pick list | Cancel on the channel and refund |
| Picked, not dispatched | Return units to a putaway location | Stop the parcel and restock | Cancel, refund and record the reason |
| Dispatched | No immediate change | Try to intercept with the courier if offered | Treat as a return once the parcel comes back |
Seller cancellations need reasons
When you cancel because stock is missing, the cancellation is your decision, not the customer’s. Marketplaces generally track seller-initiated cancellations in their own performance measures, so check each channel’s current policy and record a reason code for every cancellation. A rising count of “out of stock” reasons usually points back to allocation or stock accuracy rather than to the cancellation process.
Hypothetical partial cancellation
Assume an order contains items priced £20, £15 and £25, a total of £60, and the £15 item cannot be supplied. The OMS should cancel one line, refund £15 on the original payment method, keep the other two lines allocated and update the channel so the customer sees £60 - £15 = £45 of goods still due. Whether any delivery charge is also refunded in this case is a policy decision to write down, not something to decide per order.
7. Bring Returns Back Into Stock and Refunds
Run returns as linked records
A return should link to the original order, channel and payment. It moves through requested, authorised, received, inspected and resolved. The inspection result sets the stock outcome: back to sellable, to a seconds location, to repair or to write-off. Until inspection, keep returned units out of available stock. The reverse flow is covered in more depth in returns management.
Let the law set the refund clock
For most distance sales of goods to UK consumers who cancel within the cancellation period, regulation 34 of the Consumer Contracts Regulations 2013 requires a refund without undue delay. Where the trader has not offered to collect the goods, the deadline is the end of 14 days after the trader receives the goods back or, if earlier, after the consumer supplies evidence of sending them. The refund must normally use the same means of payment, and the original delivery charge is refundable up to the cost of the least expensive common delivery option the trader offered. Exceptions apply, so have the rules for your products confirmed.
Hypothetical delivery refund example
Assume a customer paid £50 for goods plus £6.99 for next-day delivery, while your standard delivery option was £3.99. If the customer cancels and returns the whole order within the rules, the refund is £50 + £3.99 = £53.99, not £56.99, because the extra £6.99 - £3.99 = £3.00 for the faster service need not be refunded. Build that calculation into the OMS rather than leaving it to the person processing the return.
Returns checklist
- The refund deadline is calculated from the earlier of receipt or proof of sending.
- Returned stock is quarantined until inspected.
- Inspection outcome updates stock in the right location.
- The refund is issued through the original channel and payment method.
- Return reasons are recorded so product or packing problems can be traced.
8. Keep Customers Updated and Choose the System
Decide who sends each message
Customer updates fail when two systems both send a message, or when neither does. Marketplaces often control their own customer communications, while your website may rely on your OMS or ecommerce platform.
| Event | Typical sender | OMS responsibility |
|---|---|---|
| Order confirmed | Channel or website | Store the confirmation reference |
| Part shipped | Channel, using tracking you supply | Send each parcel’s tracking against the right lines |
| Delay or backorder | Your team or website | Flag held orders before promised dates |
| Cancelled line | Channel and your team | Update the channel line status and refund amount |
| Return received and refunded | Channel or website | Record receipt date, refund date and amount |
Compare system approaches fairly
| Approach | Where it fits | Limitations to check |
|---|---|---|
| Configure your ecommerce platform | One main channel and one or two locations | Routing depth, marketplace orders, bundle handling |
| Connector or channel manager | Several channels with simple fulfilment | Split handling, cancellation sync, error visibility |
| Packaged OMS | Multichannel volume needing routing and allocation rules | Fit with your exceptions, couriers, returns and pricing |
| Focused custom application | One valuable gap packaged tools handle poorly | Scope, support, maintenance and integration effort |
| Full ERP, packaged or custom | Orders tightly tied to purchasing, production and finance | Implementation scope, migration and internal capacity |
Packaged order management tools cover the standard path well and can be quick to start. A custom application or ERP earns its place when your routing, allocation or returns rules repeatedly fall outside what configuration supports. Ask each option to run the same scenario: a bundle order, a short allocation, a split shipment, a partial cancellation and a return with a delivery refund. Include licences or build cost, integrations, support and future changes in the comparison. For a UK shortlist and buying criteria, see order management software UK.
Frequently Asked Questions
What does an order management system for ecommerce do?
It captures orders from every channel into one record, routes each to a fulfilment location, reserves stock, manages shipments, cancellations and returns, and sends status and tracking back to the channel.
What is the difference between order routing and allocation?
Routing decides which location fulfils an order. Allocation reserves specific units against order lines and decides which orders are served first when stock is short.
When should an OMS split a shipment?
When the cost of the extra parcel is worth the faster delivery to the customer. Compare split, transfer and hold costs against your delivery promise, and record the rule.
How should cancellations update stock?
Release reservations if the order is allocated but not picked, restock picked units through a putaway step, and treat dispatched orders as returns. Record a reason code each time.
How quickly must UK online retailers refund a cancelled order?
For most consumer distance sales of goods, without undue delay and within 14 days of receiving the goods back or, if earlier, the customer’s proof of sending, where the trader has not offered to collect. Exceptions apply.
Do I need an OMS if I sell only on my own website?
Not always. A single channel with one location can often run well on the ecommerce platform’s own order tools. Marketplaces, extra locations and bundles are what usually create the need.
Can OpsMavix build an ecommerce order management system?
Yes. OpsMavix can build focused applications or a full custom ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.
How OpsMavix Can Help
OpsMavix can document your routing, allocation, split shipment, cancellation and returns rules, then test them against real orders before any software decision is made.
That may involve configuring your current platform, connecting channels and couriers, introducing ecommerce inventory automation, adding an inventory automation system, building a wholesale order management system for trade orders or developing a full custom ERP.
Contact OpsMavix with one recent split or cancelled order, the records behind it and the handoff that creates the most rework. We can use that evidence to define requirements and a practical pilot.
Getting value from OpsMavix? Add us as a preferred source on Google — you'll see more of our operations content in your AI Overviews, AI Mode and Search.