Keep a file only if it helps you prove what was ordered, what was built, what was tested, and what the customer saw for a specific shipment; skip it if it cannot be tied to a SKU and a lot. The compliance records you retain after an RC (radio-controlled) toy shipment are the difference between answering an audit in a day and scrambling through a recall blind. The strongest retention system is one where commercial, technical, test, artwork, and change records all share the same SKU and lot reference — each file answers a different question, and they only work together if they point to the same physical cartons.
This guide maps each record type to what it proves, explains why a golden-sample report is not a shipment certificate, and gives you a practical checklist to review before your next PO leaves the factory.
Why does record retention matter after an CoreRCCar shipment?
Records exist to support your market and recall obligations, not to fill a folder. Supplier records for materials, production, inspection, change control, and testing should be retained long enough to support the buyer's market and recall obligations. That is the umbrella rule — no specific year count is prescribed here, because the right duration tracks your product's lifecycle and the markets you sell into.
Think of a recall or a customs hold. An authority asks: which units are affected, what did they contain, and how do we know? The answer comes from files that share one SKU and lot. If your test report says one color and your packing list says another, or your drawing revision predates the tooling that actually ran, the chain breaks. An auditor cannot confirm the tested product matches the shipped product, and a recall cannot be scoped to the correct units.
There is also a commercial angle. When you reorder the same SKU, the factory will ask which version you approved. If your retained drawing revision, FAI (first article inspection), and approved sample are linked, you can reorder with confidence. If they are scattered, you risk reordering against an outdated file — the exact failure a revision-controlled system prevents.
Which five record groups should you keep?
Group your retained files the way you will use them. Five groups cover nearly every audit and repeat-order scenario for an CoreRCCar.
Commercial records — PO, commercial invoice, packing list. These prove what you ordered and what shipped. Keep all versions, including amendments. A correction without context can look like an attempt to hide a mistake.
Technical records — the drawing or 3D-model revision, tooling records, and FAI. A drawing revision should be linked to the tooling, FAI, test sample, and production order so an old file cannot silently return to use. This is the group that stops an outdated design from sneaking back into a new production run.
Test records — lab reports, the Children's Product Certificate (CPC) for the US market, and the EU Declaration of Conformity (DoC) where applicable. This group proves what was verified. The critical limitation: a type-test or golden-sample report does not automatically cover a later production lot. You must match the report's SKU, materials, colors, and production date or cohort to the PO.
Artwork and marking records — packaging proofs, warning labels, and tracking-label artwork. Tracking information should be permanent and support product identification where applicable. Review packaging, product markings, and lot control together. What the consumer sees on the box is a controlled field that can change with the SKU.
Change records — engineering change notices (ECNs), deviation approvals, rework logs. These prove what changed between lots. If you approved a battery compartment tweak in March and the factory shipped the old design in June, the change record is what surfaces the discrepancy.
Why is a golden-sample report not enough for your shipment?
A common trap is treating one shiny test report as coverage for everything the factory ships afterward. It is not. A type-test or golden-sample report does not automatically cover a later production lot.
Importers should match the report's SKU, materials, colors, and production date or cohort to the PO. If the report says red plastic and your PO shipped blue, or the report was issued for a pre-production sample in January and your goods ran in August, the match is weak. Ask the factory to confirm the report corresponds to the actual configuration and cohort you are importing — or ask for a fresh report if the configuration changed.
The same logic applies to certificates. A Children's Product Certificate (CPC) is product-specific and should not be described as a blanket factory certificate. It is based on testing results and identifies the applicable rules and responsible parties. In the EU, CE marking and the Declaration of Conformity belong to the conformity process and must be matched to the product scope. Both must be tied to a SKU, a report, a responsible party, and a current version.
Which battery and electrical files should you retain for CoreRCCar?
CoreRCCar run on batteries, and the battery compartment is one of the first places a safety reviewer looks. Battery compartments should be checked for child access, retention, polarity protection, and correct closure after use and abuse. That means your retained test file should include evidence these checks were performed on the actual configuration you shipped — not just on the original concept sample.
If your CoreRCCar is electrically operated and intended for children 12 and under, the US certificate should list the applicable electrical regulation (16 C.F.R. part 1505) rather than only the general ASTM F963 section. If CoreRCCar has paint, the certificate should cite 16 C.F.R. part 1303. If small parts are a concern, 16 C.F.R. part 1501 applies. Ask the factory for the certificate and verify the citations match your product's features. If you are unsure which sections apply, ask the factory for the actual report and have it reviewed against the current regulation before you quote it.
Note that facts here do not name a specific battery test standard for RC compartments. If a supplier claims a particular battery standard, ask to see the report and verify the standard edition is current.
How long should you keep the files?
There is no single verified retention period in years that applies across all markets and product types. The governing principle is practical: retain records long enough to support the buyer's market and recall obligations.
What does that mean in practice? Your retention horizon should extend past the last unit sold in a market, because a recall can surface after the product is off the shelf. Many importers keep records for the life of the SKU plus several years after the final shipment, but the right number depends on your contracts, your market's rules, and your own risk tolerance.
Build a retention policy that names the record groups, the owner, and the trigger for destruction. A policy that says "keep everything forever" is as unhelpful as one that says "keep what you have." Decide what you keep, who can access it, and when it can be purged.
Key Takeaways
- Link every retained file to a SKU and a lot reference. Commercial, technical, test, artwork, and change records only support an audit or recall when they point to the same physical shipment.
- A golden-sample or type-test report does not automatically cover a later production lot. Match the report's SKU, materials, colors, and production date or cohort to your PO before relying on it.
- Certificates are product-specific, not factory-wide. A Children's Product Certificate (US) and an EU Declaration of Conformity must each be tied to a specific SKU, report, responsible party, and current version.
- Retain battery-compartment evidence covering child access, retention, polarity protection, and correct closure after use and abuse — checked on the configuration you actually shipped.
- No single retention period in years is universally prescribed. Keep records long enough to support your market and recall obligations, and document a clear retention policy with owners and destruction triggers.
Record types and what they prove for an RC shipment
| Commercial | PO, invoice, packing list. Proves what was ordered and shipped. Keep all versions and amendments. |
|---|---|
| Technical | Drawing or 3D-model revision, tooling records, FAI. Links the design to the tooling and production order so an old file cannot return. |
| Test | Lab reports, CPC (US), EU DoC. Proves what was verified for a specific configuration and cohort — not later lots. |
| Artwork & marking | Packaging proofs, warning labels, tracking-label artwork. Tracking info should be permanent and reviewed with lot control. |
| Change | ECN, deviation approvals, rework logs. Proves what changed between lots. |
| Battery file | Evidence of checks for child access, retention, polarity protection, and correct closure after use and abuse. |
How do you build a retrieval system for repeat orders?
A retention system earns its keep at reorder time. When you go back to the factory for another run of the same SKU, you need the approved drawing revision, the test report that matches the configuration, and the artwork proof — all in one place.
Ask the factory to confirm the revision status before you place the repeat PO. If the drawing changed but your file still shows the old revision, you are about to reorder against an outdated spec. The revision should be linked to the tooling, FAI, and test sample so the factory builds what you approved, not what they last had on the line.
The practical test is simple: can you pull one folder for a SKU and answer these questions? What did we approve? What did the factory build? What did the lab test? What did the customer see on the box? If the answer to any of these lives in a different system with a different reference, consolidate it.
FAQ
Do wholesale RC car suppliers provide EN71, ASTM or CE documents by SKU for export?
Reputable suppliers should provide test reports and certificates tied to a specific SKU, but you must verify the match. A report is only useful if its SKU, materials, colors, and production date or cohort match your PO. Ask the factory to confirm the document corresponds to the exact configuration you are importing, and check the standard edition is current.
What is the minimum retention period for compliance records after an RC shipment?
There is no single verified retention period in years that applies universally. The principle is to retain supplier records for materials, production, inspection, change control, and testing long enough to support your market and recall obligations. Confirm the expected horizon with your legal counsel based on your target markets.
Can I use one ASTM F963 test report for multiple production lots of the same RC car?
Not automatically. A type-test or golden-sample report does not cover a later production lot unless the report's SKU, materials, colors, and production date or cohort match the PO. If the configuration is unchanged, confirm the match with the factory; if anything changed, request an updated report.
Which battery-related records should I keep for an CoreRCCar shipment?
Keep evidence that battery compartments were checked for child access, retention, polarity protection, and correct closure after use and abuse — on the configuration you actually shipped. If the supplier claims compliance with a specific battery standard, retain the actual report and verify the standard edition is current.
What should I verify on a Children's Product Certificate (CPC) before retaining it?
Verify the CPC lists the correct regulatory citations for your product. For an electrically operated CoreRCCar intended for children 12 and under, the certificate should list the electrical regulation (16 C.F.R. part 1505). If CoreRCCar has paint, it should cite 16 C.F.R. part 1303. Confirm the certificate is product-specific and names a CPSC-accepted lab.
Sources
Request a Quote
Need help verifying that the compliance documents for your next RC shipment will match your SKU and lot? Send us your product specs and target market, and we can help you review what to request from the factory before you place the PO.