Grease Trap Cleaning Software

Grease trap software for the manifest, the cycle, and the address.

Every pump ends with the same paperwork done twice: a manifest filled in by hand at the trap, then typed again in the office before it goes to the restaurant and the city. We turn that loop into software where the record is finished once, at the trap, and the next pump schedules itself.

See our work

Bring one stuck workflow. Leave with a build, buy, repair, or wait recommendation.

Trusted by

Perceptional logoMusgrave GroupUrShipper logoBrux Dental SolutionsBella Skin Institute LogoEnergia RewardsDraftly logoTuneClub LogoSekou LMS logoLogo of food order management app gulaSnelwegDealsGrubly logoPSi logoInstantor Rewards logologo of Mobile app for events, membership clubs, and communitiesAldiFest retail campaign logoVidmattic logoEMS Connect logoWorx Squad logologo of Online Web App For Making Intrologo of Referral and Viral Marketing PlatformConcurrences logoGE logoTicketstop logo

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

The driver fills the manifest by hand, leaves a copy at the door, and the office types the same numbers in again.

02

Every site sits on a different 30, 60, or 90 day cycle, and the only reminder is someone remembering to check.

03

The permit and the past manifests live in a binder, so when a restaurant changes hands the history is gone.

Plain answer

RaftLabs builds grease trap cleaning software for commercial kitchen FOG service companies: each site keeps its own pump cycle, trap record, permit, and manifest history, drivers complete the manifest on a phone at the trap, and the office sends the same record to the restaurant and the city without retyping it.

What to remember

  • Use this when the manifest, not the pumping, is where your week goes.
  • The manifest should be finished once, on the phone at the trap, and never typed again in the office.
  • The pump cycle belongs to the site and the trap, not to the customer and not to memory.
  • The permit and the manifest history stay with the address, even when the restaurant changes hands.
  • Hire freelancers for one small, well-defined task; use one accountable agency party when the work needs coordination across screens, rules, data, and connections.

The first decision is not what to build.

It is whether software is the right answer at all. We use four possible recommendations before discussing a development scope.

  • 01

    Buy

    Choose a maintained product when it already handles your manifest format, your pump cycles, and your billing, and the remaining gaps can be solved with configuration, a connector, or a small process change. Paying for software you do not have to maintain is often the better trade.

    Run the build-vs-buy numbers

  • 02

    Repair

    Keep the existing product when drivers and the office still get value from it and the code can be understood safely. Start with evidence: where the code lives, how the data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live.

  • 03

    Build

    Own the system when the workflow shapes margin, customer experience, speed, or a product customers pay for. Start with one complete path: one route day, from the first stop to the manifest reaching the restaurant and the city.

  • 04

    Wait

    Do not turn a changing policy into permanent software. If a city is about to change its manifest format or your service rules are still moving, stabilise the rules, name the workflow owner, and measure the cost of the current process before paying for a product.

Not sure which path is yours? Bring it to a 30-minute call. Leave with the answer in writing.

Fit

Custom software should earn its maintenance burden.

A feature request is not enough. The case is real when the same constraint shows up in time, errors, margin, or customer experience.

A fit

Your office re-enters manifest details that drivers already wrote down once at the trap.

Sites sit on different mandated cycles and missed or late pumps create real risk for your customers.

Your manifest format, chain pricing, or city reporting differs enough that generic tools need constant workarounds.

Not a fit

A maintained product already handles your manifests, cycles, and billing with reasonable setup.

The team wants software to settle an unresolved operating policy, such as who owns the overdue list.

The brief is a feature list with no user, transaction, or business result attached.

Not sure which side you are on? Use the first call to make that decision. A useful answer may be to buy, connect, repair, or wait.

Start with the operation, not the software.

A grease trap business does not lose its week at the trap. The pumping is the skilled part, and your crews already know it. The week goes afterwards, at the office desk. A manifest is filled in by hand in a kitchen doorway, and a copy is left with whoever was on shift. Then the same gallons, dates, and disposal details are typed into a computer, so the record can be emailed to the restaurant and filed for the city.

Every site makes it harder. One restaurant is on a 30 day cycle because its city says so. Another is on 90 days, and its trap is barely a quarter full when the crew arrives. A chain wants one statement for all its locations, while each location keeps its own trap, its own access notes, and its own inspection history. None of this lives in one place, so the schedule depends on someone remembering to check a spreadsheet, and the history depends on a binder surviving a change of ownership.

