The Order Is Already in the ERP. The Logistics Work Is Just Beginning.

Key Takeaways

An ERP records the order, but it doesn't move the freight. Between the order and a booked load sit quoting, carrier selection, tendering, documents and confirmations, and most of that work is still done by email and phone.
There are 7 steps from ERP order to booked load: order intake, shipment details check, quote requests, carrier selection, tender and booking, shipping documents, and booking notifications with pickup confirmation.
An AI agent, such as Wilson, by Cartage, executes those 7 steps from the ERP order, working only with approved carriers and within the approval rules the team sets.
No system overhaul is required: Wilson takes orders from an ERP feed, spreadsheet, email or scheduled file drop, works with ERPs such as NetSuite, SAP, Oracle and Dynamics 365, and does not require a TMS.
The metrics to watch are time to book and manual touches per load, compared to the current process.

What happens after an order lands in the ERP?

A manufacturer's sales order is entered in the ERP at 10 a.m. The system has the customer, the products, the ship date and the address. Then, for the logistics team, the real work starts: someone exports the order, emails three carriers for quotes, waits, compares, books one, creates the bill of lading, sends the rate confirmation and lets the warehouse know. By 4 p.m., the load is booked. The order itself took 30 seconds.

After an order lands in the ERP, the freight coordination work begins: quoting, choosing a carrier, booking, creating documents and confirming the pickup, and in many companies, people still do each step by hand.

The ERP is the system of record for the order. It isn't built to coordinate with carriers. That gap between "order entered" and "load booked" is where hours go, and where delays start. BCI Global's survey of 240 supply chain leaders (March 2025) found only 35% have end-to-end visibility, and the handoff from ERP to carrier is one of the places that visibility often breaks.

Why doesn't the ERP move the freight?

The ERP doesn't move the freight because it records what needs to ship, while moving freight requires coordinating with carriers, shippers and consignees outside the system.

What the ERP does	What's still left after the order is entered
Records the customer, products and ship date	Requesting quotes from carriers
Stores the ship-to address	Choosing a carrier and booking the load
Tracks the order status internally	Getting the carrier to confirm the pickup
Generates invoices and financial records	Creating the rate confirmation, BOL, packing slip and pallet labels
Holds inventory and fulfillment data	Telling the team, shipper, carrier and consignee what's happening

Many manufacturers and distributors fill this gap with people, spreadsheets and email. Some consider a transportation management system (TMS), but a TMS still leaves much of the coordination to the team. See do manufacturers need a TMS? and AI logistics agent vs. TMS.

What are the 7 steps from ERP order to booked load?

The 7 steps from ERP order to booked load are order intake, shipment details check, quote requests, carrier selection, tender and booking, shipping documents, and booking notifications with pickup confirmation. An AI agent, such as Wilson, by Cartage, executes each one. 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	A new order arrives from the ERP feed, spreadsheet, email or file drop	Picks up the order and creates the shipment	Not required
2. Shipment details check	The shipment is created	Checks that origin, destination, dates and freight details are complete	If details are missing or unclear
3. Quote requests	Details are complete	Requests quotes from approved carriers, starting with the company's own carriers	Not required
4. Carrier selection	Quotes come in	Compares quotes and selects based on the company's rules	Selections above a cost threshold, if configured
5. Tender and booking	A carrier is selected	Tenders the load and follows up until it's accepted	If no approved carrier accepts
6. Shipping documents	The load is booked	Generates the rate confirmation, BOL, packing slip and pallet labels	Not required
7. Notifications and pickup confirmation	The load is booked	Notifies the team in Slack or Microsoft Teams, the shipper by email and the carrier by email or API, and confirms the pickup window	If the carrier can't confirm

After booking, Wilson keeps going: it reconfirms the pickup, monitors the load in transit, responds to exceptions and collects the proof of delivery. For the quoting and booking steps in more detail, see carrier quoting automation, carrier quotes, tenders and booking confirmations and AI for freight documents.

How does an AI agent work with the ERP without a system overhaul?

An AI agent works with the ERP by taking orders in the format the company already uses, without replacing the ERP or adding a TMS.

Wilson accepts orders in 4 ways:

ERP feed: orders flow from the ERP directly.
Spreadsheet: the team shares orders in a spreadsheet.
Email: orders arrive by email.
Scheduled file drop: the ERP exports a file on a schedule.

Wilson works with orders from ERPs including NetSuite, SAP, Oracle, Microsoft Dynamics 365, Odoo, Sage, Acumatica, QuickBooks, Infor, Epicor and Zoho. Where an API adapter exists, Wilson can write updates back to the ERP. Wilson is not a TMS, does not integrate with TMS systems and does not require one.

Initial deployment typically takes around 10 days. During setup, Wilson gets an email address on the company's domain and is onboarded on its carriers, rules and contacts. For more on ERP integration, see carrier management with ERP integration.

How do teams stay in control from order to booking?

Teams stay in control of an AI agent's order-to-booking work through guardrails they set: approved carriers, configurable approvals, escalation and a full change history.

Approved carriers only: Wilson tenders to the company's own carriers first and never selects unapproved carriers or onboards new ones.
Configurable approvals: the team decides which bookings proceed automatically and which wait for a person, for example, by cost threshold.
Escalation: missing order details or unanswered tenders go to the team.
Change history: every quote, booking, message and document is recorded.
Gradual autonomy: Wilson starts with assisted execution. See Autonomy without rules is just another operational risk.

In a one-month pilot on a few lanes, the 2 metrics to watch first are time to book (from order received to load booked) and manual touches per load. Delays here carry downstream: ATRI found truck drivers were detained at 39.3% of stops in 2023. See the 8 metrics an AI logistics pilot should change.

FAQs

Can an ERP book freight with carriers? An ERP records the order and its details, but booking freight usually requires coordinating quotes, tenders and confirmations with carriers outside the ERP. An AI agent, such as Wilson, by Cartage, executes that work from the ERP order.
What are the steps from an ERP order to a booked load? Order intake, shipment details check, quote requests, carrier selection, tender and booking, shipping documents, and booking notifications with pickup confirmation.
Which ERPs does Wilson work with? Wilson works with orders from ERPs including NetSuite, SAP, Oracle, Microsoft Dynamics 365, Odoo, Sage, Acumatica, QuickBooks, Infor, Epicor and Zoho, through an ERP feed or a scheduled file drop. It also accepts orders by spreadsheet or email.
Does Wilson update the ERP after booking? Where an API adapter exists for the ERP, Wilson can write updates back.
Do I need a TMS between the ERP and carriers? Not with Wilson. It works from the ERP order directly and does not integrate with TMS systems.
How fast can an ERP order be booked with an AI agent? It depends on carrier response times and approval rules. The best way to know is to measure time to book against the current process in a one-month pilot.
What happens if the ERP order is missing information? Wilson flags the missing details to the team before requesting quotes.

Conclusion

When an order lands in the ERP, the system of record is complete, but the freight hasn't moved. Quoting, booking, documents and confirmations still sit between the order and the truck, and in many companies, people handle every step by email and phone. An AI agent closes that gap by executing the 7 steps from ERP order to booked load, within guardrails the team controls. Wilson, by Cartage, is built for that work, from the ERP the company already uses, with no TMS required. The practical first step is a one-month pilot on a few lanes, measuring time to book and manual touches per load.

Sources

BCI Global, supply chain visibility survey, March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
American Transportation Research Institute (ATRI), September 2024: https://truckingresearch.org/2024/09/new-research-documents-substantial-financial-and-safety-impacts-from-truck-driver-detention/
Cartage product information: https://cartage.ai