A Good Sample Is Not Production Readiness

Short answer

A good sample proves that one acceptable unit existed under one set of conditions. Production readiness requires an agreed product revision, repeatable process, approved materials, test criteria, packaging instructions and change control. Sample approval should therefore state exactly what passed, what remains open and what evidence is required before mass production.

A sample can show that a supplier can make one acceptable unit. It does not, by itself, show how the supplier will repeat it.

The finish looks right. The controls work. The sample performs well in the buyer’s demonstration. An email goes out: “Approved. Please proceed.”

That email may be interpreted more broadly than intended. The buyer approved the appearance and function of the unit received. The supplier may read it as acceptance of the product, packaging and remaining production choices.

Before approval becomes a larger commitment, define exactly what has been approved—and what has not.

Identify what kind of sample you received

A catalogue sample, development prototype and pre-production unit answer different questions. Suppliers also use these labels differently. Ask how the unit was made rather than relying on its name.

Which materials and components does it contain? Was it assembled using the intended tooling and production process? Was it manually adjusted? What will differ in the order? A hand-built prototype is not inherently a problem; an unexplained difference between prototype and production is.

Record the sample ID, date and specification revision. Keep an agreed reference where appropriate, with clear storage and identification. A reference sample helps communication, but it does not replace measurable specifications or the checks needed for features that cannot be judged by appearance.

Translate “good” into a repeatable requirement

Imagine a brand approves a lantern because its low setting feels comfortable at a campsite table. The sample also seems to have sufficient runtime.

Those observations raise useful questions. At what viewing distance and ambient conditions was comfort assessed? Which setting was used for the runtime check? What battery and light-control components were in that unit? Were multiple units evaluated, or only one?

“Keep the light comfortable” is not yet a production instruction. The buyer needs agreed criteria, a method and a reference configuration. If low-level dimming depends on a particular component or firmware revision, that dependency should be recorded.

If a component later becomes unavailable, the response should not be an unreviewed substitution. The team needs to assess what changed, which tests must be repeated and who can authorize the revision.

Six questions before a production commitment

The depth of each check depends on the product, its risks and the size of the commitment. The point is not to create paperwork for its own sake; it is to make the remaining decisions explicit.

1. Is the product baseline defined? Confirm drawings or specifications, materials, critical components, accessories and the revision being ordered. Identify deviations from the accepted sample.
2. Is the intended production route understood? Confirm which steps are in-house or outsourced, whether production tooling is ready and how important characteristics will be controlled. Where repeatability is uncertain, consider a scoped pilot run under the intended conditions.
3. Are tests and acceptance criteria agreed? Define what will be measured, how it will be measured, who checks it and what happens when it fails. Include functional and appearance criteria; involve qualified specialists for product safety and market-specific requirements.
4. Is packaging part of the approval? Confirm artwork, labels, accessories, packing configuration and carton details. Decide what transport-related evaluation is needed rather than assuming an attractive retail box protects the product in distribution.
5. Are inspection and release responsibilities clear? Agree relevant checkpoints, access, reporting and release authority. Final inspection and production-process control are different tasks.
6. Is change control practical? Record how material, component, process or site changes are disclosed, reviewed and approved. Identify the owner and due date for each unresolved item.

Use a sample decision record—not a vague sign-off

The following structure separates evidence from approval. Complete it for the actual product and attach the relevant specification, photographs and test records.

For example: “Appearance approved against sample S-03. Runtime remains unverified. Packaging artwork requires revision. Authorization is for the next sample revision, not bulk production.” That statement is more useful than “Sample approved” because the next action is unambiguous.

Inspection cannot fill every evidence gap

A selected sample and a lot inspection should not be confused. Acceptance sampling uses units selected from a defined lot to support an accept-or-reject decision. It does not certify that every unit is defect-free or establish long-term process control. NIST’s explanation of acceptance sampling makes this distinction clear.

A last-minute inspection also cannot substitute for defining requirements early. If the buyer and supplier never agreed what constitutes an unacceptable defect, the inspection may reveal a disagreement rather than resolve one.

Avoid adopting a generic inspection level or defect threshold merely because it appears in someone else’s checklist. The plan must fit the product and its consequences of failure.

Approve the next step, not an undefined promise

A credible readiness review can end with approval, approval of a limited next step or a hold pending evidence. An unresolved issue is not automatically a reason to reject the supplier. It is a reason to decide how much commitment is appropriate while the issue remains open.

Sample approval is a decision about the evidence in front of you. Production readiness is a decision about how that result will be reproduced.

Sourcing tool / Free download / Excel

Sample Approval & Production Readiness Tracker

Record sample identity, test criteria and results, production differences and open actions. Keep sample approval separate from production release. Includes a blank tracker and an illustrative example.

Enable JavaScript to request this tool, or contact contact@sierra-scm.com.