Bring one LTL load to the demo
Key Takeaways
- The most useful LTL demo follows one of your own loads from class to invoice, not a vendor's sample shipment built to work.
- 8 stages show whether software does the work: freight class, quotes, booking, BOL and labels, pickup confirmation, tracking, POD and invoice audit.
- Freight class is the stage most demos skip, and it drives both the quote you accept and the invoice you receive.
- Wilson, by Cartage, is an AI logistics agent that runs LTL loads from class to payment, using the company's SKU catalog, approved carriers and approval rules.
- Bring the real paperwork: the order, SKU data, the quotes you got, the BOL and the carrier's invoice, including any disputed charge.
Why do LTL demos skip the hard parts?
LTL demos skip the hard parts because sample loads are built to work. Freight class, pickup reconfirmation, reclassification and invoice audit only show their problems on a real load, so the way to see them is to bring one.
This affects manufacturers and distributors that ship LTL (less-than-truckload, freight that shares a trailer with other shippers' freight and is priced by class, weight and lane). In LTL, class is set by the NMFC (National Motor Freight Classification), and a wrong class can change the price after the load moves. Class also got harder recently: according to Transport Topics, the NMFC moved many items to a 13-subprovision density scale on July 19, 2025, so accurate weights and dimensions matter more than before.
One LTL load, the way it really runs
- Monday 8:50 a.m. The order lands in the ERP: four pallets, three SKUs, one of them a new product without an NMFC code on file.
- Monday 10:30 a.m. The coordinator estimates class from a similar item and sends a quote request (a request for a price on a specific load) to four approved carriers.
- Monday 3:10 p.m. Three quotes are back. The coordinator sends the tender (the formal offer of the load) to the lowest. The carrier accepts, confirming the booking with a rate confirmation (the document recording price, pickup window and terms).
- Tuesday 11:00 a.m. The warehouse repacks: the shipment is now five pallets. Nobody tells the carrier.
- Tuesday 2:00 p.m. The driver arrives, signs the BOL (bill of lading, the shipping document signed at pickup) that still says four pallets.
- Thursday. Delivered. The POD (proof of delivery) takes six days of carrier follow-up (repeated calls and emails) to arrive.
- Three weeks later. The invoice includes a reclassification fee and a weight correction, two accessorials (charges on top of the base rate). The coordinator can't show how the class was set.
None of that would appear in a sample load. All of it shows up on yours.
What should one LTL load show in a demo?
Ask the vendor to walk your load through 8 stages, and score each one on whether the software did the work or only displayed it.
| # | Stage | What to ask them to show |
|---|---|---|
| 1 | Freight class | How class is set from your SKU data, and how a reclassification is explained |
| 2 | Quotes | Which carriers are asked, and how quotes are compared and negotiated |
| 3 | Booking | Who books, what needs approval and what happens when a carrier declines |
| 4 | BOL and labels | The BOL, packing slip and pallet labels for this load |
| 5 | Pickup confirmation | How the window is confirmed and reconfirmed before the truck is due |
| 6 | Tracking | Where status comes from and what happens when the load runs late |
| 7 | POD | How the POD is requested, followed up and filed |
| 8 | Invoice audit | How the invoice is checked against the booking before payment |
Class comes first because every later stage depends on it. A class set from a description alone often misses the density subclass; one calculated from weight and dimensions can be explained when a carrier challenges it. That only holds if your SKU data is accurate, so whoever owns the catalog matters as much as the software.
Pickup confirmation is the second weak point. LTL carriers run many stops per route, and a pickup confirmed on Monday can slip on Tuesday. A demo should show the reconfirmation before the window and what happens if the carrier is silent.
How do you prepare the load for the demo?
Prepare one load a few days ahead, and choose one that went wrong. A load with a class change, a late pickup or an extra charge tests far more than a clean one.
Pick a load from last month with a known problem.
Bring the SKU data: product descriptions, weights, dimensions and any NMFC codes you already use.
Bring what happened: the quotes, the booked carrier, the rate confirmation and the BOL.
Bring the invoice, including any charge you disputed and the outcome.
Write down your rules: approved carriers, rate targets, approval limits and who gets notified.
For a broader demo setup, see before the demo, make the software do the work.
Common mistakes when evaluating LTL software
- Accepting the vendor’s sample load. Clean data hides how class, changes and charges are handled.
- Leaving SKU data at home. Without your weights and dimensions, nobody can show how class is calculated.
- Stopping at booking. Most LTL cost surprises show up at pickup and on the invoice, not in the quote.
- Ignoring the pallet-count change. If the software can’t handle a change after booking, your BOL and invoice will disagree. See the pallet count changed after the freight quote.
How does Wilson, by Cartage, run an LTL load from quote to POD?
Wilson, by Cartage, runs each LTL load through every stage, from class to payment, using the company’s SKU catalog, approved carriers and approval rules. 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. Class | Order arrives | Looks up the NMFC classification from the product description and calculates the density-based subclass from the SKU catalog | If SKU data is missing; the company is responsible for its inputs |
| 2. Quote | Class is set | Requests and compares quotes from approved carriers and negotiates against your targets | Above the approval limit |
| 3. Book | Best option is clear | Books the carrier and sends the rate confirmation; moves to the next approved carrier if one declines | If no approved carrier accepts |
| 4. Documents | Load is booked | Generates the BOL, packing slip and pallet labels | Not required |
| 5. Pickup | Booking is confirmed | Schedules the pickup, confirms the window and reconfirms it before the pickup | If the carrier can’t confirm |
| 6. Track | Load is in transit | Tracks by carrier API, GPS or ELD data, or the carrier website by PRO number; gets a new ETA and reason if late | To decide on customer changes |
| 7. POD | Load is delivered | Requests, follows up on and files the POD | If it’s still missing past the set window |
| 8. Audit and pay | Invoice arrives | Audits and reconciles it against the booking, then pays from the preloaded wallet | To approve charges outside the rules |
When a carrier reclassifies a shipment, Wilson explains how the class was calculated: the NMFC lookup and the density subclass from weight and dimensions. The class is only as accurate as the inputs, and the company provides the SKU file, weights, dimensions and any NMFC codes it uses and is responsible for their accuracy.
The company sets the controls. Wilson starts with assisted execution, and approvals can be set on any action the company chooses, such as bookings above a cost threshold or carrier selections. Wilson escalates when no approved carrier accepts, a carrier can’t confirm or a decision exceeds the approval rules. Every message, confirmation and change on the load, including call transcripts, is recorded in a change history.
Wilson books only approved carriers and coordinates pickup times with them, but it doesn’t manage dock slots inside your warehouse. For how this compares across tool categories, see the best AI tools for LTL freight.
What should you test and write down during the demo?
Push the load off plan at least twice, then write down which stages ran without a person and which still needed one.
What to ask a vendor to show in a demo
- The class calculation for your new SKU, with the density subclass and the inputs used.
- A pallet count change after booking, and what the carrier and BOL receive.
- A declined tender, and how the next approved carrier is reached.
- A silent carrier on reconfirmation morning, and when your team hears about it.
- Your disputed invoice audited against the booking, with the reclassification explained.
Then record four things: how many of the 8 stages ran without a person doing the work, whether the class matched what the carrier billed, whether the tool waited for approval where your rules said it should, and whether every message was saved on the load. For the agent category behind this kind of execution, see what an AI logistics agent is.
FAQs
- How should I evaluate LTL freight software in a demo? Bring one real LTL load and have the vendor run it from class to POD and invoice audit. Wilson, by Cartage, runs each stage on your own load, using your SKU catalog, approved carriers and approval rules.
- What should I bring to an LTL software demo? The order, SKU data (descriptions, weights, dimensions, NMFC codes), the quotes you got, the rate confirmation, the BOL and the carrier's invoice. A load that had a problem tests the most.
- Who determines freight class in Wilson? Wilson looks up the NMFC classification and calculates the density-based subclass from the customer's SKU catalog. The customer provides the inputs and is responsible for their accuracy.
- What happens if a carrier reclassifies my shipment? Wilson explains how the class was calculated, from the NMFC lookup and the weight and dimensions used. The invoice is then audited against what was booked before payment.
- Does Wilson create the BOL and labels? Yes. Wilson generates rate confirmations, BOLs, packing slips and pallet labels.
- Does Wilson reconfirm LTL pickups? Yes. For LTL and FTL, Wilson schedules the pickup, confirms the window and reconfirms it before the pickup.
- Does Wilson audit LTL invoices? Yes. Wilson audits and reconciles each carrier invoice against what was booked, then pays the carrier from the company's preloaded wallet.
- How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson. Pricing scales down as volume grows, and Enterprise pricing is custom.
Conclusion
A sample load always looks good in a demo. One of your own LTL loads, with its real SKUs, a change after booking and a disputed invoice, shows what the software does when class, pickups and charges get messy. Follow it through all 8 stages and write down what ran without a person.
Wilson, by Cartage, runs LTL loads from class to payment with your SKU catalog, approved carriers and approval rules, and explains the class when a carrier challenges it. Bring last month's most difficult LTL load, with its SKU data and invoice, and watch Wilson run it from class to audit in a demo at cartage.ai.
Sources
- 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