MELLORCATalk to Mellorca
Patterns

Order-to-Delivery & Fulfilment

When Order Status Lives in Several Systems

If the shop, accounting, warehouse and courier each hold part of the story, no one can say where an order is. Here is the cost and how to give orders one status.

Mellorca Patterns2026-10-11

Observable condition

A customer asks a simple question: where is my order? The answer depends on whom they ask. The web shop says "processing". The accounting package shows an invoice raised. The warehouse spreadsheet has the line highlighted yellow. The courier's portal shows a waybill with no scans. Each source is partly right, and none is the answer.

So the sales assistant does what everyone does. She opens three screens, sends a message to the warehouse, waits, and phones the customer back with a best guess. The same chain repeats for the next customer, and the one after.

An illustrative example: a Port Elizabeth online retailer of pool equipment takes orders on a web store, invoices through a cloud accounting tool, picks from a warehouse sheet and ships with two couriers. During the December peak, order status questions make up most of the customer-service inbox. Staff are not slow. Every question is a small investigation across systems that were never designed to agree.

Realisation

The realisation is that there is no single record of the order. Each system holds a view of the part of the order it cares about: the shop the payment, accounting the invoice, the warehouse the pick and the courier the parcel. The order as the customer understands it, a promise that moves through all of these, exists nowhere except in the heads of the people who stitch it together.

IBM's overview of order management describes the discipline as tracking an order from receipt through fulfilment and delivery, including inventory, payment and shipping, so that all parties work from the same status. Where that central record is missing, every status question has to be answered by reconstruction.

Realisation prompt: take three recent orders. For each, how many places would you have to look to say exactly where it is, and do those places agree?

Identification

This is a pattern of fragmented order status. The visible symptom is a high volume of "where is my order?" contacts and internal queries. The common assumption is that customers are impatient or that staff need to communicate better. The structural cause is that order status is spread across several systems that use different identifiers and different words for the stages, with no master record that reconciles them.

The Pattern when customers know their order is late before your team does shows what happens when the courier or customer sees the problem first, and why does an order need so many manual touches covers the labour involved. This Pattern concentrates on the status itself and why it cannot be read from any single source.

Diagnosis

  • Different identifiers. The web order number, the invoice number, the pick-list reference and the waybill each identify the same order differently, and linking them relies on a person copying one into another.
  • Different words. "Complete" in the shop may mean paid, while in the warehouse it means packed and in accounting it means invoiced. Staff learn the translations, and customers receive them untranslated.
  • Different update speeds. One system updates instantly, one overnight and one when somebody remembers. Combined, they give a picture made of information of different ages.
  • Status changes are made by people. Moving an order from "picked" to "shipped" depends on a person doing it in one system and then informing the others.
  • Exceptions have no home. Partial shipments, back orders, substitutions and returns are the cases that cause most queries, and they are the cases systems handle worst.
  • Nobody owns the end-to-end view. Each system has an owner. The order, as a whole, does not.

Commercial impact

The commercial value at stake is customer experience, service-team capacity, cash collection and the cost of fulfilment errors.

The first cost is contact volume. Every status enquiry consumes service time, and the more orders the business ships, the more enquiries it receives. If handling each takes ten minutes of searching, a few dozen a day becomes a significant part of a service employee's paid time, which is a recurring cost rather than a project cost.

The second cost is customer confidence. A customer who is given three different answers by three different people concludes that the business is not in control. In a market where an online buyer can switch to another retailer in a few clicks, an unclear answer is itself a reason to stop ordering.

The third cost is cash. Invoices are delayed or disputed when nobody can confirm that goods were delivered. Customers may withhold payment until the dispute is settled, and a business with tight working capital feels this directly.

The fourth cost is error. When status is held in several places, some orders are shipped twice, some are not shipped at all and some are invoiced before they leave. The Pattern the hidden cost of re-keying order information describes how retyping between systems causes many of these slips.

Underlying all of these is a structural point that IBM's overview of data silos makes: when data is isolated in separate systems, different parts of the organisation work from partial and sometimes conflicting pictures. For orders, the conflict is felt by the customer.

Common misidentification

The first response is to add a tracking page to the website. If the page reads from only one of the systems, it displays one slice of the truth with more confidence than it deserves, and customers phone anyway. The second is to hire more customer-service staff. That treats the volume but leaves the cause in place, and the cost grows in step with sales.

The third is a push for a single new platform to replace everything. It may be the right long-term answer, but it is rarely quick, and businesses often find that specialist tools such as couriers' systems and bank feeds must remain. A smaller step, such as agreeing one reference and one set of status words, delivers much of the benefit sooner.

Possibility

In a better state, every order has one reference that appears in every system and one status drawn from a short, agreed list, such as received, paid, picked, dispatched, delivered and exception. Systems pass changes to one another, or to a shared record, as they happen. A service agent sees the current status and its age on one screen, and the customer sees the same.

IBM's overview of data integration notes that combining data from separate sources into a unified view is the purpose of integration work. For most small and mid-sized businesses, this can start with an order reference carried through every tool and automated updates for the two or three status changes that matter most.

Intervention

  1. Trace three real orders. Note every system touched, every identifier used and every point where status was changed by hand.
  2. Agree the master reference. Choose one order number and make every system carry it, including the courier waybill.
  3. Define the status list. Write six to eight stages, and map each tool's wording onto them. Make clear which event moves an order from one stage to the next.
  4. Automate the highest-volume changes first. Usually these are paid, dispatched and delivered. Let the courier scan or the shipping label update the record instead of a person.
  5. Create an exception list. Show orders stuck in a stage longer than an agreed time, so the team finds them before the customer asks.
  6. Expose one status to customers and staff. Send proactive notifications at the main stages, and measure how status enquiries change.

Diagnostic questions

  • How many systems must a service agent open to answer "where is my order?"
  • Does one order carry the same reference in the shop, accounting, warehouse and courier systems?
  • Which status words mean different things in different departments?
  • What share of your customer contacts are status enquiries?
  • How would you find every order that has been in the same stage for more than three days?

Bottom line

When order status lives in several systems, the customer pays for the gap in confidence and the business pays in staff time, disputes and errors. The fix usually begins with something modest: one reference, one agreed list of stages and a few automatic updates. Once the order has a single, current status, the questions that used to need an investigation can be answered on sight, or answered before they are asked.

Sources and further reading

Related Mellorca reading

Article summaryIf the shop, accounting, warehouse and courier each hold part of the story, no one can say where an order is. Here is the cost and how to give orders one status.
Explore our solutionsStart a conversation