No category
The order says shipped. The carrier says otherwise.
Key Takeaways
"Shipped" in the ERP usually records a warehouse event, not a carrier event. Many teams set it at packing, labeling or staging, hours or a day before the actual pickup.
The carrier's pickup confirmation is the status that tells you where the freight is. When the two disagree, confirm with the carrier, correct the record and give the customer the real ETA.
The gap is widest on missed pickups, because the carrier's reschedule usually lands in one coordinator's inbox and never reaches the ERP that sales and customer service read.
Wilson, by Cartage, is an AI logistics agent that confirms pickups with the carrier, tracks each load with the best source available and, when the company wants it, writes status back to the ERP.
Measure the fix with one count: orders marked shipped with no confirmed pickup, by lane, before and after.
Why does the ERP say shipped when the carrier hasn't picked up?
An ERP order says "shipped" when someone in the warehouse, or a system rule, marks it shipped, usually at packing, labeling or staging. The carrier's status changes only when the driver loads the freight. When a pickup runs late or is missed and nobody closes the loop, the two records drift apart, and whoever reads the ERP gives the customer the wrong answer.
This hits manufacturers and distributors that coordinate their own carriers by email, phone and spreadsheets: sales and customer service read the ERP, while the truth arrives in logistics' inbox. Few companies have closed that gap: in a March 2025 BCI Global survey of 240 supply chain leaders, only 35% reported end-to-end visibility.
Tuesday 1:40 p.m. The warehouse lead stages 6 pallets for a distributor's order in NetSuite and prints the BOL (bill of lading: the document the driver signs at pickup that lists the freight, origin and destination). The clerk marks the order shipped so billing can invoice.
Tuesday 4:50 p.m. The LTL carrier's pickup window was 2:00 to 5:00 p.m. The carrier dispatcher moves the pickup to Wednesday and emails the coordinator at 5:05 p.m., after she has left.
Wednesday 8:30 a.m. The customer's purchasing manager calls customer service. The rep sees "shipped Tuesday" and promises delivery Thursday.
Wednesday 9:45 a.m. The coordinator reads the dispatcher's email. The truck comes at 1:30 p.m.; delivery slips to Friday. Nobody tells customer service.
Thursday 3:00 p.m. The customer, who staffed receiving for Thursday, calls again. Now the problem is trust.
A missed pickup (one the carrier agreed to and didn't make within the window) happened, and its only record sat in one inbox.
Where does the gap between order status and shipment status come from?
The gap comes from four places: the ERP status is tied to warehouse or billing events, the pickup confirmation lives outside the ERP, missed pickups and reschedules aren't written back, and partial pickups don't match the order.
The status is set by the warehouse, not the carrier
Many ERPs mark an order shipped when the pick ticket closes, the label prints or the shipment posts for invoicing. That serves inventory and billing, but says nothing about a truck. If it's the only field sales can see, they read it as "on the truck."
The pickup confirmation lives in an inbox
The carrier's pickup confirmation arrives as an email, a portal update or a phone call. If nobody copies it into the order, the ERP never learns whether the pickup happened.
Missed pickups and reschedules are never written back
A reschedule changes the delivery date the customer cares about. Handled by phone, it leaves the original ship date on the order, and every hour it stays hidden, more people quote the wrong date.
Partial pickups don't match the order
If the driver takes 4 of 6 pallets, the order says shipped in full while 2 pallets sit on the dock, and the customer expects everything.
What should the team do when the order and the carrier disagree?
Trust the carrier’s confirmed status, correct the order, tell the customer the real ETA, and then fix the rule that created the gap.
Confirm with the carrier. Ask whether, when and how many pieces were picked up; if missed, get the new time and the reason.
Correct the order. Change the status or add a note that sales and customer service will see.
Tell the customer. Give the confirmed new ETA and the reason, not a guess.
Decide on recovery. If the carrier can’t come in time, rebook with another approved carrier, within your approval limits.
Fix the cause. Change when the ERP marks orders shipped, or add a separate “picked up” status driven by the carrier’s confirmation.
For the first hour after a missed pickup, see the carrier confirmed the rate. Then missed the pickup.
Common mistakes
Treating “label printed” as “picked up.” Customer service promises a delivery date that was never real, and the correction costs more credibility than the delay.
Fixing the order but not the cause. The same gap reopens on the next load, and the team keeps cleaning records by hand.
Letting the carrier reschedule by phone with no written record. Nobody can show when the new time was agreed, so disputes about late delivery become opinion against opinion.
How does Wilson, by Cartage, keep order status and shipment status aligned?
Wilson confirms the pickup with the carrier, tracks the load with the best source available, handles a missed pickup in a set order and, when write-back is set up, sends the status back to the ERP. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
Wilson replaces the TMS as the system of record for shipments and connects to the company’s ERP, including SAP, NetSuite, Microsoft Dynamics 365 and most others, so the two records no longer depend on someone copying an email.
Step | Trigger | What Wilson does | When a person steps in |
|---|---|---|---|
1. Schedule | Load is booked (LTL or FTL) | Schedules the pickup with the carrier and confirms the window | Booking above the approval limit |
2. Reconfirm | Before the pickup window | Reconfirms the pickup with the carrier | If the carrier can’t confirm |
3. Confirm pickup | Pickup window passes | Checks with the carrier by API, email or phone, following the SOP frequency | Not required |
4. Missed pickup | No pickup confirmed | Contacts the carrier, notifies the team, notifies the customer if configured and initiates rebooking from approved carriers | If rebooking requires approval |
5. Track | Load is in transit | Uses the carrier API, GPS or ELD data, or the carrier website by PRO number; otherwise emails or calls | Not required |
6. Notify | Status changes | Sends booked, picked up, running late, delivered and POD filed updates to the parties the company chose | Not required |
7. Write back | Status changes | Updates the ERP by CSV or Excel file, a shared table or API where available | Not required once set up |
Customers can follow shipments on a tracking link with the company’s branding. POD (proof of delivery) is the signed receipt that closes the load; Wilson follows up until it’s filed. See also what is freight execution and how AI sends shipment updates back to the ERP.
Controls
Wilson starts with assisted execution. The company decides which actions need a person, such as rebookings above a cost threshold or customer notifications, and widens automation as trust builds.
Wilson escalates when the carrier can’t confirm a pickup, no approved carrier accepts a rebooking or a decision exceeds the approval rules. Every message, confirmation and change on the shipment is recorded in a change history, and call transcripts are saved on the order.
Wilson books only carriers the company has approved and does not manage dock slots inside the warehouse. Write-back is optional, usually set up after order intake works; if the warehouse keeps marking orders shipped at packing, that field changes only if write-back is configured to update it.
What should you ask a vendor to show in a demo?
Ask the vendor to run one of your own orders from "marked shipped" to "confirmed picked up," including a missed pickup, and show you every record it touches.
Show a pickup confirmation that came from the carrier, not from the warehouse, and where it's recorded on the shipment.
Simulate a missed pickup at 4:50 p.m. Show who is contacted first and what the customer receives.
Show the ERP after the status changes. Which field changed, by which method, and how long after the carrier confirmed.
Open the change history for that load and walk through each message and confirmation.
Show which actions you can set to wait for approval, and what happens when no approved carrier accepts.
To judge the result, compare the lanes the new process runs with how they ran before: missed pickups, time from exception to notification, manual touches per load and how many orders showed shipped with no confirmed pickup.
FAQs
Why does my ERP say shipped when the carrier hasn't picked up? Because many ERPs set "shipped" at packing, labeling or invoicing, not at pickup. Without write-back, the order shows shipped even if the truck never came.
Which status should I trust, the order or the carrier? The carrier's confirmed status, because it reflects whether the driver loaded the freight.
How does Wilson confirm that a load was picked up? For LTL and FTL, Wilson schedules the pickup, confirms the window and reconfirms before pickup. After the window, it checks with the carrier through the best source available and calls if the carrier doesn't respond.
What does Wilson do when a pickup is missed? It contacts the carrier, notifies the team, notifies the customer if configured and initiates rebooking from approved carriers. Rebooking runs automatically or waits for approval, depending on the company's rules.
Does Wilson update the ERP? Yes, when the customer wants it. Write-back is optional and set up per customer, by CSV or Excel file sent by email, a shared table or an API connection where one is available.
Can my customers see the real status? Yes. Customers can follow their shipments on a tracking link with the company's branding, and consignees can get picked up, running late, delivered and POD filed updates by email or SMS.
How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson, and that one fee covers the full shipment lifecycle: create, quote, tender, track, audit and pay.
Conclusion
“Shipped” in the ERP and “picked up” by the carrier are different events, and the customer only cares about the second. Closing the gap means letting the carrier’s confirmation drive the record and getting a missed pickup to sales, customer service and the customer within the hour, not the next day.
Wilson, by Cartage, does that work on each load, the way an AI logistics agent should: it confirms the pickup, chases the carrier when the window passes, runs the missed-pickup response in a fixed order, notifies the right people and, when set up, updates the ERP. To see it on your freight, bring one order your ERP marked shipped before the truck arrived and watch Wilson confirm the pickup, follow up with the carrier and update the record 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
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 →
