IceBossPro Blog — Ice Delivery Routing

Per-Stop Delivery Quantities in Route Software

On an ice route, the number that matters most is not the address — it is the quantity. How many 7lb bags, how many 20lb bags, how many blocks went into this freezer today. That per-stop delivery quantity is what fills the account, what depletes the truck, and what becomes the invoice. Get it captured cleanly at every stop and the whole operation runs on real data; leave it to paper tickets and memory and you bleed money in unbilled and misbilled drops. Capturing quantity accurately at each stop is one of the core reasons to run ice delivery route software instead of a clipboard.

Quantity is a per-SKU number, not a checkbox

A generic delivery app records a stop as done or not done. An ice route needs more than that, because a single stop usually involves multiple products — a case of 7lb bags for the front merchandiser, some 20lb bags for the back cooler, maybe block ice for a bar. The software carries your product catalog as distinct SKUs, and at each stop the driver enters the delivered quantity per SKU. That breakdown is what makes everything downstream work: accurate billing at the right price per product, truck inventory that actually decrements, and reporting that shows which products move where. “Delivered” is not enough on an ice route; “delivered 40 seven-pound and 12 twenty-pound” is.

Two kinds of quantity: standing orders and par restocks

Per-stop quantities come in two flavors, and good ice route software handles both. A standing order is a fixed quantity the account takes every visit — a restaurant that always wants 20 bags, no more, no less. A par restock is a variable quantity computed to bring a freezer back to its target level, so the drop changes with demand. The right tool lets you set each account's default behavior: a fixed standing quantity, or a top-to-par delivery derived from the freezer's par-level. The driver sees the suggested number either way and confirms it at the stop.

The par-restock side of that equation is worth understanding on its own, and we covered it in depth in Par-Level Restocks on Ice Delivery Routes — how the target level and burn rate combine to compute the drop. Per-stop quantities are where that computed number meets reality and gets recorded as what actually left the truck.

Suggested versus actual — and why the difference matters

The route plan suggests a quantity for every stop, but the plan is not always right. A cooler might be fuller than expected because the account had a slow week, or emptier because a heat wave cleaned it out. The driver has to be able to override the suggestion on-site — and critically, it is the actual delivered quantity, not the suggested one, that the software captures and bills. This distinction is where paper routes quietly lose money: the office bills the standing number while the driver actually dropped less, or the driver drops extra and never notes it. In route software, the recorded actual is the single source of truth for both the account's fill and the invoice.

Capturing quantity at the freezer

The capture happens in the crew app, at the stop, in seconds. The driver opens the account, sees the suggested per-SKU quantities, adjusts any that are off, and marks the stop complete. That action time-stamps the delivery, attaches it to the account, and pairs it with proof of delivery — a photo of the filled freezer and, where needed, a signature. There is no end-of-day ritual of transcribing tickets, no soaked paper, no “I think it was about 30.” The quantity is recorded once, correctly, by the person who actually made the drop, at the moment they made it.

Quantities drive truck inventory

Every per-stop quantity does double duty: it fills the account and it depletes the truck. As drops are recorded through the day, the software decrements the truck's load by SKU, so the office can see how much product is left and whether a route can finish or needs a reload. Match the starting load against the day's recorded deliveries and you also see shrink — the melt and loss between what went on the truck and what got delivered. On a product that literally disappears if it sits too long, knowing your real per-truck burn is how you stop guessing at how much to load each morning.

From quantity to invoice, automatically

The reason per-stop quantity capture matters more on an ice route than almost any other delivery business is billing. The delivered quantity is the invoice. Because the software captures actual quantities by SKU at each stop, it can generate the invoice the moment the driver marks the stop complete — per-delivery billing for cash accounts, a rolled-up monthly statement for recurring ones, or consignment where the customer pays only for what sold. Card-on-file charges recurring accounts automatically, and the numbers reconcile against the delivery record instead of a stack of tickets. Every drop that goes out the door gets billed, at the right price, for the right quantity.

The compounding payoff

Clean per-stop quantities are the data layer the whole operation stands on. They feed accurate invoices, honest truck inventory, real burn-rate history for tuning par-levels, and profitability reporting that tells you which stops earn their place on the route. Capture them loosely and every one of those outputs is garbage; capture them tightly in ice delivery route software and the route runs on facts. It is the kind of unglamorous discipline that only matters if you have actually run an ice route and watched an untracked drop turn into an unpaid one — which is exactly who this software was built by.