Skip to content
A service driver in a blue hoodie on the phone in the cab of a white van, ID badge visible.
A service driver checking a device in the van cab, the visit behind a maintenance agreement.

Field service

Author
Clovis de Bontin
Published
6 November 2026
Reading time
6 min read
All articles

Maintenance agreements in an Odoo field-service scope

A maintenance agreement is a customer paying to be covered, rather than paying per visit. The scope has to say what the fee includes, which visits are still chargeable, and which parts are extra.

This sits on the field-service offer. In Odoo 20 the separate Field Service app is discontinued and its features sit inside Planning. Confirm that Planning, Timesheets, Inventory and Helpdesk are the apps in the edition you will buy.

A fee for cover, not a visit

The commercial idea is simple. The customer pays a fee, and the visits in the agreement are covered. The operational idea is harder. Someone has to know which visits are covered, which parts are included, and what happens when the customer calls on a Sunday.

If the agreement lives in a PDF and the visits live in the dispatch tool, the office decides coverage by reading both. That is where the margin leaks and the arguments start.

Who owns the agreement

An agreement has an owner on each side. On your side, someone has to decide whether a visit is covered, approve a goodwill repair, and renew the agreement before it lapses. On the customer's side, someone has to know what the agreement includes and who can call it in.

If nobody owns it, the agreement becomes a discount. The customer calls, the office sends an engineer, and the visit is absorbed because arguing about coverage costs more than the visit. Write the owner and the escalation path into the process, not only the contract.

The terms that change the build

  • Is the fee per site, per asset, or per year?
  • How many visits are included, and what happens to the next one?
  • Are parts included, excluded, or included up to a value?
  • Does a breakdown outside hours use a different rate?
  • What response time is promised, and does the customer see it?
  • Who renews the agreement, and what ends it?

Each answer becomes a field, a rule or a report. A per-asset fee needs an asset register. A visit allowance needs a counter that resets at renewal. An out-of-hours rate needs a calendar and a price list. None of that is optional if the agreement is going to be operated rather than filed.

Where it lives in Odoo

There is no single correct answer. Some companies use Subscriptions to invoice the fee on a schedule. Some put a contract on the customer and raise visits against it. Some use an invoice schedule and a report. The choice depends on the edition, the number of agreements and how the customer wants to be billed.

Discovery should choose one and write it down. Mixing two models is how a business ends up with a covered visit that nobody can find and a part that was invoiced twice.

Renewal is the test of the data model. If the agreement has a start date, an end date and an allowance, the renewal report can show what expires in the next 60 days and what the customer used. If the agreement is a PDF, the report is a calendar reminder and a guess. Add the renewal date to the scope before the first agreement is loaded.

What to test before go live

  1. 01Create an agreement for one customer, with a start date and a renewal date.
  2. 02Book a visit inside the allowance and confirm it is covered.
  3. 03Book a second visit outside the allowance and confirm it is chargeable.
  4. 04Add a part that the agreement excludes, and check the invoice line.
  5. 05Renew the agreement and confirm the allowance resets.
  6. 06End the agreement early and confirm the remaining visits are handled as the contract says.

I sincerely hope this was helpful, and if you have any remark, suggestion or question, you can email me at louis@cdb.solutions or DM me on LinkedIn.

Thank you,

Clovis

Next step

See this in practice

Book a free demo. The technical partner for your country shows the apps that fit, at no charge.

Canonical URL: https://www.cdb.solutions/articles/odoo-maintenance-agreements

FAQ

Answers to the questions this article raises

The questions buyers ask most, answered here. If yours is not covered, ask us directly.

01Is a maintenance agreement a subscription?
It often is. Whether you use the Subscriptions app, a contract on the customer, or an invoice schedule is a discovery choice, not a default on this page.
02Do you publish a fee?
No. The fee depends on the assets, the visits and the risk you are carrying. We do not publish a number without those inputs.
03Can the customer see what is covered?
If the agreement is recorded in Odoo, the portal can show the agreement and its visits. Whether the customer should see the allowance is a commercial decision, not only a technical one.

Next step

Book a free demo

Tell us the country and the operation. The technical partner for your country shows Odoo against your process, at no charge.

+33 7 69 45 83 27UK with SofthealerEverywhere else with AppNvent

Free demo

Put this against your own operation

Country, industry and company size. The technical partner scopes the work and holds the agreement.

  • Country chooses the partner. The UK is implemented with Softhealer. Everywhere else, with AppNvent.

  • The demo is specific. Industry and company size tell the technical partner which apps to show you.

  • No charge, no obligation. Scoping and any agreement come later, and only if you want them.

Tell us about the operation

01/06

United Kingdom: we implement with Softhealer, our technical partner. The agreement is with Softhealer.

Optional
Optional

Routed to Softhealer for United Kingdom. See our privacy policy.