IceBossPro Blog — Ice Delivery Software

Setting Up a Product Catalog and SKUs in Ice Software

Every number in your ice business rolls up from one place: the product catalog. What a driver drops, what a customer is billed, what your inventory report shows, and what QuickBooks records all trace back to the SKUs you defined at setup. Get the catalog right and the rest of your ice delivery software runs on clean, consistent data. Get it sloppy — three different names for the same 20lb bag, prices that live in people's heads — and every downstream feature inherits the mess. Before you build recurring routes, and it pairs directly with Building Recurring Schedules in Ice Delivery Software, take the time to set the catalog up once and set it up well.

What a SKU is in an ice operation

A SKU is a single sellable product with its own code, name, and price. In ice delivery that usually starts with your bag sizes — a 7lb bag, a 20lb bag, maybe a 40lb commercial bag — and extends to block ice, dry ice, cubed versus crushed, and event pallets. In ice delivery software you create each of these as a distinct catalog entry with a unique SKU, a description, a unit of measure, and a base price. The 20lb bag is not "ice"; it is a specific item the system can count, price, and track independently from the 7lb bag. That separation is what makes accurate quantities and clean reporting possible.

Pricing lives in the catalog, not in memory

The most important thing the catalog does is hold your prices in one authoritative place. When you set the 20lb bag at its price in the catalog, every quote, every delivery line, and every invoice pulls that number automatically. Raise the price and it updates everywhere going forward — you are not editing a hundred customer records or reminding drivers of the new rate. Ice delivery software also supports customer-specific pricing on top of the base: a high-volume grocery account might get a negotiated per-bag rate while walk-up event customers pay list. You set that once against the customer, and the software applies the right price to the right account without anyone doing math on the truck.

SKUs drive inventory and stock tracking

Because each product is its own SKU, ice delivery software can track stock by item. The system knows how many 20lb bags rolled out of the freezer this morning, how many the route consumed, and how many remain. When quantities come off completed deliveries, inventory decrements automatically per SKU — no separate stock sheet. That gives you a real-time picture of how much of each product you have and how fast it moves, which tells you when to make more and prevents the two failures that hurt an ice operation most: running out on a hot day or overproducing and paying to store melt. A clean SKU list is the foundation of that visibility.

The catalog feeds every other feature

Once the catalog exists, everything else in your ice delivery software plugs into it. Standing orders reference SKUs and quantities. The driver's mobile app shows the catalog items at each stop so the delivered lines are chosen from a fixed list, not typed freehand. Invoices price themselves from catalog rates. Reporting breaks revenue down by product so you can see whether the 7lb retail bag or the 20lb commercial bag is really carrying the business. QuickBooks sync maps each SKU to an income account so your books stay organized by product. Every one of those features assumes a catalog that is complete and consistent — which is why setup deserves real attention.

Setting it up cleanly the first time

Start by listing every distinct thing you sell and giving each a short, unambiguous SKU code and a plain-English name a driver will recognize. Set the unit of measure — bag, block, pallet — and the base price. Group products sensibly if the software supports categories, so packaged ice, block ice, and dry ice report separately. Resist the urge to create near-duplicate entries; one 20lb bag SKU, used everywhere, beats three that fragment your inventory and confuse your reports. If you offer the same product in different contexts, use customer-specific pricing rather than cloning the SKU. A tight catalog of a dozen well-defined items will serve you far better than fifty overlapping ones.

Keeping the catalog current

A catalog is not set-and-forget forever, but changes should be deliberate. When your cost of production rises, update the base price in the catalog and it flows to every future delivery. When you add a new product — say you start offering crushed ice for restaurants — create the SKU once, set its price, and it is immediately available to schedules, drivers, and invoices. When you retire a product, deactivate the SKU so it stops appearing on new deliveries while your historical records keep it for accurate reporting. Because ice delivery software treats the catalog as the single source of truth, one clean edit propagates everywhere instead of leaving stale prices scattered across the system.

The foundation everything sits on

A product catalog is not glamorous, but it is load-bearing. Define your SKUs clearly, price them in one place, and let inventory, scheduling, billing, and reporting all draw from that single list. Do that, and your ice delivery software gives you numbers you can trust — accurate deliveries, correct invoices, real inventory counts, and reports that actually reflect the business. Skip it, and you spend the season fighting inconsistencies. An hour of careful catalog setup is one of the highest-return things you will do when standing up an ice operation on software.