Order management software: evaluate it on the failure path

What order management software does

Order management software captures orders from your sales channels, allocates inventory against them, routes them to a fulfillment location, and tracks their status through to delivery. Buyers usually evaluate it on channel coverage, inventory accuracy, warehouse and 3PL integrations, returns handling and reporting.

Those are the right features to compare. The thing that rarely appears on the comparison grid is what the software does when an order stops moving, and that is where the operational cost lives.

Every order is a promise. Keeyu keeps it. Order management software records the promise. It is usually silent when one breaks.

Evaluate it on the failure path, not the happy path

Every product in this category handles a clean order well. Order comes in, stock allocates, warehouse picks, carrier delivers. Differences show up on the exception path, which is what actually consumes your team's time.

Questions worth asking in a demo:

• What happens when an order does not reach the warehouse system at all?
• How do I find every order that has not progressed in the last 48 hours?
• Where does a fulfillment hold surface, and who gets told?
• What happens when stock sells that does not exist?
• Can it act on a stalled order, or only display it?

Most tools answer the display questions well and the action questions not at all.

There is a distinction I use in every evaluation, and it decides most of them. A system of record processes the transaction. A system of notification tells someone that something happened, and it is read only. A system of action detects, notifies and writes back into the systems that own the order. I laid that out on The Ecommerce Edge. Most order management software is the first kind, most post-purchase apps are the second, and the failure path needs the third.

Order management software is one of many systems that touch an order after the buy button, and each is good at its own job. None of them is linked to the promise the shopper was given: order before two, pay express, ship same day, get it tomorrow. So when something fails, it fails silently, as I said on Marketing for SMEs.

The failure mode that no single system catches

One retailer I came across had a customer service person working with 65 tabs open, alt-tabbing between storefronts, warehouses, carriers and ERP locations all day to answer order questions. Every one of those systems was functioning. The gap was that none of them held the whole picture and stitching them together was manual.

At the start of COVID in 2020 our warehouse sale revenue skyrocketed and the storefront stopped syncing orders with the warehouse. It oversold, and when the dust settled we had a thousand customers who had paid for something they would not get. The store was fine, the warehouse system was fine, the connection between them was not, and nothing raised an alarm.

I think of it as whack-a-mole: one week stockouts, the next fraud, a SKU mismatch or a failed delivery, and once you fix one thing something else pops up. Every system is doing its job, which is why buying a better system of record does not resolve it.

Integration reality

Assume some part of your stack has no usable API. It is extremely common in warehouses and with regional carriers. We lost two customers because we could not integrate with their systems, so our CTO Tahir built browser operator functionality that lets Keeyu work through the browser and read data from systems that were never built to be automated.

Our workaround for exactly that gap is a browser operator: we log in through the browser and our agent takes thousands of photographs of it and turns them into metrics, like an agent shopping the browser all the time. It can constantly scan a carrier portal like Royal Mail, and it is how we cover a Sydney 3PL notorious for giving nobody API access.

When you evaluate order management software, ask what happens with the one system in your stack that has no modern API. That answer determines whether you get real coverage or a well-integrated blind spot.

The honest number here is time, not features. We have built more than fifty integrations and are heading towards a hundred, each systemized so a new brand comes on fast, with the data coming from APIs, webhooks, FTP or the browser operator, which I talked through on Add To Cart. When you scope any integration project, ask for the two dates that matter: how many hours of your team's time it costs up front, and what happens when a system on the list is one the vendor has never connected to before.

The layer above the software

What is missing in most stacks is not another system of record but a system of action: something that knows what each order should be doing right now, notices when it stops, and does something about it.

At EHP Labs an out-of-stock workflow that took 45 minutes now runs in five, and at one of our customers the CX team went from 18 people to 8. A brand had 70 orders on its US Shopify storefront that never synced to the warehouse and had not shipped in three days. We detected it instantly, but nobody on their side had looked, and they would have found out from 70 "where is my order" tickets.

The workflow behind that number: triggered when the warehouse types 'out of stock' into NetSuite, it searches other stores for inventory, finds product alternatives, checks the ERP for next shipments, and if no replacement stock exists, cancels the order and processes the refund.

That is proactive e-commerce operations. Detect. Decide. Act. The customer gets what they want, on time, as promised.

That layer operates where helpdesk AI cannot reach: Return to Sender, Lost in Transit, awaiting collection, out-of-stock, resolved end-to-end before a ticket exists.

See how the workflows run or book a demo.

Cost this layer against the staffing it removes. One of our customers runs twenty support people year round and scales to forty for two months around peak, a number I gave on eCommerce Australia. Order management software does not change that second figure. Something that detects and fixes the underlying failures does.

Related reading

For the system category itself, read order management system. For fulfillment, see fulfillment. For the operational layer, read post-purchase operations.

• Order management systems: what a small team actually needs
• Ecommerce returns: the half of your return rate you caused
• Proactive vs reactive customer service: the real difference

• SCOR Digital Standard, RS.1.1 Order Fulfillment Cycle Time: order fulfillment cycle time, the standard measure.
• DeHoratius and Raman, Management Science, on inventory record inaccuracy: inventory records are wrong more often than the OMS assumes.
• Marketing for SMEs, Jevon Le Roux on the E-Commerce Mistake Costing Millions - the orchestration layer, and the 55% ticket cut at EHP Labs.
• Add To Cart #578, Stop Customer Problems Before They Start: Inside Keeyu's AI Ops - stuck returns, failed payments and orders caught mid-flight.
• The Breakout CEO #86, The Pivot This Founder Made After an Investor Called It Impossible - one in five US shoppers not getting orders on time, and the ticket ratios behind it.
• Founders in Motion, The Hidden Flaw In Every Fashion Brand (He Built the Fix) - the 2020 warehouse sale where a storefront sync failure left a thousand customers paid for stock they would not get.
• Spotlight Fridays, Spotlight Fridays with Jevon Le Roux - the 65 open tabs, and post-purchase failures as whack-a-mole across systems of record.