A second product hides inside the first. Restaurants see one thing: a clean record of each visit they can hand to an inspector. Your team lives in another: route lists, overdue sites, manifest exceptions, disposal details, managing users, and a record of who did what. Quotes that squeeze all of that into an "admin panel" line item are where budgets most often break, so we quote your team's screens as their own job, with their own users, from the start.

Custom grease trap cleaning software makes sense when one owned system can remove that double handling better than a product, connector, or process change. The first release should take the smallest useful path from trigger to result: one route day, completed at the trap, filed everywhere it needs to go. It should not replace every tool at once.

We start where it hurts.

The interface is only one part of the job. The real scope includes the rules, the data, the connections to your other systems, what happens when things fail, who can see and change what, and who runs it after release.

Manifests finished at the trap

The driver completes the manifest on a phone at the stop: site, trap, gallons, condition, disposal site, photos, and signatures. The office receives the finished record when the job closes, and the restaurant and the city get that same record. The paper copy in the door and the second typing both go away.

Pump cycles that schedule themselves

Each trap carries its own cycle, commonly 30, 60, or 90 days, and the next visit is created from the last completed pump. The office works from one overdue list, most overdue first, instead of a spreadsheet and memory. When a crew finds a trap filling faster than its cycle, the condition they record is what shortens the next interval.

Site records that stay with the address

Every location keeps its own record: where the trap sits, its size, hose length, access notes, the hours the kitchen allows, the FOG permit, and every past manifest. The record belongs to the address, so it survives a change of ownership, a new manager, and a new driver on the route.

Chain and group accounts without the muddle

One restaurant group, many locations, each with its own cycle, price, and contact. Billing rolls up to one statement for the group or stays per location, with the manifest and photos attached to the invoice, and the price you agreed with each chain kept on the account instead of in someone's inbox.

Disposal and cost you can see per job

The disposal site and its rate sit on the job, so the gallons a crew pumped and the rate at the site produce the disposal cost for that stop. A route book where disposal cost is invisible per job is a book where the margin on each account is a guess.

Which one is yours?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

Who it serves

One system, different books of work.

The manifest and the cycle stay the same. What changes is the shape of the account book each operator runs.

Single-truck operators

A small book run properly: every site on its cycle, every manifest finished at the trap, and no evening spent typing up the day. The win is hours back and a record that stands up when a customer or a city asks questions.

Regional haulers with several crews

Several trucks, several cities, several manifest formats. The office needs one overdue list across all of it, drivers who see only their route, and reporting that matches each city without a separate spreadsheet per city.

Restaurant groups and chains

Many locations under one account, each on its own cycle. The group gets one statement and one place to see service history across stores, while each store keeps the record its own inspector will ask for.

Institutional kitchens

Schools, hospitals, and commissaries run on their own paperwork rules and their own access hours. The site record carries the access notes, the contact, and the documents each facility needs, so a new driver does not learn them by getting turned away at the gate.

Operators adding a new service area

A new city usually means a new manifest format and a new reporting habit. The system takes the new format as a new rule set on the same site and route structure, instead of a second way of working for one part of the book.

Proof

The fifth attempt became a product customers could keep using.

UrShipper had already worked with four development vendors. Its founder describes the communication and decisions during the recovery.

The case study documents a 14-week recovery, five carrier connections, a Shopify fulfilment workflow, and client-reported results. It is one comparable project, not a promise that every inherited codebase can follow the same plan.

Read the UrShipper case study

Which workflow is costing you the most right now?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

How it works

Close one expensive risk before opening the next.

