THE DIRECT ANSWER

Test delivery of the accepted pieces while preserving any outstanding item and documented snag. Connect the delivery record to the commission and the agreed billing decision. The result should show what the customer received, what still needs correction and who owns the next action without marking the whole commission complete.

Understand the decision

For a hypothetical bedroom commission, a bed and dresser arrive but a mirror is delayed and one drawer needs adjustment. The customer signs for the delivered pieces. A launch rehearsal should distinguish physical receipt from final completion and preserve the unresolved work after delivery.

Work through the requirements

  1. Record delivered and delayed pieces individually.
  2. Assign the drawer adjustment and next contact.
  3. Reconcile completion and invoicing with approved terms.
Information to bring to the review
Record or decisionWhy it matters
Delivery acknowledgementIdentify pieces actually received.
Snag listAssign outstanding corrective work.
Completion decisionDocument final acceptance status.
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

Closing a commission when the truck returns can erase unresolved customer work. Define which event means delivered and which means accepted, then ensure the chosen workflow carries those distinctions into reporting and the final billing review.

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 Custom furniture 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: manufacturing product configuration ↗Odoo 19: vendor pricelists ↗Odoo 19: quality control points ↗