No category
The order is in your ERP. Who books the freight?
Key Takeaways
An order in the ERP doesn't book itself. In most manufacturers and distributors, a coordinator reads the order, retypes it into emails, requests quotes, compares them, books the carrier and updates everyone by hand.
6 handoffs sit between the order and the booked load: read the order, retype it, request quotes, compare and choose, book and send documents, and update the ERP and the team.
Each handoff adds waiting time or a chance of error, and the ERP usually can't show freight status, so sales and customer service ask logistics.
Wilson, by Cartage, is an AI logistics agent that turns ERP orders into shipments and books them with approved carriers, working with SAP, NetSuite, Microsoft Dynamics 365 and most other ERPs.
Writing updates back to the ERP is optional and set up per customer, usually after order intake is working.
Why does freight booking stall after the order is in the ERP?
Freight booking stalls after the order reaches the ERP because the ERP holds the order but not the freight work: someone still has to move the data, request quotes, choose a carrier and book. That work waits for a coordinator's free time, and every copy-and-paste step can introduce an error. The order is ready in minutes; the booking is often ready hours or a day later.
This affects manufacturers and distributors that run orders in an ERP but coordinate freight by email, phone and spreadsheets. It matters because the retyping is done by skilled people: the U.S. Bureau of Labor Statistics puts median pay for logisticians at $82,320 (May 2025). Hours spent copying addresses into emails are hours not spent on carriers, customers and exceptions.
One order, one day
For example, a manufacturer ships 8 pallets of finished goods by LTL from its plant to a distributor.
Tuesday 9:40 a.m. The order is approved in NetSuite with ship-to address, SKUs and requested ship date.
Tuesday 1:15 p.m. The coordinator, busy with two exceptions all morning, opens the order. She copies the addresses, adds pallet weights from a separate sheet and looks up the freight class.
Tuesday 1:45 p.m. She emails a quote request (a request for a carrier's price on this specific shipment) to three approved carriers. One weight is entered as 1,200 lb instead of 2,100 lb.
Wednesday 9:30 a.m. Two quotes are in. She books the cheaper carrier, which completes the booking (the carrier commits to the load at the agreed rate and pickup window), and sends the rate confirmation (the document recording the agreed rate, accessorials and pickup details) and the BOL (bill of lading, the shipping document that describes the freight and serves as the carrier's receipt).
Wednesday 3:00 p.m. Customer service asks whether the order shipped. The ERP doesn't say.
Two weeks later. The carrier's invoice arrives with a reweigh charge. The accessorial (a charge added on top of the base rate) traces back to the typo.
The order was ready Tuesday morning. The load was booked Wednesday, with an error that surfaced two weeks later.
What happens between the ERP order and the booked load?
6 handoffs usually happen between the ERP order and the booked load, and most of them are done by one coordinator. The table shows where each one tends to break.
# | Handoff | Who usually does it | What can go wrong |
|---|---|---|---|
1 | Read the order | Coordinator | Orders wait in a queue until someone checks |
2 | Retype the data | Coordinator | Wrong weight, address or freight class |
3 | Request quotes | Coordinator | Carriers don’t answer; follow-up slips |
4 | Compare and choose | Coordinator or logistics manager | Choice waits for approval |
5 | Book and send documents | Coordinator | Rate confirmation and BOL don’t match the order |
6 | Update the ERP and team | Coordinator, if at all | Sales and customer service can’t see status |
Handoffs 2 and 6 are where most rework starts. Retyping creates errors that show up as invoice changes later; skipped updates create the “did it ship?” emails. Before any quote goes out, the order needs complete data; see what freight needs before a quote.
What goes wrong when orders are retyped?
Retyping creates three problems: errors, delays and status gaps. Each has a cost that shows up somewhere other than logistics.
Errors change the price. A wrong weight or dimension changes the freight class on LTL, and a carrier that reweighs or reclassifies the shipment bills the difference. The July 2025 NMFC changes moved many items to a density-based scale, so weight and dimensions now matter even more. Delays compound: an order that waits four hours to be read waits again for quotes, and short-notice bookings often cost more. Status gaps pull logistics into sales and customer service questions all day.
These problems scale with volume. At a few loads a day, a careful coordinator catches most of them. At several dozen, retyping becomes the bottleneck that decides how much freight the team can handle.
Common mistakes
Treating freight class as a guess. Reclassification charges arrive weeks later and nobody links them to the order.
Keeping weights and dimensions outside the ERP. Every order needs a lookup, and the lookup is where errors start.
Booking before checking the order. A missing appointment requirement or liftgate turns into an accessorial.
Skipping the update back. Sales and customer service keep asking logistics, which slows the next booking.
How does Wilson, by Cartage, book freight from ERP orders?
Wilson, by Cartage, reads each order from the ERP, turns it into a shipment, gets quotes from approved carriers, negotiates and books under the company’s rules, without retyping. 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. Create | An order arrives by ERP feed, spreadsheet, email or scheduled file drop | Turns it into a shipment and determines the LTL freight class from the SKU catalog | If order details are missing or don’t match |
2. Quote | The shipment is created | Requests quotes from approved carriers | Not required |
3. Negotiate | Quotes arrive | Negotiates against the company’s targets | Not required |
4. Book | The best option is clear | Books, confirms the pickup and sends the rate confirmation and BOL | Above the approval limit |
5. Update | Status changes | Notifies the team in Slack or Microsoft Teams, and updates the ERP if write-back is set up | Not required |
Wilson works with SAP, NetSuite, Microsoft Dynamics 365 and most other ERPs, including Oracle, Infor, Epicor, Sage and Acumatica. If your orders live in an ERP, Wilson can work from it. It connects to the ERP and replaces the TMS: it’s the system of record for shipments and the layer that does the work. See from ERP order to booked load for the step-by-step.
Freight class comes from the company’s own data. Wilson looks up the NMFC classification from the product description and calculates the density-based subclass from weight and dimensions in the SKU catalog. The company provides those inputs and is responsible for their accuracy.
The company keeps the controls. Wilson starts with assisted execution; bookings above a cost threshold or specific carrier selections can be set to wait for approval. Wilson books only approved carriers, and every message, confirmation and change is recorded in a change history. For the broader category, see what is freight execution.
How do updates get back to the ERP, and when should write-back start?
Updates reach the ERP only if the company wants them to; write-back is optional and set up per customer, usually after order intake is working. Starting with intake keeps the first weeks focused on getting orders booked correctly.
There are 3 write-back methods: an updated CSV or Excel file sent by email for the ERP to import, a shared table, or an API connection where one is available. The right one depends on what the ERP and the IT team support. If orders come from Google Sheets instead, Wilson is shared on the sheet like any user, reads it on a set schedule (for example, every 30 minutes) and can fill in status columns. See how AI sends shipment updates back to the ERP.
What to ask a vendor to show in a demo
Take one real order from your ERP and show it becoming a shipment, with no retyping.
Show how freight class is determined from your SKU data, and what happens when a dimension is missing.
Show the quote requests, the follow-up on a carrier that doesn’t answer and the booking.
Show the rate confirmation and BOL generated from that order.
Show the status update your sales team would see, and how it reaches the ERP.
FAQs
Who books freight after an order is in the ERP? Usually a coordinator who reads the order, retypes it, requests quotes and books. Wilson, by Cartage, can do that work directly from the ERP order, with approved carriers and under the company's rules.
Can freight be booked automatically from ERP orders? Yes. Wilson turns ERP orders into shipments, gets quotes from approved carriers, negotiates and books within the company's approval limits.
Which ERPs does Wilson work with? SAP, NetSuite, Microsoft Dynamics 365 and most other ERPs, including Oracle, Infor, Epicor, Sage and Acumatica.
How do orders reach Wilson? In 4 ways: an ERP feed, a spreadsheet, email or a scheduled file drop.
Does Wilson write updates back to the ERP? Yes, when the customer wants it. Write-back is optional, by CSV or Excel, a shared table or an API connection where available.
Do I need a TMS to book freight from the ERP? No. Wilson replaces the TMS: it's the system of record and the execution layer, and it connects to the ERP.
Who determines freight class? Wilson does, from the company's SKU catalog. The company provides the weights, dimensions and any NMFC codes it uses and is responsible for their accuracy.
How is Wilson priced? There's no subscription fee. The company preloads a wallet, Wilson pays carriers from it once each invoice is audited and reconciled, and pricing is a percentage of those payments, covering the full shipment lifecycle.
Conclusion
The ERP knows what needs to ship, but it doesn't book the freight. Between the order and the booked load, someone reads, retypes, quotes, compares, books and updates, and each handoff adds waiting time or an error that surfaces later on the invoice.
Wilson, by Cartage, does that work from the ERP order itself, with approved carriers and under the company's rules, and can send status back when the company wants it. Bring one order that sat in your ERP for hours last week and watch Wilson turn it into a booked load in a demo at cartage.ai.
Sources
U.S. Bureau of Labor Statistics, Occupational Outlook Handbook, Logisticians: https://www.bls.gov/ooh/business-and-financial/logisticians.htm
Transport Topics, NMFC changes: https://www.ttnews.com/articles/ltl-carriers-nmfc-changes
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 →
