Wilson by Cartage
Try Wilson →
Freight pickups

Load scheduling isn't a planning problem. It's an execution problem.

Key Takeaways

  • Load scheduling usually breaks down in execution, not planning. The pickup window, lane and equipment can all be right, and the load still slips because nobody requested the quote, chased the carrier or confirmed the pickup in time.
  • The work between an order and a truck at the dock has 6 steps: the order becomes freight work, carriers quote, an approved carrier is booked, the booking is confirmed, the pickup is confirmed, and the carrier is followed up until the load moves.
  • Pickup confirmation is a separate step from booking. A carrier accepting a load does not mean a truck will arrive in the agreed window. The window has to be confirmed and reconfirmed.
  • Wilson, by Cartage, is an AI logistics agent that runs these steps from ERP order to pickup and beyond, within the company's approved carriers and approval rules. One plastics and rubber manufacturer has had more than 2,800 shipments scheduled this way from daily SAP batch files.
  • Wilson replaces the TMS for freight execution and connects to your ERP rather than requiring another TMS integration. It is not a route optimization tool.

Why does load scheduling break down even with a good plan?

Load scheduling breaks down because a plan doesn't move a load on its own. Someone still has to turn the order into a shipment, request quotes, book a carrier, confirm the booking and the pickup, and react when the carrier goes quiet or changes the plan. When that work waits, the load slips, even though the plan was right.

Planning decides how a shipment should move: which lane, which mode, which pickup window, which equipment. Execution is the recurring coordination that makes the plan happen, load after load. A planning tool or spreadsheet can hold the correct pickup date while the quote request still sits in a coordinator's drafts.

That gap grows with volume. Every active load creates its own chain of emails and calls: a quote request, two follow-ups, a counter, a tender, a confirmation, a pickup reminder. When dozens of loads are open at once, the next action on each one competes for the same few people. Delays at the dock are expensive: ATRI found truck drivers were detained at 39.3% of stops in 2023.

Better data and more headcount help, but neither removes the sequence. Visibility can show that something changed. It doesn't request a quote, confirm a booking, call a carrier or start rebooking. That is why load scheduling is better treated as an execution problem: the question is who does each step, every time, on every load.

What happens between an ERP order and a booked load?

An ERP order becomes freight work when its shipment details are captured, checked and turned into a load that carriers can quote. That sounds simple, but it is where many loads lose their first day.

How orders reach the workflow

Orders usually come from one of 4 places: an ERP feed, a spreadsheet, email or a scheduled file drop. Many manufacturers export a daily batch of orders from their ERP. Others keep a shared shipping sheet or forward order emails to logistics.

A full ERP integration isn’t required to start. Wilson can work from the data flow the company already has. Sending updates back to the ERP is optional and set up per customer: an updated CSV or Excel file by email, a shared table, or an API connection where one is available. The method is usually decided once order intake is working.

What has to be checked before quoting

Before a carrier can quote, the load needs complete, consistent details:

  • origin and destination addresses
  • ready date and pickup window
  • pieces, weight and dimensions
  • product description, and freight class for LTL
  • special services such as liftgate or appointment
  • the references that tie the load back to the order

When something is missing or conflicting, the safe step is to ask before quoting rather than send carriers an incomplete request. For LTL, Wilson determines NMFC class and the density-based subclass from the customer’s SKU catalog. The customer provides the inputs and is responsible for their accuracy.

What this looks like in practice

One plastics and rubber manufacturer runs this step from daily SAP batch files. Wilson processes each day’s file, turns the orders into shipments and assigns pickup times. It has scheduled more than 2,800 shipments this way. The point isn’t the file format. It’s that the order-to-pickup handoff happens every day without someone retyping the batch into emails.

For a detailed checklist of what an order should contain, see the order is ready. Does freight have what it needs?

How do quotes, approvals and booking work with approved carriers?

Quotes go only to carriers the company has approved, and the booking decision follows rules the company sets in advance: a target rate, an approval limit and the carriers allowed on each lane.

Quote request and follow-up

Wilson requests quotes from the company’s approved carriers by email, phone or API, and follows up with the ones that don’t reply. Replies are recorded in a consistent format, so rates and service terms can be compared side by side. Comparison should use the full expected cost, not only the base rate: a quote that leaves out a needed liftgate isn’t cheaper.

Negotiation and approval

Wilson negotiates quotes against the company’s targets and books the best option under the rules and approval limits the company sets. A company might allow automatic booking below a set amount above target, and require approval above it or on certain shipment types or customers. Actions under the rules proceed automatically; the rest wait for a person.

Booking with approved carriers only

Wilson only books carriers the company has approved, and it tenders the company’s own carriers first. Cartage can introduce carriers from its network, but they’re available to Wilson only after the company approves them. If a carrier declines the tender, Wilson moves to the next approved option. If no approved carrier accepts, Wilson escalates to the team.

