Skip to content
A technician in a red uniform loading a yellow industrial vacuum into the back of a white van.
A technician at the open doors of a service van, the point where a worksheet leaves the office.

Field service

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

What to test before you trust an offline Odoo worksheet

An offline worksheet is only useful if the technician can open the job, record the work, and have that record survive the journey back to signal. Treat it as a test on the version you will run. Do not accept it as a line in a brochure.

The commercial page for this work is Odoo field service. This article is the test list you run before go live.

What changed in Odoo 20

Odoo 20 discontinued the separate Field Service app and moved its features into Planning (Odoo 20 release notes, checked 6 November 2026). Interventions are now planning shifts, and a shift can carry the customer, the address, the worksheet, the products used, photos and a signature. The mobile experience is part of that shift, not a separate application.

That change matters for this test. A team that knew the old Field Service app cannot assume the same screens, the same buttons or the same offline behaviour. The release notes describe the intent. Only a device test describes what your technicians will get.

Test on the device, not in the demo database

Use the release you will buy, the phone or tablet the technician will carry, and the worksheet template the business actually uses. A test on a desktop browser with demo data proves nothing about a plant room with one bar of signal.

  1. 01Open a job that was assigned before the device lost signal.
  2. 02Record time, a note and a part used.
  3. 03Take a photo and collect a signature if the worksheet asks for either.
  4. 04Do not create a record that the office is also creating while the van is offline.

The fourth step is the one teams skip. If the technician creates a new customer offline while the office creates the same customer, the sync has to resolve two records. Test the conflict before it happens for real.

Test what comes back

The return journey is where an offline feature earns its place. Check each of these on the office screen, not on the device that recorded it.

  • The note, the time and the part appear on the same job, not a duplicate.
  • The stock figure the stores expect is reduced by the part, or the mismatch is explained.
  • Two edits to the same job do not silently drop one of them.
  • The worksheet, photos and signature are attached to the shift the invoice will use.

The limits to write into the scope

Odoo's offline mode is built for short interruptions. The documentation says only records and views opened while the device was online can be reopened offline, attachments and images cannot be uploaded, the cache is capped at 2 GB, and a hard refresh wipes it (Odoo 20 documentation, checked 6 November 2026). Those are scope facts, not footnotes.

A useful scope sentence is: the technician opens the day's shifts before leaving the yard, records the visit offline, and syncs at the next signal. If the job runs for two days in a basement, that sentence is wrong and the process needs a different answer.

Who signs it off

Put three people in the test: one technician, one dispatcher and one person who owns the invoice. The technician tests the device, the dispatcher tests the reassignment, and the invoice owner checks that the time and the part reached the right line. Record the result in the scope, including the parts that failed.

If the test fails, the decision is not automatically a custom module. It may be a different device, a shorter offline window, or a paper fallback that the office enters the same day. Name the fallback before go live, not after the first lost worksheet.

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-offline-worksheets

FAQ

Answers to the questions this article raises

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

01Does Odoo field service work offline?
Odoo has an offline mode for short interruptions, with limits on what can be reopened, uploaded and stored. Test it on your release and your device before you rely on it.
02Who runs the test?
The technical partner, with one of your technicians and the person who owns the invoice, before go live. The United Kingdom is Softhealer. Everywhere else is AppNvent.
03What if the technician needs two days offline?
That is outside the documented short-gap design. Change the process, the device or the expectation, and write the fallback into the scope.

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.