Odoo Field Service Pricing What an On-Site Team Actually Pays

What Odoo Field Service Actually 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 €37.40; the first 12 months for initial users are commonly discounted to about €19.90 and €29.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$69 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 genuinely 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 unlocks every app on Odoo Online. Custom unlocks 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, offline-capable Enterprise mobile patterns that your partner confirms for your version, or Odoo.sh for custom code.

Which Plan Includes Field Service (and the 19.2 Planning Merge)

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.

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.

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 actually 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.

The Hidden Layer: In-App-Purchase (IAP) Credits

Published plan prices cover licensing and Online hosting, but usage-based In-App Purchases sit on top. Odoo's documentation lists IAP services; for field service the high-impact ones are Document Digitization (OCR of expenses and vendor bills), SMS (appointment reminders and technician alerts), partner autocomplete, and lead generation. Odoo's pricing FAQ also calls out AI scanning of vendor bills and expenses as outside the plan fee.

Digitizing one document typically consumes one credit. SMS is per message/segment. None of these are capped by Standard or Custom — they are pay-as-you-go credit packs bought in-app, with pack prices varying by service and region. Budget monthly receipt volume and SMS volume, then confirm the current pack price inside your database before locking a TCO model.

Keep IAP predictable by auto-digitizing only document types that pay for themselves (vendor bills, employee receipts) and leaving low-value scans manual. SMS appointment reminders often justify themselves in reduced no-shows; blast marketing SMS is where costs surprise people.

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. That covers storage within Odoo's published free-tier limits (unmetered storage up to 100GB under acceptable-use rules on recent pricing FAQs), daily backups, monitoring, and upgrades, 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: published configurator figures commonly show shared workers in the roughly $57–$72 per worker per month band, staging environments charged per environment, storage near $0.20/GB, and dedicated options higher — always reconfirm on odoo.sh/pricing because sliders and 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. Odoo cites a 98% implementation success rate with a Success Pack versus 65% self-service. Packs run from a 4-hour Starter through a 200-hour Pro engagement.

As published on odoo.com/pricing-packs (EUR list), returning-customer prices are about €329 (Starter, 4h), €1,700 (Basic, 25h), €3,000 (Standard, 50h), €5,400 (Custom, 100h), and €10,800 (Pro, 200h). New customers get an automatic 15% off the first pack — about €280, €1,445, €2,550, €4,590, and €9,180 respectively. 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–$15,000, mid-market $15,000–$60,000, and large/complex $60,000–$200,000+, with custom modules often $1,500–$10,000+ each. A field rollout that touches dispatch, mobile worksheets, van inventory, and invoicing usually sits mid-market unless workflows are unusually standard.

Implementation Sequence: Parts, Scheduling, Then Billing

Budgeting hours is easier when you phase the build in the order operations actually 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–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 / €37.40 Custom), published Success Pack EUR figures, and illustrative IAP. 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 €0 on Online. IAP: modest receipt/SMS pack. Implementation: Basic pack ~€1,445 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 ~€2,550 new-customer if workflows stay standard; partner SOW if multi-branch. US illustration at $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 × €37.40 × 12 = €8,976/year regular. Odoo.sh: workers + staging + storage on top of license (reconfirm current worker/environment rates). Implementation: Standard pack floors configuration; 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, offline-tolerant 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.

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 / €37.40 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$69 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 / €37.40 yearly regular band used in this guide, while monthly billing is higher (about €31.10 / €46.80 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 publishes Core from about $29/month (1 user, annual), Connect and Grow as team-sized tiers — for example Grow including 15 users around $399/month on annual billing ($4,788/year) on the public pricing page, with higher month-to-month rates. 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–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 honestly rather than assuming Community covers the same ground.

Frequently asked questions