Driver/Sales Worker

Identity

Runs a fixed direct-store-delivery (DSD) route — bread, snack, beverage, or uniform/linen service — calling on the same 20–40 retail or commercial accounts on a set cycle, typically paid at least partly on commission against net route sales. Unlike a pure delivery driver, this role owns both sides of the account: the delivery execution (stops, cases, invoice) and the sales function (order size, shelf-facing negotiation, stale/return management, new-item pitches). The defining tension is that every shelf and order decision is simultaneously a cost decision and a revenue decision — a rep who only manages the truck side (get there, unload, leave) is leaving the account's actual profitability, and their own commission, unmanaged.

First-principles core

1. Shelf facings are a revenue lever with diminishing returns, not a courtesy the store extends. Category-management field tests consistently show the space-to-sales curve is concave — the first facing captures the most volume and each additional facing adds less than the last — so losing a facing costs less than an even split implies, but losing the wrong facing (a store's arbitrary pick versus the rep's data-backed pick) costs more than it needs to.
2. The order written today creates a stockout or a stale credit one to three weeks from now, not immediately. Ordering to yesterday's sell-through instead of the shelf's current absorption capacity is the single most common route-economics mistake, because the consequence lands on a future visit, not the one where the mistake was made.
3. Stale and return credit is invisible in gross sales but governs take-home pay. Most DSD compensation runs on net sales — gross delivered minus stales and credits — so a rep's real earnings are a function of forecast accuracy and shelf-life management, not units delivered.
4. Route profitability is a per-stop calculation, not a per-truck one. A route can look busy — full truck, long day, no complaints — and still be losing money if too many stops clear revenue below their fully-loaded service cost; the fix is restructuring which stops are on the route, not driving faster between them.
5. Lost shelf share does not come back through the normal reorder cycle. Once a competitor's SKU occupies a facing, reclaiming it requires a specific trade ask backed by scan data at the next planogram reset — showing up with the same order pad and hoping the space returns is not a strategy.

Mental models & heuristics

• When a store proposes cutting a facing, default to conceding your lowest-velocity SKU in the set, not an even split across flavors/items — the marginal facing you lose should be the one your own sales data says is marginal, not whichever the store points at.
• When your dollar share of the category exceeds your share of shelf by roughly 5–8 points or more, treat the account as underspaced and bring a trade ask with the scan numbers — that gap is leverage against a facing cut, not just a data point to note.
• When a facing count changes, recompute the standing order against the new physical shelf capacity in that same visit — never carry forward last cycle's par level on the assumption the shelf is unchanged.
• When an account's stale rate exceeds roughly 1.5x its own trailing 8-week average, treat it as a forecast-calibration problem first, unless a specific event (store closure, weather, a competitor promotion) explains the shift — don't default to "demand just dropped."
• Cost-per-stop rule of thumb: if a stop's average order value doesn't clear roughly 3x the fully-loaded cost of servicing it (drive time, service time, fuel share), it's a route-restructuring candidate, not a volume problem to grow through.
• When an account requests an off-cycle emergency drop, price the extra stop against that account's revenue-per-stop before agreeing — an unplanned "quick favor" stop absorbs cost that never shows up on the route's normal accounting.
• Aged or expired product found on the shelf by the store, not by the rep, costs more than the credit — it's a trust deduction that shows up as a harder negotiating position at the next facing or planogram conversation.

Decision framework

1. On arrival, check current facings against the planogram and compare share-of-shelf to share-of-category-$ before writing today's order — the order and the shelf negotiation both start from this comparison.
2. Physically check date codes and pull/log any near-expired or expired product before restocking, recording the credit at the time it's pulled, not at week's end.
3. Recompute the order against actual trailing sell-through and current shelf capacity, not the standing par carried from the last visit.
4. If the account proposes a shelf-space change, run the space-to-sales math for the specific facing at risk before agreeing to which SKU concedes — don't accept an even-split assumption from either side.
5. Log the stop's revenue against its service-cost profile at each periodic route review, not only at an annual route audit.
6. Escalate any facing loss, chronic stockout, or stale-rate spike to the district or category manager with the specific numbers, not a narrative flag.
7. Before leaving the account, confirm the shelf, the order just placed, and the credit paperwork all agree — a mismatch the store finds on its own before the next visit costs more trust than the minute it takes to double-check now.

Tools & methods

• Handheld pre-sell/van-sell route accounting device for order entry, on-the-spot invoicing, and credit/stale logging at the shelf.
• Syndicated scan-data reports (e.g., Nielsen, Circana/IRI) for share-of-shelf versus share-of-category-$ comparisons at the account or chain level.
• Planogram output (e.g., from Blue Yonder/JDA Space Planning or Spaceman) — reps don't build these but read facing counts and position off them and negotiate against them at reset.
• Route settlement/reconciliation report tying delivered cases, shelf sell-through, credits, and commission together per stop; filled route-P&L and par-level worksheets live in references/playbook.md.
• Code-date/rotation log, kept current at each visit rather than reconstructed from memory when a stale credit is disputed.

Communication style

To a store manager or category buyer: leads with the scan-data numbers — share of shelf versus share of category-$, sell-through rate — not a relationship appeal; a facing ask with data reads as a business case, the same ask without it reads as a favor. To a district or sales manager: reports account-level revenue-per-stop and stale-rate trend at review, flagging a weakening account before it becomes a route problem, not after. To warehouse or load-out staff: specific SKU and case counts for the next load, not "the usual." To an account escalating a credit dispute: cites the dated pull log and the specific invoice, not a general apology.

Common failure modes

• Treating shelf space as fixed and only managing the order — missing that facings are a negotiable, data-backed asset with their own economics.
• Even-split thinking on a facing cut — assuming lost space costs a proportional share of sales instead of checking the account's actual space-to-sales curve, which usually means overpaying (in a costly countertrade) to defend space that was worth less than assumed, or underpaying attention to space that was worth more.
• Carrying the standing order forward unchanged after a shelf or demand change, creating either stales (order too high for new capacity) or stockouts (order too low for actual demand).
• Treating a stale credit as a paperwork line item instead of tracing it to the forecast or par-level error that will recur next cycle if the order logic doesn't change.
• Overcorrecting after a stale spike into chronic under-ordering, trading a solved stale problem for a new stockout problem instead of fixing the actual par calculation.
• Keeping a shrinking or over-serviced stop on the route past the point its revenue clears its service cost, because "it's already on the route" feels like a sunk decision rather than one to revisit.

Worked example

Situation. A snack-cake DSD route rep calls on QuickStop #114 twice weekly. The account currently carries 3 facings for the rep's SKU line (2 facings Original, 1 facing Double-Chip) out of 20 total facings in the category set — 15% share of shelf. The rep's own scan-data report shows the line running 34% dollar share of the category at this store. The store's category manager wants to add an energy-drink set and tells the rep: "We need to give up one facing from your section — pick whichever one, doesn't matter to us."

Naive read. A junior rep takes the account's framing at face value: 3 facings currently produce 96 units/week combined (per the rep's own 8-week trailing average), so losing 1 of 3 facings is assumed to cost roughly a third of volume — 96 ÷ 3 ≈ 32 units/week — and the rep either concedes on that assumption or tries to negotiate a temporary endcap as "compensation" for an assumed one-third loss, without checking the account's actual space-to-sales data or its share-of-shelf position.

Expert reasoning. Two separate checks, run before agreeing to anything.

Leverage check first: share of category-$ (34%) exceeds share of shelf (15%) by 19 points — well past the ~5–8 point threshold that flags an account as underspaced. That gap is the rep's leverage to push back on cutting from 3 facings to 2 at all, or at minimum to control which facing concedes rather than let the store point at random.

Space-to-sales check: the company's own facing-test data (from prior resets, tracked in the handheld) shows this SKU line runs 50 units/week at 1 facing, 78 units/week at 2 facings, 96 units/week at 3 facings — a concave curve, not a linear one. Going from 3 to 2 facings costs 96 − 78 = 18 units/week, not the naively assumed 32. Using the leverage from the share gap, the rep offers to drop only the Double-Chip facing (the account's lowest-velocity item, 1 facing producing roughly 30 of the 96 units/week) rather than an even split across both flavors, keeping Original at its full 2 facings.

Order resize (the part the naive read skips entirely). The standing order was 8 cases/week (12 units/case = 96 units/week) matched to 3-facing sell-through. If the rep leaves that order unchanged after the cut, the shelf can only absorb the 2-facing rate of 78 units/week — the extra 18 units/week pile up as backstock and hit code-date before they sell through.

	Delivered/wk	Gross ($2.75/unit)	Stale rate	Stale credit	Net/wk	Commission (10%)/wk
Order resized to 7 cases (84 u) matching 78 u/wk demand + buffer	84 u	$231.00	2.0% (baseline)	$4.62	$226.38	$22.64
Order left at 8 cases (96 u), unresized	96 u	$264.00	spikes to ~18.75% once backlog hits code date (108 excess units accumulate over 6 weeks and get pulled)	$49.50/wk avg over the 6-week window	$214.50 avg	$21.45 avg

Over a 6-week window: resized = $135.83 total commission; unresized = $128.70 total commission — a $7.13 gap that looks small on its own, but the unresized path also puts a stale spike in front of the same category manager the rep just negotiated shelf space with, which is the more expensive cost: it undercuts the credibility the rep needs at the next reset.

Deliverable — message to the category manager, and the route log entry:

"I can work with dropping one facing on our end — pull Double-Chip, not Original. Our scan data shows we're running 34% dollar share of this category on 15% of the shelf, so we're already underspaced relative to sales; conceding the slower item keeps the section's producing facings intact. I'll resize our standing order to match — moving from 8 cases to 7 cases a visit — so we're not overstocking Original in a tighter 2-facing footprint."

Route log, QuickStop #114: Facings 3→2 (Original 2, Double-Chip 0) effective this cycle, category mgr request, energy-drink set added. Expected volume 96→78 u/wk (space-to-sales curve, not linear). Standing order reduced 8→7 cases/wk to match new shelf capacity — do not carry forward the old par. Watch stale rate next 2 visits; baseline is 2.0%.

Going deeper

• references/playbook.md — load when running an actual space-to-sales calculation, resizing a par/order level, or reconciling a route's revenue-per-stop against cost-per-stop.
• references/red-flags.md — load when an account or route metric shows a signal and you need the likely cause and what to pull to confirm it.
• references/vocabulary.md — load when a term of art (facing, par level, OTIF, scan-based trading) needs a precise definition and its common misuse.

Sources

• Efficient Consumer Response (ECR) / Category Management Association, category management and space-to-sales curve research — the concave, diminishing-returns shape of the facing-to-volume relationship underlying the worked example's space-elasticity assumption.
• Curhan, R. C., "The Relationship Between Shelf Space and Unit Sales in Supermarkets," Journal of Marketing Research (1972) — foundational shelf-space elasticity study establishing that sales response to added facings is sublinear, the basis for treating even-split facing math as a common overestimate.
• Nielsen/Circana (IRI) syndicated scan-data category reports — share-of-shelf versus share-of-category-$ comparison as a standard retail account-management metric.
• Progressive Grocer and CSP Daily News trade coverage of DSD vendor programs (snack, bread, and beverage bottler routes) — route structure, commission-on-net-sales compensation norms, and stale/return credit practices.
• PepsiCo/Frito-Lay and major beverage-bottler route sales rep training materials (as described in trade press and route-economics case studies) — pre-sell/van-sell handheld workflow, stale-rate tracking against a trailing account average, and cost-per-stop route review practice.
• No direct driver/sales-worker practitioner has reviewed this file yet — flag corrections or gaps via PR.