A dispatcher sends a technician to an urgent repair without a quotation. The duration and replacement parts are unknown, but finance still needs an authorized, explainable invoice. This is the starting point of the unquoted intervention demonstrated in Odoo’s services webinar, where the presenter describes moving Field Service into Planning.
Evaluate the proposed consolidation through complete service scenarios, not an app count. Require an unquoted repair and recurring maintenance to run from scheduling through delivery evidence and billing reconciliation. Accept the workflow only when service operations and finance agree on the results. Otherwise, explicitly approve a process change or defer migration until a verified solution meets the requirement.
Establish what the demonstration must prove
The webinar explains the consolidation partly through Planning’s draft-and-publish scheduling model: an assignment can be prepared before publication notifies the employee. That distinction matters operationally. Ask dispatchers to demonstrate preparation, publication and reassignment, including which customer and employee communications should occur at each handoff.
Odoo’s version-labelled Field Service documentation describes interventions scheduled as shifts within Planning, with worksheets, materials, time and customer reports. Treat that as a documented workflow to verify, not a guarantee of production availability or compatibility with your deployment. Record the target release, edition, hosting model, installed applications and any custom modules before accepting a demonstration as relevant.
Require the implementation team to identify the commercial entitlement for worksheets, subscriptions, recurring scheduling and any proposed travel-fee functionality. A feature visible in a demonstration database is not sufficient acceptance evidence for your contracted environment.
Start with the operating process rather than preserving every existing screen. ERP expert Francesco Perrotta emphasizes objective assessment of business processes and understanding the company’s context when evaluating solutions. Apply that principle here: classify each requirement as a necessary business control, a useful operating preference or a habit the team is willing to change. This prevents both automatic rejection of a different interface and automatic acceptance of a weaker control.
Scenario: an unquoted intervention through to invoice
Use representative customer, site, employee, service-rate and parts data. In the webinar’s repair example, the presenter creates a shift without a quotation, publishes it, starts the work and records worksheet information. Your acceptance script should extend beyond those clicks to the commercial authority for undertaking work without a quoted total.
Before dispatch, require the team to show the customer and service address, assigned resource, planned window, worksheet and applicable charging policy. Decide where authorization to attend is recorded and who can approve additional work. A customer’s acknowledgement that a technician attended should not be treated as approval of every charge unless that is your agreed business policy.
Have the technician record the repair, time and replacement parts using their intended permissions. Odoo’s documentation states that adding products from a shift requires the Sales access right “User: All Documents” or Administrator. It also states that products enter the linked sales order, or create a sales order automatically when none is linked. An administrator-only walkthrough therefore leaves a material question unresolved: can the technician perform the required task with access your business is prepared to grant?
Follow the resulting records into finance. The webinar demonstrates creating an invoice after adding the service and products. For acceptance, require finance to trace every proposed charge back to the intervention: service product, rate, billable quantity, part quantity and customer approval. Inspect the worksheet or customer report presented for signature, identify the signatory and confirm who resolves a refused signature or disputed part before billing proceeds.
Include a warranty exception. The documented Under warranty setting zero-prices materials and services added from the shift, but leaves prices unchanged for items added directly to the sales order. Test both entry paths. Passing means finance can explain the resulting treatment and identify unintended charges before invoice approval. Merely finding the warranty checkbox is not enough.
Keep template spans, allocated hours and billable time separate
Do not accept a calendar entry as proof of accurate time billing. Define separately the date span produced by the planning template, the capacity allocated to the intervention, the time recorded during delivery and the quantity finance is authorized to bill. Those values may coincide in a straightforward repair; your test should deliberately make them differ.
The documented actual-time billing workflow requires Project and Timesheets, an assigned employee, and a billable project with Timesheets enabled. It states that invoicing uses the shift’s Allocated Time, updated when the shift starts and completes. This makes the transition from planned allocation to chargeable quantity a central acceptance check, not a background configuration detail.
Capture the template-generated dates and allocated hours before work begins. Then demonstrate a late start, an interruption and a corrected completion record. If several technicians attend, require an explanation of whether the proposed charge represents elapsed intervention time or each employee’s labor. These are test questions, not assumptions about supported behavior. Finance should reconcile the resulting quantity against its charging policy and retain enough evidence to explain any adjustment.
A convincing result shows the original expectation, recorded delivery, approved correction and final invoice quantity. “The timer handles it” is a weak answer when breaks, corrections or resource changes affect the charge. If the workflow requires manual reconciliation, identify the reviewer, the records they compare and whether operations accepts that workload.
Scenario: recurring maintenance tied to the right equipment
The recurring-maintenance demonstration adds a different dependency chain. In the services webinar’s maintenance example, the equipment is tracked by a unique serial number; the shift exposes the maintained equipment and product documentation. Scheduling follows the subscription start date, with recurrence reflecting the subscription and its end date. Verify that entire chain in the target environment rather than assuming that recurring shifts alone satisfy maintenance contracts.
Begin with a representative maintenance agreement, customer site and serialized asset. Require the team to trace the subscription or sales record to the correct equipment and scheduled visit. Have the technician open the relevant technical documentation from the work record, complete the required worksheet and identify the equipment serviced. A correct customer name is insufficient if the site contains similar assets with different maintenance requirements.
Test changes to the agreement, not just its creation. Move a visit, change the subscription end date and demonstrate how the next required visit is established. Include an equipment replacement or site change if those occur in your business. For each exception, require an owner and a visible way to detect a missing visit, an unwanted visit or an intervention linked to the wrong serial number.
Reconcile contract coverage separately from additional work. Finance should demonstrate which labor and parts are included in the subscription, which require separate approval, and how the invoice review avoids duplicate or omitted charges. Compare the agreement, completed visit, worksheet evidence and proposed billing outcome. Generating another appointment does not prove the maintenance obligation or charging rule has been satisfied.
Also test worksheet governance. Odoo documents that editing a worksheet template from a shift changes all shifts using that template. Change a shared template in the test environment and inspect other affected work. Decide who may authorize template changes and how completed service evidence must remain understandable after maintenance instructions evolve.
Make dependencies and exceptions part of the decision
Assess travel fees separately from the core intervention. The webinar describes fixed and distance-based fees and identifies a Mapbox integration for distance calculation. Before relying on it, verify target-environment availability, applicable charges and usage allowances, API credentials, distance origin and destination, and behavior when calculation fails. Ask what address or coordinate data is transmitted and which processing terms apply. Do not assume the capability is included or universally free.
For Odoo field service migration, require a mapping and sample reconciliation for existing tasks, custom fields, worksheet history, recurring work, equipment links and historical billing references. A newly created demonstration shift cannot establish that migrated records retain the relationships your service and finance teams need.
Maintain a scenario decision record containing pass criteria, record references, observed results, unresolved exceptions, business consequences, an owner and the evidence needed to close each issue. Perrotta identifies underestimated training as a recurring implementation problem. Have dispatchers, technicians and finance users perform their own steps so the assessment distinguishes functional fit from coaching needs.
This is an earlier decision than deployment approval. Our ERP go-live readiness analysis addresses whether the organization can operate the release being delivered. Here, decide whether to accept the demonstrated service model, change a process with its owner’s agreement, or defer migration because a critical scheduling, evidence or billing requirement remains unresolved.
Before committing, put the unquoted repair and recurring-maintenance results in front of service operations and finance together, and require a disposition for every critical exception. If you need help specifying that assessment or resolving functional and technical gaps, talk with Digiventi’s Odoo specialists about your workflows and migration requirements.
