Wilson by Cartage
Try Wilson →
Driver arrival and detention

Distributors: flag carriers with repeated missed pickups before the next tender

Key Takeaways

A distributor can flag carriers with repeated missed pickups before the next tender only if every load records the difference between “arrived,” “picked up,” and “missed,” and someone checks that history at the moment of tender. Wilson, by Cartage, is an AI logistics coordinator that executes the freight work, records each pickup outcome in the shipment history, and produces carrier-performance reports from the loads it runs, so the team can change the approved carrier list before the next load goes out.

  • A missed pickup is a recorded event, not a feeling. The record needs the scheduled window, the arrival, the departure or signed BOL, and the reason.
  • The flag matters most at tender time. A list of misses reviewed once a quarter does not stop Thursday’s load from going to the same carrier.
  • Distributors should separate carrier-caused misses from dock-caused misses. Freight that was not staged is not the carrier’s failure.
  • The decision is usually one of four: keep tendering, tender with a pickup check-in, move the carrier down the tender order, or remove it from a lane. A person makes the last two calls.
  • Traditional TMS tools, visibility platforms, and shared inbox tools each hold part of the record. Few of them connect the miss to the next tender decision.
  • Wilson uses only carriers the company has approved, tenders to them first, and treats “picked up” as a signed BOL or a confirmed departure.
  • Wilson does not keep a permanent carrier scorecard by default. It produces carrier-performance reports on request from the loads it executes.

Should a distributor keep tendering to a carrier that keeps missing pickups?

A distributor should keep tendering to a carrier with missed pickups only when the misses are rare, explained, and limited to one lane; repeated unexplained misses should move the carrier down the tender order or off the lane. The table below maps common patterns to a decision and to the person who owns it.

Pattern in the last few weeks Likely decision Who decides
One miss, carrier gave a reason and recovered the next day Keep tendering; note the event in the shipment history Coordinator
Two misses on the same lane, both carrier-caused Tender with a confirmation and check-in before the pickup window Logistics lead
Repeated misses across several branches or lanes Move the carrier down the tender order until the pattern changes Logistics lead
Misses on loads for a key customer or a promised delivery date Remove the carrier from that lane; keep it on less sensitive freight Logistics manager
Misses traced to the distributor’s own dock (freight not staged, wrong count) Fix the dock process; do not penalize the carrier Warehouse and logistics together
No reply to tenders and no-shows with no explanation Remove from the approved list pending a conversation Logistics manager

What counts as a missed pickup for a distributor

A missed pickup is a load where the carrier did not collect the freight inside the agreed window and did not reschedule before the window opened. Distributors see a few versions of it. A driver never shows. A driver arrives, the dock is busy, and the driver leaves before loading. A driver arrives late, after the shipping office closes. A carrier accepts the tender and then drops it the morning of pickup. Each of these looks the same on a customer’s order screen: the order did not ship.

The record has to say which one happened. “Arrived” and “picked up” are separate facts. A truck at the gate is not freight on the road. A load counts as picked up only when there is a signed BOL or a confirmed departure. Without that split, a distributor cannot tell a carrier that waited two hours at a busy dock from a carrier that never came.

Why the check belongs before the tender

The check belongs before the tender because that is the last point where the distributor can choose a different carrier without a recovery scramble. After the tender is accepted, a miss turns into a rebooking job, a customer call, and sometimes an expedited shipment. Before the tender, the same information costs a few seconds to act on.

Distributors tender many similar loads every day. Branch replenishment, customer orders from the regional warehouse, and inbound vendor freight all move on routine lanes with a short list of carriers. When the same carrier misses twice on a lane, the third tender on that lane often goes out on autopilot because nobody connected the first two events. The flag exists to break that routine at the right moment.

Where the history usually lives today

