IceBossPro Blog — Packaged Ice Delivery

Setting Bag Par-Levels in Packaged Ice Software

A par-level is the single number that quietly runs a packaged ice route. Set it right and a merchandiser is always full when a customer reaches in, without wasting bags that just melt. Set it wrong and you either run dry on the busy days or drown a slow freezer in product. This post is a practical guide to setting and tuning bag par-levels inside packaged ice delivery software, and to using the data the platform collects to keep those numbers honest as demand shifts.

What a par-level actually means

The par-level is the amount of a given SKU you want present in a freezer immediately after a restock. It is not the capacity and it is not the reorder point — it is the target the driver fills up to on each visit. On a par-driven route the drop quantity is never fixed; it is the par minus whatever is still on hand. That is why the number matters so much: it directly sets how many bags leave the truck at every stop. Packaged ice delivery software stores a par per SKU per merchandiser, so a single account can have a high 7lb par and a modest 20lb par side by side.

Starting from capacity and cadence

A good first par comes from two facts you already know: how many bags the freezer holds and how often you visit it. If a merchandiser holds fifty 7lb bags, you service it twice a week, and it sells roughly thirty bags between visits, your par should sit high enough to cover that thirty-bag burn plus a safety cushion for a hot day — without exceeding the physical capacity. The software lets you enter that starting par per SKU, and from there you have a baseline to refine rather than a wild guess. Setting it against capacity also prevents the impossible pars that create phantom restock quantities.

Letting the data tune the number

The first par is an estimate; the good pars come from history. Every visit, the app records the on-hand count on arrival and the quantity dropped, which means the platform can see the real burn rate between visits for each SKU in each freezer. If an account keeps arriving nearly empty, the par is too low and you are risking sold-out weekends. If it keeps arriving nearly full, the par is too high and bags are melting on the shelf. Packaged ice delivery software surfaces these patterns so you adjust pars from measured demand instead of hunches, freezer by freezer.

Seasonal par adjustments

Bagged ice is brutally seasonal, and a par that is perfect in April is far too low in July. Rather than rebuild the route every few weeks, you raise pars going into summer and lower them heading into fall. Because pars drive the restock quantities automatically, bumping a par is all it takes to make the driver start topping up to a bigger number — no need to re-key every stop. Some operators keep separate summer and off-season pars so the swing is a single toggle rather than a manual pass through every account.

Par-levels and the driver's day

On the truck, pars turn the route sheet into a plan. Each stop shows the target per SKU, the driver enters what is on hand, and the app suggests the restock quantity. The driver retains judgment — if a freezer is unusually full because a holiday killed foot traffic, they drop less and the actual number is recorded — but the default is the calculated top-up. This keeps a new or filling-in driver stocking the route the same way the regular would, because the pars carry the knowledge that used to live only in one person's head.

Pars, load planning, and shrink

Pars do not just govern individual stops; they let you plan the whole load. Sum the expected restock quantities across a route and you know roughly how many 7lb and 20lb bags to load before the truck leaves, which cuts both running short and hauling excess ice that melts. And because the software compares par-driven expectations against actual drops and returns, over-set pars show up as elevated melt on the shrink report — a direct signal to bring specific numbers down.

Reviewing pars on a schedule

Pars are not set-and-forget. The best operators review them on a cadence — monthly in the shoulder seasons, more often as summer ramps — using the par-versus-actual data the platform keeps. A short review catches the freezer that outgrew its par, the account that slowed down, and the new location whose demand has finally settled. Treating par-levels as living numbers is what keeps a route both full and lean at the same time.

For a related look at the freezers these pars are attached to, see Tracking Ice Merchandisers in Packaged Ice Software