When should a freight delay reach production or sales?

Key Takeaways

A freight delay should reach production or sales when it changes what they do: a line schedule, a customer promise or an order that now ships late.
The trigger is the new ETA (estimated time of arrival) and the reason, sent as soon as logistics has them, because that's what other teams can plan around.
Set the routing rules once with 3 questions: what kind of shipment is it, how late is it against the time that matters, and who changes their plan because of it.
Wilson, by Cartage, is an AI logistics agent that gets the new ETA and the reason for a delay, then tells the team and anyone else the company has set, by Slack, Microsoft Teams, email or SMS.
Each company chooses who's notified and how, and fewer, targeted updates keep people reading them.

Why do delays reach production and sales too late?

Freight delays reach production and sales too late because logistics hears first, but there's no written rule for who else needs to know and when. The coordinator decides case by case, between other work. A delay should leave logistics when it changes another team's plan, as soon as there's a new ETA and a reason.

This affects manufacturers that run lines on inbound material and distributors that promise ship dates to key accounts. In both, logistics is often the only group watching carriers, while the people who feel the delay sit in other systems and channels. Many companies lack a full picture: in a BCI Global survey of 240 supply chain leaders, only 35% reported end-to-end visibility.

Here's how one delay turns into a stopped line:

Wednesday 7:30 a.m.: An FTL load of resin for a plastics manufacturer misses its 6 a.m. tracking update. The carrier's API shows the truck still 300 miles out.
Wednesday 9:00 a.m.: The logistics coordinator calls the carrier dispatcher, who says the driver had a breakdown overnight. New ETA: Thursday 5 a.m.
Wednesday 9:10 a.m.: The coordinator updates the tracking sheet and moves on to a missed pickup (a truck that didn't show for a scheduled pickup) on another lane.
Wednesday 1:45 p.m.: The production planner walks over to ask where the resin is. The line will run out at 3 p.m. on its current schedule.
Wednesday 2:30 p.m.: The planner reshuffles, but a customer order that depended on that run misses its ship date.
Wednesday 4:00 p.m.: The sales rep hears about it from the customer's buyer.

Logistics knew at 9 a.m. The planner could have reshuffled five hours earlier, and sales could have called the customer first.

Which delays should reach production or sales?

Share a delay when it changes what another team does; keep it in logistics when it doesn’t.

Delay	Who needs to know	Why	When it can stay in logistics
Inbound material for production	Production planner, purchasing	The line schedule may change	Safety stock covers the new ETA
Outbound order for a key customer	Sales, customer service	The customer promise may change	The new ETA still meets the delivery window
Order that misses a delivery appointment	Sales, customer service	The customer needs an update and maybe a new appointment	The consignee already agreed to the new time
Delay with no downstream impact	Logistics only	Nothing changes for others	Always

The 3 questions that set the rules

What kind of shipment is it? Inbound for production, outbound for a customer, or a stock transfer.
How late is it against the time that matters? Two hours late against a delivery window that’s still open is different from two hours late against a line that runs out at noon.
Who changes their plan because of it? If nobody does, the update is noise.

Teams that write these answers down once, by customer or product group, typically send fewer updates nobody needed.

When should production and sales hear about it, and what should they get?

They should hear as soon as logistics has a new ETA and a reason, and every update should say what changed, why and what happens next. An alert without a time doesn’t help anyone plan.

The sequence is short: get the new ETA and the reason from the carrier, check the impact, notify the affected team in the channel they read, and update again only if the ETA changes. A useful update has four parts: the shipment and the order it affects, the old and new ETA, the reason, and who’s working on recovery. If the carrier can’t give an ETA yet, “delayed, ETA expected by 11 a.m.” is often better than silence.

Getting this wrong runs both ways. Send too late and the planner loses hours. Send everything and people stop reading. For the customer side, see a delayed delivery needs a customer update, not another internal alert, and for who owns the fix, see a delay alert needs a recovery plan owner.

Common mistakes teams make

One distribution list for every delay. Consequence: production and sales get dozens of updates that don’t affect them and start ignoring all of them.
Sending “running late” with no new time. Consequence: the planner has to call logistics anyway.
Repeating the same update every hour. Consequence: alert fatigue, with no new information.
Letting sales hear from the customer first. Consequence: the rep loses credibility, and the customer loses confidence in the date.

How does Wilson, by Cartage, notify other teams about delays?

Wilson, by Cartage, gets the new ETA and the reason from the carrier, then tells the team and anyone else the company has set to be notified, by Slack, Microsoft Teams, email or SMS. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

Wilson runs each shipment from quote to payment (see what is an AI logistics agent?) and tracks each load with the best source available: the carrier’s API, GPS or ELD (electronic logging device) data from the truck, or the carrier’s website by PRO number (the carrier’s tracking number). When none of those exist, it emails or calls the carrier.

Step	Trigger	What Wilson does	When a person steps in
1. Detect	The load is running late	Checks the best tracking source and contacts the carrier	Not required
2. ETA and reason	The carrier responds	Records the new ETA and the reason on the shipment; calls if there’s no reply	The carrier can’t give an ETA
3. Notify	The ETA is confirmed	Tells the people the company has set, in their channel	Notifications the company set to need approval
4. Update	The ETA changes again	Sends a new update with the new time	Not required
5. Recover	The load can’t make it	Escalates with options, or initiates rebooking from approved carriers if the pickup was missed	Decisions above the approval rules

Controls: approvals, escalation and change history

Each company chooses who’s notified and how. For example, the team might get every delay in Slack, the consignee “running late” by email or SMS, and the production planner might be added as a recipient. Customers can also follow their shipments on a tracking link with the company’s branding. Wilson starts with assisted execution, so customer notifications can require approval at first, and autonomy expands step by step.

Wilson escalates when a carrier can’t confirm an ETA, when no approved carrier accepts a rebooking or when a decision exceeds the approval rules. Every message, confirmation and change is recorded in the change history, so anyone can see when the delay was known and who was told.

What Wilson does not do in this flow: it doesn’t change the production schedule or promise new dates to customers on its own. Those decisions stay with the planner and sales. For the internal routing side, see the shipment status changed. Who needs to know first?

How do teams avoid alert overload?

Teams avoid alert overload by sending each delay only to the people it affects, in the channel they read, once per real change.

Set routing by shipment type and customer, not one list for everything. Use each team's own channel, whether that's Teams, Slack or email. Send a new update only when the ETA or the impact changes, and review the rules once a quarter.

What to ask a vendor to show in a demo

Show a late load from detection to notification, with the new ETA and the reason, and how long each step took.
Show how recipients are set per shipment type or customer, and how a planner is added for inbound loads.
Show the update when the ETA changes a second time, and confirm it isn't repeated when nothing changed.
Show the change history for the delay, including the carrier call transcript.

FAQs

When should logistics tell production about a freight delay? As soon as there's a new ETA, if the delay affects inbound material the line needs before that time. If safety stock covers the gap, it can stay in logistics.
When should sales hear about a freight delay? When the delay changes a customer promise, a delivery appointment or a key customer's order. Sales should hear before the customer calls.
Does every delay need to go to other teams? No. Delays that don't change anyone else's plan can stay in logistics. Sending everything is what causes people to stop reading updates.
Can Wilson notify production and sales? Yes. Wilson tells the team and anyone else the company has set to be notified, by Slack, Microsoft Teams, email or SMS. Each company chooses who's notified and how.
How does Wilson get the new ETA? From the carrier's API, GPS or ELD data, or the carrier's website by PRO number. When none of those exist, Wilson emails or calls the carrier and gets the new ETA and the reason.
Can customers track their own shipments? Yes. Customers can follow their shipments on a tracking link with the company's branding.
How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson.

Conclusion

A delay that stays in logistics can stop a line or break a customer promise, but a delay sent to everyone gets ignored. The answer is a short set of rules: share a delay when it changes another team's plan, as soon as there's a new ETA and a reason, in the channel that team reads.

Wilson, by Cartage, gets the new ETA and the reason from the carrier and notifies the people each company chooses, with a record of every message. Bring one late inbound load that surprised your production planner and watch Wilson run the carrier follow-up and the updates in a demo at cartage.ai.

Sources

BCI Global, March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
Cartage, Wilson product FAQ, October 2026: https://cartage.ai