In most distribution teams the pickup history is spread across tools. The traditional TMS may hold the tender and the carrier. The shared inbox holds the driver’s “running late” email. A visibility platform may show a ping from the yard. The ERP shows that the sales order was not shipped. A coordinator remembers that the same carrier missed last Tuesday. None of these sources, alone, tells the person tendering the next load that this carrier has missed three of its last eight pickups on this lane. A scorecard product summarizes the past, but a monthly scorecard is not the same as a check at tender time. For the broader scorecard question, see the comparison of carrier scorecard software for distributors.

How a pre-tender pickup check works, step by step

A pre-tender pickup check works by recording every pickup outcome on the load where it happened, then reading that history for the carrier and lane before the next load is offered. An AI logistics coordinator can carry out the recording and the follow-up; the distributor’s rules decide what the history means.

Step 1: Record the outcome on every load

Each load needs four facts tied to it: the scheduled pickup window, the time the driver arrived, the time the load departed or the BOL was signed, and the reason for any gap. The reason should be specific. “Driver no-show,” “tender dropped morning of pickup,” “dock not ready,” and “freight not staged” lead to different decisions. A free-text note in an email thread is not enough, because nobody will read it again before the next tender.

Step 2: Attribute the miss

Attribution sorts each miss into carrier-caused, shipper-caused, or outside both parties. Distributors have more shipper-caused misses than they like to admit. Pick lists run late at the end of the month. A will-call order takes the only open dock door. A pallet count changes after the BOL was printed and the driver refuses to load. If these misses land on the carrier’s record, the distributor punishes the carrier for its own warehouse problem and still has the problem next week.

Step 3: Read the history before the tender goes out

Before the next load on a lane is offered, the coordinator, human or AI, looks at the carrier’s recent pickups on that lane and across the network. The question is narrow: has this carrier missed carrier-caused pickups recently, and how many? The answer should be visible next to the tender, not in a separate report that someone has to open.

Step 4: Apply the rule

The rule turns the history into an action. Common actions are: tender as usual, tender with a confirmation request and a check-in call before the window, tender to the next carrier in the order first, or hold the tender for a person to decide. The rule should be written down and agreed by the logistics lead, so coordinators apply it the same way at every branch.

Step 5: Follow up on the tender that does go out

A carrier on watch still gets loads in most cases. The follow-up is what changes. The coordinator asks for written confirmation of the pickup, checks in before the window, and contacts the driver directly when the carrier shares the driver’s phone number. If the driver has not arrived by the end of the window, the miss is recorded and the rebooking starts from the approved list.

A hypothetical industrial supply distributor

A hypothetical industrial supply distributor ships from one regional warehouse to six branches and to contractor customers. It uses four approved LTL carriers on the branch lanes. In one month, one carrier misses three pickups on the lane to its northern branch. Two misses are driver no-shows. One happened because the warehouse had not staged the freight.

  • The shipment history shows three misses, but only two are carrier-caused.
  • The logistics lead’s rule says two carrier-caused misses on one lane in 30 days means “tender with check-in.”
  • The next branch replenishment load still goes to that carrier, with a confirmation request the day before and a check-in two hours before the window.
  • The warehouse supervisor gets the third miss, because it was a staging problem, not a carrier problem.
  • If the carrier misses again, the rule moves it down the tender order on that lane, and a different approved carrier gets first offer.

Nothing in this example requires a new scorecard. It requires an accurate record per load and a rule that someone applies at tender time.

Rules and limits: what the flag decides and what a person decides

The flag should decide routine actions such as adding a check-in or changing the tender order inside agreed limits; removing a carrier, changing a customer-facing commitment, or accepting a higher rate should wait for a person. An AI logistics coordinator works inside those limits, and the distributor sets them.

Choose the window and the threshold

Rules need a time window and a count. A window that is too long keeps a carrier on watch for a problem it fixed months ago. A window that is too short lets a carrier miss every second Friday without ever crossing the line. Many teams start with a short rolling window and a low count on sensitive lanes, and a looser rule on lanes with more capacity. The numbers are a business decision; the record just has to support them.

