A supplier may quote one product version, sample another, and produce a third without anyone intending to create confusion.
It happens when product changes are sent through email, chat, photos, and calls without a controlled revision. A new material is “close enough.” A dimension changes on a drawing but not in the quotation. A packaging update affects carton size but nobody asks for a shipping or pack-out review. The quote still looks valid because the title did not change.
The fix is not a complicated software system. It is a disciplined path from a requested change to an approved product revision and a confirmed supplier quote.
Treat every meaningful change as a quote question
A change is not only an engineering issue. It may change what the factory buys, makes, tests, packs, or ships.
Arena Solutions describes revisions as controlled versions used to manage pending and released changes to parts, assemblies, drawings, and other documents. It notes that revision control helps identify what revision can be ordered, built, and shipped. 1
Before you ask a supplier to “just update the price,” classify what changed.
| Change area | Quote question to ask |
|---|---|
| Material or component | Does the new item alter source, grade, availability, process, or unit cost? |
| Dimension or structure | Does it affect tooling, yield, assembly, packaging, or freight footprint? |
| Function or performance | Does it need a new component, process, sample, test, or acceptance method? |
| Artwork or packaging | Does it affect printing, labels, inserts, pack-out, cartons, or approvals? |
| Quantity or order mix | Does it change the production plan, component purchase, or price basis? |
| Quality or test requirement | Does it change inspection, equipment, testing, rework exposure, or documentation? |
| Delivery or commercial term | Does it change material timing, production priority, packaging, or logistics assumptions? |
A change can have no price impact. That is still a decision worth recording. It tells the buyer and supplier that the change was reviewed rather than overlooked.
Use one top-level revision to control the product
A buyer may have a BOM revision, drawing revision, artwork revision, packaging revision, sample ID, and inspection-checklist revision. Those can all be necessary. The supplier still needs to know which top-level product revision controls the quote and production release.
ESCATEC recommends assigning revisions to relevant build data and being clear about the revision level that controls the finished product. 2
| Field | Example |
|---|---|
| Product or assembly ID | KETTLE-300 |
| Controlling product revision | Rev C |
| Change request ID | CR-024 |
| Effective document pack | KETTLE-300 Rev C Release Pack |
| Quote reference | Q-845 Rev 2 |
| Supplier acknowledgement | Supplier confirmed Rev C on 2026-08-18 |
| Effective point | Applies to sample round 2 and any new PO issued after approval |
Do not assume the drawing revision is always the top-level controlling revision. Choose a clear rule for the project and use it consistently in the quote, purchase order, sample records, product specification, and inspection plan.
Stop informal change instructions
A chat message can identify a problem. It should not become the only record of a product change.
Use a short change request whenever the product, packaging, material, component, process, test, quantity basis, or commercial assumption may be affected.
| Change-request field | What to record |
|---|---|
| Change ID and date | A traceable reference for the decision |
| Current and proposed revision | What is changing from and to |
| Description and reason | The specific requested change and why it is needed |
| Affected files | Drawings, BOM, artwork, specification, sample, checklist, or packaging record |
| Affected quote items | Material, tooling, sample, unit price, packaging, test, MOQ, lead time, or other stated item |
| Supplier response needed | Cost, timing, feasibility, sample, test, or document impact |
| Buyer decision | Approved, rejected, held, or more information required |
| Effective point | The sample, batch, purchase order, or date at which the revision may be used |
Microsoft’s engineering-change guidance uses a structured process for requests, supporting files, affected products, review, approval, and impact assessment. 3 Your own record can be simpler, but it should preserve the same essentials: what changed, what it affects, who reviewed it, and when it becomes effective.
Ask for a quote-impact response, not a vague confirmation
“Okay, we can do it” is not a quote update.
Ask the supplier to respond against the requested change. It should identify whether the change affects the quote and, if so, which part of the commercial and production scope changed.
| Supplier response field | Why it matters |
|---|---|
| Change accepted as written? | Confirms whether the supplier read the actual revision, not only the email summary |
| Material/component impact | Shows substitutions, availability issues, or a changed sourcing assumption |
| Tooling or process impact | Identifies a new tool, fixture, process step, or production constraint |
| Sample or validation impact | Shows whether a revised sample, proof, or early validation is needed |
| Unit-price impact | Separates product price from non-recurring or sample costs where applicable |
| Packaging and freight impact | Makes carton, pack-out, or shipping-volume changes visible |
| Lead-time impact | Shows if approval, materials, tooling, or production scheduling changes the plan |
| Assumptions and exclusions | Prevents a supplier from pricing an unstated interpretation |
| Quote revision | Links the supplier’s response to a new quote document or written no-impact confirmation |
Do not force a supplier to promise a final price before it has the revised data. The buyer’s job is to ask for a clear impact assessment and then decide whether the new scope is acceptable.
Reissue the complete release pack after approval
Sending only the changed drawing creates risk. The supplier may keep the old BOM, old artwork, old packaging instruction, or old inspection criteria beside it.
ESCATEC recommends reissuing the complete build pack with an up-revision, marking old material “do not use” or “up-issued,” and asking suppliers to confirm they understand the change. 2
For a sourcing project, the release pack may contain:
| Release-pack item | Control purpose |
|---|---|
| Current product specification | Defines the product version and acceptance points |
| Current BOM or component list | Controls materials and supplier-approved components |
| Current drawing, artwork, and packaging files | Controls physical dimensions, print, and pack-out |
| Approved sample/reference record | Links the physical comparison item to the current revision |
| Inspection checklist | Tells the quality team what and how to check |
| Revised quote or no-impact confirmation | Links the commercial agreement to the current scope |
| Change log | Explains what changed from the prior release |
| Obsolete-file list | Identifies documents that must no longer be used |
Use the Product Specification Sheet Template for China Manufacturing as the product anchor. Use Packaging Dielines and Artwork: What to Send Your Supplier to control packaging-specific records.
Confirm supplier receipt and understanding
Do not assume an email attachment changed the factory’s working documents.
Ask the supplier to confirm, in writing:
- The controlling product revision and quote revision received.
- The affected documents it has replaced or withdrawn.
- The price, timing, sample, tooling, test, or packaging impact it identifies.
- The production or sample point at which the change will take effect.
- Any open questions or assumptions still preventing release.
This is not bureaucracy for its own sake. It gives both sides a point to catch a missing attachment, an incorrect revision, an old price assumption, or a change that needs a sample before normal production starts.
Separate pending changes from released changes
A buyer can explore options without authorizing them. Keep the two states separate.
| State | Meaning | Supplier instruction |
|---|---|---|
| Discussion | Idea or issue is being explored | Do not use for quote or production without a named request |
| Under review | Supplier is assessing feasibility or quote impact | Do not start production against it |
| Approved for quotation | Buyer wants a confirmed commercial response | Update quote or give written no-impact confirmation |
| Released for sample | New version may be used for the identified sample round | Label sample with revision and compare against release pack |
| Released for production | New version may be used for the named production point | Withdraw old documents and confirm effective batch/PO |
| Superseded | A former revision is no longer current | Mark as obsolete/do not use and retain only for history |
Microsoft’s guidance distinguishes a request for change from an approved change order and describes assessment of impacts on open transactions. 3 The same principle works without an ERP: a pending request must not silently become a production instruction.
Review the quote again when the sample changes
A revised sample may expose a change that was not visible in drawings or messages: a different component, added assembly time, different pack-out, an unavailable finish, or an unworkable tolerance.
When you approve a revised sample, compare it with the controlling revision and the current quote. Ask whether the supplier’s quote, lead time, materials, production method, or quality plan must be revised. Then record the decision.
For the general approval path, see How to Request a Product Sample From a Chinese Supplier and Golden Sample vs Production Sample: Why the Difference Matters. Once production begins, use How to Reduce Sample-to-Production Differences to keep the released standard active.
Keep a simple revision-and-quote register
A small register prevents the team from searching through several threads to identify the last valid commercial decision. It can be a spreadsheet or project record; the important point is that it is updated when the revision or quote changes.
| Register field | What it answers |
|---|---|
| Product revision | Which product definition is currently released? |
| Quote revision | Which supplier quote or no-impact confirmation matches it? |
| Change request | Why was the revision created? |
| Status | Is the change pending, approved for quotation, released for sample, or released for production? |
| Supplier acknowledgement | Has the supplier confirmed receipt and understanding? |
| Effective point | Which sample, PO, batch, or date is governed by the revision? |
| Open issue | What still blocks the release? |
This register should point to the controlled documents rather than duplicate them. Its purpose is to make the current revision and commercial position visible at a glance.
The practical rule
Do not manage product revisions as a chain of messages. Assign a revision, record the change, ask the supplier for a specific impact response, approve the result, reissue one complete controlled package, obtain acknowledgement, and state the effective point.
When the product version and quote version travel together, you are less likely to pay for, sample, or produce a product that nobody intended to buy.