Product Change Control With Chinese Suppliers: Stop Unapproved Changes Reaching Production

Meta description: Control supplier changes with a documented request, impact review, approval, effective lot and verification trail before production.

Do not let a proposed product change move from a chat message to the production line. Put it through five gates: identify the approved baseline, record the exact old and new state, assess the effects, issue an authorised decision, then verify the first affected lot before closing the record.

That rule applies whether the proposal concerns a material, component, dimension, process, manufacturing site, sub-supplier, tool, firmware, packaging, artwork or test method. The review depth changes with the risk; the need for an attributable decision trail does not.

This is product change control in practical terms. It does not guarantee that nothing will go wrong, and a signature does not make an unsafe change acceptable. It gives an Australian importer a way to stop undocumented drift and prove which configuration was approved for which production.

The control is simple: no change without a closed record

ISO 10007:2017 provides international guidance on configuration management—the discipline of identifying and controlling configuration information through a product's life cycle. ISO reports that the 2017 edition was confirmed in 2023; it is guidance, not a mandatory importer form.

For an importer, translate that discipline into one operational rule:

Decision rule: The supplier may propose a change, but the affected production remains on hold until the buyer's authorised process has assessed and released it. The change record is not closed until the effective production is identifiable and the required implementation evidence has passed.

Use two different decisions.

• A revision permanently updates the continuing approved baseline.
• A deviation permits a defined exception for a stated quantity, lot, serial range or period. It expires and does not silently replace the baseline.

Do not call a substitution “temporary” without a limit. Do not call it “equivalent” without acceptance criteria and evidence. And do not treat silence, a messaging-app reaction or shipment pressure as approval.

Start with a baseline that can be named

Change control cannot work if nobody can state what is changing. Assemble the controlling baseline before reviewing the proposal:

• product specification, drawing and bill-of-material revisions;
• controlled firmware, colour, artwork and packaging files where relevant;
• approved golden sample or other physical reference, including custody and precedence rules;
• applicable test reports and certificates tied to the product version;
• approved manufacturing site, material source, critical sub-supplier and process where those are controlled;
• quality-control plan, inspection criteria and test methods; and
• commercial records affected by the change, such as cost, MOQ, mould and tooling ownership controls, lead time and inventory commitments.

Give every controlled item a document identifier and revision. “Same as last order” is not enough when the last order contained multiple drawing, sample or artwork versions.

If the written specification conflicts with the sample, resolve the precedence before assessing a change. Otherwise, the supplier and buyer can both claim to preserve the baseline while following different references.

Require an exact old-versus-new request

The supplier's reason may be valid: an input may be unavailable, a component may reach end of life, a process may need improvement, or the buyer may have requested a feature. The reason does not define the effect. Require a record that makes comparison possible.

Attach marked-up documents. A clean new drawing alone hides what moved. A redline, old/new BOM extract or side-by-side material declaration lets the reviewer see the proposed delta.

The agreed change-control process should name who owns the decision status. A supplier can draft the request and provide evidence, but it should not mark its own proposal approved on the buyer's behalf unless the agreed authority model expressly permits that decision.

Assess the impact before discussing approval

Review consequences in parallel, not one department at a time after production has started.

For Australian consumer products, the ACCC's sourcing and testing guidance tells suppliers to examine factory controls, raw materials, assembly processes and quality checks. It also warns that safety testing may need to follow design, material or production changes. The required response depends on the product and applicable Australian rules.

That is not a blanket instruction to repeat every test for every wording or process change. Ask a competent reviewer which requirements could be affected, then document the justified assessment and test scope. If that expertise is unavailable for a safety-relevant change, hold the change.

For packaging or dimensional changes, use a consistent measurement method. The GS1 Package and Product Measurement Standard supports retaking measurements when a product or package change may affect linear dimensions or weight. GS1 is industry guidance and local law prevails, but the basic control is useful: do not let revised freight or identification data rest on old measurements.

Decide: reject, approve, or issue a bounded deviation

Every request needs one of three outcomes.

Reject. State why, identify whether another proposal is invited, and confirm that the existing baseline remains controlling.

Approve a revision. Name the new document revisions, evidence, conditions, effective production and required implementation checks. Release updated controlled files together so an old artwork or inspection instruction does not survive beside a new BOM.

