If the review you read last year told you to pair it with Field Service for on-site work, it’s out of date. Since Odoo 19.2, the standalone Field Service app is gone on Odoo Online, and its features now live inside Planning. That one change moved Planning from a shift scheduler to the center of how Odoo runs service delivery, and most guides haven’t caught up.
Odoo Planning is Odoo’s Enterprise app for scheduling employees and equipment into shifts on a drag-and-drop Gantt chart. It links each shift to roles, time off, sales orders, projects, and timesheets, and on current Odoo Online releases it also runs field service jobs: on-site sign-in, worksheets, customer sign-off, and billing.
This review is built from Odoo’s own release notes and documentation. It flags which features depend on your hosting and version, and it calls out a few capabilities that other guides credit to Planning but standard Odoo doesn’t document. By the end, you’ll know whether Odoo Planning fits your team, what trade-offs you’re accepting, and which alternative to trial if it doesn’t.
What is Odoo Planning?
Odoo Planning is a resource scheduling app in Odoo Enterprise that assigns shifts to employees and equipment by role, displays them on a Gantt chart, and publishes them to staff. Shifts can be created manually, generated from templates, or filled by Auto Plan, and they connect to Sales, Project, Timesheets, and Time Off.
Whether you call it the Planning app or the Odoo Planning module, four concepts do all the work. A shift is a block of time. A resource is whoever or whatever fills it: an employee, or a material such as a crane or forklift with its own working hours. A role (technician, consultant, bartender) decides who is eligible for which shifts. A template stores a shift pattern you reuse.
Roles matter more than new users expect. Get them right during setup and almost everything else behaves, including automation. Leave an employee without a role and Auto Plan skips that person entirely.
What Odoo Planning is not
Searches for “odoo planning” pull in three different tools, so rule two out early. Production scheduling (work orders, work centers, manufacturing capacity) happens inside Odoo Manufacturing, not Planning. Manufacturers that need forecasting and constraint-based production planning often add frePPLe, which maintains an Odoo connector for production and inventory planning.
Customer self-booking is also a different job. Letting clients pick a time slot belongs to the Appointments app. Planning schedules your people; it doesn’t open your calendar to the public.
Which version are you evaluating? Your hosting decides
Two companies can both say they “run Odoo 19” and have different Planning apps. Odoo ships its intermediary SaaS versions (19.1, 19.2, 19.3) only to Odoo Online, and online versions aren’t released for Odoo.sh or on-premise installations. Those get major versions only.
The SaaS track changed Planning substantially this year. The Odoo 19.2 release notes (March 2026) discontinued the Field Service app and folded its features into Planning, added multiple resources per shift, let you link a specific task to a shift, and switched worksheet templates from Studio fields to property fields. The same release removed work entries and the Planning-Payroll integration. Odoo 19.3 then added worksheets to shift templates.
| Your hosting and version | Where field service lives | Planning-Payroll link |
|---|---|---|
| Odoo Online on 19.2 or later | Inside Planning | Removed |
| Odoo Online still on 19.0 | Separate Field Service app | Still present |
| Odoo.sh or on-premise on 19.0 | Separate Field Service app | Still present |
| Any hosting after upgrading to Odoo 20 | Inside Planning | Confirm in Odoo 20 notes |
Odoo 20 was presented at Odoo Experience in late September 2026, with general availability expected in mid-October. The practical consequence: if you’re on Odoo.sh and start a free trial on odoo.com today, you’ll be testing the merged app, not the one you’d deploy until you upgrade. Test on the version you’ll actually run.
Odoo Planning features, in detail
Odoo Planning’s core features are:
- Gantt scheduling grouped by resource, role, project, or sales order
- Roles for employees and materials, with a default role per person
- Shift templates and recurring shifts
- Auto Plan to fill open shifts automatically
- Publishing with an employee portal, open shifts, and shift switching
- Conflict warnings for overlapping shifts and time off
- Links to Sales, Project, Timesheets, and Time Off
- Field service tools: worksheets, on-site sign-in, customer sign-off (Odoo Online 19.2+)
Gantt scheduling and shift states
The schedule is a Gantt chart you can group by resource, role, project, or sales order, and every shift can be dragged, resized, or duplicated. What matters for day-to-day planning management is that the chart encodes status visually. Striped shifts are drafts nobody has seen yet. Greyed blocks mark time off. A progress bar means timesheets are being logged against the shift. An orange triangle flags a shift edited after publishing, and a red triangle signals a conflict, such as an overlap or a shift on approved leave.
A scheduler who learns those five signals can audit a week in seconds. Teams on fixed rotations can also copy the previous week’s schedule and adjust the exceptions, which beats rebuilding from templates every Monday.
Roles, resources, and materials
Each employee can hold several roles, with one set as the default. That default wins when Auto Plan assigns open shifts or plans sales orders. Materials get roles and working time too, so a construction firm can schedule a crane under the same rules as the crew that operates it.
On 19.2 and later, one shift can carry several people and materials, with planned hours multiplying by team size. That matches how installation and maintenance crews actually work, where the old model forced one shift per technician. Roles can also carry custom property fields (certifications, work location, language) that appear on every related shift. Those fields inform the person scheduling; they don’t filter who Auto Plan picks.
Shift templates and recurring shifts
Templates store a start time, duration, role, and optionally a project, so a planner drops “technician, 8:00, eight hours” onto the Gantt instead of typing it. Recurring shifts repeat on the pattern you set, which suits weekly maintenance visits, monthly support windows, and subscription contracts. From 19.3, a template can also carry a worksheet, so a recurring inspection arrives with its checklist attached.
Auto Plan: what it actually considers
Auto Plan fills open shifts in one click. Its inputs are worth knowing precisely, because they define its limits. Based on Odoo’s documentation, it weighs:
- Role eligibility (employees with no planning role are excluded)
- Default role priority for people holding several roles
- Approved time off and public holidays
- Each employee’s working schedule
- Contract start and end dates
What’s missing matters as much: travel distance, cost per hour, fairness across the team, and legal rest periods. Auto Plan produces a fast first draft based on availability. It isn’t an optimizer, so budget time to review before you publish.
It also plans sold work. When a service product is linked to a role, the hours on a confirmed sales order appear in Planning waiting to be allocated, and Auto Plan can assign them.
Publishing, self-service, and shift swaps
Nothing reaches staff until you publish. You choose the period, whether to include open shifts, and who gets notified. Employees then see their shifts by email and in a personal portal, and field workers can use that portal without a paid Odoo user.
After publishing, an employee can ask to switch a shift. It stays assigned but becomes visible to colleagues with the same role, and whoever claims it takes it over. The alternative policy, Allow Unassignment, lets staff drop a shift up to a deadline you define. In Odoo 18, turning on unassignment disabled the switch flow, so the two work as either/or. Pick your policy before training anyone, and confirm the behavior on your version.
Sales, Project, and Timesheets integration
This is where Planning earns its place, and where standalone schedulers can’t follow. Sold services link to roles, so a confirmed sales order creates hours to plan. Shifts can be dedicated to a project and, on 19.2 and later, to a specific task. Timesheets logged against a shift appear as progress, and managers compare planned hours with logged hours in the same view.
Billing follows the same chain. On time-and-materials work, the hours and parts recorded on a shift update the sales order and flow to the invoice. On prepaid retainers, scheduled shifts draw down the client’s balance, so a manager sees consumption before the work starts. Quote, shift, timesheet, and invoice all sit in one database with no export in between.
Odoo field service inside Planning
On Odoo Online 19.2 and later, Odoo field service runs from Planning. A technician sees the job in their portal and taps Sign In on arrival, which logs the location. They fill in a worksheet built from standard property fields (no Studio required), attach photos that land in the final PDF report, add materials used, capture the customer’s signature on screen, and tap Complete. Break times are recorded along the way. An “Under warranty” toggle removes the charge and updates stock, and a location button opens directions to the site.
Odoo itself was candid that the merge wasn’t smooth. Its 19.1 and 19.2 release-highlights webinar set aside time for known limitations, regressions, and configuration impacts. If you ran Field Service before, test every flow you depend on before your database upgrades. Live technician tracking on a map and route optimization are announced for Odoo 20, not shipped in 19.x.
Reporting
The Planning analysis view supports pivot tables with export to .xls, which covers hours by role, project, or employee. Planned-versus-logged comparisons come through Timesheets. On 19.2 and later, the old project profitability report was replaced by dedicated budget and margin reports, so margin tracking now sits beside Planning rather than inside it.
Odoo Planning pros and cons
| Area | Pros | Cons |
|---|---|---|
| Integration | Shifts tie to sales, projects, timesheets, invoices | Value drops sharply used standalone |
| Scheduling | Visual Gantt, drag-and-drop, clear status markers | Roles and schedules need careful setup |
| Automation | Auto Plan drafts a schedule in one click | No cost, distance, or fairness optimization |
| Field service | Sign-in, worksheets, sign-off in one app | Merge had known regressions; routing awaits Odoo 20 |
| Self-service | Portal access without paid users | Switch and unassign policies are either/or |
| Compliance | Warns on overlaps and time off | No documented rest or overtime rules |
| Cost | Free as one app; included in Standard | Enterprise only; integrations need paid plan |
| Versions | Fast improvement on Odoo Online | Odoo.sh and on-premise wait for majors |
The biggest pro and the biggest con are the same fact: Planning is designed as one part of Odoo. Inside an Odoo database, it removes the spreadsheets and re-keying between scheduling, timesheets, and invoicing. Outside that context, it’s a capable but ordinary scheduler competing with tools built for nothing else.
User-review evidence is thin. The app has 22 reviews on G2 averaging 4.0, with praise for the interface and complaints about setup complexity. That pattern fits what the configuration demands: roles, working schedules, and contracts all feed the scheduling logic. Flexible-hours staff are a known snag, and Odoo’s own forum shows admins moving working schedules from the employee to the contract to plan them freely.
If you’re judging the whole platform rather than one app, our breakdown of Odoo’s pros and cons covers support, upgrades, and implementation risk.
Does Odoo’s Planning app enforce labor-law rules or skills matching?
Odoo’s Planning app doesn’t enforce labor-law rules or skills matching out of the box, based on Odoo’s documentation. Standard Planning warns when a shift overlaps another shift or approved time off, and Auto Plan respects roles, working schedules, and contracts. Minimum rest periods, weekly hour caps, overtime rules, and certification-based filtering require configuration, custom development, or a specialist tool.
This section exists because several guides ranking for “Odoo Planning” describe rest-period enforcement, skills-based filtering, blocking conflict levels, and night or weekend premiums flowing into payroll as standard features. We couldn’t match those claims to Odoo’s documentation or release notes, and one is contradicted outright: Odoo 19.2 removed the Planning-Payroll integration. Even Odoo Gold Partners writing about Planning describe allocation by skills, certifications, or language as a configuration or customization project.
The fair counterargument: Odoo is open and extensible, so a partner can build rest rules, skill filters, and premium calculations, and some companies need exactly that. It’s a legitimate path, and custom Odoo development exists for it. But it’s a build with a budget and ongoing upgrade maintenance, not a feature you get on day one. Before you sign anything, reproduce every claimed capability in a trial database with your own roles and staff.
Is Odoo good for planning?
Odoo is good for planning when the time you schedule is time you sell or track. Service crews, consultants, installers, and maintenance teams already on Odoo get scheduling, timesheets, and invoicing in one flow. It’s weaker for hourly rostering driven by labor laws and demand forecasts, and production scheduling belongs in Odoo Manufacturing instead.
A quick test before committing to Odoo for planning: list the three things your scheduler deals with after a roster is published. If they’re timesheets, sales orders, and invoices, Planning fits. If they’re a labor-compliance checklist, a sales forecast from your point of sale, and a payroll export, a specialist scheduler will serve you better.
Who is Odoo Planning for?
| Your situation | Fit | Why |
|---|---|---|
| Field service or maintenance on Odoo Online 19.2+ | Strong | Scheduling, sign-off, billing in one app |
| Consulting, agencies, software teams selling capacity | Strong | Sold hours flow to roles and timesheets |
| Installation or construction crews with equipment | Strong | People and machines share one shift |
| Existing Odoo users with a shift-based team | Good | Employees, Time Off, portal already set up |
| Field service on Odoo.sh or on-premise 19.0 | Conditional | Merged app arrives with Odoo 20 |
| Restaurants and retail with volatile hourly demand | Weak | No demand forecasting or labor rules |
| Large dispatch fleets needing routing today | Weak | Route optimization is on the Odoo 20 roadmap |
| Odoo Community users | Not available | Planning is an Enterprise app |
| Manufacturers scheduling production | Wrong tool | Use Manufacturing work order planning |
The strongest fit is a service business where the shift is the billable unit. Say a consulting firm sells 400 hours of a senior developer role: it can see, on the Gantt, whether that capacity actually exists before the project kicks off. A maintenance company sees a visit move from contract to shift to signed worksheet to invoice without anyone retyping it.
The weakest fit is a business that wants a roster and nothing else. Odoo’s free plan will give you Planning alone with unlimited users, and it works. You’ll just be paying for the setup effort of an ERP app while using it like a standalone calendar.
How much does the Planning app cost?
Planning is part of Odoo Enterprise, so it’s priced through Odoo’s plans rather than as a separate app. Odoo’s pricing page lists three options:
- One App Free: the Odoo Planning app alone, unlimited users, hosted on Odoo Online.
- Standard: every app on Odoo Online, per user per month.
- Custom: adds Studio, multi-company, external API access, and Odoo.sh or on-premise hosting.
The free option is real, but the Sales, Timesheets, and Project links that make Planning distinctive are separate apps, which pushes most service businesses to Standard. Rates vary by country, and paid plans show an introductory price for the first 12 months that renews higher, so budget on the renewal rate. Staff who only view shifts through the portal don’t need paid users, which keeps licensing tied to managers and office users. Implementation is billed separately.
Odoo Planning alternatives
SmartStream ERP implements Odoo, Acumatica, and NetSuite, so two of the options below are platforms we also deploy. We’ve grouped the alternatives by the reason you’d leave Planning, because that reason decides the right replacement.
| Alternative | Best for | Beats Odoo Planning on | Trade-off |
|---|---|---|---|
| Deputy | Hourly shift teams | Labor forecasting and compliance | Separate from your ERP |
| 7shifts | Restaurants | Labor cost tied to POS data | Hospitality-specific |
| Homebase | Small hourly teams | Cost-based auto-scheduling, geofenced clock-in | Built for hourly staff, not projects |
| Connecteam | Frontline teams | Scheduling plus team communication | Not an ERP |
| Acumatica Field Service Edition | Mid-market field service | Dispatch, skills, routing, equipment | Full ERP switch |
| NetSuite Field Service Management | NetSuite-based service firms | Skills and proximity dispatch | Service module licensed separately |
| Jobber, ServiceTitan | Trades and home services | Purpose-built field service workflows | Needs a separate ERP |
| OCA Field Service modules | Odoo Community users | Free, open source | Community-supported |
| frePPLe | Manufacturers | Production and inventory planning | Solves production, not staffing |
If your problem is hourly compliance and labor cost, look at specialist schedulers. Deputy is known for automated scheduling with labor forecasting and compliance, 7shifts builds scheduling around labor cost and POS data for restaurants, and Connecteam pairs scheduling with frontline communication. Homebase targets small hourly teams with auto-scheduling based on labor costs and geofenced time clocks. Each can connect to Odoo for payroll or accounting, but you lose the shift-to-invoice chain.
If your problem is dispatch-heavy field service today, compare full ERPs with service built in. Acumatica’s Field Service Edition is one of the few mid-market cloud ERPs that ships dispatch, service contracts, equipment tracking, and full accounting in one product. NetSuite Field Service Management uses a drag-and-drop schedule board that assigns technicians by skills and proximity, creating service orders from cases, sales orders, projects, or customer assets. Pure-play tools like Jobber and ServiceTitan are strong on trade workflows but need an ERP behind them. If you’re weighing a full platform change, our Odoo vs NetSuite comparison covers cost and fit side by side.
If you’re on Odoo Community, Planning isn’t available. The Odoo Community Association maintains an open-source field service project with modules for version 19.0, supported by the community rather than Odoo SA.
If you meant production planning, stay in Odoo Manufacturing for work orders and consider frePPLe for forecasting and constraint-based scheduling. And if you’re questioning Odoo as a whole, not just this app, our guide to Odoo alternatives compares full platforms.
What’s changing in Odoo 20
Partner coverage of Odoo’s roadmap describes Odoo 20 pushing Planning further toward being the single resource engine for the business. Announced items include unified scheduling of resources, roles, and tasks, materials assigned directly to employees, and AI-suggested timesheet entries. Partners have also reported MapBox travel times in the Gantt view, route optimization on the map, live technician locations, customer equipment and intervention history inside Planning, fixed-fee travel time invoicing, and website forms that feed service requests.
Treat all of it as roadmap until it appears in the official Odoo 20 release notes and works in a test database. If live tracking and route optimization ship as described, the “weak” rating for dispatch-heavy fleets in the fit table above deserves a fresh look.
Frequently asked questions
Is Odoo Planning free?
Yes, as your single app on Odoo’s One App Free plan, with unlimited users on Odoo Online. Connecting it to Sales, Timesheets, or Project requires a paid plan.
Is Odoo Planning available in Odoo Community?
No. Planning is an Enterprise app. Community users typically turn to OCA modules or third-party apps.
Can employees see their schedule without an Odoo license?
Yes. Published shifts reach staff by email and through a personal portal that doesn’t require a paid user.
Does Odoo Planning integrate with payroll?
Not on Odoo Online 19.2 or later, where Odoo removed the Planning-Payroll integration and work entries. Base pay on timesheet or attendance data, and check how Odoo 20 handles it before relying on planned hours.
What happened to Odoo Field Service?
It was discontinued as a standalone app in 19.2, and its features now live in Planning. Odoo.sh and on-premise databases on 19.0 keep the separate app until they upgrade to Odoo 20.
How to decide whether Planning fits
Odoo Planning is strongest as the scheduling layer of a service business already running on Odoo, and weakest as a standalone roster tool. The field service merge widened that gap in both directions. Here’s the order we’d evaluate it in:
- Confirm your hosting and version, because that decides which Planning you’d get.
- Write down what happens after a shift is worked: billed, paid, or only recorded.
- Build one real week in a trial database with your roles, templates, and time off, then run Auto Plan.
- Publish it and have two staff members test the portal and shift switching on their phones.
- If you do field work, run one job end to end: sign-in, worksheet, materials, signature, invoice.
- List every gap and price it three ways: configuration, custom development, or an alternative.
If you’d like a second pair of eyes on that list, SmartStream ERP is a certified Odoo Ready Partner that also implements Acumatica and NetSuite, so we’ll tell you plainly when Planning isn’t the answer. Talk to our Odoo team about your scheduling setup.