Pest control is a recurring-service business wearing a project-services ERP. A single commercial contract might be twelve visits a year across four sites, each with a different treatment plan, each consuming a scheduled quantity of a registered product that a regulator can ask you to account for down to the millilitre. ERPNext core gives you Customer, Contract, Item, Stock Entry, Sales Invoice and a Maintenance Schedule that was designed for equipment servicing — it can tell you a visit is due, but it has no concept of a treatment plan, a bait station, a re-entry interval, an applicator licence, or a chemical batch traceable from a stock bin to a specific customer premises. Most operators end up bridging that gap with a scheduling spreadsheet, a paper chemical register and a WhatsApp thread with technicians, then rebuild the numbers by hand when an audit or a renewal season arrives.

ECOSIRE builds this as a proper Frappe app — its own module, installed on your bench with bench get-app and bench install-app, versioned in a git repository you own. The data model is a set of purpose-built DocTypes that link into ERPNext rather than replacing it: Pest Control Contract (with a child table of covered sites and scheduled treatments, linked to the ERPNext Customer and to a Sales Order or Subscription for billing), Service Site with its own address, access notes and site plan attachments, Treatment Plan defining target pests, methods, approved products and frequency, Treatment Visit as the operational document a technician completes, and Chemical Product extending the ERPNext Item with registration number, active ingredient, approved dilution range, re-entry interval and safety data sheet attachment. Applicator Licence tracks each technician's certification class and expiry.

The automation lives where Frappe expects it. Scheduler events registered in hooks.py materialise the next window of Treatment Visit records from every active contract's frequency rule, flag contracts entering their renewal window, and raise alerts for applicator licences and product registrations approaching expiry. Doc events on Treatment Visit submit enforce the rules that matter: an unlicensed technician cannot be assigned to a restricted-product treatment, a recorded dose outside the approved dilution range is blocked with a clear validation message, and submitting the visit posts a Stock Entry that consumes the actual chemical quantity from the technician's van warehouse — so batch and serial traceability, if you use it, runs straight through ERPNext's own inventory ledger instead of a parallel paper register. A daily route sheet groups the day's visits by technician and sequence, and the mobile-friendly visit form (a client script over the standard Frappe form, so it works in the Frappe mobile view without a separate app) captures findings per bait station or treatment point, pest activity levels, customer signature and photos. On submit, a Jinja print format renders the service report and, where the contract requires it, a numbered treatment certificate, emailed automatically to the site contact.

Everything is reachable over the Frappe REST API and a small set of @frappe.whitelist() methods, so a field app, a customer portal page or a third-party scheduling tool can read the day's route and post back visit results without touching the database directly. Permissions ship as role profiles — Technician, Service Supervisor, Compliance Officer, Accounts — with user permissions restricting technicians to their own visits and supervisors to their branch. Reporting includes chemical usage by product, site and period (the shape most regulators ask for), visit completion and SLA adherence, pest activity trends per site, and a contract renewal pipeline with expiry-dated value. Everything is built and tested against Frappe/ERPNext v15 and v16, on your version and your deployment.

This is build-to-order, not a marketplace download. You request a quotation, we run a scoping call to map your contract types, treatment plans, chemical register and the reports your regulator actually asks for, and we come back with a fixed scope, price and timeline. Typical delivery is one working week from confirmed scope. We install and configure on your staging bench first, run UAT with your supervisors and one or two technicians against real contracts, then deploy to production with a documented rollback plan. You receive the full source, the git repository, technical and user documentation, a live training session and a post-go-live support window.