Waste collection is a business of recurring service events attached to physical assets sitting on customer sites. A skip goes out on Tuesday, comes back Thursday at 3.42 tonnes of mixed C&D, gets tipped, and has to be rated against a contract that charges a rental day-rate plus a per-tonne gate fee with a contamination surcharge above a threshold. Odoo core has no vocabulary for any of that. stock.lot is not a skip, project.task is not a lift, and sale.order.line has no concept of a gross-minus-tare weight captured on a weighbridge at 06:10. Operators end up running routes on a whiteboard, containers in a spreadsheet nobody trusts, and billing in a monthly manual reconciliation between the weighbridge printout and the ERP — which is exactly where the revenue leakage lives.

We build a dedicated operations layer inside your database rather than bolting a second system onto the side of it. The core is a container asset model (ecosire.waste.container) carrying type, capacity, tare weight, current location as a res.partner site, and a full movement history, so at any moment you know which asset is on which customer site and how long it has been there. A service order model (ecosire.waste.service.order) represents one lift, exchange, delivery or collection, sequenced through states with @api.depends computed fields for planned versus actual, and grouped onto a route (ecosire.waste.route) with driver, vehicle and ordered stop lines. Routes are planned from calendar and list views, dispatched, and closed out against actuals; recurring contracted collections are generated ahead of time by an ir.cron scheduled action from a frequency rule on the contract, so Monday's commercial round appears without anyone re-keying it.

Weighbridge capture is a first-class model (ecosire.waste.weighbridge.ticket) holding gross, tare and a computed net weight, the material line-up by waste stream, the vehicle, the ticket reference and the timestamp. Tickets can be keyed at the gate on a stripped OWL form built for touch, or pushed in from an existing indicator or weighbridge PC over the XML-RPC/JSON-RPC API — we implement the ingest method and the idempotency key so a retried post never double-charges. Each ticket links back to its service order and container, and a QWeb report renders the customer-facing weighbridge docket plus, where you need it, the waste transfer note layout your regulator expects. Recycling material tracking sits alongside as waste-stream records with per-stream rates, contamination capture and inbound/outbound tonnage, which gives you a recovery-rate figure drawn from the same rows the invoice comes from rather than from a separate report nobody can tie out.

Billing is where the module earns its keep. A contract model holds the commercial terms — rental per container per day or per month, per-lift charges, per-tonne gate rates by material, minimum charges, surcharge rules and escalation dates — and an invoicing run walks unbilled service orders and weighbridge tickets for the period, rates each one, and produces account.move drafts with lines that link straight back to the docket. Nothing posts automatically without your say-so; a review step is deliberately built in. Security is real, not decorative: ir.model.access.csv grants for driver, weighbridge operator, dispatcher and manager groups, plus record rules so a driver sees only their assigned route and a multi-company operator sees only their own depot's containers. Everything is standard Odoo — models, views, security, reports — so it upgrades and backs up with the rest of your database.

Delivery is build-to-order, and we are explicit about what that means. This is not a listing you download from apps.odoo.com today. It starts with a short scoping call where we go through your container types, route structure, weighbridge hardware and above all your rate card, because the billing rules are the part that is genuinely different in every yard. We come back with a written scope and a fixed quotation. Once you confirm scope, typical delivery is one working week to a working build installed on a staging copy of your database for UAT, followed by go-live with a rollback plan, a training session for dispatch and gate staff, and a post-go-live support window. You receive the full installable source for your Odoo version — 17.0, 18.0 or 19.0, Community or Enterprise — along with the git repository, so nothing about this leaves you dependent on us to keep operating.