Freight operations software for distributors: what needs to happen on every load?

Key Takeaways

A distributor should hold freight operations software to a per-load spec: ten things that must happen on every load, from the customer order to the paid carrier invoice.
The spec matters most on small, fast orders, where a skipped step stays invisible until a customer calls about a missed promise date.
Four decisions come before any quote: order source, ship-from warehouse, parcel or LTL, and customer-routed or company-booked.
Each requirement names a trigger, an action and an end state the buyer can check on the shipment.
Wilson, by Cartage, is an AI logistics agent that replaces the TMS for freight execution, connects to the ERP and runs each load through the spec under the distributor's approved carriers and rules.

What should freight operations software do on every distributor load?

It should take each load through the same ten checkpoints, from the customer order to the audited and paid carrier invoice, with none skipped because the order was small or the day was busy.

One warehouse might release 120 orders in a day (an illustrative figure), most of them a few cartons or a pallet or two, many promised for next-day delivery. Some ship parcel, some LTL, a few on the customer's own carrier. Teams rarely fail on the big truckload, because it gets attention. They fail on the routine one-pallet order whose delivery appointment nobody confirmed, or the parcel shipment whose tracking number never reached the customer.

A capability list asks whether the software can book LTL. The spec asks whether it booked, confirmed, updated and closed every LTL load the warehouse shipped yesterday. Comparisons of the software categories distributors choose from narrow a shortlist; the spec tests it.

How to write the spec: decide, execute, close

Each line of the spec names a trigger, the required action and an end state someone can check on the shipment. Three phases show where a vendor's coverage stops.

Decide, before anything is booked: the order arrives, the ship-from warehouse is confirmed, the mode is set, and the load is marked customer-routed or company-booked. A wrong ship-from produces a wrong quote, pickup and BOL.
Execute, from quote to delivery: company-booked loads are quoted and booked, appointments confirmed, customers updated at chosen milestones, and exceptions worked until the load is rebooked or a person decides.
Close, after delivery: the POD is filed so billing can invoice the customer, and the carrier invoice is audited and paid.

Write each line as: "When [trigger], the software [action], and the load shows [end state]." For example: "When a retail order needs a delivery appointment, the software requests it, confirms it with the carrier before pickup, and the load shows the confirmed time." Vendors then answer yes, partial or no on real loads.

What makes distributor loads hard to run the same way every time

Distributor freight breaks on volume and variety, not on any single difficult load.

Many small orders against fast promise dates. A same-day cutoff leaves little time between release and pickup. If each booking waits in someone's inbox, the promise date slips without anyone deciding to let it.

More than one warehouse. The ERP or order desk decides which building ships. Freight software should take that ship-from as given, use the right origin, dock hours and pickup contacts, and treat a split order as two loads tied to one promise.

Parcel versus LTL. The line between a multi-carton parcel shipment and an LTL pallet is a rule based on weight, cartons, dimensions and customer requirements, set ahead of time, as covered in deciding parcel or LTL before the order arrives.

Customer-routed versus company-booked. On customer-routed loads, the customer names the carrier and usually pays. On those loads the customer has already chosen the carrier, so there is nothing to quote or book, but pickup, paperwork, status and POD still need an owner; see who follows up on customer-routed and company-booked loads.

Retail and jobsite deliveries. Retail receivers often require appointments, and contractors want material timed to the jobsite. A missed appointment can mean a refused delivery and a second trip.

How should a distributor hold a vendor to the spec?

The spec passes only if it holds across a full day of real orders, not one hand-picked load.

Test a whole day. Run every order one warehouse shipped on one day; the small orders a demo would skip are where the spec breaks.
Count skipped checkpoints, not features. A product that completes all ten on large loads and four on small ones fails.
Check that decisions are inherited. Ship-from, mode and routing type should flow from the order and the rules, not be re-decided by a coordinator on every load.
Agree on exceptions in advance. Will-call orders the customer collects may follow a shortened spec; write those cases down first.
Know what stays with people. Allocating inventory between warehouses, changing a promise date, routing disputes and claims are judgment calls that should reach the right person with the load's history attached.

The per-load operations spec: a checklist for every distributor load

#	Requirement	Must happen on every load	Done when	Most often skipped when
1	Order intake	Load created from the ERP release or customer order with ship-to, weight and promise date	The load references the order and promise date	The order arrives by email
2	Ship-from warehouse	Origin, dock hours and pickup contact match the shipping warehouse	BOL and pickup show the right building	Stock is split across warehouses
3	Parcel or LTL	The mode rule is applied	Mode recorded with the rule that set it	The order sits near the cutoff
4	Routing type	Marked customer-routed or company-booked, instructions captured	Customer's carrier on the load, or load moves to quoting	Instructions live in a sales rep's email
5	Quote and booking	Quoted with approved carriers and booked within the rules	Acceptance and rate confirmation on file	Someone phones the usual carrier at cutoff
6	Delivery appointment	Requested where required and confirmed with the carrier	Confirmed time on the load	The receiver moves it after booking
7	Customer updates	Customer and sales told about pickup, delays and delivery	Updates recorded on the load	The order is small
8	Exceptions and rebooking	Carrier contacted; rebooking started from approved carriers	New carrier or ETA on the load, or a person decided	It happens after the shift ends
9	POD for billing	POD requested and filed for customer invoicing	POD attached to the load	Tracking shows delivered, no document
10	Invoice audit and payment	Invoice checked against the booking, paid under approval rules	Payment recorded against the load	Small invoices get paid unchecked

How Wilson, by Cartage, runs the spec on each load

Wilson, by Cartage, is an AI logistics agent that runs each distributor load through these checkpoints, under the distributor's approved carriers and approval rules. It replaces the TMS for freight execution and connects to the ERP. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica, and other ERP environments, with the exact connection depending on the customer’s data flow and scope. Orders can also come by file drop, spreadsheet, email or API.

Wilson works from the orders and warehouse locations the distributor already has and runs parcel, LTL and FTL in one workflow. On company-booked loads, it requests quotes from approved carriers and tenders them first, negotiates against rate targets within approval limits, books, and generates the rate confirmation, BOL, packing slips and pallet labels; if no approved carrier accepts, it escalates. On customer-routed loads, it follows up on pickup, status and POD with the customer's carrier, as configured. It confirms pickup and delivery times with carriers, updates the team in Slack or Microsoft Teams and customers by email or SMS, and on a missed pickup contacts the carrier and initiates rebooking from the approved carrier list, within the rules or with approval. After delivery, it files the POD, audits and reconciles the carrier invoice, and pays from the Wilson Wallet under the distributor's rules.

Wilson starts with assisted execution, and execution can expand step by step. Messages, confirmations and changes are recorded in the shipment history, so each checklist line can be verified on the load.

Bring a day of orders from one warehouse and see in a demo how Wilson runs each load against the spec, from the ship-from decision to the paid carrier invoice.