Retail Clouds is the Omni Channel platform for Retail Businesses. Intelligent Robotized SaaS platform for Retailers.
An order isn't a single event - it's a status that keeps changing, across every channel it can arrive from, until it reaches the customer's door or doesn't. Managing that change, cleanly, is most of what order management is.
A single order can start its life on a website, a mobile app, a marketplace listing, a store associate's tablet, or a B2B ordering portal. Wherever it starts, it enters the same pipeline and moves through the same set of possible states on its way to being fulfilled - or not.
The pipeline sits downstream of a decision already covered in inventory management: once an order is confirmed, stock for it is blocked and routed to the nearest fulfilment centre that can actually cover it, not just quoted from a central number. Order management inherits that assumption - it takes stock availability as given and focuses on what happens to the order itself as it moves from notified, to confirmed, to a resolved outcome.
Every order moves toward fulfillment or away from it. The forward path runs from being noted, through confirmation and shipping, to the customer's door. The paths off that route - cancelled, rejected, returned - need the same rigor as the happy path, because from the customer's side, they are the order's outcome.
The order has been notified to the system but not yet confirmed. No stock has been committed and no fulfilment centre has been assigned.
The order is accepted, and stock is blocked at the specific fulfilment centre it will ship from. This is the point the order becomes a firm commitment to the customer.
The customer cancels the order. Blocked stock is released back to the fulfilment centre, and any payment already collected is returned to the customer.
Goods are packed, billed, and dispatched from the fulfilment centre. From here the order is in the hands of delivery, not stock management.
The customer sends the order back - for quality issues, a wrong item, or simple preference. Returned stock needs inspection before it re-enters sellable inventory.
The retailer declines the order - most often because stock isn't actually available, or because no logistics option can reach the customer. No stock was ever held, so nothing needs releasing.
B2C and B2B orders move through the same six states, but what those states mean in practice diverges quickly. A consumer order is usually one shipment to one address; a business order is often a negotiated quantity tied to a purchase order, with a delivery window that matters contractually.
Shipped is not the same as delivered. Once goods leave a fulfilment centre, they reach the customer's door by one of two routes: the retailer's own delivery staff, or a third-party logistics partner. Both need to feed status back into the same order record - a shipment handed to a partner is no less the retailer's responsibility for visibility purposes.
Where an order is post-paid - cash or card collected on delivery - order management needs a payment capability built into the doorstep step itself, whether that means a handheld terminal for the retailer's own staff or a settlement process coordinated with the logistics partner. The order isn't fully closed until both the goods and the payment are confirmed received, and a delivery attempt without payment capture is functionally an incomplete delivery, not a completed one.
An order that reaches Shipped, Returned, or Rejected isn't finished from the customer's point of view - it's the moment they form an opinion about whether the whole system worked. Order management has to capture that opinion, not just the logistics event that triggered it.
A complaint tied to a shipping delay, a rejection, or a return should route back to whoever owns that stage of the pipeline, not sit in a separate customer-service system disconnected from order status. Treated this way, feedback becomes a second data source on how well the pipeline is actually running - often surfacing friction before it shows up in fulfillment metrics.
The order pipeline ends at Shipped or Returned. The relationship doesn't - and the feedback loop is where the two get reconnected.
With orders arriving from every channel and moving through six possible states across dozens of fulfilment centres and delivery partners, no single team can track outcomes by asking around. An omnichannel platform needs a dashboard that shows, at a glance, where every order sits - and flags the ones that are stuck.
The dashboard's job is to make exceptions visible before they become complaints - an order sitting in Confirmed too long, a fulfilment centre falling behind on shipping, a spike in returns from one channel. Monitoring order counts alone isn't enough; the view has to be built around service-level thresholds, so a team can act on what's breaching before a customer has to ask where their order is.
