THE DIRECT ANSWER

Inspect the returned assembly against an expected component list before deciding whether any part is sellable. Link missing or damaged pieces to the customer resolution and supplier claim where applicable. Demonstrate that a complete-unit stock quantity cannot be created from an incomplete return merely because the original invoice describes one fixture.

Understand the decision

A boxed fixture comes back with the main body intact but a missing fitting and damaged finish. The customer expects a full credit, while the warehouse cannot offer the same unit to another buyer. The workflow needs separate evidence for physical completeness and the commercial settlement.

Work through the requirements

  1. Compare the return with expected components
  2. Record condition and missing pieces
  3. Approve stock disposition and credit treatment
Information to bring to the review
Record or decisionWhy it matters
Return component checklistShows what physically arrived
Condition evidenceSupports resale or supplier decisions
Customer resolutionExplains approved credit or replacement
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

Counting boxes rather than complete assemblies can inflate usable inventory. Define what makes a sellable unit and require the return process to prove that condition before it increases availability or closes the supplier recovery task.

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 Plumbing distribution 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.

Import vendor pricelists ↗Units of measure ↗Packaging ↗