Missed Orders: The Leak Nobody Counts

Most branches track on-time orders. Almost none track missed orders — the ones that fell through before anyone logged them. A customer calls, the item isn't in stock, the counter person says "I'll call you back," and nobody does. That order doesn't show up in any report.

Internal data from trade supply operations shows that unlogged missed orders run 3–5% of will-call volume in a typical branch. At a branch doing $1.2M in annual revenue, that's $36K–$60K in orders that walked out the door and never came back through the door they entered.

Compounding the problem: the customer who got ghosted doesn't call to complain. They just stop calling. You find out three months later when they're buying from your competitor and your counter staff says "they must have switched distributors."

Fixes that actually work:

  • Log every will-call that can't be filled at the promised time. Not "did we ship it?" — "did we even take the call?" A simple paper ticket or counter log that captures the attempt is enough. No software required.
  • Weekly review of the unlogged miss log. The branch manager looks at it once a week and makes one phone call per miss. Personal recovery rate on these runs 40–60%.
  • Stock-then-cancel logic for long-tail SKUs. If a counter person can enter the order and flag it "await stock," it shows up in the overnight pull list instead of vanishing.

Benchmark: branches running a miss log recover 15–25% of lost orders within 4 weeks. Year one recovery on a $1.2M branch: $5K–$12K.

Overtime: The Margin Eater Hiding in Plain Sight

Overtime is the most visible and least addressed leak in supply branch operations. Everyone knows it's a problem. Most branches have done "something about OT" at least once — usually a stern conversation that lasts about three weeks before the schedule reverts.

The reason it doesn't stick: overtime isn't a scheduling problem. It's a dispatch and order-management problem. The hours get burned because of how work flows into the branch, not because of who's on the clock.

Common root causes:

  • Late truck arrivals collapsing the evening pull. If the inbound freight gets delayed and the pull list runs at 4pm instead of 1pm, you're running overtime to make the window. The fix is a morning truck cutoff with branch accountability and a carrier SLA tracker.
  • Batch-and-spray dispatch chaos. When the driver gets twelve calls between 3pm and 5pm, every one of them gets an ETA of "within the hour." That's twelve customer promises that require twelve runs in the last 90 minutes of the shift. Sequence and stagger dispatch — 20-minute windows per customer instead of "I'll be there soon" — cut this by 30–40%.
  • Counter orders placed after the pull is done. A customer walks in at 4:45pm and asks for 200 feet of pipe that isn't on the pick list. Counter enters it, warehouse has to re-open the pick. Fix: cutoff the counter entry window 90 minutes before close. Orders entered after cutoff go to tomorrow's list. Counter staff resist this for two weeks, then stop noticing.

Benchmark: branches with overtime above 25 hours/week typically run 38–45 hours after a dispatch SOP is implemented. At $35/hour loaded cost, that's $455–$700/week recovered. $23K–$36K/year.

Inventory Accuracy: The Silent Stock-Out Driver

A shelf that says you have 12 of something and actually has 3 is a stock-out waiting to happen. More importantly, it's a reorder that's running blind — you're buying what the system says you need, not what you actually need.

The typical trade supply branch runs 72–81% inventory accuracy on cycle counts. That means roughly 1 in 5 items is miscounted. In a 4,000-SKU branch, that's roughly 800 items with bad data driving reorder decisions.

The leak isn't the stock-out itself — it's the replenishment cycle that over-buys fast movers (because fast movers are also the items most frequently miscounted) while under-buying slow movers that are actually in stock but flagged as zero.

What "fixing inventory accuracy" actually means in the field:

  • One fast-moving SKU class at a time. Don't try to cycle count everything. Pick the top 20 SKUs by order frequency and get those to 95%+ accuracy first. That alone moves the needle on 30–40% of counter orders.
  • Same-person cycle counts. Whoever pulls the order does the count check. Accountability on the same person reduces variance significantly vs. rotating the task.
  • Write the count in the bin, not just in the system. Physical location plus system count. When they don't match, system wins for ordering, physical wins for what's actually available to sell.
  • Dead stock audit every quarter. Items with zero movement in 90 days should trigger a physical count and a disposition decision, not sit in the bin being counted incorrectly forever.

