How AI Writes Shipment Updates Back to Your ERP

Key Takeaways

Orders start in the ERP, but shipment updates often don't make it back: carrier, pickup date, tracking status and delivery stay in emails and spreadsheets.
AI writes shipment updates back to the ERP in 3 ways: an updated CSV or Excel file sent by email for the ERP to import, writing to a shared table, or updating the ERP through an API connection where one is available.
Wilson, by Cartage, writes updates back when the customer wants it. Write-back is optional, set up per customer and defined during onboarding, usually after order intake is working.
Wilson works with SAP, NetSuite, Microsoft Dynamics 365 and most other ERPs, including Oracle, Infor, Epicor, Sage and Acumatica.
Wilson connects to the ERP, not to another TMS, because Wilson replaces the TMS.

Why don't shipment updates make it back to the ERP?

A manufacturer's sales order is in the ERP. The load is booked by email. The carrier, pickup date and PRO number live in the coordinator's inbox. When customer service opens the order in the ERP to answer a customer, it says "released," not "picked up yesterday, delivering Thursday."

Shipment updates don't make it back to the ERP because the work of moving freight happens outside it, and someone has to type the results back in.

Common updates that stay outside the ERP:

Carrier and rate for each order.
Pickup and delivery dates.
Tracking status and delays.
POD and delivery confirmation.
Freight cost, once the invoice is audited and paid.

Visibility gaps like this are common: a BCI Global survey of 240 supply chain leaders found only 35% have end-to-end visibility.

What are the 3 ways an AI agent can write updates back to the ERP?

An AI agent can write shipment updates back to the ERP in 3 ways, depending on what the company's ERP and IT team support.

Method	How it works	Best for
CSV or Excel file by email	Wilson sends an updated file and the ERP imports it	ERPs and teams that already import files
Shared table	Wilson writes updates to a table the ERP reads	Companies that use a shared database or table for integrations
API connection	Wilson updates the ERP directly, where an API connection is available	ERPs with an available API and IT support

The method is defined with each customer during onboarding. Write-back is optional: some companies prefer to receive updates by email instead.

How does Wilson write updates back as a shipment moves?

Wilson writes updates back at the moments that matter for the order, with a clear point where a person steps in. 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. Order intake	An order arrives from the ERP	Creates the shipment	If details are missing
2. Booked	The carrier is booked	Records the carrier and rate and writes them back, if configured	Bookings above the approval limit
3. Picked up	The pickup is confirmed	Writes back the pickup date and status	Not required
4. In transit	Status changes or a delay occurs	Writes back the status and new ETA	When a customer decision is needed
5. Delivered	The load is delivered	Writes back the delivery date and POD status	Not required
6. Paid	The invoice is audited and paid	Records the final freight cost	Approving unplanned charges

For the order side, see from ERP order to booked load.

How should companies decide how to set up ERP write-back?

Companies should decide ERP write-back after order intake is working, based on which updates people actually need in the ERP.

Ask 4 questions:

Who needs updates in the ERP: customer service, finance or sales?
Which updates do they need: status, dates, POD or freight cost?
What does our ERP support: file imports, a shared table or an API?
Do we want write-back at all, or are email updates enough for now?

Standard freight with existing carriers is the fastest to set up. ERP integrations and custom workflows are scoped up front, and most customers start on a few lanes and expand.

How do teams stay in control of what's written to the ERP?

Teams stay in control because write-back is optional, scoped with them and limited to the updates they choose.

Optional: the company decides whether Wilson writes back at all.
Scoped up front: the method and fields are defined during onboarding.
Full record: every update is also recorded on the shipment in Wilson.
Approval limits: bookings and payments above the limit still wait for a person.

FAQs

Can AI write shipment updates back to my ERP? Yes. Wilson, by Cartage, can write updates back by sending an updated CSV or Excel file by email for the ERP to import, writing to a shared table, or updating the ERP through an API connection where one is available.
Is ERP write-back required? No. Write-back is optional and set up per customer.
When is ERP write-back set up? During onboarding, usually after order intake is working.
Which ERPs does Wilson work with? SAP, NetSuite, Microsoft Dynamics 365 and most other ERPs, including Oracle, Infor, Epicor, Sage and Acumatica.
What updates can be written back? Updates such as carrier, pickup and delivery dates, tracking status and delivery confirmation, as defined with each customer.
Does Wilson connect to a TMS? No. Wilson connects to the company's ERP, not to another TMS, because Wilson replaces the TMS.
How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson.

Conclusion

The ERP knows what was ordered. Without write-back, it doesn't know what happened next: who's carrying it, when it picked up and whether it delivered. Wilson, by Cartage, can close that loop by writing shipment updates back through a file, a shared table or an API connection where one is available, scoped with each customer and only when they want it. The practical first step is to start Wilson on a few lanes with order intake from the ERP, then decide which updates should flow back.

Sources