Did your supplier send a sample that you approved, then quietly change a material, trim, colour, label, or construction detail before mass production? When the finished goods arrive, can you show which sample was approved, what changed, who proposed the change, and whether anyone authorised production to continue?
If the answer depends on a long chat thread, a phone photograph with no filename, or someone’s memory, the problem is not only the change. The problem is that the decision trail has disappeared.
A China supplier sample deviation log gives an overseas buyer one working record for the period between sample approval and production release. It lets you compare the approved reference with the proposed production version, attach evidence, assign an owner, and stop an unconfirmed change from being treated as an approved instruction. This is especially useful when buying through a factory, trading company, sourcing agent, or several suppliers around Yiwu and other China production centres.
This guide explains a practical method for building that record before mass production. It is an operational control, not a contract, product certification, legal opinion, or guarantee that a supplier will never make an unapproved change. It also does not replace a suitable inspection, destination requirement review, or written commercial agreement.
What a China supplier sample deviation log is for
A sample deviation log records a difference between an agreed reference and a later proposed or observed version. The reference may be a physical sample, a dated specification, an approved artwork file, a packaging instruction, a colour reference, or a combination of these. The log should make the difference understandable to someone who was not in the original conversation.
The focus is the change after sample approval and before mass production. That keeps this document distinct from a general supplier comparison, a golden-sample explainer, or a broad pre-shipment inspection report. The W32 routing for this topic identifies five useful control points: sample identity, approved specification, dated revision, substitution, and the owner and status of approval.
A useful log answers these questions for every deviation:
- Which order, product, SKU, or style does it affect?
- Which sample or document is the approved baseline?
- What exactly is different?
- When was the difference proposed or found?
- Why is the supplier proposing it, if a reason has been given?
- What evidence shows the proposed alternative?
- Does the change affect fit, function, appearance, packaging, labelling, cost, destination requirements, or production handling?
- Who must review it?
- Is it approved, rejected, returned for clarification, or still open?
- What production instruction reflects the final decision?
A log is not a place to write “supplier changed quality” and move on. That description is too broad to guide a factory or a buyer. Record the physical or documentary difference in terms that can be checked.
Set the baseline before logging a deviation
You cannot identify a deviation until you define what the supplier was expected to follow. Start by assigning a clear identity to the approved sample. “The blue sample from last month” is not a reliable identifier when several versions exist. Use a practical reference such as product name, SKU or style code, sample revision, approval date, and the person or company that approved it.
The baseline can be described in a small reference table:
| Baseline field | What to record |
|---|---|
| Product identity | Product name plus SKU, style, colourway, or internal code |
| Sample reference | Sample label, photo set, shipment reference, or physical sample location |
| Approved revision | Revision number or dated file name |
| Approval date | Date and time zone when practical |
| Approval owner | Buyer, brand representative, agent, or other authorised reviewer |
| Attached specification | Dimensions, material description, artwork, packaging, and other agreed instructions |
| Approval scope | What the approval covers and what remains open |
The approval scope matters. A buyer may approve the shape and colour of a sample while leaving packaging artwork or a destination label pending. Do not allow a supplier to treat approval of one area as approval of every area. Write “approved for appearance only” or “packaging not yet approved” when that is the actual decision.
For a physical sample, take photographs that show the whole item and the details most likely to be changed. Keep the original file names or assign stable IDs. A photograph is useful evidence, but it does not by itself prove material composition, internal construction, production quantity, or compliance with a destination rule. Those matters need their own evidence and review.
Build the log around one deviation per row
The most workable format is one row per distinct change. If a supplier changes a zipper pull and a carton mark, record them separately even if they were mentioned in one message. Separate rows make ownership and approval clearer. They also prevent a buyer from approving one change accidentally while intending to review another.
Recommended columns include:
| Column | Recording rule |
|---|---|
| Deviation ID | Use a stable ID such as SD-001, SD-002, and do not reuse it |
| Order and product | Identify the purchase order, SKU, style, and affected colour or pack |
| Baseline reference | Link the approved sample ID and approved revision |
| Proposed revision | Give the new drawing, photo, file, or sample a dated ID |
| Change description | State the old version and new version in observable terms |
| Source and date | Record who proposed or found it and when |
| Reason given | Quote or summarise the supplier’s stated reason without upgrading it to fact |
| Evidence | List photographs, marked-up drawings, messages, test documents, or sample IDs |
| Impact review | Note affected function, appearance, packaging, labelling, cost, or destination need |
| Decision owner | Name the party who can approve this change |
| Status | Open, clarification required, approved, rejected, or superseded |
| Production instruction | Record the final instruction and the revision to be used |
| Closed date | Close only after the decision is documented and communicated |
The phrase “reason given” is deliberately cautious. If a supplier says a material was unavailable, record that as the supplier’s explanation. Do not rewrite it as a verified supply-chain fact unless you have independent evidence. The same discipline applies to statements about quality, safety, compliance, or delivery impact.
Step 1: Freeze the approved sample identity
Before discussing a new sample, confirm which sample is the reference. Ask the supplier to confirm the sample ID and keep a dated image set. If you work with an agent or a warehouse, confirm where the physical reference is held and who can inspect it.
For a Yiwu sourcing workflow, this simple step prevents a common mix-up: the buyer approves a sample in a chat, the agent receives another version, and the factory works from a third version. The log should show whether the baseline is a physical sample, an electronic file, or both. If a physical sample and a file disagree, open a clarification item rather than choosing silently.
Step 2: Capture the approved specification in plain language
Do not rely on “same as sample” as the complete specification. Write the characteristics that a later reviewer can observe or measure according to the buyer’s own requirements. Depending on the product, this may include material description, colour reference, components, artwork, dimensions, stitching or assembly details, care or warning labels, carton marks, and packing arrangement.
The goal is not to invent tolerances. If no tolerance or acceptance level has been agreed, do not add one to make the table look precise. Instead, state that the dimension or characteristic requires buyer confirmation. A clean unknown is safer than an invented number.
Step 3: Give every new proposal a dated revision
A supplier may send a replacement photograph or updated file without saying that it is a revision. Treat every new version as a revision when it could affect the order. Record the date, sender, file name, sample label, and the related deviation ID.
Use revision language that travels well across email, messaging apps, spreadsheets, and warehouse notes. For example, “Approved baseline: SAMPLE-02, approved 2026-08-04” is easier to check than “the final sample.” “Proposed revision: SAMPLE-02B, received 2026-08-06” keeps the decision open until it is reviewed.
Never delete the earlier reference after approval. A later file should not overwrite the evidence of what was previously approved.
Step 4: Describe the change as a comparison
A strong description has three parts: approved version, proposed version, and affected area. “The zipper pull is different from the approved sample; supplier proposes an alternate pull shown in photo SD-001-03” is useful. “Hardware changed” is not.
For each row, ask:
- Can a person identify the old version without guessing?
- Can a person identify the proposed version from the attached evidence?
- Is the affected component named?
- Does the description separate what was observed from what was explained?
If the change is visual, use a side-by-side image with labels such as “approved baseline” and “proposed revision.” If the change is in artwork or packaging, use a marked-up file and record the file revision. If the change is internal and cannot be confirmed from a photograph, request the appropriate sample, drawing, or written specification before deciding.
Step 5: Attach evidence that supports the decision
Evidence should help the reviewer make a decision, not simply create a larger folder. Name each attachment with the deviation ID. A practical set may include a comparison photograph, a marked-up specification, a supplier message, a revised artwork file, and a sample receipt note.
Keep the evidence distinction clear:
- A photo can show a visible feature at the time the photo was taken.
- A supplier message can show what the supplier said or proposed.
- A marked-up file can show an intended revision.
- A sample receipt can show that a sample was received and identified.
- An inspection or test document may address a defined checkpoint, but it does not automatically answer every quality or compliance question.
A photo is not proof that the pictured item represents every production unit. It is also not proof of authenticity, shipment contents, or claim acceptance. Those conclusions need separate controls. This is why the sample deviation log should preserve evidence without pretending that one attachment settles every downstream question.
Step 6: Review operational impact before approval
A small-looking change can affect a later stage. Review the deviation against the product specification, packaging, labelling, counting, inspection plan, consolidation, freight handoff, and destination requirements that apply to the order.
Use an impact checklist rather than guessing severity:
| Review area | Questions to ask |
|---|---|
| Function | Could the change affect use, fit, closure, strength, or assembly? |
| Appearance | Does it alter colour, surface, proportion, logo placement, or finish? |
| Materials and components | Is the substitute identified well enough for the buyer to review it? |
| Packaging | Does it change unit packing, carton marks, protection, or count? |
| Labelling | Does it affect artwork, language, product information, or destination instructions? |
| QC method | Does the change require a revised checkpoint or comparison reference? |
| Cost and order record | Does the commercial record need written confirmation? |
| Destination requirements | Does the buyer need a separate compliance or import review? |
| Schedule and handoff | Could a revised sample or approval affect the planned production release? |
This table does not create an acceptance standard. It tells you where to ask a more specific question. If a change touches a regulated or destination-specific requirement, keep the article’s operational log separate from the legal or compliance determination.
Step 7: Route the decision to the right owner
A supplier can propose a change, but the supplier is not automatically the buyer’s approval owner. A sourcing agent can coordinate the comparison, but coordination is not the same as authorisation. The log should identify who can make the decision for each area.
A simple responsibility pattern is:
| Decision area | Supplier | Sourcing agent or coordinator | Buyer or brand owner |
|---|---|---|---|
| Explain why a change is proposed | Provide information | Clarify and translate where needed | Review the explanation |
| Provide revised sample or evidence | Prepare and label | Receive and organise | Confirm evidence is sufficient |
| Compare with approved baseline | Support comparison | Document differences | Decide whether the difference is acceptable |
| Approve commercial or brand change | Acknowledge instruction | Record and communicate | Give written approval |
| Release production instruction | Follow confirmed revision | Distribute the approved record | Confirm release authority |
This is a workflow model, not a legal allocation of liability. Adjust it to your actual agreement and team. The important part is that “received,” “reviewed,” and “approved” are separate statuses.
Do not mark an item approved because someone said “okay” without a clear reference. Ask which deviation ID, product, and revision the approval covers. If a message approves only the colour but not the component substitution, record the narrow scope.
Step 8: Create a production-release gate
Before mass production starts, compare the release instruction against the open deviation log. The release packet should identify the approved sample revision and list any approved deviations. Open or rejected items must remain visible.
A release check can be short:
- Every product and colourway has an approved baseline.
- Every proposed change has a deviation ID.
- Evidence is attached or its absence is explicitly recorded.
- The decision owner is identified.
- No item with “open” or “clarification required” status is silently treated as approved.
- Approved changes are reflected in the current specification, artwork, packing instruction, or production note.
- The supplier confirms which revision will be used.
- The buyer keeps the prior approved reference and the final release record together.
This gate does not promise that production will match the sample. It gives the buyer a documented point at which unresolved changes can be questioned before production proceeds.
An illustrative log entry
The following example is a format demonstration, not a claim about a real order:
| Field | Example entry |
|---|---|
| Deviation ID | SD-001 |
| Product | Canvas tote, style CT-07, colourway pending confirmation |
| Approved baseline | SAMPLE-02, physical sample plus photo set, approved 2026-08-04 |
| Proposed revision | SAMPLE-02B, supplier photo set received 2026-08-06 |
| Change | Zipper pull shape differs from the approved baseline; proposed alternative shown in SD-001-03 |
| Reason given | Supplier says the original component is unavailable; this is recorded as an explanation, not independently verified fact |
| Impact review | Appearance and component identity require buyer review; no conclusion recorded about function |
| Decision owner | Buyer or brand owner |
| Status | Clarification required |
| Release instruction | Do not include this item in an approved production revision until written decision is recorded |
Notice what the entry does not do. It does not invent a defect rate, tolerance, cost saving, lead-time promise, or remedy. It does not state that the alternate is equivalent. It preserves the question until the person with approval authority decides.
When a supplier says the change is minor
“Minor” is a useful prompt for a closer description, but it is not a decision status. A change that seems minor to the supplier may be important to the brand, the customer, the packaging workflow, or a destination requirement. Ask the supplier to identify the exact component and provide the revised evidence.
You can then decide whether the change is acceptable, reject it, request another option, or ask for a new sample. Record the decision and its scope. If the buyer accepts an alternate only for one colourway or one order, do not write a general approval that can be reused later without review.
Keep the log usable after production release
Once the decision is made, preserve the full history. Mark the deviation as approved, rejected, superseded, or closed, but do not erase the proposed version. Attach the final production instruction and note who received it. If a later inspection or receiving check refers to a revised component, the inspector or warehouse team should be able to find the same revision ID.
For multi-supplier orders, use a separate prefix or supplier field so that SD-001 from Supplier A cannot be confused with SD-001 from Supplier B. At consolidation or warehouse receiving, the log can support a handoff conversation, but it should not replace counting, carton identification, inspection, or document checks. Keep those records linked by order and product identity. The Style Sourcing guide to warehouse receiving, QC, and pre-shipment inspection roles helps separate those downstream checkpoints from this pre-production approval record.
This is also where a broader supplier-verification or China quality-control workflow may help. The relevant Style Sourcing guides on wholesale bag supplier verification and quality control for bags from China address adjacent operational questions. They should complement the deviation log rather than turn this narrow record into an all-purpose inspection report.
A printable pre-production checklist
Use this checklist during the final review before production release:
- [ ] The approved sample has a stable ID and dated approval record.
- [ ] The approved specification, artwork, packaging note, or other baseline is attached.
- [ ] Each proposed or observed difference has its own deviation ID.
- [ ] The old and new versions are described in observable language.
- [ ] Each file, photograph, sample, or message is named against the deviation ID.
- [ ] The supplier’s explanation is separated from independently verified evidence.
- [ ] Function, appearance, materials, packaging, labelling, QC, commercial record, and destination questions were considered where relevant.
- [ ] The correct decision owner is named for every open item.
- [ ] “Received,” “reviewed,” and “approved” are not being used as synonyms.
- [ ] Approved changes are copied into the current production instruction.
- [ ] Open, rejected, and superseded items remain visible in the history.
- [ ] The supplier has the same final revision the buyer is using for release.
- [ ] The final package is stored with the order record for later receiving and QC reference.
FAQ
Is a sample deviation log the same as a golden sample?
No. A golden sample or approved sample is a reference. The deviation log records changes against that reference and tracks the decision. You may use the approved sample as the baseline, but the log should still identify it precisely and preserve any later revisions.
Should every supplier message be copied into the log?
No. Keep evidence that supports identification, impact review, and the decision. A message that changes the meaning of an instruction or explains a proposal is important. Routine discussion that adds no decision evidence can remain in the normal order record, provided the deviation log points to the relevant source when needed.
What if the supplier changes something without telling the buyer?
Record the observed difference as a deviation, identify the reference used for comparison, attach the evidence, and set the status to open or clarification required. Do not rewrite an unconfirmed explanation as fact. The log creates a clear question for review; it does not itself decide responsibility or remedy.
Can a sourcing agent approve a change for the buyer?
Only when the buyer’s actual agreement or written delegation gives the agent that authority. Otherwise, the agent can coordinate evidence and communicate instructions while the buyer or brand owner remains the decision owner. Record the authority and scope clearly rather than assuming it.
Do I need a new sample for every change?
That depends on the change and the buyer’s acceptance process. A document or photo comparison may be enough for one visual update, while a component, construction, fit, or packaging change may require a physical sample or a more specific review. The log should record what evidence was used and why the decision owner considered it sufficient.
Does this log replace quality inspection?
No. It controls the approval trail for changes. It does not establish a sampling plan, inspect all units, verify every carton, determine compliance, or guarantee the contents of a shipment. Use the log as one input to the quality and shipment workflow.
How early should I start the log?
Start when the first approved reference exists and keep it active until the production revision is released. Starting only after a dispute appears usually means the original baseline and decision scope are harder to reconstruct.
Turn sample changes into a decision record
The practical value of a China supplier sample deviation log is its clarity. The buyer can see the approved reference, the proposed difference, the evidence available, the impact questions, and the person who must decide. The supplier receives a specific instruction instead of an informal memory. A sourcing coordinator can organise the record without pretending to approve what the buyer has not approved.
If your China sourcing workflow has several suppliers, revised samples, translated messages, or packaging and labelling handoffs, Style Sourcing can help you structure the sourcing conversation around the records that need to be checked. Review the China sourcing service page for the relevant service bridge, or use the Style Sourcing contact page to describe the product, supplier situation, approved baseline, and the changes that remain unresolved. Keep the request factual: a service conversation should begin with the evidence and decisions you actually need to organise.