Each stage answers a buyer question and leaves behind a decision you can inspect. The next stage only opens when the expensive uncertainty in the current one is small enough to accept.

  1. 01
    Understand

    Trace the real workflow

    Where is the cost or failure actually coming from?

    Follow one driver and one route day from the first stop to the manifest reaching the restaurant and the city. Include the paper form, the copy left at the door, the office re-entry, the overdue checks, and the calls that happen when a record cannot be found.

    Decision produced

    A map of the workflow, exceptions, owners, systems, and the baseline cost or delay worth changing.

    Risk closed

    Paying to automate the visible symptom while the expensive constraint remains.
  2. 02
    Shape

    Choose the first useful release

    What needs to exist together for one useful result to work?

    Choose the shape from the way the work happens, not from a preferred technology. Name the user, the device, the data, the system connections, who can access what, the exceptions, and the result the first release must complete: a finished manifest and a next visit on the calendar.

    Decision produced

    The right mix of phone and office surfaces and behind-the-scenes connection work, with the first-release boundary and a clear definition of done.

    Risk closed

    A small-looking feature list that quietly depends on several interfaces, systems, and owners.
  3. 03
    Prove

    Review working software

    Will it hold up outside a controlled demo?

    Review the product against the agreed workflow, not a tour of finished screens. Run a real route day through it, complete a manifest with no signal, and pull the history for one address the way an inspector would ask for it.

    Decision produced

    Working checkpoints tested with realistic data, real user types, system connections, recovery plans, and the people who will use or run the system.

    Risk closed

    Discovering the important gaps during migration or after customers depend on the release.
  4. 04
    Transfer

    Release, measure, and hand over

    Did the new workflow improve the original constraint, and can another capable team operate it?

    Move one crew or one service area first. Compare manifest handling time, overdue sites, and records produced on request with the starting point before adding the next workflow.

    Decision produced

    A controlled release, comparison with the baseline, operating notes, account ownership map, and a recommendation for what should happen next.

    Risk closed

    Measuring development activity instead of the business result, or depending on the original vendor to keep the system running.

What stays out of the black box

These are operating conditions to put in the engagement, not claims to take on faith.

The scope names one complete workflow

The user, the trigger, the decisions, the data, the exceptions, and what 'done' looks like. A screen list is not enough.

Progress is visible in working software

Reviews against the product at agreed checkpoints, while there is still time to act.

A scope change has a price before it has code

A new workflow or system connection shows its effect on cost and timing before anyone approves it.

Ownership exists throughout, not only at handover

Code, cloud, data, and provider access stay visible and under your control from day one.

The work is checkable without being technical

Checkpoints are working software you use yourself, reported in plain language.

The surfaces and systems a grease trap platform usually needs around it.

What it costs

Every project starts at $10K.

The first phase turns the costliest patched workflow into a scoped build with written acceptance criteria.

Starting investment

Starts at $10K

Workflow complexity, systems to connect, data migration, and user roles set the scope. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.

Buy a product or own the system

Buy an existing productOwn custom software
Best fitHandles your manifest format, cycles, and billing with reasonable setup, and its pricing makes senseYour manifest formats, chain pricing, or city reporting are the way you work, not a setting
Manual workConfiguration and process changes can remove the double handlingThe office still re-enters what drivers already recorded, and that cost repeats every route day
ConnectionsExisting connections to your billing and accounting work with reasonable setupA critical connection to your other systems cannot be done cleanly any other way
Platform routeConfigure an established platform when its site, manifest, and permission model fitsOwn custom software only when the differentiating process, client product, system network, or cost of constraint justifies build and support

Work with us

Bring one stuck workflow. Leave with a decision.

In a 30-minute call, we will help you decide whether to buy, connect, repair, build, or wait. If custom software is not the sensible next move, that is still a useful answer.

  • One named workflow owner and one complete path for the first phase.
  • Scope, price, what 'done' looks like, and exclusions agreed before paid work starts.
  • Code, cloud, data, and provider access remain under your control.
  • Post-launch warranty cover for defects in the agreed scope.

Frequently asked questions

Straight answers to what buyers ask before they scope. Still stuck? .

It is the system a grease trap and FOG service company runs its work on: site and trap records, recurring pump schedules, the manifest the driver completes at each stop, photos, billing, and the copies that go to the restaurant and the city. Custom software fits that system around your manifest format, your cities, and your way of running routes, instead of asking you to change how you work to match a generic field service tool.

The driver opens the stop, confirms the site and the trap, and fills the same fields your paper manifest carries: date, gallons removed, condition of the trap and baffles, disposal site, and signatures. Photos of the trap before and after attach to the same record. When the driver closes the job, the office already has the finished manifest. Nobody types it a second time, and the restaurant and the city get the same record, not two versions of it.

Yes. Each trap carries its own cycle, commonly every 30, 60, or 90 days, set by the city rule, the permit, or what your crew actually finds in the trap. The next visit is created from the date of the last completed pump, not from the date someone planned it. A weekly overdue list, sorted with the most overdue site first, shows the office what to book before a site drifts past its required date.

