Odoo Maintenance documentation describes internal equipment and corrective or preventive work; Field Service documentation describes customer service-task workflows. Begin by separating equipment your business maintains for its own use from work sold to a customer. Agree the record owner and the relationship between equipment, inventory identity and service jobs, then demonstrate those relationships. Do not assume that an internal maintenance record provides a complete customer-equipment or oilfield asset-management model.
Understand the decision
In this illustrative exercise, a contractor maintains its own workshop equipment and also repairs equipment under customer jobs. Both records use similar equipment names. The review must preserve who owns the equipment, where the work belongs and whether the resulting cost is internal or part of a commercial job, without silently merging the histories.
Work through the requirements
- Classify each sample as company equipment, customer equipment or stock awaiting a commercial decision
- Name the system of record and owner for equipment identity and work history
- Demonstrate any required relationship with customer jobs and inventory movements
- Review unresolved asset, inspection and operational-system requirements as separate scope
| Record or decision | Why it matters |
|---|---|
| Equipment ownership register | Separates internal responsibility from customer work |
| Maintenance or service reference | Identifies the purpose of the work record |
| Identity relationship map | Defines how equipment, stock units and jobs relate |
| Scope-gap register | Makes unproven specialist requirements reviewable |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
Avoid importing every piece of equipment into one undifferentiated list. Ownership, commercial responsibility and the authority for operational records determine the relationship to test, not a shared label on two source files.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Oil & gas in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19.0: Field Service product management ↗Odoo 19.0: product tracking with lots and serial numbers ↗Odoo 19.0: project profitability ↗Odoo 19.0: maintenance setup for internal equipment ↗Government of Alberta: About Oil ↗