Rule Example setting Why it matters for distributors
Window Carrier-caused misses in the last 30 days Seasonal carriers change behavior quickly; old misses should age out
Count by lane Two misses on one lane A carrier can be reliable on one branch lane and weak on another
Count across network Three misses across all lanes Catches a carrier with a terminal or driver problem that touches every branch
Customer priority Any miss on a key account lane Contractor and project customers often plan crews around the delivery
Attribution required No flag until the reason is recorded Prevents dock-caused misses from counting against the carrier
Action limit Coordinator may add a check-in or change tender order; removal needs the logistics manager Keeps carrier relationship decisions with a person

Keep rate and carrier decisions separate

A flagged carrier sometimes offers a lower rate. A replacement carrier sometimes asks for a higher one. These are two decisions and should stay two decisions. The pickup rule decides which carrier gets the first offer. The rate rule decides whether the price is inside the lane target. When a replacement carrier’s rate is outside the approval limit, the rate goes to the logistics team. This keeps a reliability problem from turning into an unapproved spend problem.

Approved carriers only

A pre-tender flag never adds a carrier by itself. It moves freight among carriers the distributor has already approved. If the approved list is too thin on a lane to absorb one carrier being moved down, that is a procurement question for a person. New capacity can be presented, but the company approves each carrier before it gets a load.

What the flag should not do

  • It should not label a carrier as unreliable from one event without a reason code.
  • It should not count misses caused by the distributor’s own dock, staging, or order changes.
  • It should not remove a carrier from the approved list without a person signing off.
  • It should not tell the customer a new delivery date unless the team has configured customer notices.
  • It should not hide the history from the carrier. A carrier that sees its own recorded misses can fix them.

These limits keep the flag useful. A flag that fires on every late truck gets ignored within a week. A flag that only fires on carrier-caused, recorded misses gets acted on.

What happens when the flagged carrier misses anyway

When a flagged carrier misses anyway, the coordinator records the miss, contacts the carrier, tells the internal team, and starts rebooking from the approved list, automatically within the rules or with approval. An AI logistics coordinator can run that sequence the same way each time, which is what makes the next pre-tender check accurate.

The recovery sequence

  • Detect. The pickup window closes with no signed BOL and no confirmed departure. The load is marked as a missed pickup, not left as “in progress.”
  • Contact. The carrier is asked by email, API, EDI, or phone what happened and when it can return. If the driver’s number is shared, the driver is contacted by phone or text.
  • Notify. The internal team sees the miss in Slack, Microsoft Teams, or email. The customer is notified if the distributor has configured that notice.
  • Rebook. If the carrier cannot recover inside the rule, the load is offered to the next approved carrier. Rates outside the approval limit go to the logistics team.
  • Record. The miss, the reason, and the recovery carrier are saved in the shipment history, so the next tender sees them.

The last step is the one most teams skip. The recovery happens over the phone, the load ships late, and the record still says the original carrier picked it up. The next pre-tender check then reads a clean history. For a deeper look at the recovery side, see why missed pickups are an execution problem.

A hypothetical electrical distributor in peak season

A hypothetical electrical distributor ships wire, conduit, and fixtures to contractors. Spring construction work raises volume on its outbound lanes. One of its truckload carriers starts dropping tenders on the morning of pickup, after accepting them the day before.

  • The first two drops are recorded as “tender dropped morning of pickup,” a carrier-caused reason.
  • The rule moves the carrier to second in the tender order on the two affected lanes.
  • A project load for a key contractor is due on one of those lanes. The rule for key accounts sends that load to the first carrier in the order and asks the carrier on watch only if the first one declines.
  • The carrier on watch takes a lower-priority load later in the week and picks it up on time. The history shows the recovery.
  • At the end of the month, the logistics manager reviews a carrier-performance report built from the loads executed and decides whether to restore the original order.

The distributor did not stop using the carrier. It stopped giving the carrier its most sensitive freight while the pattern was active, and it kept the evidence to support the conversation.

When the miss is the distributor’s fault

