THE DIRECT ANSWER

Record the reason for a return visit before deciding whether its time and materials are billable. Link the visit to the original equipment and job, then distinguish a missing supplier part, customer change and corrective work. Review the customer agreement rather than allowing every new technician entry to become an invoice line.

Understand the decision

An initial diagnosis may consume a small component without resolving the fault, while a later visit installs a replacement assembly. Dispatch, stock control and finance need a shared account of which parts were fitted, returned or merely carried, and who authorized the extra visit.

Work through the requirements

  1. Classify the return-visit reason.
  2. Record fitted and returned quantities.
  3. Approve the proposed billing treatment.
Information to bring to the review
Record or decisionWhy it matters
Visit recordConnects work to equipment history.
Parts movementExplains consumed and returned stock.
Billing decisionSeparates chargeable work from correction.
TRY THIS WITH YOUR TEAM

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.

0 of 3 marked

Watch for this failure

Do not equate a technician's completed task with permission to charge again. Review the visit reason, material movement and agreement together so operational effort stays visible without automatically becoming customer revenue.

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 guide
FROM REQUIREMENTS TO A REAL SCOPE

Bring your workflow to the conversation.

Discuss requirements for HVAC contractors 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: field service materials and warehouse configuration ↗Odoo 19: helpdesk after-sales workflows ↗Odoo 19: sales quotations and invoicing methods ↗