Step What happens When a person decides
Quote request Quotes requested from approved carriers, with follow-up on silent ones If no approved carrier can serve the load
Comparison Full expected cost and service compared against the company’s rules When rules conflict, such as a lower price with a worse service record
Negotiation Quotes negotiated against the target rate If the best rate stays above the approval limit
Tender The selected carrier receives the load offer If the company requires approval before tendering
Next option A declined tender moves to the next approved carrier If no approved carrier accepts

Wilson does not maintain a standing carrier scorecard or recurring rate-benchmarking workflow by default, but it can use shipment and rate data from the loads it runs to produce performance or lane-rate reports on request. Over time, that history makes the next quote and the next carrier choice better informed.

What should booking and pickup confirmation look like?

A load is booked when the carrier has accepted it in writing, the rate confirmation is sent and the shipping documents are ready. The pickup is confirmed only when the carrier has agreed to the pickup window, and that window is reconfirmed before the truck is due.

Booking confirmation

Booking confirmation closes the commercial side of the load. Wilson records the carrier’s acceptance and generates the rate confirmation, the document that confirms the agreed price and terms. It also generates the bill of lading (BOL), packing slips and pallet labels. Without a rate confirmation, the team has no reliable way to check the invoice later.

Pickup confirmation

Pickup confirmation closes the operational side. For LTL and FTL shipments, Wilson schedules the pickup with the carrier, confirms the pickup window and reconfirms it before the pickup. That second check matters: plans change between booking and pickup, and a carrier that accepted on Monday may have reassigned the truck by Wednesday.

This is where the plastics and rubber manufacturer’s workflow ends each day. The order from the SAP batch file has a booked carrier and an assigned pickup time, and the shipping team knows when the truck is coming.

Wilson coordinates pickup and delivery times with carriers. It does not manage dock slots inside a warehouse or plant; dock scheduling is on Wilson’s roadmap. The facility’s receiving and shipping schedule stays with the team.

Carrier follow-up

Carrier follow-up keeps both confirmations honest. When a carrier hasn’t confirmed the window, hasn’t replied to a reconfirmation or hasn’t sent a status update, Wilson follows up through the configured channel and calls when needed. Teams set the frequency in their SOP, for example calling every hour until the load is picked up. Call transcripts are saved on the order. If the carrier still can’t confirm, Wilson escalates to the team.

See what a pickup confirmation should include and the carrier accepted the tender. Is the load actually booked?

What happens when the plan changes after booking?

When a carrier cancels, misses a pickup or runs late, the response should follow a fixed order: confirm with the carrier, tell the team, tell the customer if configured, and start rebooking from approved carriers if needed.

Detecting the change

Wilson tracks each load with the best source available: the carrier’s API, GPS or ELD data from the truck, or the carrier’s website by PRO number. When none of those exist, it emails or calls the carrier. If a load is running late, Wilson gets the new ETA and the reason for the delay, then tells the team and anyone else the company has set to be notified.

Responding in order

When a carrier cancels or misses a pickup, Wilson:

contacts the carrier,

notifies the team,

notifies the customer if configured,

initiates rebooking from the approved carrier list.

Rebooking runs automatically or waits for approval, depending on the company’s rules. A company might allow routine rebooking within a cost limit and route higher-cost or key customer loads to a person.

Keeping a record

Every message, confirmation and change on each shipment is recorded in a change history. When a load slips, the team can see what was tried, when and with whom, instead of reconstructing it from inboxes.

See the carrier confirmed the rate. Then missed the pickup.

Where does this fit: ERP, TMS and what stays with your team?

Wilson replaces the TMS for freight execution and connects to your ERP rather than requiring another TMS integration. It is the system of record for shipments and the layer that does the work, and teams can use its dashboard the way they would use a traditional TMS.

It also helps to be clear about what this workflow is not:

  • Not route optimization. Wilson doesn't plan routes or optimize a network. It executes the loads the company needs to move.
  • Not a visibility platform. Visibility shows where a load is. Wilson acts on what it finds: it contacts the carrier, updates people and starts rebooking when needed.
  • Not dock scheduling. Wilson coordinates pickup and delivery times with carriers. Managing dock slots inside a facility is on the roadmap.

What stays with your team is the judgment: which carriers are approved, the target rates and approval limits, decisions above those limits, and the customer and carrier relationships. Wilson starts with assisted execution, and the company expands what it handles automatically step by step as trust builds.

The test for fit is how much recurring coordination your team does every day, not company size. Look at one lane you ship every week. If quote requests, booking confirmations, pickup confirmations and carrier follow-up still run through one person's inbox, that lane is an execution problem.

Want to see that lane run end to end? Bring one recent order from your ERP and walk it from order to confirmed pickup with our team.

Sources