From a SAP order to a booked load: what to test

Key Takeaways

Test with real SAP orders and delivery data, including one where the weight or dimensions don't match what's on the floor.
Run 6 tests: order intake, delivery data checks, quoting, booking, shipping documents and status back to SAP.
Bad order data often surfaces at the quote or at pickup, so the most useful test is what a tool does when the data is wrong.
Wilson, by Cartage, is an AI logistics agent that works with SAP and turns orders into quoted, booked, tracked and paid shipments.
Status back to SAP is optional and set up per customer, usually after order intake is working.

Why do SAP orders stall before the load is booked?

SAP orders stall because the order and delivery data live in SAP, but quoting, booking and follow-up happen outside it, and data gaps often surface only when a carrier asks. An evaluation should test whether a tool catches those gaps before the quote and then finishes the work.

This affects manufacturers and distributors that run SAP as their ERP and ship with their own carriers across LTL, FTL and cross-border lanes. In a BCI Global survey of 240 supply chain leaders (March 2025), only 35% reported end-to-end visibility. LTL adds pressure: the NMFC moved many items to a 13-subprovision density scale on July 19, 2025, according to Transport Topics, so weights and dimensions now drive class more directly.

One SAP order, step by step

Here is how one LTL order moves at a manufacturer today (times are for example):

Wednesday 8:20 a.m. An order is confirmed in SAP and a delivery is created: 6 pallets, 4,200 lb.
9:00 a.m. The coordinator emails three carriers for a quote, a carrier's price for this specific load, using the SAP weight and a class from an old spreadsheet.
11:40 a.m. She sends the tender, the formal offer of the load, to the lowest quote. The carrier dispatcher accepts and sends the rate confirmation, the document that fixes the rate and terms. The booking is done.
1:00 p.m. The warehouse stages 7 pallets, not 6. Nobody updates the delivery.
Thursday 10:15 a.m. The driver flags the extra pallet at pickup. The BOL, the bill of lading the driver signs, is reprinted by hand.
Two weeks later. The carrier reweighs and reclassifies the shipment, and the invoice comes in higher than the quote.

The data was in SAP. The mismatch between SAP and the floor was found by the carrier, and paid for by the shipper.

What should a SAP user test from order to booked load?

Run 6 tests, in order, on real SAP orders, and include at least one order with a known data error.

#	Test	What to try	What a pass looks like
1	Order intake	Send orders the way they’d really flow: an ERP feed, an export file or email	A shipment with the right ship-to, items, dates and references
2	Delivery data checks	Send a delivery with a wrong weight, missing dimensions or no delivery contact	The gap is flagged to a person before quoting, not guessed
3	Quoting	Request quotes from your approved carriers	Quotes compared on the same services and class
4	Booking	Tender and book the selected carrier	A rate confirmation sent and the pickup window confirmed
5	Shipping documents	Generate the BOL, packing slip and pallet labels, plus commercial invoice and packing list for cross-border	Documents match the SAP order and delivery
6	Status back to SAP	If you want write-back, check booked, picked up and delivered	Updates arrive by the method you agreed on

Test 2 decides how much rework you’ll have. A tool that quotes whatever it receives will repeat the reclassification above at scale. For the documents in test 5, see shipping documents to have ready before pickup.

How should a SAP team run the evaluation?

Scope it to a few lanes and one or two modes, agree on the intake method, then run real orders with a coordinator watching.

Pick recent orders across your main lanes and modes, including a few with known data gaps.
Agree on the intake method you'll really use, such as an ERP feed or a scheduled file drop.
Share the SKU file, weights and dimensions used for LTL class.
Load your approved carriers and approval limits so booking follows your rules.
Run each order through data checks, quote, booking and documents, then compare the results with how those lanes run today.

What to ask a vendor to show in a demo

Show a SAP delivery with the wrong weight and where it gets caught.
Show how LTL class is calculated from my SKU data, and what happens when a dimension is missing.
Show the BOL and pallet labels next to the SAP delivery.
Show a cross-border load's commercial invoice and packing list, and the follow-up with my customs broker.
Show a status update arriving back by the write-back method we'd use.

Common mistakes in SAP evaluations

Testing only clean deliveries. The tool looks perfect until the first staged-pallet change.
Treating class as the carrier's job. Reclassifications then arrive on invoices, after the quote was approved.
Leaving the warehouse out. Pallet counts change on the floor; if nobody updates the delivery, every tool quotes the wrong load.

