IceBossPro Blog — Ice Delivery Scheduling

Auto-Scheduling Ice Deliveries by Par-Level

The best delivery schedule is the one you barely have to think about — where the freezer itself decides when the truck comes back. That is what par-driven auto-scheduling does: instead of you guessing how often to visit an account, the software watches each freezer's draw-down and generates a delivery when it nears the par level you set. It is the smartest lever inside modern ice delivery scheduling software, and once it is dialed in, a big chunk of your schedule builds itself. This post walks through how par-driven scheduling actually works and how to set it up so it earns its keep.

What a par level really is

A par level is the amount of ice you want present in an account's freezer or merchandiser after a restock — the “full” number. A c-store merchandiser might hold 40 bags, and you set a par of 40. Below the par sits a trigger point: the level at which the account needs to be back on the schedule. When the projected on-hand quantity crosses that trigger, the software knows a delivery is due. Par levels turn a vague sense of “they're probably getting low” into a hard number the schedule can act on, which is what makes automation possible in the first place.

How the software knows a freezer is running low

Par-driven scheduling works because every completed delivery feeds the system data. Each time a driver restocks an account and logs the quantity dropped, IceBossPro records the burn since the last visit. Over a few cycles that history becomes a burn rate — bags per day for that specific freezer. From the last known fill and the burn rate, the software projects the current on-hand level forward day by day. When the projection reaches the trigger point, it generates a scheduled delivery for that account. No one has to notice the freezer is low; the math already did.

Fixed schedules versus par-driven schedules

A fixed standing order fires on set weekdays no matter what — every Monday and Thursday, full stop. That is perfect for steady, predictable accounts. But plenty of accounts are lumpy: slow most weeks, then slammed during a local event or a hot stretch. A fixed schedule either over-serves them (melt and wasted stops) or under-serves them (dry freezers). Par-driven scheduling adapts. The delivery lands when the freezer actually needs it, tightening up during a rush and stretching out when demand cools. Most operators run a blend — fixed standing orders on the rock-steady accounts, par-driven auto-scheduling on the variable ones.

Setting it up right

Auto-scheduling is only as good as the numbers behind it. For each par-driven account you set the freezer capacity, the par level, and the trigger point — how low it can get before a delivery is generated. The trigger has to leave enough lead time for the account to land on a real route day before the freezer hits empty. Set the trigger too low and you are always cutting it close; set it too high and you are visiting a still-mostly-full cooler. IceBossPro seeds reasonable defaults from capacity, then the burn-rate history tunes them as real deliveries pile up. After a month of data, the triggers reflect how each freezer truly behaves.

Auto-generated deliveries still land on route days

A common worry is that par-driven scheduling will scatter one-off stops all over the map. It does not. When the software determines an account is due, it places the generated delivery on the next appropriate route day for that account's area, so it slots into an existing route instead of sending a truck out of its way. The freezer sets the timing; the routing logic keeps it efficient. You get demand-driven frequency without demand-driven chaos.

Where par-driven scheduling pays off most

The accounts that benefit most are the ones a human scheduler gets wrong. Seasonal venues, event-driven concessions, and any freezer whose demand swings week to week are exactly where a fixed cadence leaks money in both directions. Par-driven auto-scheduling catches the swings automatically — it pulls the next visit forward heading into a busy stretch and pushes it back when things go quiet. That means fewer dry freezers during a rush and fewer half-wasted stops in the slow weeks, without anyone babysitting the calendar.

Let it run, then trust the data

The hard part of par-driven scheduling is resisting the urge to override it before it has data. Give the system a few delivery cycles to learn each freezer's real burn, keep the drop quantities accurate at the truck, and the auto-generated schedule gets sharper every week. Pair it with a raised base frequency for the summer peak, and you have a schedule that both anticipates the season and reacts to each freezer in real time — the closest thing to a route that runs itself.

For more, see Ramping Ice Delivery Schedules for Summer.