Say no to any factory change notice you cannot compare against the sealed golden sample on your QC shelf. That single physical piece — not an email, not a Fair photo — is the acceptance standard for a repeat order, and every proposed component or process change should be reviewed against it on five axes: performance, compatibility, compliance, cost, and customer communication.
This checklist walks importers, Amazon sellers, supermarket buyers, gift distributors, and private-label buyers through the sequence: log the notice, compare old part versus new part against the physical sample, confirm revision identity, demand samples before lot release, map compliance paperwork to the correct market and lot, review packaging and the booking file, check spares and old/new compatibility, document cost impact, and pre-write the customer message. Release only after every checkpoint passes. If a lot fails, isolate it, record defect class, and release only after rework.
Key Takeaways
- A supplier should notify the buyer before changing resin, colorant, mold, process, component, sub-supplier or packaging that can affect the CoreRCCar — treat silence as a red flag, not as continuity.
- Approve only against the sealed golden sample; a photo, a Canton Fair booth unit, or a chat acknowledgement is not an approved baseline.
- A production lot should be traceable to a defined product model, material or component lot, process window and production time range — if the factory cannot name which lots a change touches, you cannot scope the review.
- A useful traceability record links the SKU, mold cavity, resin lot, component lots, production date, operator/process and carton or pallet identifier; without it, a change notice is just paperwork.
- For spray, lithium, FCC, or IP claims, request the actual report for the specific market and lot — do not accept a summary sentence, and do not let one certificate cover two different tests.
What counts as a change notice on CoreRCCar reorder?
A change notice is any factory-declared or buyer-requested difference from the last approved production baseline that can affect the CoreRCCar — and the list is wider than most buyers assume. It covers resin, colorant, mold, process, component, sub-supplier, and packaging. A new ABS supplier, a repaired or re-cut injection tool, a swapped electronic component, a different spray nozzle, a revised colorant batch, a new carton printer, or a moved production line all qualify.
A repeat order can carry the same product name and the same part number while the material, dimensions, construction, packing, label artwork, supporting documents, quantity, or schedule have moved. "Same as last time" is not a specification. The correct reference is the last released production baseline — the final specification revision, supplier product code, approved sample identity, packaging artwork revision, and document list — not the original quotation and not the newest file in the email thread.
A process window defines the stable range of temperatures, speeds, pressures, times and cooling conditions that produce acceptable parts. If the factory shifts that window to raise output, the parts can still look right on the shelf and fail in the field. That is why process changes belong in the same review queue as component changes.
Worked example (illustrative, not a real shipment)
This scenario is illustrative only. A buyer places a repeat order for two SKUs of 2.4GHz RC cars with lights and spray, roughly 5,000 pieces total, split across two destinations: 3,000 units to a US Amazon FBA prep route and 2,000 units to an EU gift distributor. The packaging differs by market — retail blister for the US, window carton with multi-language labeling for the EU — and the cartons for the EU leg travel LCL, so the booking file specifies double-wall board, corner boards, ECT rating, and a maximum pallet height.
Two weeks before production, the factory issues a change notice: the spray nozzle sub-supplier has changed, and the ABS resin lot is from a different supplier. The buyer's review stops at step three. The new nozzle has not been compared to the sealed golden sample for spray pattern and finish; the resin change has no first-article samples; and no test report has been mapped to either market or to the affected lots.
Where this gets held: the lot is not released. The factory is asked for pre-production samples of the changed nozzle against the sealed sample, the tool number and revision card for both SKUs, and the actual test report covering the affected market and lot. Because the EU leg is LCL and corner-sensitive, the booking instruction is re-checked before the cartons are printed — packaging claims are won or lost on that file, not on a vague line in the booking instruction.
Only after the sample comparison, the revision confirmation, and the report mapping pass does the buyer approve. Had the change been accepted on the factory's "equivalent" wording alone, the risk would have surfaced at Amazon receiving or at the EU distributor's shelf — after freight, duty, and prep costs were already sunk.
Change-Notice Review Steps: What to Check and What to Reject
| Step 1 — Log the notice: old part vs new part, stated reason, affected lots/SKUs | What to check: written old reference, new reference, reason, affected SKU list, and the first affected lot or PO date. Red flag: a chat message that says "small change" with no part numbers and no affected scope. |
|---|---|
| Step 2 — Pull the sealed golden sample and compare against it | What to check: colour, fit, flash, and function against the physical piece on the QC shelf. Red flag: approval based on a photo, a Fair booth unit, or a rendering. |
| Step 3 — Confirm revision identity (tool number and revision card) | What to check: whether the revision card or tool number for the affected SKU has changed since the last release. Red flag: a supplier who cannot state the current revision for the SKU in production. |
| Step 4 — Request pre-production / first-article samples of the changed part | What to check: sample identity, date, and comparison notes against the golden sample before lot release. Red flag: production scheduled before samples are reviewed. |
| Step 5 — Map compliance paperwork to market AND lot | What to check: which test report covers which market and whether it references this specific lot; UKCA and a VOC file are different papers for different purposes. Red flag: one certificate stretched across two markets or two different tests. |
| Step 6 — Review packaging and the booking file for corner-sensitive goods | What to check: double-wall board, corner boards, ECT rating, pallet height — written into the booking instruction. Red flag: an LCL booking instruction that reads like a thank-you note. |
| Step 7 — Check spares availability and old/new compatibility | What to check: whether spares for the old part remain available and whether new parts are backward-compatible with units already in the field. Red flag: a change that strands existing inventory or warranty stock. |
| Step 8 — Document cost impact (unit cost, MOQ, tooling) | What to check: written unit cost and MOQ effect, plus any tooling implication; MOQ is confirmed per SKU and per change, not assumed. Red flag: a price change disclosed after the PO is issued. |
| Step 9 — Pre-write the customer communication | What to check: what downstream buyers — Amazon, supermarket, gift — need to know and when. Red flag: a change that reaches the retail shelf before the buyer's own customer message is drafted. |
| Step 10 — Approve, hold, or reject the lot | What to check: every prior checkpoint passed, with a named owner and a decision recorded. Red flag: release on silence. If a lot fails, isolate it, record defect class, and release only after rework. |
Which certification applies CoreRCCar sold in the EU, and which to the US?
The certification that applies depends on the destination market, the product category, and the specific claim being made — and the buyer's job is not to memorize the list but to map each file to the correct market and the correct lot. UKCA and a VOC file on an electric bubble machine are different papers; a buyer once tried to use one certificate for both. That is a paperwork mismatch, and paperwork that does not match the lot is not paperwork.
For spray, lithium, FCC, or IP claims, ask the factory for the actual report rather than a summary. The report should reference the specific market and, where the factory's system supports it, the affected lot. If the official text does not confirm an application date for a given regime, write that the timeline is not confirmed from official text — do not convert a headline year into a mandatory date on every unit. Digital Product Passport, GPSR, CoreRCCar safety rules are separate regimes and should never be collapsed into one deadline.
One short compliance box belongs in your change log per SKU: market, applicable document, lot reference, and open question. Anything you cannot fill in is an open item, not an approval.
Change-Control Record: Fields to Fill Before Release
| Change ID | Unique reference for this notice |
|---|---|
| Project / PO | The repeat order this change affects |
| Buyer SKU / supplier reference | Both sides' identifiers |
| Approved baseline revision and sample ID | Last released spec revision and sealed sample identity |
| Affected area | Component, process, material, packaging, sub-supplier |
| Current condition vs proposed condition | Old part and new part stated in writing |
| Reason for the change | Factory's stated reason, recorded verbatim |
| Affected scope | Which lots, SKUs, markets, and first affected PO date |
| Evidence requested | Samples, reports, revision card, booking file |
| Owner and due date | Named role, not a team |
| Disposition | Unchanged / accept with documents / sample review required / revise / reject / hold |
| Effective boundary | First affected PO, shipment, lot, or date |
| Closure and linked files | Approval date, linked evidence, open actions |
What to ask suppliers before approving a repeat-order change
Put these questions in writing and require written answers. A supplier who cannot answer them is not ready for the change to enter production.
Ask for the old part number, the new part number, and the stated reason for the change. Ask which production lots are affected and from which date. Request pre-production samples of the new part for comparison against your sealed golden sample. Ask for the tool number and revision for the affected SKU, and whether the revision card has changed. Ask which test report covers this change, for which market, and whether it references this specific lot. For spray, lithium, FCC, or IP claims, ask for the actual report — not a summary.
Then move to commercial and downstream questions: unit cost and MOQ impact of the change; whether spares for the old part remain available and whether new parts are backward-compatible; what packaging and booking specification applies to this lot; and what the factory's internal defect-class and rework procedure is if this lot fails. Finally, ask what the first affected PO or shipment date is, so the effective boundary is recorded before material enters production.
Two cautions. First, do not ask for an AQL number from a catalogue sentence — the number comes from the agreed inspection plan on the PO. Second, if the factory says the change is "equivalent," treat that as a conclusion to be evidenced, not an answer. Request the current state, the proposed state, the reason, the affected scope, the implementation boundary, and the supporting documents.
FAQ
Can a factory change a component on a repeat order without telling me?
No — a supplier should notify the buyer before changing resin, colorant, mold, process, component, sub-supplier or packaging that can affect the CoreRCCar. If the factory's own agreement does not state which changes require notification and approval, write that clause into the next PO.
Do I need a new sample every time the factory issues a change notice?
No universal rule applies. If the approved configuration, application, finish, packaging, and acceptance basis are unchanged and documented, no new sample may be needed. A changed or unknown interface, appearance, function, or requirement justifies focused evidence or a new sample — decide per change, and record the decision.
How long should I hold a change before releasing production?
Hold until every checkpoint in the review passes: sample comparison, revision confirmation, compliance mapping, spares and compatibility, cost, and customer communication. The release is gated by evidence, not by the calendar — if the factory cannot supply the evidence before the planned production date, move the date.
Which document proves the change is compliant for my market?
A report that covers the specific market and references the affected lot — not a generic certificate covering a different test or a different market. Map market, lot, and which file covers which test before release. If the application date for a regime is not confirmed in official text, treat the timeline as unconfirmed rather than mandatory.
What if the change affects packaging or cartons for an LCL shipment?
Re-check the booking file before printing: double-wall board, corner boards, ECT rating, and pallet height should be written into the instruction. Corner-sensitive goods fail in LCL when the booking instruction is vague, and claims are won or lost on that file.
What do I do if the changed lot fails inspection?
Isolate the failed lot, record the defect class, and release only after rework. The defect classification should come from the agreed inspection plan on the PO, not from a catalogue sentence or an improvised standard.
Should I update my inspection checklist when I approve a change?
Yes — the change record authorizes the version; the inspection checklist verifies that the delivered order matches it. Updating one without the other leaves records pointing at different approved states, and a shipment inspection cannot fix an unclear approval history after production.
Sources
- Before Reordering Disposable Protective Products: Build a Change-Control Record
- How to Evaluate Repeat-Order Consistency in Portable Speaker Manufacturing
- LED Display Screen Supplier BOM Locking: Component Substitution Rules, Firmware Versions and Batch Traceability
- Repeat Lock Order Change-Control Checklist WELLHW
Put the checklist on your next repeat order
Copy the change-control record fields into a spreadsheet and use them for every factory change notice on your next reorder. When a supplier proposes a component, process, or packaging change, the answer is not yes or no — it is which checkpoints have evidence attached. Require written answers to the supplier questions above, record the effective boundary, and release only after the sample comparison, revision confirmation, and report mapping pass.