Sales keeps promising delivery dates logistics can't meet. What do we do?
Key Takeaways
- Sales overpromises when it doesn't have reliable delivery dates to quote. Fix the information first, then the behavior.
- Publish a transit-time reference by lane and mode, built from your own shipment history, so every promise starts from the same numbers.
- Set order cutoffs per site and mode. An order entered after the cutoff ships the next working day, and the promised date moves with it.
- Give sales the same shipment status logistics sees. Most "where's my order?" escalations disappear when sales can answer the question itself.
- Write rules for expedite requests: who can ask, who approves the cost and who pays. Then bring data, not complaints, to sales leadership.
- Wilson, by Cartage, is an AI logistics agent that books, tracks and handles exceptions on every load, so delays reach the team and, where configured, the customer while there is still time to act.
Why does sales keep promising dates logistics can't meet, and what should you do?
On Thursday afternoon, a sales rep at a hypothetical industrial supply distributor closes a large order and tells the customer it will arrive Monday. The order reaches the warehouse at 4:30 p.m., after the day's pickups have left. It's six pallets going 900 miles by LTL. The earliest realistic delivery is Wednesday. The logistics coordinator finds out when the customer calls on Monday asking where the truck is, and the rep asks logistics to "just expedite it." It's the third time this month.
When sales keeps promising dates logistics can't meet, the fix is to give sales reliable inputs and clear rules: a transit-time reference by lane and mode, order cutoffs by site, shared visibility into shipment status, and a written expedite process, then agree on them with sales leadership using your own delivery data. The problem is rarely bad intent. Sales is trying to win and keep customers. It promises what it believes is possible because nobody has given it a better number.
Why it keeps happening
Sales promises dates for understandable reasons. Customers ask for a date before they buy. Competitors may promise faster. Reps often don't know which warehouse will ship, what mode the order will move on, when the warehouse's last pickup is or how long LTL takes across a region. Without those inputs, a rep guesses. And because the cost of a missed promise falls on logistics and customer service, not on the rep's quota, the guesses tend to be optimistic.
What it costs
Missed promises cost in four ways. Expedited freight costs more than standard service, sometimes much more. Customer trust drops with each missed date. Logistics and customer service spend hours chasing and explaining. And for retail customers with delivery windows, a missed date can mean a deduction. If that applies to you, see how to avoid retailer chargebacks for late shipments.
Why blaming sales doesn't work
Logistics teams often respond by telling sales to stop promising dates. That rarely works, because the customer still asks. A better response is to make the right date easy to find, and to make the consequences of a wrong promise visible to everyone. That is a process change, and it needs both departments to agree.
How do you fix the process step by step?
Work in five steps: measure what's actually happening, build the transit-time reference, set order cutoffs, share shipment status, and write expedite rules. Then put it in front of sales leadership with the numbers.
Step 1: Measure promised versus actual
For the last three to six months, pull the promised delivery date (from the order, quote or customer PO) and the actual delivery date (from the POD) for each shipment. Group the misses by cause: order entered late, freight not ready, carrier late, transit longer than promised, or the promise was never achievable. This tells you how much of the problem is the promise and how much is execution. Be honest: some misses will be logistics' own.
An example of what the measurement shows
Consider a hypothetical distributor that reviews 600 shipments from the last quarter and finds about one in five delivered after the promised date. When the misses are sorted by cause, the picture changes. A large share were orders entered after the day's LTL pickup, which had no chance of shipping that day. Another group were promises shorter than the lane's typical transit, mostly on cross-country LTL. A smaller group were carrier delays and missed pickups, and a few were orders the warehouse didn't finish in time.
That breakdown matters. Only the carrier and warehouse misses are execution problems logistics can fix alone. The rest are promise problems that need cutoffs and a transit table. Showing both, side by side, is what makes the later conversation with sales productive instead of defensive.
Step 2: Build a transit-time reference
Turn your own shipment history into a table of realistic transit times by origin, destination region and mode (details below). Publish it where sales works: in the CRM, the ERP order screen or a shared page.
Step 3: Set order cutoffs
For each shipping site and mode, set the time of day after which an order won't ship that day. Publish it alongside the transit table.
Step 4: Share shipment status
Give sales and customer service access to the same shipment status logistics uses: booked, picked up, in transit, delayed, delivered, with the carrier and expected delivery date.
Step 5: Write the expedite rules
Define when an expedite is allowed, who approves it, who pays and how it's requested. Publish it with the other rules.
Step 6: Agree and review
Meet with sales leadership to agree on the rules, then review promise accuracy every month together. Adjust the transit table and cutoffs as the data changes.
How do you build transit-time references and order cutoffs sales can use?
Build the transit table from your own delivered shipments, not carrier marketing, and show a realistic range rather than the best case. Combine it with cutoffs so the rep can calculate a date in one step: order date, plus processing time, plus transit, adjusted for cutoffs, weekends and holidays.
Where the numbers come from
Use pickup and delivery dates from your own loads, by carrier and lane. Carrier transit maps are a starting point, but they show standard service under normal conditions. Your history shows what actually happens on your lanes, including terminal transfers and delivery appointments. If you don't have enough history on a lane, start with the carrier's published transit and adjust as loads move.
What the table should look like
Keep it simple enough that a rep can read it on a call:
| Origin | Destination region | Mode | Typical transit (business days) | Promise to customer |
|---|---|---|---|---|
| Plant A | Same state | LTL | 1 to 2 | 3 business days from ship |
| Plant A | Neighboring states | LTL | 2 to 3 | 4 business days from ship |
| Plant A | Cross-country | LTL | 4 to 6 | 7 business days from ship |
| Plant A | Any US destination | Full truckload | 1 to 5, by distance | Ask logistics for a quote |
| Plant A | Any US destination | Parcel ground | 1 to 5, by zone | Use the carrier's zone transit plus 1 day |
| Warehouse B | Canada | LTL cross-border | Varies with border clearance | Ask logistics |
These numbers are placeholders to show the structure. Fill in your own from your shipment history. The last column matters most: it's the date a rep can safely promise, with a buffer built in. Include a note that delivery appointments, liftgate deliveries, remote areas and holidays can add time.
Order cutoffs
An order cutoff is the latest time an order can be entered and still ship that day. It depends on how long the warehouse needs to pick and pack, and when carriers pick up. For example, if the LTL carrier picks up at 3 p.m. and the warehouse needs three hours for a typical order, the LTL cutoff is noon. Set separate cutoffs for parcel, LTL and truckload, because each has a different pickup time and lead time.
| Site | Mode | Carrier pickup time | Order cutoff | Notes |
|---|---|---|---|---|
| Plant A | Parcel | 4:00 p.m. | 1:00 p.m. | Single cartons only |
| Plant A | LTL | 3:00 p.m. | 11:00 a.m. | Up to 6 pallets |
| Plant A | Full truckload | Booked per load | 2 business days before ship | Needs carrier booking |
| Warehouse B | LTL | 2:00 p.m. | 10:00 a.m. | Appointment customers need 1 more day |
Orders entered after the cutoff ship the next working day, and the promise moves with them. Build the cutoff into the order entry screen if your ERP allows it, so the system suggests a ship date instead of leaving it to the rep.
Weekends, holidays and receiving hours
A promise date has to account for days nobody moves freight. Most LTL carriers don't pick up or deliver on weekends, and carrier holiday schedules can add a day or more around major holidays. Many customers receive only during set hours or by appointment, which can push a delivery to the next day even when the truck arrives on time. Count business days, not calendar days, publish the carrier holiday schedule with the transit table and note which key customers need appointments.
Processing time
Some orders need more than pick and pack: assembly, testing, custom packaging or a quality hold. Add processing days for those items to the ship date. If production makes the item to order, the promise starts from the production finish date, not the order date.
Keep it current
Review the transit table and cutoffs every quarter, and whenever a carrier, site or pickup schedule changes. Out-of-date numbers teach sales to ignore the table.
What rules should govern expedites and shared status?
Expedites need written rules on who can request them, what qualifies, who approves the cost and who pays, and sales needs the same status information logistics has so it can answer customers without escalating. Without rules, every promise becomes an expedite request and every expedite becomes an argument.
When an expedite makes sense
Expedited freight is a tool, not a failure. It makes sense when a customer's production line is down, when a key account has a real emergency, or when a contract requires a date. It doesn't make sense to cover a promise that was never achievable on standard service.
Rules to write down
- Who can request. Sales reps or customer service, through one channel (a form, a shared inbox or a Slack or Teams channel), never by calling the carrier directly.
- What the request must include. Order number, required delivery date, reason and the customer's willingness to pay.
- Who approves. Set approval by cost: logistics can approve expedites under a set amount; above it, the sales manager or a finance approver signs off.
- Who pays. Decide whether the customer pays, the sales budget pays or logistics absorbs it. Charging expedites to the sales budget changes promising behavior quickly.
- Response time. Logistics answers within a set time with options and prices: faster LTL service, a dedicated truck, a team driver or air.
Track the requests
Log every expedite: who asked, why, cost, whether the date was met and whether the original promise was achievable. Review the log with sales leadership monthly. When one rep or one customer accounts for most of the expedites, the conversation becomes specific.
Give sales the shipment status
Many escalations start because sales can't see where an order is. When a customer asks, the rep emails logistics, logistics checks the carrier and replies, and an hour is gone. Give sales read access to shipment status: booked carrier, pickup date, tracking status and expected delivery. Better, send customers proactive updates when a load is delayed, so the customer hears it before asking. For how that works, see how to automate customer updates when a shipment is delayed.
When the carrier is the problem
Some misses are on the carrier side: a missed pickup, a terminal delay or a late delivery. Those are logistics' responsibility to recover. A clear first-hour response to a missed pickup, with rebooking from approved carriers and a same-day update to sales, protects the promise more often than an expedite does. See what to do in the first hour after a missed pickup.
Tell sales about delays early
When a load is at risk, sales should know the same day, not when the customer calls. Decide which delays go to sales and at what point. For example, any delay that moves a key account's delivery by a day or more goes to the account owner. See when a freight delay should reach production or sales.
Decision rules for common situations
| Situation | Rule | Who decides |
|---|---|---|
| Customer asks for a date before ordering | Quote from the transit table and cutoffs | Sales rep |
| Customer needs it faster than the table allows | Request an expedite quote before promising | Sales rep, logistics |
| Order entered after cutoff | Ships next working day; update the promise | Sales rep |
| Load delayed in transit | Notify account owner and customer the same day | Logistics |
| Promise already missed | Offer options and costs; don't promise again without logistics | Sales, logistics |
| Repeated expedites for one customer | Review terms, stock levels or mode with the account owner | Sales manager, logistics |
Mistakes to avoid
- Publishing best-case transit times as standard
- Letting reps call carriers directly to "speed things up"
- Expediting without recording who asked and who pays
- Hiding logistics' own misses, which makes the data look biased
- Setting rules without sales leadership's agreement
How do you have the conversation with sales leadership?
Bring data on promised versus actual delivery, the cost of expedites and the causes of misses, propose specific rules, and ask sales leadership to co-own the result. The goal is a shared process, not a win for logistics.
Prepare the numbers
Before the meeting, prepare three things from your measurement:
- Promise accuracy. How many orders delivered on or before the promised date over the last few months, by rep or team, by mode and by region.
- Causes of misses. How many came from late order entry, unrealistic promises, freight not ready and carrier delays. Include logistics' own failures.
- Cost of misses. Expedite spend, extra customer service time and any customer deductions or credits.
Frame it as a customer problem
Sales leadership cares about customers, revenue and reps' time. Present missed dates as a customer retention risk and expedites as margin lost on sales' orders. Show the time reps spend chasing status that they could spend selling.
Propose, don't complain
Bring a draft of the transit table, cutoffs, status access and expedite rules. Ask sales leadership to change what doesn't work for their customers. A rule that sales helped write is more likely to be followed.
Agree on what each side commits to
| Logistics commits to | Sales commits to |
|---|---|
| A current transit table and cutoffs, reviewed quarterly | Quoting dates from the table, with the buffer |
| Same-day notice of delays on key accounts | Entering orders before cutoff when a date matters |
| Expedite quotes within an agreed response time | Requesting expedites through the agreed channel |
| Shared shipment status for every order | Checking status before escalating |
| Honest reporting of logistics' own misses | Reviewing promise accuracy monthly with logistics |
Handle the common objections
Expect pushback, and prepare answers:
- "Competitors promise faster." Ask whether they deliver on it. A reliable date often wins repeat business over a fast date that slips. If a competitor really is faster on a lane, look at a different mode, carrier or stocking location for that lane instead of promising what the current setup can't do.
- "The table is too conservative." Show the actual delivery data behind it. If the data supports a shorter promise on some lanes, shorten it.
- "Customers won't accept a later date." Then the order needs an expedite quote before the promise, and the customer or the sales budget decides whether it's worth the cost.
- "Logistics misses dates too." Agree, and show the carrier and warehouse misses alongside the promise misses. Each side fixes its own share.
Review together every month
Hold a short monthly review: promise accuracy, misses by cause, expedite spend and any rule changes. When reps see their own accuracy next to their peers', behavior tends to change without further discussion. If one side keeps breaking the agreement, the data makes that visible too. For how pickup confirmations feed into reliable dates, see the freight pickup guide.
How does Wilson, by Cartage, help logistics keep the promises sales makes?
Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays freight for manufacturers and distributors, so every order has a booked carrier, a tracked status and an exception response that starts as soon as something slips. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
For the gap between what sales promises and what logistics delivers, Wilson helps in several places:
- Fast quotes and booking. Wilson requests quotes from the company's approved carriers, compares them on total cost and negotiates toward the company's rate targets within approval limits. That includes faster service options when an expedite is requested. Rates outside approval limits go to the logistics team, which keeps expedite approval with the people the company names.
- Pickup scheduling. Wilson books with written acceptance and a rate confirmation and schedules the pickup, so the ship date behind the promise is confirmed with the carrier.
- Tracking. Wilson tracks each load with the best source available: a carrier API or EDI, GPS or ELD data where the carrier shares it, the carrier's website by PRO number, or email or phone calls when nothing else is current.
- Exceptions. When a pickup is missed, a carrier cancels or a load is delayed, Wilson contacts the carrier, tells the team in Slack, Microsoft Teams or email, tells the customer by email or SMS if configured, and starts rebooking from the approved carrier list automatically within the rules or after approval. Sales and customer service can be included in those updates, so they hear about the delay the same day.
- Records and reports. Every message, confirmation and change is kept in the shipment's change history. Wilson can produce carrier-performance and lane-rate reports on request from the loads it runs, which helps when updating the transit table.
Wilson books only carriers the company has approved and covers LTL, FTL, ocean, drayage, parcel and cross-border freight. It also generates bills of lading, packing slips and pallet labels, files PODs, audits each carrier invoice against the rate confirmation and POD, and pays carriers from the Wilson Wallet, with payments above the approval limits or outside the rules waiting for a person.
Wilson replaces the TMS for freight execution and connects to the company's 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. Teams start with assisted execution, set their own approval limits and let routine actions run automatically within those rules as the workflow is proven.
Pricing
Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract. Timing depends on scope: most teams start on a few lanes and expand from there.
FAQs
Sales keeps promising delivery dates logistics can't meet. What do we do?
Give sales reliable inputs and clear rules: a transit-time reference by lane and mode from your own history, order cutoffs per site, shared shipment status and written expedite rules. Then agree on them with sales leadership using data on promised versus actual delivery. Wilson, by Cartage, an AI logistics agent, books and tracks each load and sends delay updates to the team and, where configured, the customer.
How do I build a transit-time table for sales?
Use pickup and delivery dates from your own delivered shipments, grouped by origin, destination region and mode. Show a realistic range and a safe promise date with a buffer, and review it quarterly.
What is an order cutoff time?
It is the latest time an order can be entered and still ship that day. It depends on warehouse processing time and the carrier's pickup time, and it usually differs by site and mode.
Who should pay for expedited freight?
Decide it in writing. Common options are the customer, the sales budget or logistics. Charging expedites caused by unrealistic promises to the sales budget tends to change promising behavior.
Should sales reps be allowed to contact carriers directly?
Generally no. Expedite and change requests should go through logistics, so the booked carrier gets one consistent message and the cost is approved.
How can sales see shipment status without asking logistics?
Give sales read access to the shipment status logistics uses, including carrier, pickup date, tracking status and expected delivery. Proactive delay updates to customers reduce the questions further.
How do I show sales leadership the cost of missed promises?
Measure promised versus actual delivery dates, group misses by cause and add up expedite spend, customer credits and deductions. Include logistics' own misses so the data is trusted.
Why are carrier transit times different from what we see?
Published transit times describe standard service under normal conditions. Your actual results include terminal transfers, delivery appointments, accessorial deliveries and the specific lanes you ship, so your own history is the better guide.
How often should transit times and cutoffs be updated?
Review them quarterly and whenever a carrier, site, pickup schedule or mode changes. Outdated numbers teach sales to ignore the table.
Should promised delivery dates include a buffer?
Yes. Quote a date that covers the typical transit plus a margin for weekends, appointments and normal variation. Customers usually prefer a reliable date to a fast one that slips, and early delivery is rarely a complaint unless the customer has a delivery window.
What should happen when a delivery promise is already missed?
Tell the customer and the account owner the same day, offer options with costs and don't make a new promise without checking with logistics first.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai