← All postsDistribution

How to allocate stock when a shipment comes in short, without losing your best accounts

iotoms team · September 15, 2026 · 5 min read

A janitorial and paper supplies distributor ran eight routes out of a single warehouse, selling case-pack toilet tissue, trash liners, and cleaning chemicals to restaurants, hotels, and office buildings. Every account had a standing order pattern — the hotel chain took forty cases of tissue a week, the diner down the street took four. Both mattered. Neither had ever been told, in writing, which one mattered more when supply got tight.

Supply got tight in the third week of a paper shortage that hit the whole region. A vendor who normally shipped a full truck sent two-thirds of it. The warehouse manager found out at 7 a.m., an hour before the first van loaded, holding a purchase order for 400 cases and a delivery of 260.

The scramble that happens without a rule

With no allocation plan, what actually happened was whoever asked first, or shouted loudest, got served first. The office manager who called at 7:15 asking "did my order come in?" got her full case count. The hotel chain's purchasing contact, who didn't call until 9, found out at 9:15 that there wasn't enough left for her order — the same account that generated a fifth of the warehouse's weekly tissue revenue and had a signed fill-rate expectation in her contract.

By early afternoon the warehouse manager was on the phone apologizing to the hotel's regional buyer, offering a rush delivery for the following morning that cost more in freight than the shortfall was worth. The diner got its four cases. The route rep covering the hotel account came back from that stop having burned the trust it took eighteen months to build, because the shortage landed on the customer who could least afford to hear "we're out" and who had the most leverage to take the business elsewhere.

Nothing about that outcome was a supply problem. The supply problem — a vendor short-shipping — was outside anyone's control that morning. Who got served first was entirely inside the warehouse manager's control, and it went to whoever happened to call earliest, not to the account the business could least afford to lose.

Why "first come, first served" quietly costs the most

Distributors default to first-call, first-served because it feels fair in the moment — nobody's playing favorites, everyone's treated the same. But treating unequal accounts equally is its own kind of unfairness. A contract account with a fill-rate commitment and a small walk-in account with no commitment are not the same customer, and a shortage that lands on the wrong one turns a supplier's problem into a churn risk.

The compounding cost shows up over months, not that one morning. The hotel's regional buyer remembers being told "sorry, we're out" with no warning and no plan — and remembers it again next quarter when a competing distributor calls with a pitch. Meanwhile the diner, which would have accepted two cases and a promise of the rest on Thursday, never knew there was a shortage to be flexible about, because nobody asked.

The turning point: allocate before the shortfall, not during it

The fix the warehouse manager settled on wasn't a better phone script for the morning of a shortage — it was a rule decided in advance, before any specific shipment came up short, so nobody had to make a judgment call under pressure while three phones were ringing.

The rule had three parts:

  1. Rank accounts by protection tier, not by size alone — contract commitments and fill-rate obligations first, high-volume regulars second, everyone else after. Decide this on a calm Tuesday, not a short Thursday.
  2. Split the shipment against that ranking automatically, filling protected accounts to their standing order first and spreading whatever's left across the rest — rather than filling in call order.
  3. Flag the shortfall to affected accounts before they notice, with a real delivery date for the remainder, so a partial case count arrives with an explanation attached instead of arriving as a surprise.

None of that requires more inventory. It requires the shortfall to be visible — how many cases are actually on the truck versus what routes expect to load — early enough to run the allocation before vans leave the yard, and a record of which accounts are protected so that decision doesn't live in one manager's memory.

What changed on the next short shipment

Two months later a different vendor ran short on a liquid detergent SKU. The warehouse manager pulled up the same allocation rule, filled the hotel chain's order in full, split the remainder across four smaller accounts at 70% of their normal case count, and called each of those four before their route left — not to apologize, but to tell them what was coming and when the rest would arrive. Three of the four rearranged their week around it without complaint. The fourth asked for a small discount on the partial delivery, which cost far less than the freight had cost two months earlier.

Practical takeaway

  • Rank every account into a protection tier before a shortage hits — contract/fill-rate accounts first, volume regulars second, the rest last.
  • Compare what's actually arriving against what routes expect to load before vans leave the yard, not after a route rep calls in short.
  • Split shortfalls against the ranking, not against who called first.
  • Notify affected accounts proactively with a real date for the remainder — a warned customer tolerates a partial order; a surprised one remembers it.
  • Log the shortfall and the allocation decision against the vendor and the SKU, so a pattern of short shipments shows up before it becomes a habit.

iotoms keeps live inventory and standing order data in one place, so when a receipt comes in under the purchase order, the shortfall is visible against every route's expected load before vans are dispatched — and account tiering means the split follows a rule instead of a phone queue.

See your own routes running on iotoms

Book a demo