How does Wilson, by Cartage, take a SAP order to a booked load?

Wilson works from your SAP orders: it creates the shipment, checks the data it needs, quotes and books with approved carriers, prepares the documents, tracks the load and, if you want it, sends status back to SAP. 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. Intake	Order is ready in SAP	Receives it by ERP feed, spreadsheet, email or scheduled file drop and creates the shipment	If shipment details are missing
2. Class	Shipment is LTL	Looks up the NMFC classification and calculates the density-based subclass from the SKU catalog	If SKU, weight or dimension inputs are missing
3. Quote	Shipment is ready	Requests quotes from approved carriers and negotiates against the company’s targets	If no quote meets the rules
4. Book	Best option is clear	Books the carrier, sends the rate confirmation and confirms the pickup	Above the approval limit
5. Documents	Load is booked	Generates the BOL, packing slip and pallet labels, plus the commercial invoice and packing list for cross-border	If product data is missing
6. Track	Load is in transit	Tracks the load and updates the people the company has chosen	If the delay needs a decision
7. Write-back	Status changes, if configured	Sends status back by CSV or Excel file by email, a shared table or an API where available	Method is set during onboarding

Wilson starts with assisted execution. Your company decides which actions need approval, such as bookings above a cost threshold or specific carrier selections, and autonomy expands step by step. Wilson escalates when data is missing, when a carrier can’t confirm, when no approved carrier accepts or when a decision exceeds the approval rules.

Your company provides the SKU file, weights, dimensions and any NMFC codes it already uses, and is responsible for their accuracy. If a carrier reclassifies a shipment, Wilson explains how the class was calculated. Every message, confirmation and change is recorded in a change history.

Wilson is not a customs broker and does not clear customs; it follows up with your broker, carriers and freight forwarder until the shipment moves. It books only carriers your company has approved. See AI logistics automation and ERP integration.

What should SAP users decide before connecting freight automation?

Decide the scope, the data ownership, the write-back and the approval rules before you connect anything.

Scope: which lanes or mode go first. Most customers start on a few lanes and expand.
Data ownership: who corrects a weight or SKU dimension when it’s wrong, and whether the warehouse updates SAP when the pallet count changes.
Write-back: whether you need it, which statuses (booked, picked up, delivered, POD filed) and by which method. The POD is the proof of delivery, the signed receipt from the consignee.
Approvals: which actions need a person, and at what cost threshold.

For who should own booking once the order is in the ERP, see the ERP order: who books the freight?.

FAQs

What should a SAP user test in a freight automation evaluation? Six things, on real orders: order intake, delivery data checks, quoting, booking, shipping documents and status back to SAP. Wilson, by Cartage, works with SAP and can run all 6 on your own orders.
Does Wilson work with SAP? Yes. Wilson works with SAP, NetSuite, Microsoft Dynamics 365 and most other ERPs. If your orders live in an ERP, Wilson can work from it.
How do SAP orders reach Wilson? In 4 ways: an ERP feed, a spreadsheet, email or a scheduled file drop.
Does Wilson write updates back to SAP? Yes, when you want it. Write-back is optional and set up per customer, by CSV or Excel file by email, a shared table or an API where available.
Does Wilson replace SAP? No. Wilson connects to the ERP. It replaces the TMS: it is the system of record for shipments and the execution layer that does the work.
Does Wilson handle cross-border documents? Wilson generates the commercial invoice and packing list and follows up with your customs broker. It is not a customs broker and does not clear customs.
How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson, covering the full lifecycle from create to pay.

Conclusion

For a SAP team, the order and delivery data are already there. What’s missing is the work between the delivery and the booked load, and a check on the data before a carrier finds the problem. Six tests on real orders, with at least one known data error, show whether a tool does that work. For the category, see what an AI logistics agent is.

Wilson, by Cartage, works from SAP orders and runs the freight from quote to payment, with write-back when you want it. Pull one recent SAP delivery whose weight or pallet count changed before pickup, and watch Wilson check, quote and book it in a demo at cartage.ai.

Sources

BCI Global, “No visibility, no resilient supply chain,” March 2025: https://www.bciglobal.com/bci-global-report-no-visibility-no-resilient-supply-chain
Transport Topics, LTL carriers and NMFC changes, 2025: https://www.ttnews.com/articles/ltl-carriers-nmfc-changes
Cartage, Wilson product FAQ, October 2026: https://cartage.ai