How it works › Configuration
Data you edit, not code you call about.
Systems in this trade are built for one contractor and bent to fit the next. In Mercovi, the things that differ between contractors are settings.
What is yours to edit.
Wastes, containers, disposal facilities, management methods, billing methods, qualifications, pay categories, lab pack categories, floor plans and storage limits.
Storage limits per facility.
Each facility carries its own ordered rules — transfer hold, generator accumulation, storage permit — and the first rule matching a container governs its clock. No day count is stored in the software.
Lab pack categories.
Your own categories with their generic proper shipping names, and the category pairs that must not share a drum.
Floor plans.
Bays, racks, floor areas and docks for each facility, because every building is different.
Settings.
Every list a contractor would ever need to be different is a setting. Adding a disposal facility is a form, and the storage limits are ordered rules you write per facility.
| # | If the container | Then the clock is |
|---|---|---|
| 1 | arrived manifested from our own job | the transfer facility hold · 40 CFR 263.12 |
| 2 | is a third-party inbound | the generator's accumulation limit · 40 CFR 262 |
| 3 | anything else | the limit in this facility's permit |
Asked before the demo.
What happens when I need a new disposal facility?
Add it in settings — its name, EPA ID and approvals — and it is available on waste streams and manifests. There is no developer ticket.
Where do storage limits come from?
From you, per facility, as ordered rules. Because the governing limit depends on the facility's status, the generator's status and the state, Mercovi stores no day count in code.
Reports
A report and an invoice describing the same work cannot disagree, because the report counts each stream the way that client is actually charged for it.
ReportsClients and sites
The client is where the terms live. The site is where the templates live. A job at that site starts as a copy of both, and the copy belongs to the job.
Clients and sitesSee it run a job end to end.
Tell us what you run — events, plant pickups, lab packs, a floor — and we'll show you the screens that matter to you.
Last reviewed 2026-10-02