Benchmark: a branch running 72% accuracy that gets to 88% typically frees $15K–$30K in working capital from over-ordered stock and reduces stock-out revenue loss by 20–30%.

Branch Health Scorecard
Quantify your own leaks in 4 minutes.
10 questions across 4 pillars. Written leak report with dollar estimates in your inbox within 24 hours. No sales call — just data.
→ Take the Branch Health Scorecard

Dead Accounts: The Revenue Sitting in Your CRM With Zero Activity

Every supply branch has them. Accounts that ordered regularly six months ago and have gone quiet. The counter staff know who they are. Nobody's called them.

Dead accounts are the lowest-cost revenue recovery in the branch. The relationship exists. The delivery route exists. The counter person has a relationship. What's missing is the follow-up.

Why dead accounts stay dead:

  • No systematic reactivation cadence. Reactive follow-up ("we haven't seen you in a while") feels awkward and gets dropped. A structured list with a script and a three-touch sequence changes the dynamic.
  • Attribution confusion. If the account went silent because of a competitor offer, a job completion, or a personnel change — nobody knows why and nobody has time to find out. The script needs to handle all three.
  • No "account health" trigger. Branches don't have a flag that says "this account hasn't ordered in 60 days" — it just falls off the radar until the counter person notices.

Reactivation sequence that works:

  • Day 1 (account goes 45 days silent): Personal call from counter — not a form letter. Script: "Hey [name], it's [your name] at [branch]. I noticed we haven't seen your orders come through in a while. Everything OK over there? I wanted to make sure we weren't missing something on our end."
  • Day 5 (no response): Text or email with a specific offer: "We just restocked [top SKUs for that customer]. Happy to set aside a few items if you're picking up this week."
  • Day 12 (no response): Last touch — "Wanted to make sure you still have our pricing on file. Let me know if anything's changed on your end."

Benchmark: accounts reactivated within 60 days of going silent have a 60–70% 90-day retention rate. Accounts that go 120+ days silent have a 20–30% reactivation rate. The window matters. A branch with 50 dead accounts that reactivates 10 at $800/month average order value: $96K/year recovered.

The 60-Day Fix Sequence

None of these leaks fix themselves. But they all follow the same pattern: once you measure it, the fix becomes obvious to the people doing the work. Here's how to sequence it over 60 days without overwhelming the branch.

Days 1–14: Quantify the leaks. Don't fix anything yet. Count the missed orders (put a log on the counter for one week). Pull the overtime sheets and identify which hours aren't attached to a scheduled reason. Run a cycle count on the top 20 SKUs. Pull the dead account list from your POS — everyone with $0 orders in the last 60 days. You can't argue with numbers you collected yourself.

Days 15–30: Fix the highest-value leak. Pick the one with the clearest ROI for your branch. Usually that's overtime or dead accounts — they have the most immediate cash impact. Implement the counter-side process first (the log, the cutoff, the call script). Get the branch manager buying in by showing them the numbers before and after week one.

Days 31–45: Reinforce and expand. Second leak gets the same treatment. First leak gets reviewed — what's slipping? Who needs coaching? This is where most branches give up: they fixed something for two weeks, it slipped back, and they decided it didn't work. It didn't work because nobody owned it. Assign ownership.

Days 46–60: Build the tracking cadence. The processes exist. Now make them automatic. Weekly review meeting. Monthly metrics snapshot. Dead account flag in the CRM (even if it's a spreadsheet). The branch should be able to run itself by day 60 — not perfectly, but independently.

None of this requires new software. It requires someone willing to count the problem, assign the fix, and follow up. That's what we do in the first 14 days of a BranchOps engagement — quantify the leaks, rank them by monthly impact, and build the 90-day fix plan with the branch team. If you want to see where your branch is leaking, take the 4-minute Branch Health Scorecard — we'll quantify your top leaks and email you a written report within 24 hours.