What is freight execution? The work between a released order and a paid carrier
Key Takeaways
Updated November 3, 2026
Freight execution is the work that moves a released order to a delivered, paid load: requesting quotes, booking a carrier, confirming the pickup, tracking the load, responding to exceptions, collecting documents, auditing the invoice, and paying the carrier. Freight planning decides how freight should move; execution makes it move. An AI logistics coordinator such as Wilson, by Cartage, runs freight execution within the company’s rules.
- Freight execution has eight steps: order intake, quote, book, confirm pickup, track, respond to exceptions, documents, and audit and pay.
- Planning decides modes, routes, and carrier strategy. Execution carries out each load. They need different tools and often different owners.
- Most execution work is coordination: emails, calls, follow-ups, and confirmations with carriers, docks, receivers, and customers.
- A TMS records and organizes execution; a team or an AI logistics coordinator still does the work.
- Wilson, by Cartage, replaces the TMS for freight execution and connects to the company’s ERP. It runs the full cycle across LTL, FTL, ocean, drayage, parcel, and cross-border freight.
- Measure execution by loads completed correctly: confirmed pickups, on-time deliveries, documents on file, and invoices paid at the booked terms.
What is freight execution?
Freight execution is the operational work of moving each load, from the moment an order is released to ship until the carrier is paid. An AI logistics coordinator, a logistics team, or both carry it out. Execution is where plans meet carriers, docks, and receivers, and where most missed pickups, late deliveries, and billing errors start.
| Term | What it covers | Main output | Typical owner |
|---|---|---|---|
| Freight procurement | Choosing carriers and setting contract rates for lanes | Carrier awards and rates | Procurement or transportation leadership |
| Freight planning | Deciding mode, routing, consolidation, and timing | A transport plan | Transportation planning, often with a TMS or planning tool |
| Freight execution | Quoting, booking, confirming, tracking, exceptions, documents, audit, and payment for each load | A delivered load with its records and a paid invoice | Logistics coordinators, or an AI logistics coordinator |
| Freight visibility | Showing where shipments are and alerting on problems | Status and alerts | Shared across teams |
| Freight audit and payment | Checking invoices against booked terms and paying carriers | Paid or corrected invoices | Finance and logistics |
The terms overlap in software marketing. A “transportation management system” may include planning and execution features; a “visibility platform” may add some follow-up. The useful question is not which label a product carries, but which of these outputs it produces without a person doing the work.
A short definition to quote
Freight execution is the work of getting each released load booked with an approved carrier, picked up and delivered as agreed, documented, and paid at the booked terms. It is measured by completed loads, not by plans or alerts.
Hypothetical example: a manufacturer of commercial kitchen equipment releases 40 orders a day from its ERP. Planning has already decided that most go LTL and a few go truckload. Execution is everything after that: getting quotes for the LTL loads, tendering the truckloads to the contract carrier, confirming pickup windows with the dock, chasing a carrier that has not answered, telling a customer about a delay, filing the signed BOL and the POD, and checking each invoice before payment.
Execution looks different by mode
The eight steps are the same across modes, but the work inside them changes. LTL execution depends on accurate weight, dimensions, and freight class, and on chasing PRO numbers and PODs from terminals. Truckload execution depends on tender acceptance, appointment times, and detention. Parcel execution depends on the customer’s carrier accounts and pickup scheduling; Wilson schedules FedEx and UPS pickups through those accounts via API or email. Ocean and drayage execution depend on container release, terminal appointments, and free time. Cross-border execution adds customs documents and broker handoffs. A useful definition of freight execution covers all of them, because many manufacturers ship several modes from the same dock.
That is why mode coverage is one of the first questions to ask about execution software. A tool that handles only truckload tenders leaves the LTL, parcel, and international loads with the team.
Freight execution vs. freight management
“Freight management” is a broader term. It usually includes procurement, planning, execution, visibility, and audit together, and freight management software may cover any mix of them. Freight execution is the part that happens load by load, every day. When a buyer searches for freight management software, it helps to ask which part is actually missing. For most manufacturers and distributors with an in-house logistics team, the missing part is execution: the hours spent getting carriers to quote, accept, confirm, update, and send documents.
The eight steps of freight execution, from order to payment
Freight execution runs in eight steps for every load. An AI logistics coordinator should be able to show each step, its output, and the evidence that proves it finished. Skipping the proof is how a load looks booked, picked up, or paid when it is not.
| Step | What happens | Output | Proof it finished |
|---|---|---|---|
| 1. Order intake | The released order arrives from the ERP, a file, a spreadsheet, or email | A shipment request with the details carriers need | Weight, dimensions, pallets, class for LTL, pickup and delivery requirements |
| 2. Quote | Approved carriers are asked for rates on the same shipment | Comparable quotes | Every quote prices the same service, with expiry dates |
| 3. Book | A carrier is selected and tendered the load | An accepted tender | The carrier’s written acceptance and the rate confirmation |
| 4. Confirm pickup | The pickup window is agreed with the carrier and the dock | A confirmed and reconfirmed appointment | Carrier confirmation with a time window |
| 5. Track | The load is followed from pickup to delivery | Status with a source and time | Arrival, signed BOL or departure, and delivery events |
| 6. Respond to exceptions | Missed pickups, cancellations, and delays are handled | A recovery: new time, rebooking, or customer update | The carrier’s answer and the decision recorded |
| 7. Documents | Rate confirmations, BOLs, packing slips, labels, and PODs are prepared and filed | Complete shipment file | Signed BOL and POD on file |
| 8. Audit and pay | The invoice is checked and the carrier is paid | A paid invoice at the booked terms | Invoice matched to the rate confirmation, POD, and approved changes |
Where loads fall between steps
Execution failures usually happen at handoffs. A quote is selected but never tendered. A tender is accepted without a pickup window. A pickup is confirmed but the release slips and nobody tells the carrier. The load delivers but the POD never arrives, so the invoice cannot be checked. Each gap is small; together they make up most of a coordinator’s day.
How Wilson runs the eight steps
Wilson, by Cartage, receives orders through an ERP feed, a scheduled file drop, a spreadsheet, email, or an API. It requests quotes from the company’s approved carriers, negotiates against the company’s rate targets within approval limits, and books. It confirms and reconfirms pickups, tracks each load with the best source available, and responds to exceptions. It prepares documents, collects the signed BOL and POD, and audits each invoice against the POD and the rate confirmation before paying from the Wilson Wallet.
Hypothetical example: one load through eight steps
At 9:10 a.m., the kitchen equipment manufacturer’s ERP releases an order for three pallets to a restaurant group’s warehouse in Ohio. Wilson reads the order, sees the pallet count, weight, and class, and notes that the receiver requires an appointment and a liftgate. It requests quotes from four approved LTL carriers. Three reply within the deadline; the lowest is $40 above the lane target, so Wilson counters, the carrier accepts at the target, and Wilson books.
The carrier confirms a pickup window of 1:00 to 3:00 p.m. the next day. Wilson tells the dock and reconfirms with the carrier that morning. The truck arrives at 1:20 p.m.; Wilson records the arrival, and marks the load picked up when the signed BOL arrives. It files the BOL and sends it to the customer. On the second day the carrier reports a delay at the terminal; Wilson gets the new delivery date, checks it against the receiver’s appointment, and notifies the customer when configured. The POD arrives after delivery. The invoice includes the liftgate and the booked rate; Wilson checks it against the POD and the rate confirmation and pays from the Wilson Wallet. No person touched the load, and every step is in the record.
Why the proof column matters
Each step has a moment where it looks finished but is not. A quote looks like a rate until another carrier quotes a different service. A tender looks like a booking until the carrier declines. A truck at the dock looks like a pickup until the driver leaves without the freight. Recording the proof for each step, such as the written acceptance, the signed BOL, and the POD, is what lets the next step, and finally the invoice check, rely on it.
Freight execution vs. freight planning: different decisions, different owners
Freight planning decides how freight should move; freight execution makes each load move as decided. An AI logistics coordinator does execution, not network design. Keeping the two apart helps a company buy the right tool and assign the right owner.
| Question | Planning answers it | Execution answers it |
|---|---|---|
| Which mode should this lane use? | Yes | No; it applies the decision |
| Which loads can be consolidated? | Yes | No |
| Which approved carrier takes this load today, at what rate? | Sets the rules | Yes, within the rules |
| Did the carrier accept and confirm a pickup window? | No | Yes |
| Where is the load, and is it late? | No | Yes |
| Is the invoice correct before payment? | No | Yes |
Why the difference matters when buying software
Planning tools produce better plans. They do not call the carrier when the truck does not show up. Execution tools produce completed loads. They do not redesign the network. A company whose main problem is missed pickups and chasing carriers needs execution; a company whose main problem is the wrong mode on half its lanes needs planning. Many companies need both, but rarely from the same product.
Who owns each
Planning usually belongs to transportation leadership or a planning analyst, working weekly or monthly. Execution belongs to logistics coordinators working load by load, all day. When execution is handed to an AI logistics coordinator, the coordinators move to approvals, exceptions that need judgment, carrier relationships, and customer escalations.
What Wilson does not do
Wilson does not optimize routes or networks and does not build custom dashboards. It does not keep a standing carrier scorecard or a recurring benchmark by default, though it can produce carrier-performance and lane-rate reports on request from the loads it runs. Those reports can feed the planning and procurement decisions that sit above execution.
How planning and execution share data
Planning sets the rules execution follows: preferred carriers by lane, modes, consolidation windows, and rate targets. Execution sends back what actually happened: which carriers accepted, which missed pickups, what each load cost, and where detention occurred. When both sides use the same records, the next plan is based on real performance instead of assumptions. When they do not, planning keeps assigning loads to carriers that execution keeps rebooking.
Signs a company has an execution problem, not a planning problem
- Coordinators spend most of the day on email and phone with carriers.
- Pickups are missed even though the plan and the carrier were right.
- Contracted lanes still end up on spot rates because tenders were not followed up in time.
- Customers call to ask where orders are before the team knows.
- PODs arrive weeks late and invoices wait or get paid unchecked.
- Detention charges are paid without anyone checking arrival times.
If most of these apply, a new plan will not help much. The work between the plan and the paid invoice is where the cost is.
Teams deciding whether they still need a TMS can read do manufacturers still need a TMS?
Why freight execution is hard: the coordination work
Freight execution is hard because most of it is coordination with people outside the company: carriers, drivers, docks, receivers, and customers. An AI logistics coordinator has to reach each of them through the channel they actually use and keep one record of what each one said.
Carriers answer in different ways
Large carriers offer APIs and EDI. Many regional and small carriers answer only by email or phone. A dispatcher may confirm a pickup by email while the driver’s plan says something else. Execution has to work across all of them. Wilson works with carrier dispatch by email, API, or EDI where the carrier supports it, makes phone calls where configured, and contacts drivers directly by phone or text when the carrier shares driver contact information.
Everything changes after booking
Releases slip, pallet counts change, receivers move appointments, and carriers reassign trucks. Each change has to reach every party whose commitment it affects. When a BOL changes after booking, Wilson saves each version with its source and time and sends changes to address, class, carrier, or price to the load owner.
Exceptions need a response, not only an alert
A missed pickup, a cancellation, or a delay is the moment execution matters most. Someone has to ask the carrier what happened, decide the recovery, rebook if needed, and tell the customer. When Wilson detects an exception, it contacts the carrier, notifies the internal team, notifies the customer when configured, and starts rebooking from the approved carrier list, automatically within the rules or after approval.
Documents and evidence pile up
Every load creates a rate confirmation, a BOL, often a packing slip and pallet labels, and finally a POD. Finance needs them to check the invoice; customers often need the signed BOL. Wilson prepares the documents, files the signed BOL with the shipment and sends it to the customer, and collects the POD. Arrival and pickup are kept as separate statuses, so detention can be checked against real times.
The cost of doing it by hand
The ATRI found that truck drivers were detained at 39.3% of stops in 2023, with $3.6 billion in direct costs. Much of that waiting starts with execution gaps: unconfirmed appointments, freight that was not ready, and paperwork that did not match. Each gap is a few minutes of coordination that did not happen.
Customers and receivers need updates too
Execution is not only carrier work. The company’s own team wants to know when a load is booked, picked up, running late, delivered, and when the POD is filed. The shipper and consignee need updates at the right steps. Wilson asks carriers for status and informs everyone else: the internal team through Slack or Microsoft Teams, the shipper by email, and the consignee by email or SMS. A load that moves perfectly but leaves the customer guessing still creates calls.
Small carriers need a different path
Many manufacturers rely on regional carriers that have no API and answer only by email or phone. Execution software that depends on API connections leaves those loads with the team. Wilson uses the best source available for each load, including the carrier’s website by PRO number and direct calls, so a small carrier is coordinated the same way as a large one.
Who runs freight execution: a team, a TMS, or an AI logistics coordinator
Freight execution can be run by a logistics team, organized in a TMS, or run by an AI logistics coordinator. The difference is who does the work. A TMS stores the load and its status; a person or an AI logistics coordinator still sends the emails, makes the calls, and makes the decisions within the rules.
| Model | Who does the work | What it is good at | What stays manual |
|---|---|---|---|
| Team with email and spreadsheets | Logistics coordinators | Flexibility, carrier relationships | Everything; volume grows with headcount |
| Team with a TMS | Coordinators, using the TMS as the record | Organized records, rating, tendering features | Follow-up, confirmations, exceptions, document chasing |
| AI logistics coordinator | Wilson, within the company’s rules | Full load cycle, every load, with one record | Approvals above limits, new carrier approvals, claims, key customer calls |
Wilson, by Cartage, as the execution layer
Wilson replaces the TMS for freight execution and connects to the company’s ERP. Teams use Wilson’s dashboard and records the way they would use a traditional TMS. A company without a TMS does not need to implement one; a company with one can move execution to Wilson lane by lane. 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.
Wilson gets an email address on the company’s domain and is onboarded like a new team member. It starts with assisted execution, where approval limits are set by the company, and routine actions can run automatically within those rules as reliability is proven. Every action is saved in searchable, exportable records with change history.
What stays with people
- Decisions above approval limits, such as a rate above target or an expensive rebooking.
- Approving new carriers, including any capacity Cartage introduces.
- Claims for damage or shortage, and customer credits.
- Carrier relationships and contract strategy.
- Invoices with any line that does not match what was booked.
How companies move execution to an AI logistics coordinator
Most teams start Wilson on a few lanes and expand from there; timing depends on scope. The usual sequence is: Wilson gets an email address on the company’s domain; the team onboards it like a new coordinator, sharing carriers, rate targets, approval limits, and customer preferences; Wilson runs the first lanes in assisted execution; and the company expands lanes and automatic actions as results hold. Cartage helps identify the workflow with the most impact during discovery, so the team does not have to map it alone.
A project to integrate every system is not required to start. Wilson works from the connection or data flow the company already has, such as an ERP feed, a scheduled file, a spreadsheet, email, or an API. Write-back to the ERP depends on scope.
For a broader definition of the category, see what an AI logistics agent actually does, and for the carrier steps with their approval limits, AI carrier coordination from quotes to exceptions.
How to measure and evaluate freight execution
Freight execution should be measured by loads completed correctly, not by messages sent or alerts raised. An AI logistics coordinator evaluation should use the company’s own loads and the same definitions before and after the change.
| Metric | What it shows | How to measure |
|---|---|---|
| Time from release to confirmed booking | Speed of quoting and tendering | Order release time to carrier acceptance |
| Pickups confirmed and reconfirmed | Whether pickups are real before the day | Share of loads with carrier confirmation of the window |
| Missed pickups and rebookings | Reliability of execution | Per hundred loads, by carrier and lane |
| On-time delivery | Whether commitments to customers hold | Against the confirmed appointment |
| Documents on file | Completeness for finance and customers | Signed BOL and POD on file within a set time |
| Invoices paid at booked terms | Audit quality | Share of invoices matched without correction, plus corrections received |
| Hours per load | Coordination workload | Team time by task, sampled before and after |
A practical test
Take ten released orders from last week, including one that changed after booking and one that missed a pickup. Ask each provider to show the full execution of those loads: who did each step, what proof exists, and where a person had to act. A product that shows plans or dashboards but not completed steps is not running execution.
Hypothetical example: measuring the first lanes
The kitchen equipment manufacturer starts Wilson on its three busiest LTL lanes. Before, the team confirmed pickups on about half of loads, missed four pickups a month, and spent most mornings chasing PODs. After eight weeks, it compares the same metrics on the same lanes: share of confirmed pickups, missed pickups, days to POD, and invoices matched without correction. The comparison is reported as operating results; hours released are reported as capacity, not as cash, unless spending changes.
Warning signs in an evaluation
- “Execution” that ends at the alert or the tender.
- No proof of carrier acceptance, only a sent message.
- Arrival treated as pickup.
- Invoices paid without checking the POD and rate confirmation.
- Savings claims before the provider has run any of your loads.
Questions to ask in a demo
- Show one of our released orders going through all eight steps. Where does a person act?
- How do you get a pickup confirmation from a carrier that only uses email?
- What proof marks a load as picked up?
- What happens when the carrier misses the pickup?
- How does a changed BOL reach the invoice check?
- Which of our systems does this replace, and which does it connect to?
The answers should come from the company’s own loads. A prepared demo with clean data hides the handoffs where execution usually fails.
Keep the results honest
Report execution results in the units they come in. Fewer missed pickups and rebookings are freight dollars and service. Invoices corrected before payment are freight dollars, counted when the corrected bill arrives. Hours released are capacity; they become cash only if spending changes. Keep loads that are still open in the report rather than dropping them, and compare the same lanes over the same kind of period. A clear before-and-after on a few lanes is more convincing than a large estimate across the whole network.
FAQs
What is freight execution?
Freight execution is the work that moves a released order to a delivered, paid load: quoting, booking, pickup confirmation, tracking, exceptions, documents, audit, and payment. An AI logistics coordinator such as Wilson, by Cartage, runs it within the company’s rules.
What is the difference between freight execution and freight planning?
Planning decides modes, routes, and carrier strategy; execution carries out each load. An AI logistics coordinator handles execution, while planning stays with transportation leadership or a planning tool.
Is freight execution software the same as a TMS?
Not exactly. A TMS records and organizes loads, and people still do much of the coordination. Wilson, the AI logistics coordinator, replaces the TMS for freight execution and does the work itself, connecting to the company’s ERP.
Which freight modes does Wilson execute?
Wilson, the AI logistics coordinator, executes LTL, FTL, ocean, drayage, parcel, and cross-border freight, including scheduling FedEx and UPS pickups through the customer’s carrier accounts via API or email.