Commercial cleaning is a recurring-service business running on a stack that was never designed for it. A contract says "Site A, three nights a week, 22:00, two operatives, plus a monthly deep clean" — and in stock ERPNext there is no DocType that holds that sentence. Firms end up with the roster in a spreadsheet, checklists on paper or in WhatsApp photos, consumable usage guessed at month-end, and invoices typed by hand from a supervisor's notebook. ERPNext core gives you Customer, Item, Sales Invoice, Stock Entry, Employee, Timesheet and Project — good primitives, but nothing that generates next month's jobs from a contract, proves a job was completed to a standard, or reconciles the mop heads and chemicals actually consumed at a site against what you billed. Maintenance Schedule comes closest, and it is built for equipment servicing visits, not multi-operative shift work with per-site task lists and QA scoring.

We build a proper Frappe app — its own repository, its own module, installed on your bench with bench get-app and bench --site install-app — rather than a pile of Custom Fields bolted onto ERPNext core. The spine is a Cleaning Contract DocType holding the customer, the sites, the billing cadence and a child table of service schedules (weekday pattern, start time, duration, crew size, checklist template, rate). A scheduler event registered in hooks.py under scheduler_events runs a daily materialisation job that reads active contracts and creates Cleaning Job records across a rolling horizon, honouring the Holiday List and per-site blackout dates. It is idempotent: a re-run, a restart mid-job, or a manual trigger never double-books a shift. Each Cleaning Job carries a Job Checklist child table stamped from a versioned Checklist Template, so a site's task list can change next quarter without rewriting what was signed off last quarter. Supervisors close jobs from the mobile-friendly Frappe UI or through whitelisted methods (@frappe.whitelist()) that a lightweight field form posts to over the REST API, attaching before/after photos to the File doctype and computing a weighted QA score.

Downstream, the app posts real transactions instead of shadow records. Confirming a job's consumables writes a Stock Entry (Material Issue) from the van or site warehouse, so chemicals and supplies actually deplete and site-level cost becomes visible against contract revenue. Staff assignment writes Timesheet detail rows against the operative's Employee record and the correct Activity Type, giving you paid hours per site that flow into ERPNext job costing and payroll without re-keying. Billing runs off a second scheduler event that groups the period's submitted jobs per contract and drafts a Sales Invoice — flat contract value, per-visit, or contract plus billable extras such as deep cleans, callouts and over-hours, controlled by a field on the contract. Doc events in hooks.py (validate, on_submit, on_cancel) keep the chain consistent: cancelling a job reverses its stock movement and unlinks it from an unsubmitted invoice, and submitting an invoice locks the jobs it covered. Client scripts drive the supervisor form; server scripts hold tenant-specific pricing rules so they survive app upgrades. Everything respects Frappe permissions, with role profiles for Operative, Supervisor, Contract Manager and Accounts, and User Permissions restricting an area manager to their own customers and sites.

Reporting is built on Query Reports and dashboard charts that a manager can act on the same morning: jobs missed or late by site, checklist completion and QA score trend, consumable cost per visit, contract margin after real labour, and completed-but-unbilled work at period end. Every DocType is exposed through the standard Frappe REST API (/api/resource/Cleaning Job) alongside a small set of whitelisted endpoints for a field app or an access-control system, so your operational data is never trapped behind our UI. We build and test against Frappe/ERPNext v15 and v16 and pin the delivered app to the exact version and branch your bench runs.

This is a build-to-order product, not a marketplace download — there is nothing to install today. We start with a scoping call to map your contracts, sites, checklists, shift patterns and billing rules, then produce a written scope you sign off before development begins. Typical delivery is 2–4 weeks from confirmed scope. The app is deployed to a staging site first for UAT against your real contracts, then goes live on a scheduled window with a documented rollback plan, followed by a support window for defects and configuration questions. The source lives in a git repository handed over to you with full commit history — no licence key, no runtime check, and no dependency on us to keep it running.