The record belongs to the address. The trap, its size and location, the access notes, the FOG permit, and every past manifest stay attached to the site when the business name on the door changes. The new owner becomes the contact and the billing name; the compliance history does not start over, and your crew does not have to rediscover where the trap is or how it behaved last time.

Buy an existing product when it already handles your manifest format, your cities' reporting, and your billing without workarounds. Go custom when the way you run routes, price chains, or file with your cities is itself the advantage, or when your team keeps copying records between a scheduling tool, paper manifests, and a billing system by hand. If your service rules are still changing every week, wait and settle them first.

For a small, well-defined task with someone technical managing it, freelancers are often cheaper. The pattern that goes wrong is a non-technical buyer coordinating several freelancers becoming the project manager, the tester, and the person who discovers the pieces don't fit. A development company earns its fee when the work needs coordination across screens, rules, data, and connections: one accountable party, one phase price, and checkpoints against the whole workflow. If your need is one screen or one fix, hire the freelancer.

The first paid phase may cover a bounded audit, a proof of concept, a recovery plan, or a small first release. The final price depends on how deep the workflow goes, how many kinds of users it serves, what it needs to connect to, whether your site and manifest history needs moving over, and the manifest and reporting formats your cities require. The agreed phase is priced in writing before it starts.

Timing depends on scope: a manifest and scheduling release for one service area is a smaller engagement, while several cities with different manifest formats, chain billing, and years of paper records to move over takes longer. The schedule is set once the first workflow and what 'done' looks like are clear.

Yes. Takeover is a common first engagement, and it always starts with an audit: where the code lives, how your data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live. Code that is understandable and fit for the next release stays; only the parts blocking reliability get replaced. And if you already paid another vendor and have nothing working, the audit tells you which story you have before you spend more.

Security starts with the data, the people, who can see and change what, the systems it connects to, and where it runs. The scope can include access controls, separate testing and live environments, protected passwords and keys, activity logs, backups, and recovery plans. One point matters in this trade: the software keeps and sends the records your FOG programme requires, but your company stays responsible for the accuracy of each manifest and for meeting each city's rules.

We need one person who owns the workflow, sample manifests and permit documents from each city you serve, access to the relevant users and systems, timely answers on business rules, and someone who can accept or reject each milestone. A weekly working session is usually enough once the scope is stable. Your team should not have to manage developers day to day. The team that scopes your project is the team that does the work: no handoff to another vendor after you sign, and you can talk to the people doing the work directly.

Ask for the quote to name everyone who will use the system, including your own team. Every platform has two products: what customers see, and what your people use all day: the driver's screens, the office screens for scheduling, exceptions, and reporting, managing users, and a record of who did what. When that second product is quoted as an 'admin panel' on a single line, it becomes the overrun. Our quotes treat your team's screens as their own scope, with their own users. Then the phase names the workflow, what 'done' looks like, the price, and the exclusions, all before paid work starts.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the workflow agreed at the start: run a real route day through it, complete a manifest, and pull the record an inspector would ask for. Progress is reported in plain language: what changed, what's next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads. Our job is to make the work checkable; your job is to check it against your business.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

Every launch includes post-launch warranty cover for defects in the agreed scope, release support, and small screen corrections. After that, work can continue as another fixed phase or an ongoing product engagement. The code and accounts stay under your control either way.

The account and the sites stay separate on purpose. One restaurant group can hold many locations, each with its own trap, cycle, price, and contact. Billing can roll up to one statement for the whole group or stay as one invoice per location, and the completed manifest and photos attach to the invoice either way, so a manager who questions a charge can see the record of the visit.

The stop can be completed without a signal for the workflows designed for it. The phone stores the manifest, the readings, and the photos, shows clearly what is saved and what is still waiting, and sends everything when the signal returns. Test this with a real site, not in an office with perfect Wi-Fi, because a manifest that only works with a strong signal will fail exactly where traps are hardest to reach.

Yes, if the record is kept by site. An inspector asks about an address, not about your filing system, so the search starts from the site and returns every manifest, photo, and permit for that address in date order. Years of history should take seconds to produce, whether the restaurant needs it for its own inspection or a city asks your office for it.