Most teams that run Odoo eventually hit the same wall on workforce scheduling. Employees, contracts, and working calendars already live in hr.employee and resource.calendar, but Odoo core has no first-class concept of a published shift roster — who works which slot, on which site, with which skills, and whether the day is covered. Planners fall back to spreadsheets that drift out of sync with attendance, time-off, and payroll, so double-bookings, uncovered slots, and unapproved swaps surface only after the fact. The native planning app (Enterprise) covers some of this for shift planning, but many businesses need site-specific rosters, coverage rules, and swap approvals that a generic setup does not model.

This is a made-to-order module we design and build for your operation. At its core is a dedicated shift model (shift.schedule / shift.line) linked to hr.employee, resource.calendar, and — where relevant — hr.department and analytic accounts, with @api.depends computes for shift duration, coverage counts, and cost estimates. Overlap and rest-period rules are enforced with @api.constrains so one employee cannot be booked into conflicting slots or scheduled through a time-off record in hr.leave. Rosters are exposed through Gantt, calendar, list, and Kanban views (XML/OWL), with a QWeb PDF roster you can hand to a site supervisor and a portal view so staff see their own upcoming shifts. Automated actions and scheduled crons handle recurring roster generation and reminder notifications, and every model ships with ir.model.access.csv plus record rules so planners edit only their own department or site while staff see read-only their own lines.

Because it is built on standard Odoo ORM and the shared calendar/employee data, the module integrates cleanly with the rest of your instance rather than sitting beside it. Approved shifts can feed attendance expectations and, where you use it, project or field-service planning; the whole thing is reachable over the XML-RPC/JSON-RPC API so external kiosks, mobile clients, or a workforce app can read and post shift data. We build against your Odoo edition and version — Community or Enterprise, 17.0, 18.0, or 19.0 — and reuse native models wherever they already do the job instead of reinventing them.

Delivery is build-to-order. We start with a short scoping call to confirm your roster structure, coverage rules, approval flow, sites, and reporting needs, then send a fixed quotation and timeline. Typical delivery is one working week from confirmed scope, depending on integration and localization depth. You get installable source code for your Odoo version, deployment on your server or Odoo.sh, UAT on a staging database, and a post-go-live support window. Pricing starts from $999 (indicative, single-company base scope); multi-company rosters, extra integrations, custom approval hierarchies, and higher data-migration volume increase the quoted scope. The exact number is fixed in writing after the scoping call — there is no instant download and no per-seat surprise.