Waste collection is a rounds business, not an order business. Revenue comes from a container standing on a customer's site, a truck arriving on the right day, a weighbridge printing a gross and a tare, and a monthly invoice that mixes a fixed service charge with per-lift fees and a per-tonne disposal rate. ERPNext out of the box has no concept of any of that. There is no Route, no Container, no Weighbridge Ticket; a skip on hire is not a Serial No and not an Asset; a collection round is not a Delivery Note; and a landfill gate fee that must be passed through at cost with a handling uplift is not something a standard Sales Invoice line knows how to compute. Operators end up running round sheets in a spreadsheet, the weighbridge in the bridge vendor's own software, and ERPNext only as the place invoices are typed in afterwards — which is exactly where missed lifts and unbilled tonnes hide.

ECOSIRE builds a proper Frappe application — its own app on your bench, with its own module, fixtures and migration path — rather than a pile of Customize Form overrides that break on the next bench update. The core DocTypes are Waste Container (registry with type, capacity, current site, hiring customer, hire start, RFID/barcode identifier and a dated movement-history child table), Collection Route and Route Schedule (a route template with an ordered stop child table plus a recurrence pattern that a daily scheduler_events job expands into dated Collection Run documents), Collection Run with its Route Stop child rows (per-stop outcome: collected, no-access, blocked, contaminated, container missing — each with a reason code, timestamp, driver and optional photo attachment), Weighbridge Ticket (gross, tare, net, vehicle, material, bridge ticket number, in/out timestamps, disposal site) and Waste Material classified as recovered or residual. Container movement runs through a controlled state machine so a skip cannot be delivered to two sites at once, and Weighbridge Ticket submission is idempotent on the bridge ticket number so a re-imported export file or a retried API call never double-counts a load.

Technically it is ordinary, maintainable Frappe. Business rules live in Python controllers and hooks.py doc_events — validate and on_submit on Weighbridge Ticket post net weight back to the originating Route Stop and the material ledger, and on_cancel reverses cleanly — not in fragile client-side hacks. Client Scripts handle the driver-facing niceties (fast stop completion, container scan-in), while whitelisted methods (@frappe.whitelist()) expose a small, permission-checked surface for the parts that matter: capture_weighbridge_ticket, complete_stop, container_scan and a route-manifest endpoint. Weighbridge indicators, in-cab tablets and barcode scanners talk to those methods over the standard Frappe REST API with token or API-key authentication, so there is no bespoke transport to maintain; bridges that only produce batch exports get a file import that runs through the same validation and the same idempotency check. Billing is generated by a scheduled job that walks completed Collection Run and submitted Weighbridge Ticket records for the period against a Waste Service Contract — fixed rental, per-lift, banded per-tonne rates, minimum charges, contamination surcharges and pass-through gate fees — and drafts native ERPNext Sales Invoice documents against your real Items, tax templates and accounts, so your GL, ageing and tax reporting stay in core ERPNext. Recovered material posts through standard Stock Entry documents when you want recyclate treated as sellable inventory, giving a genuine tonnes-in / tonnes-out reconciliation. Role Profiles and permission rules ship for Driver, Weighbridge Operator, Dispatcher, Contracts and Accounts, with User Permissions available for depot-level or company-level segregation.

This is a build-to-order engagement, not a marketplace download. You request a quotation, we run a scoping call, and we write down exactly which container types, stop reason codes, contract rate structures, weighbridge hardware and disposal-site rules apply to your operation. From confirmed scope, typical delivery is 2-4 weeks: we build against your ERPNext version (v15 or v16), install on a staging bench, run UAT with your dispatcher and weighbridge operator against your own routes and rate cards, then deploy to production with a documented rollback path and a pre-deployment backup. You receive the full source in a Git repository you own, with no licence key and no runtime dependency on us, so a future change never has to come back through ECOSIRE.