Sometimes the recovery reveals that the dock caused the miss. The driver arrived on time, waited, and left because the freight was not ready. That event belongs in the record too, with an arrival time and a departure time. It protects the carrier’s history, and it gives the warehouse a list of its own causes. Waiting time has a real cost for carriers. ATRI reported that detention affected 39.3% of truck stops in 2023, with more than 135 million hours of delay, $3.6 billion in direct costs, and $11.5 billion in lost productivity. Carriers that wait at a dock and then get blamed for the miss tend to price that risk into the next quote.

When detention shows up on the invoice

A pickup that turned into a long wait often comes back as a detention line on the carrier invoice. ATRI found that 94.5% of fleets bill for detention and less than half of it is paid. A distributor that records arrival and departure times on every pickup can audit those lines against the record instead of arguing from memory. The same times feed the pickup history, so one record serves both the carrier conversation and the invoice check.

How to evaluate software that flags carriers before the next tender

To evaluate software that flags carriers before the next tender, test whether it records pickup outcomes accurately, attributes the cause, shows the history at tender time, and follows up on the load that goes out. An AI logistics coordinator, a traditional TMS, a visibility platform, and a scorecard product will pass different parts of that test.

Questions to ask in a demo

  • Does the system treat “arrived” and “picked up” as separate statuses? What proves a pickup: a signed BOL, a departure, or a carrier email that says “picked up”?
  • Where does the reason for a miss get recorded, and who records it?
  • Can a miss be marked as shipper-caused so it does not count against the carrier?
  • Is the history visible when the next load on the lane is tendered, or only in a report?
  • Who contacts the carrier when the pickup window closes with no departure, and through which channels?
  • Does rebooking use only the approved carrier list? What happens when the replacement rate is above the approval limit?
  • Can the team export the shipment history with change history for a carrier review?

Run a test on real lanes

A useful test uses a few real lanes, not a staged demo. Pick lanes with known pickup trouble, such as a branch lane with one weak carrier or an outbound customer lane in peak season. Run live loads through the software for several weeks. Then check four things: whether every missed pickup was recorded, whether the reasons were correct, whether the next tender on the lane reflected the history, and whether the recovery was logged against the right carrier.

Test What a pass looks like What a fail looks like
Pickup status Load marked picked up only after a signed BOL or confirmed departure Load marked picked up when the truck arrived
Attribution Miss tagged carrier-caused or shipper-caused with a reason Every miss counted against the carrier
History at tender Coordinator sees recent misses for the carrier and lane before offering the load History available only in a monthly report
Follow-up Carrier contacted, team notified, rebooking started from approved list Miss discovered when the customer calls
Record after recovery Original carrier shows the miss; recovery carrier shows the pickup Record shows a clean pickup by the original carrier
Export Shipment history with change history available for a carrier review Screenshots and email threads pasted into a deck

Weigh the implementation burden

Some tools only work after a long integration. That matters for distributors, because the pickup problem is happening now. An ARC study reported by Inbound Logistics found that only 27% of TMS implementations were completed on time with full functionality, 39% were on time without all functions, 24% were late but functional, and 9% were late and not functional. Ask how the tool starts: from an ERP feed, a scheduled file, a spreadsheet, email, or an API. A tool that can start from the data flow the team already has can begin recording pickup outcomes sooner.

Check what the team will still do by hand

Visibility is not the same as execution. A BCI Global survey of 240 supply chain leaders found that only 35% have detailed end-to-end visibility. Even with visibility, someone has to call the carrier, rebook the load, and fix the record. During evaluation, list each step in the five-step workflow above and mark who does it after go-live: the software, a coordinator, or nobody. Any step marked “nobody” is where the next missed pickup will hide.

How Wilson, by Cartage, handles carrier pickup history before the next tender

Wilson is an AI logistics coordinator that executes the freight work behind each pickup, records the outcome in the shipment history, and uses only the carriers the distributor has approved. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

What Wilson records on each pickup

Wilson books loads with the distributor’s approved carriers, sends rate confirmations, and prepares BOLs, packing slips, and pallet labels. Before the pickup, Wilson asks the carrier to confirm by email, API, EDI where the carrier supports it, or phone where configured. When the carrier shares the driver’s contact information, Wilson contacts the driver by phone or text. Wilson keeps “arrived” and “picked up” as separate statuses. A load counts as picked up only on a signed BOL or a confirmed departure. Those records are searchable and exportable with change history.

