OMS in retail: what data it must sync with ERP, POS and the online store to avoid stalled orders

An order that gets stuck between purchase confirmation and delivery almost never stalls for a single reason. It stalls because the system that should be coordinating inventory, payments, picking, invoicing and delivery, the OMS or Order Management System, does not have the full picture, gets it late, or does not have it in sync with the rest of the systems. This article explains what an OMS does in retail from the point of view of daily operations, not theory, and what specific data it needs to receive and send so an order moves without friction from confirmation to delivery.

Quick summary

• An OMS does not replace the ERP or the WMS: it coordinates between them. Its value depends almost entirely on the quality of its integrations.
• Stalled orders are almost always explained by four causes: stock out of sync, payment confirmation that never arrives, statuses that do not make it back to the channel, and returns that do not release inventory.
• Before switching OMS it is worth ruling out that the problem is one of integration: that is more common and much cheaper to solve.

What an OMS actually does in the operation

The OMS is the system that orchestrates the full life cycle of an order: where it will be prepared, with which stock, how it will be invoiced, who will ship it and what happens if it has to be returned. It does not replace the ERP or the WMS; it coordinates between them. In a single-channel operation, that coordination is simple and the ecommerce platform often handles it on its own. The complexity appears when the same order can be fulfilled from three different places, a central warehouse, a branch with available stock or a supplier with drop shipping, and someone has to decide which one makes sense in each case. That decision, taken hundreds of times a day, is exactly what an OMS automates. When there is no OMS, or when there is one but it is not properly integrated, that coordination ends up falling on people who check spreadsheets or who get pinged on chat when something gets stuck.

The data an OMS needs to exchange

System	What the OMS receives	What the OMS sends
ERP	Stock per warehouse, costs, invoicing terms, customer tax details	Sales order, data to issue the document
Ecommerce and POS	Order, originating channel, customer data	Order status, tracking number, document
Payment gateway	Payment confirmation, chargebacks	Capture or reversal request
WMS or warehouse	Real physical availability, picking confirmation	Preparation and packing instructions
Logistics	Shipment status, tracking, delivery	Carrier assignment and label
Returns	Reverse logistics status, product intake	Authorisation, stock re-entry, credit note

The distinction between accounting availability (what the ERP says) and physical availability (what is actually on the shelf) is what stalls the most orders. The OMS needs both: the accounting one to decide whether it can commit a sale, and the physical one to confirm that preparation is possible.

Why orders get stalled

• The OMS sees available stock in the ERP, but the physical warehouse does not have it. This is the gap between accounting stock and real stock, and it gets worse with inventories adjusted once a month.
• Payment is confirmed at the gateway, but that confirmation takes time to reach the OMS and the order sits in limbo: charged from the customer’s point of view, not released from the operation’s.
• The order changes status in the ecommerce, but that update never reaches the customer or the support team, which answers with stale information.
• A return is not reflected in time and the stock that should be available again stays frozen, blocking new sales.
• A mandatory customer tax field is missing and invoicing stops without anyone getting an alert.

Almost all of these cases share a pattern: they are not OMS failures, they are failures of the information flow reaching the OMS.

What a well-orchestrated order looks like, step by step

1. Intake. The order comes in from any channel with a normalised data structure, regardless of whether it came from the own store, a marketplace or the POS.
2. Payment validation. The OMS waits for real payment confirmation before releasing for picking. This simple control avoids preparing orders that are later cancelled.
3. Origin assignment. Routing rules are applied: proximity to the customer, available stock, shipping cost, branch capacity.
4. Inventory reservation. Stock is committed in the source system so no other channel can sell it.
5. Preparation. The WMS or the branch receives the instruction and confirms picking; discrepancies are reported back to the OMS, not resolved silently.
6. Invoicing. The ERP issues the document linked to the order with a unique key.
7. Dispatch and tracking. Logistics status flows back to the originating channel and becomes visible to the customer and to support.
8. Closing or return. If there is a return, the same flow runs in reverse, with stock re-entry and a credit note.

Every step that is not integrated turns into a manual intervention. And every manual intervention is a point where the order can stall without anyone noticing.

Signs that your OMS needs better integration, not a new OMS

Before evaluating a platform change, it is worth checking whether the problem is really the OMS or the way it is connected to the rest of the stack. The typical signs of an integration problem are:

• The OMS works well in one channel but fails when a second or third sales channel is added.
• The customer support team has no visibility of an order’s real status without asking another team.
• Stock update times between channels are measured in hours, not minutes.
• Every time a channel or a marketplace is added, a custom integration has to be built from scratch.
• Errors are detected through customer complaints and not through system alerts.

If three or more of these signs are present, changing OMS will probably not solve the problem: it will reproduce it on a new tool. The prior diagnosis runs through mapping the existing integrations before taking any purchasing decision.

What to measure to catch stalled orders before the customer does

A well-integrated OMS makes it possible to instrument the operation. The minimum indicators:

• Orders with no status change beyond the expected time for each stage.
• Average time between payment confirmation and release for picking.
• Rate of orders with a stock discrepancy at the moment of preparation.
• Orders with no associated tax document after X hours.
• Returns with no stock re-entry after being received.

These indicators are the basis of an integration dashboard that shows the state of the operation without waiting for the month-end report.

Frequently asked questions

What is the difference between an OMS and an ERP? The ERP manages the transactional and accounting information of the whole company. The OMS specialises in the order life cycle and in deciding how to fulfil it across multiple stock origins. An ERP can cover OMS functions in simple operations; when there are several channels and several dispatch points, the routing logic usually exceeds what the ERP handles out of the box. Does every retail company need an OMS? No. With one sales channel and one warehouse, the ecommerce platform and the ERP are usually enough. An OMS starts to pay for itself when there are multiple channels, multiple stock origins or differentiated delivery promises (in-store pickup, ship from branch, same-day delivery). Can an OMS be integrated without having a WMS? Yes. In that case, preparation confirmation comes from the warehouse or the branch through the POS or a picking app. What matters is that there is a point where physical availability is confirmed, not that this point is necessarily a WMS. How much stock should the OMS reserve when confirming an order? The reservation should happen at the moment the sale is confirmed, not when the order is prepared. A safety margin per channel can help in high-turnover operations, but it is a patch: it reduces overselling at the cost of selling less. Does the OMS replace the integration with the ERP? No. The OMS adds one more participant to the data flow. Without an integration layer that organises that exchange, an OMS can increase complexity instead of reducing it.

OMS integration checklist

• Does the OMS receive payment confirmation before releasing the order for picking?
• Does the stock the OMS sees reflect the real physical availability of the warehouse, and not just the accounting one?
• Do returns update available stock automatically?
• Is order status synced in near real time with the sales channel and with customer support?
• Are there alerts for orders with no movement beyond the expected time?
• Does adding a new channel mean a new integration, or does it connect to the existing flow?

You may also be interested in reading: • “How to integrate POS, ecommerce and ERP without breaking inventory, pricing or invoicing” • “Integration dashboards: how to measure sales, stock, orders and invoicing in real time” • “VTEX, ERP and marketplaces: which flows to integrate to run catalogue, stock and orders without friction” With its retail systems integration, Weavee connects your OMS with ERP, POS, ecommerce, payments and logistics in a single flow, with traceability per order, so a stalled order stops being a mystery you have to solve by hand.