Approve a deviation. State the exact quantity, lot, serial range or time window; acceptance criteria; any additional checks; inventory disposition; and expiry. After expiry, production returns to the original baseline unless a separate permanent revision is approved.

A decision should show who had authority to make it. Engineering or product may assess function; compliance may assess an applicable rule; quality may set verification; procurement may accept cost and schedule. Define who must concur for the change category before the request arrives.

Conditional approval is not permission to fill evidence in later. Phrase conditions as gates: “approved for lot L2408 only after report X passes acceptance criterion Y,” not “approved, test report to follow.”

Control the effective lot and old stock

The approval has little value if the factory cannot say where the new state begins.

Record an effective lot, date, serial range or other production marker that can be found in factory records and, where necessary, on the product or packaging. Then reconcile:

1. unissued old raw material and components;
2. work in progress at each process step;
3. finished but unshipped product;
4. packaging, labels, manuals and spare parts;
5. open purchase orders and reorders; and
6. inspection plans and test records.

Choose a disposition for each: consume under an approved limit, rework, relabel, return, scrap, quarantine or keep as service stock. These are case-specific commercial and technical decisions. The control is that no category remains invisible.

Do not rely on a planned implementation date alone. A delayed material delivery or mixed-bin issue can shift the actual boundary. Require the supplier to record the actual first affected lot and confirm that old and new stock were segregated.

Verify the first affected production

Approval predicts that the change is acceptable. Implementation verification checks what the line actually produced.

Choose evidence from the assessed risk:

• first-off or first-article measurement against the released revision;
• the relevant product sample stage when buyer approval is required;
• targeted safety, compliance, functional, material or reliability test;
• updated incoming, in-process or final checks in the quality-control plan;
• an appropriate quality inspection stage; and
• lot, serial, material, process or packaging records linking the result to the affected production.

Do not use inspection as a substitute for an unresolved design decision. Inspectors can compare output with a defined requirement; they cannot decide what an ambiguous requirement should have been.

Keep the request open until the implementation evidence passes, affected documents are released, actual effective production is confirmed, old stock is disposed of and any failed condition has a recorded response. “Approved” and “closed” are different statuses.

Worked example: a proposed material substitution

This example is hypothetical. The material codes, document numbers and results are not an OPL customer case or supplier claim.

A supplier asks to replace housing resin ABS-A with ABS-B because its current source cannot meet the next order date. The controlled baseline is drawing R07, BOM R12, golden sample GS-04 and an applicable test file tied to ABS-A.

The example does not prove ABS-B is equivalent to ABS-A. It shows why a trade name or supplier assurance cannot replace the affected-requirement review. If the evidence passes for the bounded lot and the buyer wants the change to continue, issue a separate permanent revision.

Use the change log as a production control

Maintain one register across email, messaging and factory documents. At minimum show:

Reconcile open changes before releasing a purchase order, before bulk production, before inspection and before approving shipment. An old “approved” request can still be open if the effective lot or implementation evidence was never confirmed.

Use this supplier instruction:

Do not change any approved material, component, dimension, process, manufacturing site, sub-supplier, tooling, firmware, packaging, artwork or test method without a written change request. Show the current and proposed state, reason, affected documents, inventory, cost, MOQ, schedule, risk and required evidence. Do not implement until the named buyer approvers issue a release identifying the effective lot or deviation limit. Provide first-implementation evidence for closure.

Adapt the categories and approvers to the product. A generic clause is not a substitute for an operating register that both sides actually use.

What to do next

Choose one active SKU and assemble its controlled baseline. Open a change register with the fields above, define who can approve each risk category, and tell the supplier which changes require a request.

For every open proposal, force four facts into view: the exact old and new state, the evidence needed for decision, the production boundary, and the proof of correct implementation. If one is missing, the change is not ready for release.

The aim is not to prevent all improvement. It is to ensure that cost, availability or speed never changes the product invisibly—and that an approved change can be traced from its reason to the first conforming production lot.

Sources

1. ISO 10007:2017 — Quality management: Guidelines for configuration management
2. ACCC Product Safety — How to source and test products
3. GS1 Package and Product Measurement Standard, Release 3.3