When a China Factory Proposes a Substitution: The Buyer’s Change-Control Record

A factory’s substitution request should trigger a document decision before it triggers a production decision. “Equivalent” is not a complete approval: the buyer needs to know which approved reference is changing, what evidence supports the replacement, who can release it, and which order or lot is covered.

The safest practical rule is to keep the original requirement active until a named buyer-side owner records a different decision. If the proposed material, component, process, or source cannot be matched clearly to the purchase order and product revision, production should remain on hold for the affected item.

Start with the proposed change, not the supplier’s conclusion

Ask the factory to describe the substitution in specific terms. The notice should identify the product or SKU, purchase order, current approved item, proposed item, reason for the request, affected production date, and any upstream manufacturer involved. “New supplier” may mean a different raw-material maker, a different subcontractor, a different machine, or simply a new internal code. Those are not interchangeable risks.

Request the factory’s comparison in a format that can be checked against your own records. For a material, compare grade, formulation, color reference, dimensions, performance data, and manufacturer. For a component, compare part number, electrical or mechanical characteristics, compatibility, and revision. For a process change, record the equipment, location, subcontractor, process sequence, and inspection points.

Pull the controlled references before judging the request: the purchase order, drawing or specification, bill of materials, approved sample, packaging artwork, inspection instruction, and any customer or market requirement supplied for that product. The internal quality-plan article on agreeing checks before a China production run is relevant here because the reference set should be dated and tied to the SKU and order.

Separate an administrative change from a product change

Some changes alter the item itself. Others alter the route by which the item is made or documented. Treat both as change-control events, but do not ask the same questions of each.

Proposed change	What the buyer should verify	Possible release consequence
Raw material or formulation	Identity, grade, manufacturer, specification, and effect on finished-product characteristics	Technical review, targeted testing, and sample or first-article approval may be needed
Component or subassembly	Part number, interface, rating, dimensions, function, and availability of traceability	Do not release production if compatibility or safety evidence is incomplete
Machine, process, or subcontractor	Production location, process sequence, capability, inspection access, and lot identification	Require a revised process record or pilot verification before normal release
Packaging, label, or artwork	Revision, language, markings, carton fit, barcode, and destination requirements	Hold packing or shipment if the released artwork cannot be identified

This table is an operational recommendation, not a universal certification or testing rule. ISO describes the ISO 9000 family as helping organizations “consistently meet customer expectations” and identifies customer focus, the process approach, and continual improvement among its quality-management principles. That context supports controlled review, but it does not prescribe the test method or acceptance limit for a particular substitution.

Match each evidence item to the risk it is meant to answer

A document is useful only when it answers a defined question. Ask the supplier for the evidence that corresponds to the changed characteristic rather than collecting generic certificates.

• Identity: What exactly is the proposed material, component, process, or source? Request a part number, manufacturer, revision, and batch or lot reference.
• Performance: Which approved requirement could change? Request the relevant specification, test report, data sheet, or comparison result.
• Fit and appearance: Will the replacement look, assemble, or pack differently? Request photographs and a physical sample or first article when those characteristics matter.
• Traceability: Can the factory identify affected production? Request the lot, date, line, subcontractor, and records that distinguish old production from new production.
• Implementation: When will the replacement enter the order? Record the effective date, first affected lot, and remaining inventory of the original item.

Check whether the evidence refers to the exact proposed item. A generic supplier declaration may describe a product family without proving that the delivered part matches the declaration. Record document titles, revision numbers, issue dates, test methods, sample IDs, and the person who supplied each file.

Where a change could affect fit, function, appearance, durability, electrical behavior, odor, or packaging, a revised sample gives the buyer something concrete to compare. A sample does not automatically prove production consistency, so record its measurements and observations separately from any later production inspection.

Give one person authority to release the substitution

Procurement can coordinate the review, but one named role should own the final status. That owner may need input from quality, engineering, compliance, packaging, or the customer-facing team. Their task is not simply to collect opinions; it is to decide whether the evidence is sufficient for the defined order and requirement.

Use a status that tells the factory what it may do next:

• Approved: the replacement is released for a named product, order, revision, and effective date.
• Rejected: the original requirement remains in force and the proposed item may not be used.
• On hold: production, packing, or shipment of the affected scope cannot proceed until a stated question or evidence gap is resolved.
• Conditionally approved: a limited quantity or pilot may proceed under written checks, a defined reviewer, and a release condition.

Do not let a conditional approval become a permanent undocumented exception. State the permitted quantity, inspection point, evidence deadline, and action if the result fails. Communicate the result through the purchase-order or change-control record, not only through an informal chat message.

Build the change log around the next shipment decision

The record should allow a replacement buyer, inspector, or warehouse team to understand what was approved without reconstructing a message history. Include the change number, date opened, supplier, factory, SKU, purchase order, affected lot, old and new references, reason for change, evidence reviewed, unresolved questions, decision owner, status, conditions, effective date, and implementation check.

Add the consequence of a mismatch. For example, the instruction might say that goods using an unapproved component are to be segregated, or that shipment cannot be released until the revised label is checked against the current artwork. The exact remedy depends on the contract and product; the record should state the operational next step without pretending to create a legal remedy.

Payment and shipment gates can use the same evidence logic. The related guidance on payment milestones before production emphasizes linking a payment event to a verifiable trigger, evidence, approver, and permitted action. That is a useful model for a substitution record, although payment terms remain a contractual matter.

Hypothetical example: a connector substitution

Hypothetical example: A factory reports that the connector listed on a small electronic assembly is unavailable and proposes another manufacturer’s part. The buyer opens a change record against the affected purchase order and asks for the new part number, manufacturer, drawing, ratings, interface dimensions, compatibility statement, remaining stock of the original connector, and the first lot using the replacement.

The technical owner compares the documents and a sample against the approved connector. The buyer records that the sample is acceptable for a limited pilot but does not release the full order. The factory receives one instruction: produce the agreed pilot quantity, identify the pilot lot, and wait for the recorded inspection result before continuing. If the sample does not match, the status returns to hold or changes to reject; the original connector requirement remains active unless a new decision is issued.

This example demonstrates record structure, not a universal connector test or acceptance limit. The required review depends on the product specification, destination market, customer commitments, and consequences of failure.

What a complete substitution record proves

A complete record shows what changed, the affected requirement, evidence reviewed, decision owner, and the lot or shipment scope. Missing fields leave the factory to infer approval.

Preserve prior revisions. Update purchase and inspection documents only after approval; open a new record for each later substitution.

Frequently Asked Questions

Can a supplier approve its own proposed substitution?

The supplier can provide the technical explanation and supporting documents, but the buyer-side approval should come from a named person with authority over the affected requirement. The supplier’s statement that an item is equivalent is evidence to review, not a substitute for the buyer’s release decision.

When should the buyer request a physical sample?

Request a sample or first article when the substitution could affect fit, function, appearance, durability, electrical behavior, odor, assembly, or packaging. A low-impact administrative change may need only a documented comparison, but the record should explain why a sample was unnecessary.

What should happen if the factory uses the replacement before approval?

Identify the affected material, component, process, production date, and lot, then place the affected scope on hold while the buyer reviews evidence. Record whether the goods will be inspected, reworked, rejected, or released under a documented exception. Do not silently treat unauthorized use as approval.