IceBossPro Blog — Packaged Ice Delivery

Per-Bag Invoicing in Packaged Ice Software

Ask an ice operator where they lose the most money and a lot of them will point at the truck, or fuel, or the freezer that keeps failing. The real leak is usually quieter: the gap between what got delivered and what got billed. A driver drops eighteen bags but the office invoices for the standing twenty, or drops twenty-five on a busy Friday and only bills twenty because nobody told the office it ran heavy. Multiply a two- or three-bag error across a hundred stops a day and you're giving away a truck's worth of product a month without ever seeing it leave. Per-bag invoicing exists to seal that gap, and it's the billing model that packaged ice delivery software should be built around.

The delivered quantity is the invoice

Per-bag invoicing means one thing: you bill for the exact number of bags that came off the truck, priced per SKU. In IceBossPro the driver records the delivered count at each stop — so many 7lb bags, so many 20lb bags, however many blocks — and that count is the invoice. Not the standing order, not last week's number, not a guess reconstructed at the office three days later. The document that bills the customer is generated from the same number the driver captured standing in front of the freezer, which means the invoice and the delivery can never drift apart.

Every SKU carries its own price

Bagged ice isn't one product at one price. A 20lb bag isn't priced like a 7lb bag, block ice sells differently than cubes, and a given account might have a negotiated rate that differs from your walk-up price. IceBossPro's product catalog holds a price for every SKU, and per-bag invoicing multiplies each delivered quantity by that SKU's rate for that customer. The driver never does pricing math — they count bags. The software turns counts into line items and line items into a total. That separation is what keeps invoices accurate even when a single stop takes four different products at four different prices.

Invoices that generate themselves at the stop

The moment a driver confirms a delivery in the mobile app, the invoice for that stop exists. There's no evening data-entry session where someone transcribes a stack of paper tickets into an accounting system and introduces a fresh batch of typos. A ninety-stop day produces ninety invoices, each built from its own delivered count, by the time the trucks are back in the yard. The office work shrinks from "key in the whole day" to "review the exceptions," and the exceptions are flagged for you instead of hidden in a pile.

Proof of delivery behind every number

A per-bag invoice is only as strong as the record behind it. When a customer disputes a charge — "we only got fifteen bags, not twenty" — you need more than your word. IceBossPro attaches proof-of-delivery to each stop: the timestamp, the delivered quantity, and a captured signature. The invoice isn't a claim, it's a receipt backed by a signed record of what landed in that freezer. Disputes that used to turn into he-said-she-said credits get settled by pulling up the delivery. That evidentiary trail is worth as much as the accurate billing itself.

Card-on-file closes the loop

Accurate invoices don't help cash flow if they sit unpaid. Per-bag invoicing in IceBossPro pairs with card-on-file so the charge for each delivery can run automatically on your billing cycle. The customer's card is charged for the exact bags they received, the payment posts against the invoice, and you stop mailing statements and chasing checks for variable weekly amounts. For consignment and recurring accounts especially, having the settlement charge run on its own means the money follows the delivery without a collections step in between.

Books that stay current with the route

Per-bag invoicing only pays off fully when the numbers land in your accounting without re-keying. IceBossPro syncs invoices and payments to QuickBooks, so a day of deliveries becomes a day of clean books — revenue per SKU, per account, per route — without a bookkeeper rebuilding it from tickets. You can finally answer "what did each product actually earn this month" because the accounting is assembled from real delivered counts, not month-end estimates. For a related look at how the standing quantities behind those invoices get scheduled in the first place, see Recurring Bag Orders in Packaged Ice Software.

Bill for what you actually delivered

The case for per-bag invoicing is simple: you sell a physical product in countable units, so your billing should be tied to units, captured at the point of delivery, priced by SKU, and backed by proof. Do that and the two- and three-bag leaks close, disputes resolve on the record, cash follows the drop, and the books keep pace. The bags that leave your truck are the bags on the invoice — every stop, every day — and that's how the margin you thought you were making becomes the margin you actually keep.