HomeIndustriesGrease Traps
The trap belongs to the restaurant. The interval belongs to the municipal bylaw.
A restaurant owner forgets their grease trap pump-out; the municipal bylaw never does. OpsNode is built to track an asset the customer owns — not rented, not billed as a rental — on a schedule dictated by regulation rather than by anyone's memory.
A customer-owned asset, a bylaw-driven schedule
A grease trap isn't rented equipment: it belongs to the restaurant, installed under its service dock or in its kitchen, and it stays there. What's sold is the maintenance — a pump-out at an interval set by the municipality, not by the restaurant owner's convenience. The customer-owned asset model, tracked on a schedule with no rental contract attached, is already what OpsNode applies to septic services; it covers grease traps the same way, with nothing reinvented.
The resulting route is dense and urban: lots of short stops along the same commercial strip, access through the service dock, a service window limited to the kitchen's off-hours so it doesn't interfere with service. This isn't the rhythm of a job-site route — it's a proximity business, where stop order matters just as much as the schedule itself.
And the bylaw doesn't settle for an interval respected on paper: come inspection time, it demands proof. A missed interval doesn't show up right away — it surfaces months later, as a backup or a fine, by which point it's already too late to avoid.
Built for an owned asset, not a rental contract
Every capability below answers a real constraint of the business — not a checkbox generic rental software had to fill.
Customer-owned asset
The trap belongs to the restaurant, not the rental operator: it's tracked on a schedule like any other unit in the fleet, with no rental contract or usage billing built around it.
Same mechanism as septic servicesPer-unit schedule, fixed days available
The regulatory interval is set trap by trap; a fixed day applies whenever the municipality or the restaurant requires it, with no drift over the months.
Set unit by unitVisits generate themselves
Once the schedule is set, future pump-outs appear on their own and group by address — useful on a commercial strip where several restaurants sit side by side.
No manual route entryRoutes on the real road network
Stop order adapts to a dense urban route — service docks, one-way streets, kitchen off-hours — not a straight line between two addresses.
Calculated on the real road networkChecklists with timestamped proof
Every pump-out follows a checklist specific to its type; a timestamped photo and the driver's location accompany completion — ready to produce if an inspector asks.
Photo + location at every visitEnd-of-day report and billing
Billable visits are detected automatically instead of being reconstructed by hand at month-end, and the PDF invoice follows directly from them.
Automatic detection, no reconstructionThe bylaw doesn't ask for trust — it asks for proof
A municipal inspector who shows up doesn't want to hear that the pump-out "must have happened": they want to see the date, the photo, and the person responsible for the visit. Every visit leaves that record at the moment it happens, on site — no after-the-fact reconstruction from a spreadsheet or a fuzzy memory.
The end-of-day report goes out by email, configurable to whatever the operator wants to see in it; billable visits are detected automatically instead of being reconstructed at month-end, and the PDF invoice follows directly from them — for forty traps spread across a commercial strip just as much as for a single restaurant out on the edge of town.
A grease trap route to put on a bylaw-driven schedule?
Show us your current municipal intervals — we'll show you how OpsNode would have sequenced them on an urban route this week.
See a demo