No category
Shipment Status Changed: Who Needs to Know First?
Key Takeaways
Every shipment status change has a different audience. Telling everyone everything creates noise; telling no one creates surprises.
There are 5 status changes that matter most: booked, picked up, running late, delivered and POD filed.
The right audience depends on the status: the team, the carrier, the shipper and the consignee each need different updates.
Wilson, by Cartage, is an AI logistics agent that sends each update to the right people through the right channel, and each company chooses who's notified and how.
Customers can follow shipments on a tracking link with the company's branding, so they don't need to ask.
Why do shipment updates reach the wrong people, or no one?
A load is running three hours late. The carrier tells the coordinator. The coordinator is busy and doesn't tell the warehouse. The consignee's receiving team waits at the dock. The customer's buyer calls the sales rep, who knows nothing. Five people needed one update; one person got it.
Shipment updates reach the wrong people because there's no rule for who needs to know each status change, so updates depend on someone remembering to forward them.
Visibility gaps are common: a BCI Global survey of 240 supply chain leaders found only 35% have end-to-end visibility.
Who needs to know about each shipment status change?
Each status change has its own audience. This is Wilson's default notification setup; each company chooses who's notified and how.
Status | Company's team | Carrier | Shipper | Consignee |
|---|---|---|---|---|
Booked | ✓ Slack or Teams | ✓ Email or API | Not by default | |
Picked up | ✓ | ✓ | ✓ | ✓ Email or SMS |
Running late | ✓ | ✓ | ✓ | ✓ |
Delivered | ✓ | ✓ | ✓ | ✓ |
POD filed | ✓ | ✓ | ✓ | ✓ |
The consignee usually doesn't need "booked"; it needs to know when the freight is coming and when it's late.
Who needs to know first?
For most status changes, the company's team should know first, because they may need to make a decision before anyone else is told.
Running late: the team first, then the shipper and consignee, so the team can decide whether to rebook or reschedule.
Picked up and delivered: everyone can hear at once; these are good news.
Exceptions such as cancellations: the team first, then the customer if the company has configured it.
How does Wilson, by Cartage, send status updates?
Wilson sends each status update to the people the company has set, through the channels the company has chosen. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
Step | Trigger | What Wilson does | When a person steps in |
|---|---|---|---|
1. Status change | Wilson records a new status | Determines who needs to know | Not required |
2. Team | The status matters to the team | Posts it in Slack or Microsoft Teams | Not required |
3. Carrier and shipper | The status affects them | Sends the update by email or API | Not required |
4. Consignee | The status affects delivery | Sends the update by email or SMS | Not required |
5. Delay | The load is running late | Gets the new ETA and reason first, then notifies everyone set to be notified | When a customer decision is needed |
6. Tracking link | Any change | Updates the branded tracking link customers can follow | Not required |
See how to give customers branded shipment tracking.
How should teams set up notification rules?
Teams set up notification rules by deciding, for each status, who needs to know and through which channel.
List the audiences: team, carrier, shipper, consignee and key customers.
Pick the statuses each audience needs.
Choose channels: Slack or Microsoft Teams for the team, email, SMS or API for others.
Decide what needs approval, for example customer notifications on high-priority accounts.
Review after a few weeks and remove updates nobody uses.
FAQs
Who needs to know when a shipment status changes? It depends on the status. The company's team, carrier and shipper typically get booked, picked up, running late, delivered and POD filed; the consignee gets all except booked.
Who should know first about a late shipment? Usually the company's team, so it can decide whether to rebook or reschedule before the customer is told.
Which channels does Wilson use for updates? Slack or Microsoft Teams for the team; email or API for carriers; email for shippers; email or SMS for consignees.
Can I choose who gets notified? Yes. Each company chooses who's notified and how.
Can customers track shipments themselves? Yes. Customers can follow shipments on a tracking link with the company's branding.
What happens when a load is running late? Wilson gets the new ETA and the reason, then tells the team and anyone else the company has set to be notified.
How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson.
Conclusion
Every shipment status change should reach the people who need it, in the order that lets them act. Without rules, updates depend on someone forwarding an email. Wilson, by Cartage, sends each status change to the team, carrier, shipper and consignee through the channels the company chooses, gets the details first when a load runs late and keeps a branded tracking link current. The practical first step is to set the notification rules for a few lanes, start Wilson there and compare "where's my order?" calls with how those lanes run today.
Sources
BCI Global, supply chain visibility survey, March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
Cartage, Wilson product FAQ, October 2026: https://cartage.ai
Other latest news and success stories

January 25, 2022
Best AI Tools for Carrier Follow-Up in 2026
Read more →

January 25, 2022
Best Bill of Lading (BOL) Software for Manufacturers in 2026
Read more →
