Watch an order. Not from the customer’s perspective but from inside the operation.
A customer clicks “place order” at 2:47 PM on a Tuesday. The order contains three items: one from the warehouse in Ohio, one from a store in Denver that offers ship-from-store, and one that’s drop-shipped directly from the vendor. The customer selected expedited shipping and applied a promotional discount that took 20% off the second item. They’re paying with a gift card covering part of the total, credit card for the rest.
In the next few seconds, that simple customer action triggers a cascade of complexity.
The moment of order
The e-commerce platform captures the order. But “capture” is just the beginning. The system needs to:
Validate inventory. Are all three items actually available at the locations that were promised? Availability was checked at cart, but inventory moves. Between adding to cart and completing checkout, someone else might have bought the last unit.
Process payment. The gift card system needs to authorize the partial payment. The credit card processor needs to authorize the remainder. Both need to succeed; if one fails, the order can’t proceed.
Apply promotions correctly. That 20% discount on the second item: how does it interact with the expedited shipping charge? Does it apply before or after tax? The promotional rules engine needs to calculate correctly or the customer is over- or under-charged.
Split or consolidate? Three items from three sources. Ship as three separate packages? Wait until all items are ready and ship together? This decision affects shipping cost, customer experience, and operational complexity.
All of this happens in the seconds between “place order” and “order confirmed.”
Routing and fulfillment
Now the order needs to reach the places that will fulfill it. Each item has a different path.
The warehouse item goes to the warehouse management system (WMS). The order appears in a pick queue, gets assigned to a picker, gets located in the warehouse, picked, packed, and labeled. If the item isn’t where the WMS thinks it is, exceptions occur. If the item is damaged, exceptions occur. If the packer runs out of the right-sized box, decisions happen.
The ship-from-store item goes to... what? Stores often don’t have a WMS. They might have a store fulfillment app, a notification system, or just an email. The store associate needs to find the item on the floor (or in the back), pack it appropriately (stores aren’t optimized for shipping), and get it to a carrier. Store fulfillment processes are rarely as mature as warehouse processes, so this is where errors concentrate.
The drop-ship item goes to the vendor. The order data needs to be transmitted in a format the vendor accepts, which might be EDI, an API call, or heaven forbid, a manually-processed email. The vendor fulfills from their own inventory, but you’re on the hook for the customer experience.
Three items, three fulfillment paths, three potential points of failure.
The exception landscape
If everything went as expected, order management would be straightforward. Nothing goes as expected.
Inventory exceptions. The item wasn’t where it was supposed to be. The warehouse shows 5 units, but the shelf has 3. The store shows available, but it was sold in-store between online purchase and fulfillment attempt.
Payment exceptions. The credit card authorization succeeded, but capture fails days later. The gift card balance was already used. The fraud system flags the order for review after it was already confirmed.
Fulfillment exceptions. The item is damaged. The carrier missed the pickup. The vendor is out of stock despite their feed showing availability. The store associate can’t find the item and marks it unfulfillable.
Customer-initiated changes. The customer wants to cancel one item. Add an item. Change the shipping address. Upgrade to faster shipping. Each change ripples through the system: some are easy, some are impossible depending on fulfillment state.
External events. Weather delays carrier pickup. A warehouse system goes down. A vendor stops shipping temporarily. Global supply chain disruption (remember 2020?) makes everything uncertain.
Each exception needs a response. Some can be automated; most require human judgment and intervention. The quality of exception handling often determines the quality of the customer experience more than the happy-path processing does.
Visibility and communication
While all this happens operationally, the customer expects to know what’s going on.
Order confirmation. Immediate: the customer needs to know the order was received and what they’re getting.
Shipping confirmation. When items ship. But if items ship separately from three locations, that’s three shipping confirmations. Is that helpful or overwhelming?
Tracking. The customer wants to know where their stuff is. But you have three carriers (warehouse uses UPS, store uses FedEx, vendor uses USPS), three tracking numbers, three different tracking experiences.
Proactive communication about problems. If an item is delayed, the customer shouldn’t find out by tracking a package that hasn’t moved. Proactive communication preserves trust; silence erodes it.
Delivery confirmation. Ideally unified (“your order has been delivered”), even when three packages arrived on three different days.
Orchestrating this communication across multiple fulfillment streams, with accurate and timely information, while avoiding spamming the customer with twelve emails about one order: that’s a user experience design problem layered on top of a data integration problem.
The returns dimension
The order doesn’t end at delivery. Returns are part of order management too.
The customer decides to return one item. Where can they return it? The warehouse item might go back to the warehouse. The ship-from-store item might go back to any store. The drop-ship item might need to go back to the vendor.
Does the customer get a label? Store credit or refund to original payment? What if they paid with a gift card that’s been discarded? What if the promotional discount made the returned item $0? Do they get money back, or just the item value?
Return processing needs to handle condition assessment (is the item resalable?), inventory adjustment, financial reconciliation, and customer communication. Returns often touch different systems than fulfillment and frequently have worse process definition.
The system landscape
Supporting all this is a constellation of systems:
Order Management System (OMS). The hub that orchestrates order flow, maintains order state, routes to fulfillment, handles exceptions, and tracks everything. Some retailers use their e-commerce platform’s built-in OMS; others use dedicated systems.
Warehouse Management System (WMS). Controls warehouse operations: receiving, putaway, picking, packing, shipping.
Store systems. POS, store inventory, store fulfillment applications. Often less integrated than warehouse systems.
Payment systems. Gateway, processor, fraud screening, gift card system. Often multiple vendors.
Carrier systems. Rate shopping, label generation, tracking integration. Multiple carriers with different APIs.
Vendor/partner systems. EDI or API connections for drop-ship, marketplace, or wholesale fulfillment.
Customer communication systems. Email, SMS, app notifications. Need order data to communicate accurately.
Making these systems work together (passing orders, status updates, inventory changes, and exception information smoothly) is the integration challenge at the heart of order management.
Why this matters
Order management is where all the complexity of commerce converges. Inventory, payments, fulfillment, logistics, customer communication, exceptions, returns. All of it touches every order.
The customer doesn’t see this. They see “order confirmed” and “your package is on the way.” The simplicity of their experience depends on the sophistication of the operation behind it.
Retailers who treat order management as a solved problem (just use whatever came with the e-commerce platform) often find it becomes a constraint as they grow. Ship-from-store doesn’t work well. Inventory isn’t accurate. Exceptions pile up. Customer service becomes a bottleneck.
Retailers who invest in order management capability (robust OMS, clear fulfillment processes, strong exception handling, good communication) create operational advantage. They can promise more, fulfill more reliably, and recover more gracefully when things go wrong.