Tracking order status across suppliers and channels: one status board for the whole chain

Short answer. You build an overview of open orders across all your suppliers by running every order past one status board that covers the entire chain: purchased, paid, shipped, in transit, received, forwarded and delivered. You pull statuses automatically from supplier portals, carriers and your sales channels into one place, and you flag what is late at each step.

An order is only done once the customer is holding the package. Everything in between is chain, and that chain is spread across places where you are not in charge. The supplier has its own portal, the carrier its own track and trace, and bol and Amazon have their own view of the same order. I ran it this way for years, and the problem is never that information is missing. The problem is that nobody brings it together in one place.

Why order status fragments across suppliers and channels

A typical reseller order runs through a fixed chain. Received on your channel, purchased from the supplier, paid, shipped by the supplier, in transit, arrived at your end, forwarded to the customer, delivered, and sometimes returned. Each step lives in a different system. The purchase status sits in the supplier portal or an order confirmation by email. The shipment in transit sits with PostNL, DPD or a foreign carrier. The customer side sits in your webshop, with bol or with Amazon.

None of these parties has any interest in showing your full chain. The supplier stops at "shipped". The carrier only starts at "label created". Your channel only knows what you reported back. The gap sits exactly in between, and that gap is where orders get stuck without anyone seeing it.

What one status board across the whole chain needs to show

The goal is control, not just saved time. I want to see on a single screen which orders are still open, which step they are stuck in, and which of those are critical because a customer is waiting. That status board needs, per order, at a minimum:

• the current step in the chain, not the status of one subsystem
• the supplier and the channel the order came from
• the date the step started, so you can measure how it progresses
• a "late" flag as soon as a step exceeds its agreed lead time
• a "critical" flag when there is a customer waiting on the other end

The difference between a supplier that is slow at forwarding internally and a supplier that keeps your customer waiting is the whole point. The first is annoying, the second is a refund or a bad review. A status board that does not make that distinction is a list, not a steering instrument.

Audit the process first, then build

Before I build anything, I lay the existing chain flat on the table. In an operation that has grown over years there are almost always steps that once made sense and now only add noise. A manual intermediate check that a system already does itself. A supplier you still chase by email while its portal has a clean status export. A double entry because two tools were never connected.

This is a deliberate step, not an excuse to build nothing. Some steps can go, some can be done smarter, and only what remains is worth automating. Whoever automates their mess gets faster mess. The automation has to come, but it has to serve the right chain.

Build versus buy: where off-the-shelf packages stop

There are good standard solutions for parts of this story. Order management tools like Picqer, ChannelDock and GoedGepickt bring orders from multiple channels together, and shipping software like Sendcloud or MyParcel gives you a real-time overview of outgoing shipments with track and trace and alerts on delays. For the channel and shipping side you should seriously consider those kinds of tools before building anything yourself.

Where the off-the-shelf package stops is the purchasing side and your exceptions. Most packages cover the happy path: order in, label out, customer happy. They rarely connect cleanly with the portals of twenty small suppliers, they do not allocate costs per supplier and channel, and they do not know your exceptions. The order that ships partly from stock and partly waits on purchase. The supplier that only emails an Excel. The cross-border shipment that goes through two carriers. That is the moat. A status board that also covers those cases is something you knit together yourself: scrapers and portal connections for the purchasing side, your carrier API for in transit, your channels for the customer side, and on top of that your own thresholds for late and critical.

When does an order count as late

Late is not a fixed number, it is an agreement per step. Per supplier and per channel you set an expected lead time, and anything beyond it jumps onto your board. A supplier with a fixed delivery time of two days is late on day three. A dropship order that still has no shipping confirmation after 24 hours is suspect. By making those thresholds explicit, you no longer chase every order, only the orders that deserve it. The rest you leave alone, because the system guarantees it will pick them up the moment something does go wrong.