Orders & fulfillment
No visibility into backorders until a customer calls
The customer calls to ask where their order is. That call is how your team learns the order is backordered at all—and that the vendor's ship date slipped two weeks ago, and that the promise date you gave the customer passed yesterday.
The information existed somewhere: an ERP line status, a vendor confirmation email, a portal update nobody checked. What never existed was a place where it all came together in time to matter.
What it looks like
- The customer is consistently the first to raise the issue. Your team's backorder discovery process is the inbound phone call.
- The buyer knows a vendor is late—from a confirmation email buried in their inbox—but the rep who promised the date to the customer has no idea.
- Partial shipments go out without explanation, and the customer has to call to learn the rest is coming in three weeks.
- Promise dates drift silently. Nobody revisits what was committed until someone complains.
- The weekly backorder report gets printed, glanced at, and set aside—hundreds of lines, no priorities, no owners.
Why it happens
The ERP records a backorder as a line status, but nothing watches it. Nothing ages it, compares it to the promise date, or tells the person who made the promise. The vendor's real ETA lives in a confirmation email or a supplier portal, disconnected from the sales order it affects.
So the company has all the facts and none of the visibility. Purchasing sees vendor side, sales sees customer side, and the connection between the two—this late PO means that broken promise—exists only when someone manually pieces it together, which usually means after the customer calls.
What it costs
The honest answer is that it depends on your volumes, your margins, and how long it has been going on. What is consistent across companies is where the cost shows up:
Expediting
Late discovery turns normal replenishment into emergency freight—paid at the worst possible moment, on the worst possible terms.
Labor
Every 'where is my order' call sends someone hunting through the ERP, the buyer's inbox, and a vendor portal to reconstruct an answer.
Lost orders
Customers who find out late cancel and buy elsewhere—often without telling you the backorder was the reason.
Customer trust
A backorder you report early is a hiccup. A backorder the customer discovers is a breach. The difference is who calls whom.
How a purpose-built system fixes it
A backorder control tower connects the three facts that currently live apart: the open order line, the vendor's real ETA, and the date you promised the customer. Every open line sits on one board with its age, its status, and its owner.
The system's real value is the early warning: when a vendor ETA slips past a promise date, the rep and the buyer find out the same day—not when the customer calls. Proactive updates go out while there is still something to say.
Concept Interface
Backorder control tower
Every open line, aged and owned, with the promise date next to the vendor ETA.
| Order line | Customer | Vendor ETA | Promised | Status |
|---|---|---|---|---|
| SO-22714 / 3 | Cresta Foods | Aug 02 | Jul 28 | ETA past promise date |
| SO-22720 / 1 | Brightwell Facilities | No confirmation | Aug 04 | Vendor response overdue |
| SO-22698 / 7 | Marlow Industrial | Aug 01 | Aug 05 | Customer update due |
| SO-22731 / 2 | Hydroline Supply | Aug 06 | Aug 08 | On track |
Example System — the board your team would check before the phone rings, not after.
This changes the economics of a backorder. You cannot prevent every late vendor—but you can almost always be the one who makes the call, with options, before the promise breaks.
When a simpler fix is enough
If your open backorder lines fit on one page, a scheduled ERP report plus a standing rule—every rep reviews their lines every morning—can genuinely work. Discipline on a small list beats software nobody logs into.
It stops working when lines number in the hundreds across dozens of vendors, when ETAs live in multiple inboxes and portals, and when no one person can hold the whole picture. That is when a purpose-built operational view starts catching things the report never will.
Related systems and industries
- Operational dashboardsOne board for open exceptions, aged and owned—built for the morning check, not the monthly review.
- Workflow systemsAlerts and escalation when vendor ETAs slip past customer promises.
- Wholesale distributionWhere backorders are a daily fact and early warning is the whole margin on service.
Common questions
- Unreliable ETAs are exactly the case for one. A control tower tracks which vendors confirm, which go silent, and which dates keep moving—so 'vendor response overdue' becomes a chased item the same day instead of a surprise in three weeks. You cannot force a vendor to be reliable, but you can stop their unreliability from being invisible.
- A report is a snapshot of line statuses. The missing pieces are the joins—vendor ETA against promise date, backorder against the rep who made the promise—and the alerts that fire when those cross. ERPs hold the data; they rarely watch it for you.
The next backorder your customer discovers is already late.
A Workflow Review maps how backorders surface in your operation today—and what it would take to find out first.