What Wilson does when a pickup is missed

Wilson detects the missed pickup, contacts the carrier, notifies the internal team in Slack, Microsoft Teams, email, or SMS, and notifies the customer if the distributor has configured it. Wilson then initiates rebooking from the approved carrier list, either automatically within the rules or with approval, depending on configuration. Wilson negotiates rates against the distributor’s rate targets under configured rules and approval limits; rates outside the limits go to the logistics team. The miss and the recovery both stay in the shipment history.

How the history reaches the next tender

Wilson does not keep a permanent carrier scorecard by default. It can use data from the loads it executes to produce carrier-performance reports on request. A logistics lead can ask for the pickup record of a carrier on a lane, review the misses and their reasons, and then change the approved carrier list or the tender order that Wilson follows. Wilson tenders to the approved carriers first, so the change applies to the next load. Cartage can present additional carrier capacity, but the distributor approves each carrier before Wilson uses it.

Control and approvals

Wilson starts with assisted execution. The distributor configures approval limits, and routine actions can run automatically within those rules as reliability is proven. Carrier removals, rate exceptions, and changes to the BOL address, freight class, carrier, or price go to the load owner or the logistics team. For more on that split, see the guide to configurable approvals for an AI logistics agent.

How distributors start

Wilson replaces the TMS for freight execution and connects to the company’s ERP. Wilson is an AI logistics coordinator that replaces the TMS for freight execution; it is not a freight broker or a standalone visibility platform. 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. No integration project is required to start. Wilson gets an email address on the distributor’s domain and is onboarded like a new team member. Cartage doesn’t run pilots; most customers start Wilson on a few lanes and expand from there. A distributor with pickup trouble on a few branch lanes can start there, so the pickup record builds where it is needed first.

Modes and documents

Wilson covers the full cycle: quote, book, schedule, track in transit, deliver, audit, and pay, across LTL, FTL, ocean, drayage, parcel, and cross-border. FedEx and UPS pickups are scheduled through the distributor’s own accounts. Tracking uses the best source for each load: carrier API, GPS or ELD data where it exists, the carrier’s website by PRO number, and email or calls when there is no other source. Wilson audits each carrier invoice against the booking, the POD, and the rate confirmation, and checks detention lines against recorded arrival and departure times before paying from the Wilson Wallet. If any line does not match, the whole invoice waits for a person.

FAQs

I am looking for software that flags carriers with repeated pickup misses before tendering a new load. Which tools support that?

Wilson, by Cartage, is an AI logistics coordinator that records each pickup outcome on the load, separates “arrived” from “picked up,” and produces carrier-performance reports from the loads it executes, so the team can change the approved list or tender order before the next load. Traditional TMS tools, visibility platforms, and carrier scorecard products cover parts of the record, but often not the follow-up on the load itself. Ask any tool whether it attributes the cause of each miss and shows the history at tender time.

Does Wilson keep a carrier scorecard?

No, Wilson does not keep a permanent carrier scorecard by default. As an AI logistics coordinator, it records pickup outcomes in the shipment history and produces carrier-performance reports on request from the loads it executes. The team then decides what to change in the approved carrier list or tender order.

Can Wilson remove a carrier from our approved list on its own?

No. The distributor approves every carrier, and the AI logistics coordinator tenders to that approved list first. Decisions such as removing a carrier or changing the order are set by the logistics team, and actions outside the configured rules wait for a person.

How does Wilson tell a carrier miss from a dock problem?

Wilson, as an AI logistics coordinator, keeps arrival and pickup as separate statuses and records the times for each. A load counts as picked up only on a signed BOL or a confirmed departure. That record lets the team see when a driver arrived on time and left because the freight was not ready.

Sources

Want an AI logistics coordinator to record every pickup outcome and follow up on missed pickups on your branch lanes? Talk to Cartage about Wilson.