A supplier message saying “the material is unavailable” or “we found an equivalent component” can arrive when production is under pressure. The proposed change may be sensible. It may also affect product appearance, fit, performance, packaging, quality checks, cost, lead time, or the records supporting the product. The problem is not that factories propose changes. The problem is allowing a change to move from a chat message to the production line without a controlled decision.
Factory production changes in China should be handled through a simple written process: identify the approved baseline, document exactly what will change, assess the impact, make an authorised decision, identify the first affected production, and verify implementation. This lets a buyer accept sensible improvements without losing track of the product version being made.
This guide is for importers, brands, and e-commerce sellers. It provides operational guidance, not legal, regulatory, engineering, or contract advice for a specific product.
Start with an approved baseline
You cannot control a change unless you can name the current product version. Assemble the documents and physical references that define the approved baseline before production begins. Depending on the product, this may include the specification sheet, drawings, bill of materials, component list, approved sample, packaging artwork, labeling files, quality checklist, test plan, and supplier quotation.
Give each document a clear identifier and revision number. “Same as last order” is not enough when a factory has worked from more than one sample, color reference, artwork file, or component option. If the written specification and physical sample conflict, resolve the conflict before reviewing a proposed change.
Arena describes an engineering change order as a formal review process for a proposed change to an established product baseline. It identifies affected components and the reason for the change, and can include document markups, implementation instructions, and part effectiveness information.1
For a sourcing order, the same discipline can be practical without creating an overly complex system. The buyer needs to know what was approved, what will change, and when the new version takes effect.
Require a change request that shows old and new states
A supplier should not need a long legal form to propose a change. It should provide enough information for the buyer to compare the current and proposed state. “Equivalent material” is not a usable request unless the supplier identifies the current material, proposed material, reason, affected product version, and supporting evidence.
Ask the factory to submit a change request before implementation. The request should include:
| Change-request field | What to record |
|---|---|
| Product identity | Product code, SKU, order number, and current revision |
| Current baseline | Existing material, component, drawing, artwork, packaging, process, or supplier reference |
| Proposed change | Exact old value and new value, with marked documents or side-by-side comparison |
| Reason | Availability, obsolescence, quality correction, cost, lead time, buyer request, or process improvement |
| Scope | Products, components, lots, packaging, tools, work instructions, or suppliers affected |
| Timing | Requested decision date and proposed effective production date or lot |
| Commercial impact | Price, MOQ, lead-time, tooling, freight, inventory, or packaging effect |
| Evidence | Samples, material information, drawings, test results, photographs, or supplier declarations |
SourceDay explains that material substitution can begin with a genuine supply disruption, but that technical acceptance alone does not resolve the operational question. Availability, timing, pricing, supplier commitment, and current planning information need to align before production can rely on the substitute.2
The same principle applies to a new zipper, package insert, logo method, mold adjustment, production site, or sub-supplier. The buyer does not need to assume every change is unsafe. The buyer needs enough information to decide whether the specific change is acceptable for the product and order.
Assess the impact before approving anything
Review the impact across the product and the order. A small material change can affect appearance or performance. A packaging change can affect damage risk, carton dimensions, barcodes, and freight. A component change can affect compatibility, quality checks, or customer instructions.
Use a cross-functional review when the product warrants it. The sourcing lead can gather factory information. The product owner can assess design and customer impact. A quality lead can set verification. A qualified regulatory or technical adviser can assess a product-specific requirement where needed. Procurement or commercial owners can assess price, MOQ, and schedule.
| Impact area | Questions to resolve |
|---|---|
| Product fit and function | Does the change affect dimensions, interfaces, performance, appearance, or user operation? |
| Materials and components | Does the new item match the approved requirement, and can the supplier document it? |
| Quality and reliability | Do inspection criteria, tolerances, workmanship, or functional checks need updating? |
| Packaging and identification | Do packaging protection, artwork, labels, barcode, carton dimensions, or shipping marks change? |
| Supply and timing | Can the supplier deliver the proposed input in time and identify when it will enter production? |
| Commercial terms | Do price, MOQ, tooling, lead time, payment, or freight assumptions change? |
| Inventory and traceability | What happens to old materials, work in progress, finished goods, spare parts, and packaging? |
| Product-specific obligations | Could relevant testing, labeling, documentation, or other qualified review be affected? |
Do not approve a change only because it sounds minor. Review depth should match risk. A spelling correction to non-critical artwork may need a short document update. A change to a safety-related component or a regulated product feature may need qualified review and supporting evidence.
Choose the right decision type
A change request should result in a clear decision. The buyer can reject it, approve a permanent revision, or approve a bounded deviation. These operational labels help the supplier know whether the current product baseline remains in force.
A rejected change leaves the existing version unchanged. State the reason and tell the supplier whether it should propose another option.
A permanent revision changes the continuing production baseline. The buyer should identify the new documents, approved evidence, effective production point, and any new inspection or packaging controls.
A bounded deviation permits an exception for a stated quantity, lot, serial range, or time period. It should state the scope, acceptance criteria, evidence required, and expiry. It should not silently become the new standard after the exception ends.
Ocean Port Link describes this distinction as a practical control: a revision permanently updates the approved baseline, while a deviation authorises a defined exception and expires unless a separate permanent change is approved.3 The labels can vary by company. The important point is that the supplier knows which version applies and how long the exception is valid.
Control the first affected lot and old stock
An approval is incomplete if the factory cannot identify where the new product state begins. State the first affected lot, production date, serial range, work order, or another traceable marker. The factory should confirm the actual implementation point after production begins.
Then identify what happens to old materials, work in progress, finished goods, packaging, and spare parts. The buyer and factory may decide to use existing stock, rework it, relabel it, segregate it, return it, or handle it in another appropriate way. The decision depends on the product and commercial relationship. The control requirement is that old and new versions are not mixed invisibly.
This is particularly important when a change affects packaging, color, labels, or an internal component. A mixed shipment can create customer-service, inspection, documentation, and inventory problems even when each version is acceptable by itself.
Use the factory’s production records, carton marks, batch identifiers, or other agreed traceability method to link the change request with the finished product. Do not rely only on the date that the supplier expected to make the change; material availability or a line delay may shift the actual boundary.
Verify the first production after the change
Approval predicts that a proposed change is acceptable. Verification checks what the factory actually implemented. The required evidence depends on the change and product risk. It may include a first-off comparison, updated sample, measurement, functional check, packaging review, material declaration, targeted test, or inspection against an updated checklist.
Arena recommends documenting implementation steps and reviewing change orders after implementation to confirm that the change meets the required quality and performance requirements.1 For a sourcing project, that means keeping the request open until the buyer has the agreed implementation evidence and can identify the affected production.
Do not ask an inspector to decide whether a vague change is acceptable after goods are complete. The product and acceptance criteria should be defined before the inspection. The inspector can then compare the production units with the approved revision, sample, and checklist.
Keep one change-control log
Supplier emails, chat messages, files, and inspection reports can fragment a change history. Maintain one log that records each request from proposal to closure. It can be a controlled spreadsheet for a smaller program, provided every party uses the same current record.
| Status | Meaning | Production instruction |
|---|---|---|
| Proposed | Supplier has requested a change | Do not implement |
| Under review | Buyer is assessing impact and evidence | Do not implement |
| Rejected | Existing baseline remains in force | Do not implement proposed change |
| Approved revision | New continuing version released | Implement only from the stated production point |
| Approved deviation | Limited exception released | Implement only within stated lot, quantity, or time period |
| Implemented | Factory reports the change entered production | Verify first affected output |
| Closed | Evidence, documents, and production boundary reconcile | Archive the record |
Review open changes before a production milestone, inspection, and shipment release. An old request that was approved in principle but never verified may still create uncertainty. Treat approval and closure as different stages.
Confirm release documents before shipment
Before shipment approval, reconcile the final product version, packaging version, carton marks, inspection report, and shipment documents against the closed change log. If a production lot was made under a bounded deviation, make sure the documents identify the agreed exception and that the shipment is not described as the permanent baseline. This last review helps the buyer avoid sending an older specification to the freight team or receiving a document set that does not match the product in the cartons.
Give the factory a simple written rule
A factory instruction should be direct and usable. The following wording can be adapted to your product and purchase order:
Do not change an approved material, component, dimension, process, production site, sub-supplier, tool, firmware, packaging, artwork, or test method without a written change request. Show the current and proposed state, reason, affected production, commercial impact, and evidence. Do not implement the change until the buyer issues written approval identifying the effective lot or exception limit. Provide the agreed first-implementation evidence before the request is closed.
This rule does not prevent a factory from raising a real supply or manufacturing problem. It gives the factory a route to explain the problem and gives the buyer a controlled way to decide.
Frequently asked questions
What should I do when a factory says a substitute is equivalent?
Ask for the exact old and proposed item, the reason for the change, affected product version, availability, cost and lead-time impact, and evidence relevant to the product requirement. Review the change against the approved baseline before allowing it into production.
Can a supplier make a temporary change without approval?
A temporary change can still affect the product, shipment, or records. If the buyer accepts a time-limited exception, define the exact lot, quantity, or period and the conditions. Do not rely on an informal statement that the change is temporary.
Does a change request replace quality inspection?
No. Change control defines the product version and the evidence needed for approval. Inspection verifies finished or in-process output against the approved product standard and inspection criteria. Use both where appropriate.
Make changes visible before they become inventory
Factory production changes in China are easier to manage when every change starts with a named baseline, a documented old-versus-new request, a proportionate impact review, an authorised decision, a traceable production boundary, and verification. The process protects both the buyer and the factory because it turns hidden assumptions into a visible decision trail.
Supplier Ally can help buyers maintain product records, gather supplier change information, coordinate sample and production reviews, track effective lots, and support quality-control communication. For technical, regulatory, contract, or product-safety questions, seek qualified advice before approving a change.
EN 
ES 