ERPNext HR ships a Shift Type, Shift Assignment and Shift Request DocType and will resolve an employee's shift when it processes attendance — but it has no visual roster. Scheduling a hospital ward, a hotel front desk or a three-line manufacturing plant means creating Shift Assignment records one form at a time, with no calendar to see who is on, no way to spot that Saturday night is short two nurses until it is too late, and no self-service path for staff to swap or pick up open shifts. Rotating patterns (four-on-four-off, early/late/night cycles) get rebuilt by hand every cycle. Teams end up back in spreadsheets and WhatsApp, and the attendance ERPNext eventually computes no longer matches what actually happened on the floor.

ECOSIRE builds the Advanced Shift & Roster Planner as a proper Frappe app (its own module, installed via bench get-app / bench install-app) that sits directly on the native HR DocTypes rather than replacing them. The centrepiece is a drag-and-drop roster calendar — a custom Frappe Page backed by whitelisted server methods — where a scheduler drags an employee onto a day and cell to create a real Shift Assignment, drags to move or resize it, and sees the whole week or month per department, branch or location. A Roster Pattern DocType lets you define rotating cycles once (sequence of shift types, on/off days, cycle length) and generate assignments forward for any date range and employee group in a single background job. Publishing a roster flags it, snapshots it, and notifies affected employees.

Technically it is honest ERPNext engineering, not a black box. Shift-swap and open-shift pickups are their own submittable DocTypes with a workflow and role-based approvals wired through hooks.py doc events (validate, on_submit) so an approved swap writes back to the underlying Shift Assignment and stays in sync. Coverage rules compare required headcount per shift/skill against what is actually rostered; a scheduler_events cron evaluates upcoming days and raises understaffing alerts (in-app notification plus optional email) before the gap becomes a no-show. An auto-assign routine reconciles the published roster against Employee Checkin records so the shift that best matches a check-in is assigned, keeping attendance processing accurate. Everything is reachable over the standard Frappe REST API and whitelisted methods, so a kiosk, mobile view or the Frappe HR app can read and post to it. Permissions use ERPNext role profiles — schedulers manage their own department, employees only raise requests, managers approve.

Because this is build-to-order, nothing is a generic download you install and hope fits. We start with a short scoping call, confirm your shift model, rotation rules, coverage thresholds, approval chain and locales, then build against your ERPNext version (v15 or v16). Typical delivery is 2 to 4 weeks from confirmed scope. You get the app validated on a staging copy of your site through UAT, deployed to production with a rollback plan, and a post-go-live support window — plus the full git repository so your team (or ours) can maintain and extend it.