Stop missing specifications at the sales-to-production handoff
Define what engineering needs from an accepted manufacturing order. Keep missing specifications, release decisions and late customer changes visible.
An accepted manufacturing order should reach engineering or production with enough information for that team to make its next decision. Define the required specification and an explicit hold for missing information. A confirmed sale is a commercial event; it is not automatically proof that every drawing, unit or customer option is ready for release.
Odoo 19 Sales documents that confirming a quotation turns it into a sales order. Its manufacturing documentation describes the bill of materials as the component quantities needed for the product, with operations where configured. Those are related records with different purposes. Odoo quotations and bills of materials.
Define what the receiving team needs
Ask engineering to take one permitted recent order and mark every point where it had to return to sales for clarification. Separate facts that sales could collect from decisions requiring technical review. A salesperson can capture the customer's requested dimension without being authorized to approve its engineering suitability.
Use the production-model card to identify when the definition becomes fixed. A repeat standard item and a newly designed assembly should not inherit identical readiness requirements just because both appear on sales orders.
| Readiness field | Evidence to pass | Who resolves a missing or conflicting value |
|---|---|---|
| Product or requested outcome | Approved item identity or clear design request | Commercial owner with technical reviewer |
| Quantity and units | Customer requirement with units shown | Order owner |
| Options and exclusions | Chosen allowed options and explicit exceptions | Scope owner |
| Drawing or specification | Exact reference and revision | Engineering owner |
| Delivery requirement | Customer request distinguished from confirmed commitment | Authorized planning/commercial role |
| Open decisions | Question, consequence, owner and needed date | Named decision owner |
| Acceptance of the handoff | Receiving role and evidence reviewed | Engineering or production lead |
Do not turn this into a form where every field can be satisfied by entering “TBD.” An unresolved field is useful only when its consequence is visible and someone owns the next step.
Show a hold without erasing the sale
For a fictional fabricated bracket order, sales has an accepted quantity and finish but two different thicknesses appear in the attached documents. Engineering can acknowledge receipt of the order while holding the affected definition for clarification.
The hold should identify the conflicting documents, the person resolving the discrepancy and what work can safely proceed under the business's rules. It should not invite an operator to choose the latest-looking filename.
Some activities may remain possible, such as reviewing capacity or confirming standard material availability. Others may need to wait. Have the responsible technical and operating owners define that boundary; this worksheet does not decide what is safe to manufacture.
The crucial acceptance test is visibility. Can a planner tell the difference between a commercially accepted order and a released manufacturing definition without calling the salesperson?
Check the exception that arrives after acceptance
Start with a complete order in a rehearsal environment. Then introduce a revised customer attachment before production release. Ask the receiving team to identify the new request and distinguish it from the previously reviewed definition.
Next, introduce the same attachment after work has been released. The result should enter the agreed change process rather than quietly replacing the instruction already used. The engineering-change release guide helps define that later decision.
These are business acceptance conditions. They do not assert that Odoo automatically blocks a manufacturing order based on every field in this worksheet. The implementer must show what standard configuration, approval rule, manual control or extension enforces the agreed readiness boundary.
Measure clarification work at the handoff
For the pilot, keep a simple log of orders submitted, orders accepted by the receiving team and orders returned with a reason. Retain the actual missing field rather than a generic “bad data” label. Do not interpret one week's figures as a permanent performance benchmark.
Review the recurring questions with sales and engineering. If the same information is repeatedly absent, improve its collection at the point where the customer can answer it. If a technical decision is repeatedly misassigned to sales, change the owner instead of adding another mandatory sales field.
The finished design gives an incomplete order a visible state and a route to resolution. It lets the business preserve the customer commitment while preventing an unanswered specification question from becoming an instruction on the shop floor.