THE DIRECT ANSWER

Assess the missing component against the build sequence, rework risk and approved alternatives before starting partial assembly. Identify which operations can proceed safely and where work must stop. The plan should preserve the outstanding component requirement and the ownership of its resolution, rather than treating a partly issued kit as fully ready.

Understand the decision

In a sample order, most components are available but a connector is delayed. Starting the boards may save time, although fitting the connector later could require extra handling and inspection. An alternative is available locally, but engineering has not approved its footprint and the customer expects a particular connector family.

Work through the requirements

  1. Identify the shortage and affected operation.
  2. Review partial-build and substitution options with engineering.
  3. Approve a stop point and named resolution owner.
Information to bring to the review
Record or decisionWhy it matters
Kit shortageRecord missing component and quantity.
Build decisionDefine permitted work and hold point.
Alternative reviewDocument approval or rejection evidence.
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

Starting every available operation can create hidden queues of almost-finished boards. Include handling and repeat inspection effort in the decision, and keep the incomplete kit visible so production progress does not imply a deliverable finished assembly.

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 Electronics assembly 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: multilevel bills of materials ↗Odoo 19: lot numbers ↗Odoo 19: quality control points ↗