Keep a Per-Customer Ice Machine Service History So You Never Re-Diagnose the Same Unit Twice
You pull up to a restaurant for the third time this year on the same modular cube machine — "it's not making ice again" — and you're standing there trying to remember whether you already cleaned the condenser, swapped the water inlet valve, or descaled the evaporator. A per-customer, per-unit service history fixes that: R-Pro's field app captures what you did on this exact machine while you stand in front of it, and the office ERP turns that record into clean quotes, invoices, and parts tracking — so the next visit starts from what you already know, not from scratch.
On site: tie every visit to the exact machine, not just the customer
- Open the customer, pick the specific ice machine, and you see every past visit on that unit — last descale date, the failed water inlet valve you replaced in March, the harvest-cycle symptom from the summer call.
- Scan the nameplate once (Manitowoc, Hoshizaki, Scotsman model and serial) and it auto-fills the equipment record — so a 'no ice' callback is matched to the right unit even at a site with three machines.
- Run AI fault diagnosis on the new symptom — long freeze cycle, thin or cloudy cubes, machine cycling but no harvest — built on 600+ real refrigeration cases that walk symptom to cause to repair steps.
- Add a voice memo while your hands are wet ('scale on evaporator again, recommend water filter') so the detail isn't lost by the time you're back in the truck.
- All of it works fully offline — walk-in coolers and back-of-house mechanical rooms with no signal don't stop you from reading or writing the history.
In the office: turn that history into quotes, invoices, and parts you can track
- Every logged visit feeds the customer ledger, so you can see this restaurant has had three calls on the same cube machine — useful when you propose a replacement or a service contract.
- Quote the recurring fix properly — an itemized estimate for descaling plus a water filtration install — using your own labor rates and parts pricing.
- Issue the invoice or tax invoice with your country's tax set the way you need it (VAT, GST, or sales tax — your own name and rate).
- Track the water inlet valves, scale cleaner, and inlet filters you keep stocking for this exact model through inventory, suppliers, and purchase orders.
- Run reports that show which customers generate repeat ice-machine calls, so you know where a maintenance agreement actually pays off.
The connection: field work flows into the books with no double entry
- The on-site receipt you issue from the field app and the office invoice are the same job — you don't re-key the visit into accounting at night.
- Because the unit's history lives at equipment level, a callback under warranty is obvious: you already see you were here six weeks ago and what you charged.
- Parts used on the repair tie back to inventory and purchases, so the cube machine's true cost-to-service is visible, not guessed.
- Sales, purchases, and expenses from these recurring ice-machine calls roll into net profit automatically — one subscription, both tools, all 10 languages.
- Next visit, the tech opens the same per-unit record the office sees — one source of truth instead of a memory test.
One service history. Two tools that earn their keep.
R-Pro pairs a field app — AI fault diagnosis on 600+ real cases, nameplate and receipt scanning, voice memos, per-unit service history, on-site receipts, fully offline — with a full office ERP for quotes, invoices and tax invoices, accounting, inventory, suppliers, and customer ledgers. Two equally strong products, one subscription, 10 languages, with field work flowing straight into the books so you never diagnose the same ice machine twice.
Get R-Pro →FAQ
How do I keep two ice machines at the same restaurant from getting mixed up?
Each machine is its own equipment record under the customer, created when you scan the nameplate (model and serial). So 'the cube machine in the back bar' and 'the flaker in the kitchen' carry separate service histories — a no-ice call is logged against the right unit, not just the address.
Can I see what I already did on this unit before I start diagnosing again?
Yes. Open the customer, select that ice machine, and the full visit history is right there — past descales, the parts you replaced, prior symptoms and voice memos. You start from what's known instead of repeating tests on a problem you already chased down once.
Does the history work if the machine is in a basement or cooler with no signal?
It does. The field app is fully offline — you can read the unit's past visits and write the current one with no connection. It syncs when you're back in coverage, so nothing from the no-signal job is lost.
How does a recurring service call become an invoice without re-typing it?
The visit you log and the receipt you issue on site are the same job the office ERP sees. You quote, invoice, and post it to accounting from that one record — and the parts used tie back to inventory and purchases. No double entry between the truck and the books.