A Shipment Is Late. What Does It Put at Risk?

A carrier pushes back a delivery date, or a supplier emails that a shipment will slip two weeks. Someone on the team knows about the delay, but nobody yet knows what it means.

Does the PO still show the old date? Is there enough stock to cover the gap? Which jobs and customer orders depend on those parts?

At most mid-size manufacturers, answering those questions means checking the ERP, a spreadsheet and supplier email, then calling planning. The delay is visible. What it puts at risk is not.

Knowing where a shipment is doesn't tell you what to do

Tracking tools show location, carrier status and estimated arrival. They don't show which delays matter.

Take two shipments. One is three days late, but there's enough stock to keep the line running. The other is one day late and carries a part needed for tomorrow's run.

The shorter delay is the bigger problem. You can only see that by connecting the shipment to:

• The purchase order and the supplier's latest commitment
• Inventory and material requirements
• The production schedule
• The customer orders that depend on it
• What the supplier has said about recovery

Without those connections, people end up connecting everything by hand.

What one exception costs today

A buyer with 142 open POs gets an email saying a tooling problem moves PO 4512 from Oct 12 to Oct 26. The ERP still says Oct 12, and planning needs the parts by Oct 20 for a run that two customer orders depend on.

To understand it, the buyer finds the email, checks the ERP, asks planning for the need date and works out which customer orders are affected. In our illustrative demo, that takes about 45 minutes for one exception.

Then the supplier writes "working on recovery." It sounds like progress, but it isn't a date.

From alert to resolution

Work. Each late shipment becomes one record, tied to its PO, its supplier and the job that needs it.

Context. It shows what changed against the promise, with the evidence for each date. When the supplier says Oct 26 and the ERP says Oct 12, both are shown, and the ERP stays the record.

Decision. It shows what the delay puts at risk downstream and who decides: split the shipment, expedite, resequence the run or tell the customer. People make the call.

Action. The next step and its follow-ups are tracked until the exception closes on proof. That proof is a firm date in writing, an ERP that matches, the parts received and the run protected.

Tracking an exception is not the same as resolving it.

See it in the demo

The Supplier Delivery & PO Exception demo shows two shipment problems side by side:

• PO 4512: the new date misses the need date by six days. Splitting the shipment protects both customer orders for about $1,800 in premium freight, against $9,400 to expedite everything. It closes when the split is confirmed in writing and the first 60 housings arrive.
• PO 4540: the carrier is holding the shipment at a terminal until Thursday. The supplier's ship notice said Tuesday, and the run needs the parts Wednesday. The suggested next step is to ask for a release and a Tuesday pickup.

Each item keeps its evidence, decision and history, so nobody rebuilds the story when the next email arrives.

Why this matters for mid-size manufacturers

Large enterprises buy transportation systems and control towers. Most mid-size manufacturers have an ERP, spreadsheets, and supplier and carrier email, and what they're missing is the connection between them.

They don't need another portal that every supplier has to adopt. They need to use the information they already have.

Try this week

• Pick five late inbound shipments. For each, write down the need date and what the delay affects, and time how long it takes.
• Compare the latest supplier or carrier date with the ERP date on your 20 most urgent POs.
• Ask who owns each open shipment exception, and what will close it.

The goal isn't knowing a shipment is late. It's knowing what the delay puts at risk, and seeing it through to resolution.

Connect the evidence. See what needs attention. Resolve it as a team.