Odoo Field Service Pricing: Modules, Plans and What an On-Site Team Pays
Odoo Field Service now lives in Planning (19.2). See which plan includes it, Enterprise vs OCA Open FSM, 15-tech cost, and how it compares with D365.
Key takeaways
- There is no line item called 'Odoo Field Service.' On-site dispatch, worksheets, mobile time capture, and parts usage ship as part of Odoo's Services stack and are included the moment you pay for either all-apps plan, Standard or Custom.
- Odoo sold per-app licenses years ago; today the platform is three plans, and the plan, not the app picker, sets your per-user cost.
- Field Service capability is covered by both Standard and Custom because both are 'all apps' for a single per-user fee.
- Teams that standardize on Odoo Community cannot use the Enterprise field service features.
What Odoo Field Service Costs
There is no line item called 'Odoo Field Service.' On-site dispatch, worksheets, mobile time capture, and parts usage ship as part of Odoo's Services stack and are included the moment you pay for either all-apps plan, Standard or Custom. You budget the plan price times paying users, not an app SKU and not a per-technician surcharge for Gantt, map view, or on-site invoicing.
On Western/Northern Europe list prices (annual billing), Standard is €24.90 per user per month after the introductory window, and Custom is €44.90; the first 12 months for initial users are discounted to €19.90 and €35.90. Odoo regionalizes pricing heavily: independent scrapes of odoo.com pricelists as of August 2026 show US yearly rates around $31.10 (Standard) and $61.00 (Custom), with monthly billing near $38.90 and $76.20, and Canada near C$44 / C$73 yearly. Always model from a region-specific quote, not a single global number.
A One App Free plan exists on Odoo Online, but a real field-service operation outgrows it almost immediately: jobs need Sales, Inventory, Timesheets, and Accounting beside Planning/Field Service. Community Edition (self-hosted, no Enterprise license) does not include the official Field Service/Planning Enterprise capabilities; teams that stay Community typically use OCA or third-party FSM modules and accept the ops burden. The parts that are extra, and that most worksheets miss, are Odoo.sh hosting if you need custom code, In-App-Purchase credits for OCR and SMS, and one-time implementation via a Success Pack or certified partner.
How Odoo's Per-User Plan Pricing Works
Odoo sold per-app licenses years ago; today the platform is three plans, and the plan, not the app picker, sets your per-user cost. One App Free gives a single app (plus its free dependencies) for unlimited users on Odoo Online. Standard includes every app on Odoo Online. Custom includes every app plus Odoo Studio, multi-company, the external API, and the right to host on Odoo.sh or download Enterprise for self-hosting. All paid plans include unlimited email support, maintenance, upgrades, and Odoo Online hosting when you stay on the managed cloud.
The discount shown on the pricing page is a 12-month introductory rate applied to the initial users you order; after that the regular yearly (or monthly) rate applies. A 'paying user' is an internal person who creates, views, or edits documents in the Odoo backend, Odoo explicitly lists 'an employee who reports their expenses or timesheet' as a paying user. Portal customers and suppliers are free. For field service that means every technician who opens a worksheet, starts a timer, or logs mileage is a paid seat, even if they never touch Accounting.
Because field operations depend on Project/Planning, Timesheets, Inventory, Sales, and Accounting, almost every deployment lands on Standard or Custom. Standard is enough if you host on Odoo Online and need no custom modules. Custom is required the moment you need Studio, multi-company, external API integrations, or Odoo.sh for custom code.
| Plan | Price (intro ~12 mo) | Price (regular yearly) | Hosting | Field Service / Planning? |
|---|---|---|---|---|
| One App Free | €0 | €0 | Odoo Online | No (one-app limit) |
| Standard | ~€19.90/user/mo | €24.90/user/mo | Odoo Online | Yes (all apps) |
| Custom | ~€35.90/user/mo | €44.90/user/mo | Online / Odoo.sh / on-prem | Yes (all apps + Studio/API) |
Which plan includes field service, and what the 19.2 Planning merge changes
Field Service capability is covered by both Standard and Custom because both are 'all apps' for a single per-user fee. Odoo's pricing page states that Standard and Custom include all apps; the Field Service product page is still the marketing entry point for on-site scheduling, map view, mobile worksheets, spare-parts capture, signatures, and prefilled invoicing. There is no Field Service cart line and no per-technician add-on for those features.
Edition boundary: official Field Service / Planning field operations are Enterprise capabilities, not Community core. One App Free on Odoo Online is the only no-cost route and still caps you at one app (plus free dependencies), unworkable for full job-to-cash. If you standardize on Community Edition self-hosting, the official Enterprise field stack is not available at any price; community alternatives include OCA Field Service Management modules and other open FSM addons, with you owning hosting, upgrades, and support.
Since Odoo 19.2 (March 2026 release notes), the standalone Field Service app has been discontinued and its features merged into Planning. Commercial pricing is unchanged: on-site worksheets, time tracking, and resource allocation live inside Planning, which remains part of the all-apps bundle. Your cost calculation does not jump between Odoo 18, 19, and 19.2, you still pay plan×users whether the menu says Field Service or Planning.
The merge changes how people work more than what they pay. Odoo's 19.2 release notes say the Field Service app has been discontinued and its features are integrated into Planning. They also list worksheet templates that use property fields instead of Studio fields, several resources on the same shift, and shifts that link to a specific task. If you run Odoo 19.1 or earlier, you keep the standalone app today. Before you upgrade past 19.2, plan a short process review: the Field Service menu goes away, and worksheet templates built in Studio need to be rebuilt as property-field templates.
| Area | Before 19.2 | From 19.2 |
|---|---|---|
| Where dispatchers work | Separate Field Service app | Planning app |
| Worksheet templates | Designed in Studio; enabling worksheets installs Studio, which may affect your price plan | Property fields instead of Studio fields |
| Technicians per shift | One resource per field service task | Several resources can be assigned to the same shift |
| Link to tasks | Field service tasks in Project | Shifts can be linked to a specific task |
| Plan that pays for it | Standard or Custom | Standard or Custom, no new SKU |
Enterprise Planning vs OCA Open FSM: which edition to buy
Teams that standardize on Odoo Community cannot use the Enterprise field service features. The Odoo Community Association maintains the OCA/field-service repository, known as Open FSM, under AGPL-3.0. Its 19.0 branch lists 34 modules, including territories and branches, equipment and warranty, routes and vehicles, a customer portal and digital signatures. The OCA blog dates Open FSM to 2018 and Odoo SA's own Field Service app to Odoo Enterprise 13 in 2019, with the two teams coordinating early to limit overlap.
Open FSM fits when you need Community licensing, territory models or vehicle-centered stock, and you have an OCA specialist to support it. Enterprise Planning fits when you want Odoo SA's Gantt and map dispatch, worksheets and the Sales to task to invoice flow inside one standard rollout. The two are not drop-in equivalents. Open FSM has its own data model and upgrade path, so the edition decision should come before any configuration work.
On cost, Community has no seat fee, but you pay for hosting, upgrades and support yourself, and the OCA modules still need configuring and testing. For a 20 to 100 person trades business, price both paths with the same job in mind before committing.
| Decision factor | Odoo Enterprise (Planning) | OCA Open FSM (Community) |
|---|---|---|
| Edition | Enterprise, Standard or Custom plan | Community, AGPL-3.0 modules |
| Who supports it | Odoo SA plus your implementation partner | The OCA community plus a specialist implementer |
| Sales to job to invoice | Built into Sales, Timesheets and Accounting | Bridge modules for sales, accounting, stock and timesheets that you configure |
| Territories, routes, vehicles | Basic resource and role model | Modules for territories, routes, vehicles and equipment |
| Seat cost | Plan price × paying users | None; hosting, upgrades and support are yours |
Timesheets: Included, Not a Paid Add-On
Timesheets is bundled into Standard and Custom, not a Harvest-style parallel subscription. Odoo groups it with Projects, Helpdesk, and Planning in its Services implementation estimator. The timer a technician starts from a field task writes to Timesheets on the same database at no extra license cost.
Time tracking is the spine of field-service billing. Timer → task → timesheet lines → draft invoice → Accounting is one record chain under one per-user fee. For a 15-technician team that is 15 seats of time tracking absorbed into the plan rather than billed as a second SaaS. Odoo even positions Timesheets against standalone time tools on its pricing comparisons.
Where Timesheets can generate extra cost is usage, not licensing. AI digitization of paper timesheets, SMS reminders to technicians, or lead-generation services that pull jobs into CRM consume In-App-Purchase credits. The timer, weekly grid, and project profitability reports themselves are included.
What the mobile app does and what it costs
Odoo's product page says technicians can manage an appointment from start to finish in the mobile app: complete the worksheet, record the spare parts used and bill them to the client, log the time spent, and collect employee and client signatures. Because the app writes back to the same task or shift, the coordinator sees the result in Planning and accounting sees it at billing time.
None of this is a separate fee. The cost sits in seats and setup. Every technician who logs time or parts needs a paying user. On 19.0 and earlier, the worksheet documentation notes that designing templates installs Studio, which may affect your price plan, so check whether you need the Custom plan. From 19.2, property-field templates remove that dependency.
Before go-live, test the app on real van routes and in dead zones, and confirm offline behavior in a demo database rather than from a feature list. Budget Success Pack hours for worksheet design per job type and for a short technician training session.
Travel Expenses, Mileage, and Reinvoicing to the Job
Travel and expense handling ships in the Expenses app, also bundled into all-apps plans. Odoo groups Expenses under Human Resources and Finance and positions it against Expensify-class tools. A technician can log mileage, photograph a hotel receipt, submit for approval, post to Accounting, and, when configured, reinvoice travel to the customer on the same job that carries labor and parts.
That single-record model is the economic argument for Odoo in field service: timesheet hours, expense lines, and spare parts can land on one task/sales order and flow to one invoice without paying for three products. Multi-currency, approval chains, and per-diem style policies are configuration work, not extra seats.
The genuine add-on cost is receipt scanning. Document Digitization (OCR/AI for receipts and vendor bills) is billed via IAP credits, typically one credit per digitized document, not via the plan fee. Teams that snap hundreds of receipts a month should budget credits explicitly; 'Expenses is included' does not mean 'unlimited OCR is included.'
How Time, Parts, and Mileage Become an Invoice
The cost model only makes sense if you understand the job-to-cash path that Standard/Custom already pays for. A typical flow: a sales order or helpdesk ticket creates a Planning/Field Service task; the dispatcher assigns a resource on the Gantt or map; the technician records time with the integrated timer, logs parts from Inventory (van stock or warehouse), and submits mileage/expenses; signatures and worksheet answers close the visit; Accounting raises an invoice from the sales order or timesheet/expense lines, often on-site from the mobile app with prefilled forms.
What you are not buying separately: a dispatch SaaS, a time tracker, an expense app, a basic inventory tool, and an invoicing tool. What you are still responsible for: clean product/service catalog design (fixed-price vs time-and-materials), pricelists for travel and after-hours rates, van-stock replenishment rules, and who is allowed to confirm invoices. Those are implementation and process costs, not license SKUs.
If you only need quote → schedule → invoice for a single trade and never want ERP depth, a Jobber-class product can be simpler on day one. The moment you need warehouse parts, multi-company accounting, manufacturing or rental of equipment, or one ledger for office and field, the all-apps fee starts to look cheaper than stitching five subscriptions, even before you count integration maintenance.
Two billing patterns dominate service SMEs. Fixed-price jobs: sell a service product that creates a task on confirmation; technician completes the worksheet; invoice the sales order as ordered (parts overages can be added as extra order lines). Time-and-materials: service product invoices based on timesheets and delivered products; every minute and every part becomes revenue only if technicians log them, which is why paid seats for techs are non-negotiable even when owners wish portal-only pricing applied. Hybrid retainers (prepaid hours + overage) usually need Studio or careful product setup on Custom, which is a commercial reason some multi-branch firms leave Standard.
Hosting: Free on Odoo Online, Paid on Odoo.sh
Hosting is free if you stay on Odoo Online, the managed cloud that ships with paid plans. It comes with the plan, with no separate hosting line. For a field-service SME running Planning/Field Service, Sales, Accounting, Inventory, and Timesheets out of the box, Online is usually enough and adds zero hosting cost on top of plan fees.
Hosting becomes a paid line on Custom when you choose Odoo.sh for custom modules, CI branches, and multi-environment development. Odoo.sh pricing is additive to the Enterprise license: the odoo.sh pricing page charges per worker per month, per staging environment and per GB of storage, with dedicated hosting required above 16 workers or 512 GB. Read the current figures on odoo.sh/pricing, because the sliders and your region change the quote. The license never includes Odoo.sh; Online hosting is the free path.
The trigger for Odoo.sh is technical, not functional: custom modules, branch-based development, or integrations that need the full external API deployment model your partner designs. A configuration-led field rollout on Online pays nothing for hosting. Decide whether van stock, worksheets, and billing can live in standard apps before you budget a CI platform.
Implementation: Success Packs and Partner Work
Implementation is the largest year-one variable and is sold separately from licensing. Odoo Success Packs are prepaid consultant-hour blocks. Packs run from a 4-hour Starter through a 200-hour Pro engagement.
As published on odoo.com/pricing-packs (EUR list, October 2026), returning-customer prices are €587.06 (Starter, 4h), €3,100 (Basic, 25h), €5,500 (Standard, 50h), €9,900 (Custom, 100h) and €19,800 (Pro, 200h). New customers get an automatic 15% off the first pack: €499, €2,635, €4,675, €8,415 and €16,830. Travel time is billable; travel expenses are billed separately. Currency display can follow your account region, so treat these as the official pack structure and confirm the invoice currency before purchase.
Above roughly 50 employees, Odoo steers buyers to certified partners. Independent 2026 guides still cluster small-business implementations around $5,000 to $15,000, mid-market $15,000 to $60,000, and large/complex $60,000 to $200,000+, with custom modules often $1,500 to $10,000+ each. A field rollout that touches dispatch, mobile worksheets, van inventory, and invoicing usually sits mid-market unless workflows are unusually standard.
| Pack | Hours | New customer | Returning customer |
|---|---|---|---|
| Starter | 4 | €499 | €587.06 |
| Basic | 25 | €2,635 | €3,100 |
| Standard | 50 | €4,675 | €5,500 |
| Custom | 100 | €8,415 | €9,900 |
| Pro | 200 | €16,830 | €19,800 |
Implementation Sequence: Parts, Scheduling, Then Billing
Budgeting hours is easier when you phase the build in the order operations depend on. Phase 1, products and inventory: service products, parts, van locations or kits, reordering rules, and barcode habits. Without clean stock masters, technicians cannot consume parts on the job and your invoice will miss materials.
Phase 2, planning and mobile: resources, working schedules, Planning/Field Service tasks, worksheet templates, map/Gantt habits, and who may reassign work. This is where Success Pack hours disappear fastest if roles and SLAs are unclear. Phase 3, time, expenses, and billing: timesheet policies, mileage products, expense categories, tax mapping, and the invoice trigger (order-based vs timesheet-based vs mixed).
Skipping ahead to pretty dispatch boards before inventory and invoice rules are ready creates a double cost: rework in configuration and eroded trust when the first month's invoices are wrong. For a 10 to 20 person service firm, a Basic or Standard Success Pack often covers a configuration-led path; multi-branch, multi-company, or heavy Studio work pushes you toward Custom/Pro packs or a partner SOW.
Concrete configuration checklist that burns Success Pack hours: resource calendars and skills/tags for dispatch; worksheet templates per job type (HVAC install vs emergency callout); tax-inclusive vs exclusive service products; after-hours pricelists; default analytic accounts so every job hits the right P&L; portal access for customers to approve quotes without becoming paid users; and UAT scripts that force a full cycle, quote, schedule, parts consume, timesheet, expense, invoice, payment, before go-live. Skipping UAT on the invoice step is the most expensive shortcut in field ERP.
Total Cost of Ownership: 5, 15, and 20 User Examples
These examples use Western Europe regular yearly list prices for licenses (€24.90 Standard / €44.90 Custom), published Success Pack EUR figures, and a rough IAP allowance. They are shapes, not quotes, US and Canadian buyers should swap in regional rates from the geo-pricing section.
Example A, 5-technician HVAC SME, Standard, Odoo Online, Basic Success Pack. License at regular rate: 5 × €24.90 × 12 = €1,494/year (intro year nearer 5 × €19.90 × 12 = €1,194). Hosting is €0 on Online and IAP stays a modest receipt and SMS pack. Implementation: Basic pack at €2,635 for a new customer. Year one is dominated by implementation; steady state is license + small IAP.
Example B, 15 field techs + office seats counted as 15 paying users on Standard, Online, Standard Success Pack. License: 15 × €24.90 × 12 = €4,482/year regular (€3,582 at €19.90 intro). Hosting €0. IAP: plan for higher SMS (appointment reminders) and OCR if every tech photographs receipts, still usually far below license. Implementation: Standard pack, €4,675 for a new customer if workflows stay standard; partner SOW if multi-branch. At the US list of $31.10 Standard yearly: 15 × $31.10 × 12 ≈ $5,598/year license alone, still one fee for field + accounting + inventory.
Example C, 20-user multi-branch on Custom with Odoo.sh and partner customization. License: 20 × €44.90 × 12 = €10,776/year regular. Odoo.sh: workers + staging + storage on top of license (reconfirm current worker/environment rates). Implementation: A Standard pack (€4,675 for a new customer) covers configuration only; custom modules and data migration often exceed pack hours. Here hosting + services can rival or exceed year-one license, plan for that pattern once you leave pure Online configuration.
Devices are rarely in the Odoo invoice but always in the project budget. Budget rugged phones or tablets, connectivity for basements and rural sites, and optional barcode hardware if van stock is serious. Odoo Online does not charge per device, only per paying user, so two devices for one technician still cost one seat if only that person logs in. Shared 'crew' logins violate both security practice and Odoo's user definition; plan one seat per human who creates or edits operational documents.
| Component | 5-user SME (Standard, Online) | 15-user crew (Standard, Online) | 20-user mid-market (Custom, Odoo.sh) |
|---|---|---|---|
| License (regular, 12 mo) | €1,494 | €4,482 | €10,776 |
| Hosting | €0 (Online) | €0 (Online) | Workers + staging + storage |
| IAP credits | Small | Moderate (SMS + OCR) | Higher volume |
| Implementation (one-time) | €2,635 Basic (25h) | €4,675 Standard (50h) | Pack + partner SOW |
| Custom dev (if needed) | None | Rare on Online | €/module or day-rate |
Geo-Pricing, US/Canada Rates, and 2026 Surcharges
Odoo does not charge one global price. Independent analysis of odoo.com pricelists documents roughly a dozen tiers across eight currencies and 179 countries, with Standard yearly rates spanning about $8.95 to $31.10+ depending on country and Custom yearly from about $13.60 to $61.00 in major USD lists (monthly billing higher). Western Europe list figures in this guide (€24.90 / €44.90 yearly regular) are not what a US buyer should model.
As of August 2026 scrapes of the USA/Americas pricelist, Standard is about $31.10 per user per month yearly ($38.90 monthly) and Custom about $61.00 yearly ($76.20 monthly). Canada list figures sit near C$44 Standard and C$73 Custom on yearly billing. Partner commentary in early 2026 described US/Canadian subscription increases of up to roughly 30% taking effect around the 2026 cycle, which is why North American TCOs must use a current quote, not a European blog post.
Separately, Odoo introduced a 25% surcharge for legacy (non-covered) Enterprise versions for contracts renewed after mid-2025, with charging described as starting April 2026 for customers still on unsupported versions. That is a version-support fee, not the Field Service app price. Field-service buyers on Online stay on current versions automatically; self-hosted and long-running Odoo.sh custom databases should factor upgrade cost versus the 25% surcharge. Also watch contract indexation clauses (reports of up to ~7% annual adjustment language on new/renewed contracts).
UK and other Western European buyers should still verify on odoo.com from a local IP or via the pricing configurator: published Western/Central Europe lists cluster at the €24.90 / €44.90 yearly regular band used in this guide, while monthly billing is higher (about €31.10 / €56.90 on independent scrapes). Multi-year US options on some pricelists exist but savings beyond annual billing are modest compared to the lock-in, treat multi-year as a finance decision, not a Field Service feature decision. When comparing vendors, normalize to the same currency, the same number of paying technicians, and the same inclusion of accounting and inventory; raw 'per user' headlines mislead when one product is FSM-only and the other is all-apps ERP.
Odoo vs Jobber-Class Tools vs Dynamics 365 Field Service
Three different buying motions get compared in the same RFP. Jobber-class field service software is a vertical SaaS for trades: fast quoting, scheduling, and payments. Dynamics 365 Field Service is a deep Microsoft stack product with optional optimization and Copilot/agents. Odoo is an ERP suite where field operations are one slice of an all-apps seat.
Dynamics 365 Field Service list pricing (Microsoft, paid yearly) is about $105 per user per month for the full Field Service license and about $50 per user per month for the Field Service Contractor license. That seat is primarily field service, not a substitute for full financials, warehouse, or manufacturing, which are other Dynamics or Business Central SKUs. Resource Scheduling Optimization and Copilot Credits can add further usage cost. For 15 full FS seats: 15 × $105 × 12 = $18,900/year in FS licenses alone before Azure, RSO, or partner implementation.
Jobber's public pricing page lists Core at $21/month for one user in year one ($29 after 12 months) on annual billing, with Connect and Grow above it. Its Plus tier covers 15 users at $371/month in year one and $399/month after, which is $4,788/year. That is often cheaper pure-play scheduling/payments for a small crew that already has QuickBooks and does not need warehouse-grade inventory or multi-company ERP. It is not an all-in ERP replacement.
Odoo wins the TCO argument when one database must cover field + inventory + accounting + sales without five integrations. It loses the 'set up this afternoon' argument against Jobber for a five-person lawn-care crew, and it loses deep automated optimization and Microsoft ecosystem depth against D365 Field Service with RSO. Feature-level Odoo capability (worksheets, mobile, the Planning merge) is covered in our Odoo Field Service module guide; the D365 license breakdown lives in our Dynamics 365 Field Service pricing guide.
A practical shortlist rule for 2026: under ~8 techs, QuickBooks + Jobber (or similar) often ships faster and cheaper for pure residential trades; 8 to 40 techs with warehouse parts, multi-entity accounting, or manufacturing/rental of equipment should model Odoo Standard Online before buying a third integration; Microsoft-centric enterprises with IoT, complex SLAs, and need for Resource Scheduling Optimization should cost D365 Field Service properly, including the FS seat, Contractor seats for subcontractors, and any Copilot Credit burn, rather than assuming Odoo's Gantt equals automated optimization. Practitioner chatter still celebrates Odoo Community as '$0 forever' against Salesforce/SAP sticker shock, but field-service buyers who need official Enterprise worksheets and support should price Standard/Custom seats at their real cost rather than assuming Community covers the same ground.
| Option | Public license shape | 15-seat annual cost | Best fit |
|---|---|---|---|
| Odoo Standard (EU list) | €24.90/user/mo yearly, all apps | ≈ €4,482 (EU) / ≈ $5,598 (US $31.10) | SME needing ERP + field in one DB |
| Odoo Custom (US list) | ~$61/user/mo yearly + optional Odoo.sh | ≈ $10,980 license | Multi-company, Studio, custom code |
| Jobber Plus | $399/mo at 15 users after year one, annual billing | ≈ $4,788 | Trades FSM without full ERP |
| D365 Field Service | $105/user/mo yearly (full FS) | ≈ $18,900 FS only | Microsoft stack, advanced optimize |
When Odoo fits, and when to pick Dynamics 365 instead
Odoo fits trades and service businesses that want dispatch, on-site work, parts and billing in one system: HVAC, plumbing, electrical, facilities, equipment repair, and IT or AV installation. It is strongest when you already run, or plan to run, Sales, Inventory, Helpdesk or Accounting in Odoo, because the field record flows straight into those apps.
Choose Dynamics 365 Field Service instead when you need constraint-based route optimization across many technicians, which Microsoft covers with Resource Scheduling Optimization, or deeper asset and IoT-driven service. Before you decide, trace three real jobs through the system: a sold installation, a repair escalated from the helpdesk, and a warranty revisit. If all three flow cleanly from Planning through Sales, Inventory and invoicing, Odoo is usually the right call.
How Flectic can help
Flectic implements Odoo for companies of 20 to 100 people in the US and Canada that schedule technicians and want time, parts and mileage to flow into invoices from one database. We choose the edition and hosting with you before work starts, and the written proposal gives each phase a fixed price. Core operations (four to six apps, a basic data import, up to 25 users) has a planning range of $6,000 to $30,000, not a quote. Review the Odoo implementation scope, then Book a free discovery call.
Sources
Standard €24.90 and Custom €44.90 per user a month on yearly view, €19.90 and €35.90 for the first 12 months on initial users; Custom adds Studio, Multi-Company, External API and Odoo.sh or on-premise hosting.
odoo.comCheckedSuccess Packs: Starter 4h to Pro 200h, EUR prices, 15% off a new customer's first pack.
odoo.comCheckedOdoo.sh is priced per worker, per staging environment and per GB; dedicated hosting above 16 workers or 512 GB; excludes the Enterprise license.
odoo.shCheckedIn-app purchases (IAP), Odoo 19 documentation
odoo.comDocument Digitization IAP service
iap.odoo.comMobile app: complete worksheets, record spare parts billed to the client, log time per appointment, collect employee and client signatures.
odoo.comCheckedThe Field Service app has been discontinued and merged into Planning; worksheet templates use property fields; several resources can share a shift; shifts can link to a task.
odoo.comCheckedUS yearly $31.10 Standard and $61.00 Custom (monthly $38.90 and $76.20); Canada yearly C$44 and C$73 (oec.sh listing of odoo.com pricelists).
oec.shCheckedVentorTech, legacy 25% surcharge and US/Canada 2026 subscription increases
ventor.techDynamics 365 Field Service pricing ($105 full / $50 Contractor, yearly)
microsoft.comCheckedJobber annual billing: Core $21/mo year one then $29; Plus 15 users $371/mo year one then $399.
getjobber.comCheckedOdoo Implementation Costs in 2026, globalteckz (SMB to large ranges)
globalteckz.comOdoo Pricing Configurator (on-prem / Odoo.sh options)
odoo.comX post, Odoo Community free narrative vs SAP/Salesforce/Dynamics seat prices (Jul 2026)
x.comX post, Odoo Community FSM modules for Odoo 19 field ops gaps (Feb 2026)
x.comOCA/field-service is AGPL-3.0 and its 19.0 branch lists 34 modules including territories, equipment warranty, routes, vehicles, portal and signatures.
github.comCheckedEnabling worksheets installs Studio, which may affect the price plan; required fields must be filled before a worksheet is saved.
odoo.comCheckedOpen FSM OCA was released in 2018; Odoo SA launched its Field Service app with Odoo Enterprise 13 in 2019.
odoo-community.orgChecked
Frequently asked questions
Is there a separate price for the Odoo Field Service app?
No. Field Service capabilities are bundled into the all-apps Standard and Custom plans; there is no standalone Field Service SKU or per-technician surcharge for Gantt, worksheets, or on-site invoicing. Since Odoo 19.2 the standalone Field Service app is discontinued and features live in Planning, still covered by the same all-apps fee.
How much does Odoo Field Service cost per user in 2026?
You pay the plan rate, not an app rate. Western Europe regular yearly list is about €24.90/user/month Standard and €44.90 Custom (first year €19.90 / €35.90 for initial users). US yearly list scrapes as of August 2026 show about $31.10 Standard and $61.00 Custom ($38.90 / $76.20 monthly). Canada is near C$44 / C$73 yearly. Get a region-specific quote.
What does a 15-technician Odoo Field Service rollout cost?
License floor at EU Standard regular rates: 15 × €24.90 × 12 ≈ €4,482/year if all 15 are paying users (US Standard ≈ 15 × $31.10 × 12 ≈ $5,598/year). Add a Success Pack (often Basic to Standard, roughly €2,635 to €4,675 for a new customer on the EUR pack list) or partner SOW, plus IAP for SMS/OCR. Hosting is €0 on Odoo Online. That single seat fee also covers Accounting, Inventory, Sales, and Timesheets, compare carefully to D365 FS at $105/user/month for the field product alone.
Can I run Field Service on the free One App Free plan or Community Edition?
One App Free gives one app plus free dependencies on Odoo Online, which is operationally insufficient for full job-to-cash (you need Sales, Inventory, Timesheets, Accounting alongside Planning/Field Service). Official Enterprise field features are not in Community Edition; Community teams use OCA/Open FSM-style modules and self-fund hosting, upgrades, and support.
How much do Odoo Success Packs cost in 2026?
On odoo.com/pricing-packs (EUR), returning customers pay €587.06 / €3,100 / €5,500 / €9,900 / €19,800 for Starter through Pro (4 to 200 hours). New customers get 15% off the first pack (€499 to €16,830). Travel is extra. Above ~50 employees, Odoo usually recommends a certified partner instead of packs alone.
Is Odoo cheaper than Jobber or Dynamics 365 Field Service?
Depends on scope. Jobber Grow-class tiers can be a few thousand dollars per year for a ~15-user trades crew and win on pure FSM simplicity. Dynamics 365 Field Service lists about $105/user/month yearly for full FS (~$18,900/year for 15 seats) before other ERP modules. Odoo is usually lower TCO when you need field + inventory + accounting in one system; it is not always the cheapest pure scheduling tool and does not match D365 RSO-depth optimization out of the box.
Did Odoo raise prices or add surcharges in 2026?
Yes on multiple fronts. US/Canada subscription list prices moved up (partner reports of up to ~30% regional increases; current US Custom yearly ~$61 and monthly ~$76.20 on independent scrapes). Separately, a 25% surcharge for legacy unsupported Enterprise versions is described for renewals after mid-2025 with charging from April 2026 if you remain off covered versions. Model from a live quote and check your contract's indexation clause.
Does every field technician need a paid Odoo seat?
Yes, if they create, view, or edit backend documents, including timesheets, worksheets, expenses, or inventory moves. Odoo lists employees who report timesheets or expenses as paying users. Customer portal users who only view their own invoices or appointments are free. Shared logins are a compliance and audit risk and do not reduce legitimate seat count.
Is Odoo Field Service still a separate app after version 19.2?
No. Odoo 19.2 release notes state the Field Service app has been discontinued and its features are integrated into Planning. Marketing pages may still say Field Service, and older databases retain history, but commercially you still buy Standard or Custom all-apps seats, the merge does not create a new SKU or remove the capability from paid plans.
What is the difference between Odoo Enterprise field service and OCA Open FSM?
Enterprise field service is Odoo SA's product, now part of Planning, and is paid for through the Standard or Custom plan. Open FSM is a set of AGPL-3.0 modules from the Odoo Community Association for Community Edition, with territory, vehicle and equipment modules. Open FSM has no seat fee, but you carry hosting, upgrades and support yourself.