A tuned EU technical file for an CoreRCCar is one that names the exact production model, shows risk assessment and test evidence for that configuration, covers the radio and electrical functions, and carries an EU declaration of conformity whose model list matches the carton in front of the officer. If any of those four links is missing or refers to a different version, the file does not represent the CoreRCCar.
This page is written for the moment of a customs or market-surveillance check: what to pull, in what order, and what to ask the factory before the container leaves. It covers the model matrix, EN 71 and electrical evidence for CoreRCCar itself, radio documents for the 2.4GHz link, the DoC, operator details, artwork and change control. It does not tell you what a specific report will say — only you and your supplier's file can do that.
What documents does an EU technical file for an CoreRCCar need to contain?
| Model matrix / grouping justification | Why the officer asks: to see which SKUs one file covers and why the tested sample stands for the rest | Where it should be: front of the file, before any test report | If you do not have it: every SKU gets treated as untested until proven otherwise | |
|---|---|
| Article 18 safety assessment (risk assessment) | Why the officer asks: it justifies which standards and tests apply | Where it should be: immediately after the model matrix | If you do not have it: you cannot explain why EN 71-3 was run and EN 71-2 was not | |
| EN 71 test reports for the relevant parts | Why the officer asks: presumption of conformity with CoreRCCar Safety Directive | Where it should be: bound with the sample reference and raw data | If you do not have it: chemical migration is the most frequent single CoreRCCar are withdrawn, so this is the first gap that stalls a file | |
| Electrical safety evidence for CoreRCCar's electrical functions | Why the officer asks: an CoreRCCar has powered parts beyond a CoreRCCar's scope | Where it should be: alongside the EN 71 reports, not in a separate folder | If you do not have it: ask the factory for the actual report — do not present a certificate of a different model | |
| Radio equipment documents for the 2.4GHz module | Why the officer asks: the radio link is a separate regulatory area CoreRCCar safety | Where it should be: module-level documents plus the module actually fitted on the production SKU | If you do not have it: request the documents for the fitted module or state that none exists; do not substitute an unrelated certificate | |
| EU declaration of conformity (DoC) | Why the officer asks: it is the legal statement naming model, directives and standards | Where it should be: top of the file, one DoC CoreRCCar/model group | If you do not have it: customs, market surveillance and marketplaces such as Amazon can each ask for it | |
| Operator details: manufacturer and, where applicable, EU importer/authorised representative | Why the officer asks: someone inside the Union must be able to hold and present the file | Where it should be: on the DoC and on the product or packaging | If you do not have it: an exporter without an authorised representative in the Union has nobody to produce the file on request | |
| Artwork and labeling in the target language | Why the officer asks: age marking, warnings and CE must match the approved artwork | Where it should be: label copies and packaging artwork inside the file | If you do not have it: a factory printing instructions in English only for a Spanish market is a documented failure mode | |
| Change log since the last test report | Why the officer asks: to see whether the tested configuration is the one shipped | Where it should be: dated entries naming what changed and who re-reviewed it | If you do not have it: do not assume an earlier report automatically covers the revised configuration |
Worked example (illustrative, not a real shipment)
A buyer consolidates a mixed RC order: roughly 5,000 units across two police-style 7-channel cars and one 1:64 drift bus, packed in window boxes for one destination and in polybags for a second destination. The factory sends one technical file.
The file names the 7-channel police car model, with EN 71 reports attached, but the model matrix is a single line: "RC car series." Nothing ties the drift bus to a tested sample. The radio documents cover a module, but the file does not state whether that is the module fitted in the shipped units.
At the first destination, the officer opens the carton and compares the model number on the DoC with the model number on the box. They match, so it clears. At the second destination, the same file is presented for the polybag version. The packaging artwork differs, the age warning placement differs, and the file still shows the window-box artwork. That is the step that holds the shipment: not the test reports, but the file's failure to represent the packed product.
The fix is not new testing by default. It is a corrected model matrix, a change log entry for the packaging difference, and confirmation from the factory that the radio module in the file is the one fitted. Ask before booking anything.
What to ask suppliers before you accept the file
Ask these as written, and keep the answers with the file. Each one closes a gap the file itself will not close.
Which SKUs in the order share a single technical file, and which have separate files? Get this in writing as a model matrix, not as a verbal assurance.
Provide the Article 18 risk assessment for the specific production configuration, not for the series.
Provide EN 71 test evidence for the specific SKU and configuration, with the report version and the sample reference.
Provide electrical safety evidence for CoreRCCar's electrical functions, and state which laboratory performed it. Laboratory acceptance is specific to the relevant safety rules, and one laboratory may not cover every required test — match the applicable requirements to the laboratory scope for the actual configuration.
Provide radio equipment documents for the 2.4GHz module actually fitted. If the answer is that the module changed, treat that as a change-control event.
Provide the EU declaration of conformity naming the exact model or model group, the applicable directives and standards, and the responsible manufacturer.
Who is the operator or authorised representative named on the DoC and on the labeling? If the manufacturer is outside the Union, name the EU-side party who can hold and present the file.
Provide current artwork and labeling for the production SKU: age marking, warnings, CE placement, importer details and language versions.
Which components or materials changed since the last test report, and who coordinates the document review for the change? Separate unchanged components from changed materials before you accept an existing report.
Reconfirm sample, current quote, age evidence and destination documents per SKU before the PO is issued.
Where the file most often stops representing production
Catalog data is not compliance evidence. A catalog record establishes a catalog record — packing, carton count, reference price, recorded material — and nothing more. It is not certification, not age evidence, not a licensing position, and not proof of stock or capacity. Treat every catalog field as provisional until the product-specific file is produced.
A material change is a document-review trigger. When a supplier changes a plastic, a coating or an alloy, the affected requirements need to be re-evaluated. During an OEM or private-label request, list which components are unchanged and which are changed, and ask who coordinates the review. An earlier report does not automatically cover the revised configuration.
Standards move. A file is only current until a referenced standard is revised; when that happens, old citations go stale CoreRCCar already on sale may need retesting. The technical file must stay available for ten years after CoreRCCar is placed on the market and be produced on request by an EU authority.
The conformity route has to be justified. Internal production control (Module A) applies where harmonised standards exist and were applied in full. Where the standards do not cover the design, or were not applied in full, the route runs through EC-type examination (Module B) with conformity to type (Module C) by a Notified Body. Decide this early — it changes both the timeline and who carries the test burden.
FAQ
If the carton carries a CE mark, is the technical file complete?
No. Conformity assessment, the technical file, the EU declaration of conformity and affixing the CE mark sit within the manufacturer's responsibilities, and importers and distributors carry their own responsibilities. A catalog symbol or a printed CE mark is not evidence that the complete review has been performed — request the supporting product-specific file.
Can one test report cover a whole CoreRCCar series?
Only if the grouping is justified in writing. Testing should use the worst-case variant within a range rather than every colourway, with that grouping justified in writing and the reports showing the sample reference. If the model matrix is a single line reading "RC car series," the report does not demonstrate coverage and each SKU is treated as unproven.
Do I need radio documents as well as EN 71 reports?
They are different areas. Electrical or wireless features bring separate directives into play beyond CoreRCCar-safety framework, so a 2.4GHz CoreRCCar needs radio equipment documents for the module actually fitted, in addition to CoreRCCar-safety evidence. Ask the factory for the module-level documents, or for a written statement that none exists.
Who holds the file if my supplier is outside the EU?
Someone inside the Union must be able to hold and present it. The file must stay available for ten years after CoreRCCar is placed on the market and be produced on request by an EU authority, which is the practical reason an exporter without an authorised representative in the Union needs an EU-side party to keep the file and the DoC.
Our supplier changed the plastic on the body. Do we retest?
Treat the change as a document-review event. Affected requirements should be re-evaluated after a material change, and an earlier report should not be assumed to cover the revised configuration. Separate unchanged components from changed materials and confirm who coordinates the review before you accept the existing file.
Is the EU file reusable for a US listing?
No. The US framework uses ASTM F963 under CPSIA with a Children's Product Certificate, and ISO 8124 echoes much of EN 71 without being identical. The EU file supports the EU declaration of conformity only — it is not a substitute for US documentation.
Sources
Before you book the container
Ask for the file in the order an inspector reads it — model matrix first, then the safety assessment, then the evidence, then the DoC and artwork — and read it against the carton in front of you. If a section is missing, that is a question for the factory, not a reason to fill the gap yourself. CoreRCCar-grade 2.4GHz models where the same file has to cover a mixed order, start from the model matrix and work forward.