IceBossPro Blog — Commercial Ice Delivery

Recurring Schedules in Commercial Ice Software

A standing order tells you what an account gets. A recurring schedule tells you when, and how often, forever. It is the clock that fires every delivery on your book without anyone winding it. In commercial ice delivery software the recurring schedule is the engine that turns a list of accounts into a route that appears on the board every single morning, correctly, whether or not the office remembered to build it. If standing orders are the backbone of an ice route, recurring schedules are the heartbeat.

How a recurring schedule is defined

A recurring schedule is a repeating pattern attached to an account: every Tuesday and Friday, every Monday-Wednesday-Saturday, every other Thursday, the first of each month. In IceBossPro you set the pattern once and the system generates the delivery instances forward in time automatically. A bar on a Tuesday/Friday schedule simply appears on both those route boards, week after week, with its standing quantity attached. Nobody re-enters it, nobody remembers it — the schedule remembers for them. The office's job shifts from creating deliveries to handling the exceptions.

Different accounts, different cadences

The trade is full of mismatched rhythms and the software has to hold all of them at once. A high-volume nightclub might need daily service in season. A neighborhood restaurant runs twice a week. A slow C-store is fine weekly. A seasonal marina goes dark all winter and daily in July. IceBossPro lets every account carry its own cadence, and the route planner merges them into a coherent daily run. The dispatcher does not think about frequencies at all; they open tomorrow's board and every account whose schedule fires tomorrow is already on it, sequenced and ready to load.

Seasonal patterns without a rebuild

Ice is a seasonal business, and recurring schedules have to flex with it or they fight you. An account that runs weekly in February needs three-times-a-week service by July. Rather than deleting and rebuilding schedules twice a year, IceBossPro lets you shift an account's cadence from a chosen date forward — bump it up for summer, ease it back for winter — while the delivery history stays intact. Across a whole book, that turns the seasonal ramp from a dreaded project into a routine adjustment you make account by account as demand climbs.

Skips, holidays, and one-off changes

Recurring does not mean rigid. A restaurant closes for a private renovation week. A bar is shut for a holiday. A store wants to skip the day after a slow stretch. The schedule has to accommodate a one-time skip without deleting the whole pattern. In IceBossPro you skip a single occurrence and the schedule keeps running on either side of it, so a Fourth-of-July closure does not require rebuilding the account's Tuesday/Friday pattern afterward. The same is true in reverse — you can insert an extra on-demand drop into a recurring account's week without disturbing the underlying schedule.

Schedules drive the route board

The payoff of recurring schedules is that the route builds itself. Every night the system rolls the next day's fired schedules onto the route board, and the planner sequences them into an efficient run. Because the deliveries are generated ahead of time, you can see committed volume days out, decide whether a heavy Saturday needs a second truck, and load each vehicle to the quantities the schedules already specified. The morning is calm because the work was defined the moment each account's schedule was set, not scrambled together at 6am.

Recurring schedules and multi-location accounts

Chains stack schedules. A twenty-store restaurant group might have twenty different cadences under one billing relationship, each store on the frequency its own traffic demands. IceBossPro carries a recurring schedule per location beneath the shared parent account, so the busy downtown store runs daily while the suburban location runs twice a week, and both roll up to one statement. The dispatcher services twenty independent rhythms; the customer sees one coordinated vendor. That separation of scheduling from billing is exactly what lets a small ice operation serve large accounts without drowning.

Where recurring schedules fit

Recurring schedules sit at the center of everything else the software does. They fire the standing orders, feed the route planner, drive the par-level restocks, and generate the invoices — all from one repeating pattern set once per account. Get the schedules right and the rest of the system runs on rails. We covered the quantity side of this in our piece on Par-Levels for Commercial Ice Accounts in Software, where the schedule sets the visit and the par sets the fill.

A route that builds itself every morning is not a fantasy — it is just recurring schedules doing the job you set them to do while you go run the business.