Sample Approval vs Production Commitment: Reading Two Quotes as Two Separate Decisions
Keep the sample quote and the production quote as two separate documents, because they are not one decision at two prices. The sample quote buys information: a representative unit made to a stated specification that you can measure, test and reject. The production quote buys a commitment: an agreed quantity, an agreed specification, an agreed schedule and an agreed payment path. When both stages live in the same thread or the same price line, what was true for one unit quietly turns into an assumption about an entire run, and that assumption is where most later disputes start.
Why the two stages get merged
The merge usually happens for practical reasons. A supplier sends one quotation that covers a sample and then a follow-up order, a buyer replies with a single approval, and both sides move on. Nothing is wrong with that sequence, but the approval message ends up doing two jobs at once: accepting one physical unit and signalling an intention to order. Those are different acts, and only one of them should be treated as binding at the time you send it.
There is also a structural reason. A sample is usually made under different conditions from a production run: a different setup, a different level of finishing attention, and a different quantity economics. That does not mean the sample is misleading. It means the sample answers a narrower question than the one buyers often think they are asking. The sample answers whether the specification is achievable; only the production terms answer whether it is achievable repeatedly, at a stated quantity, on a stated schedule.
The two-stage comparison
| Sample stage | Production stage | |
|---|---|---|
| What you are buying | One representative unit, or a small stated number, for evaluation | A repeatable supply commitment over a stated quantity or period |
| What the supplier commits | To attempt the stated specification once, at the stated sample price | To deliver the agreed quantity to the agreed specification on the agreed schedule |
| What you commit | The sample fee, the sample shipping cost, and any stated sample tooling cost | Payment per the production payment terms, and acceptance of deliveries under the agreed acceptance process |
| Price basis | A one-off unit price, which does not by itself establish volume economics | A unit price tied to a quantity band, including what happens above or below that band |
| Time | Elapsed time to produce and dispatch the sample | Elapsed time from order confirmation, and from any deposit, to each delivery |
| Specification authority | Which document or reference governs: your drawing, a reference sample, or a written description | The same authority, plus what happens if the specification changes during the run |
| Acceptance | What approved means in writing, and what happens to the approved reference unit | How each lot is checked, who checks it, and what happens to a lot that fails |
| Tooling | Who owns any tooling, where it is kept, and whether it may be used elsewhere | The same, plus what happens if tooling is modified, moved or retired |
| Exit | Whether you may stop after the sample with no further obligation | What ends the arrangement, and what happens to remaining stock, tooling and open orders |
Reading the table left to right is the useful habit. Any row where the two columns differ, or where one column is silent, is a question to put in writing before the next stage begins.
Where the drift usually appears
The differences that matter most tend to be quiet ones. A specification that was described in conversation during sampling becomes the governing specification during production. A unit price quoted for one quantity band is applied to a different band without being restated. A lead time is quoted from the sample approval date rather than from the order confirmation or deposit date. Each of these is fixable with one sentence in writing, and each is expensive to fix after the fact.
Shipping terms deserve particular care. Incoterms-type terms allocate transport responsibilities, costs and risk between the parties; they do not by themselves establish product quality, and they do not establish payment terms. A quote that shows a shipping term and nothing else has told you about logistics, not about what you will receive or when you must pay.
The same caution applies to quality management language. ISO publishes an overview of ISO 9001, a quality management standard, which is a useful frame for thinking about how a supplier organises quality. It is not a substitute for confirming what a specific supplier's system covers, and a screening result, listing or self-declared statement is not a certification. Treat any quality claim as a claim to be verified against separate evidence for that supplier.
Blank worksheet: fill it in before you approve
Use one line per question and leave anything blank that the quote does not actually state. A blank cell is information, not an oversight to be filled with assumptions.
| Field | Sample quote states | Production quote states | Difference to confirm in writing |
|---|---|---|---|
| Item and specification reference | |||
| Quantity, and the quantity band the price applies to | |||
| Unit price, and what that price includes | |||
| Tooling cost and ownership | |||
| Start of the clock for lead time | |||
| Shipping term, and which costs it does not cover | |||
| Payment amounts and the trigger for each | |||
| Acceptance method and who performs it | |||
| Handling of rework, rejection and replacement | |||
| Conditions for stopping without further obligation |
The handoff record when you approve a sample
Approval is a handoff, so it deserves a record of its own rather than a reply in a thread. Keep the following fields together with the approval, even if some are unresolved at the time:
- The specification reference that governs the approval, named precisely enough that someone else could find it later.
- Which physical unit is the reference unit, and where that unit will be stored.
- What was confirmed by measurement or testing, as opposed to visual inspection.
- What was explicitly not approved, including any deviation left open for the production stage.
- Which characteristics of the sample still need confirmation at scale.
- Who approved it, in what role, and on what date.
Two editorial suggestions follow from the record, offered as suggestions rather than requirements. First, write approvals so that they accept the sample and nothing else, and keep any statement about future ordering in a separate message. Second, if a deviation was tolerated in the sample, decide at approval time whether it is a one-time allowance or a specification change, because leaving it undecided moves the decision into the production stage where it is harder to revisit.
What to send next
Keep the sample quote, production quote, completed worksheet and sample approval record together as one draft brief. The on-site Sourcing Desk tool does not send it or arrange a review. Supplier capability, certification, quotations and any introduction or next step all need separate case-specific confirmation.
If you have only one document covering both stages today, the smallest useful step is to split it: write down what applies to the sample, write down what would apply to production, and treat every difference as a question rather than a detail to resolve later.