The question is who, not what
When a European retailer asks whether a hand warmer is covered, the conversation often starts with test reports and ends with a shrug about who is legally standing behind the product. The framework in force in the EU puts that question first: a product placed on the market needs an economic operator established in the Union who can be identified and contacted, and the documentation supporting the product has to exist and be producible on request. Neither requirement is satisfied by a laboratory report alone.
For a buyer sourcing a rechargeable warmer from outside the Union, that reshapes the paperwork conversation. The supplier can build the product and run the tests, but the operator named on the market-facing documentation is usually the importer or the brand owner, and the technical file has to be assembled around that entity rather than around the factory.
What the technical file has to contain
Pages to assemble
| Section | Content | Who normally produces it |
|---|---|---|
| Product description | Model list, configuration, intended use, age group | Brand owner with supplier input |
| Risk assessment | Hazards identified for a heated, battery-powered hand-held article | Brand owner, reviewed by a competent assessor |
| Bill of materials | Components, materials, element and pack references | Supplier engineering |
| Test and assessment records | Electrical, thermal, mechanical and material evidence | Laboratory plus supplier |
| Marking and instructions | Label artwork, manual, warnings, language versions | Brand owner with supplier artwork |
| Traceability | Batch or date coding and the link to records | Supplier production |
| Incident handling | How complaints and returns are recorded and escalated | Brand owner |
| Change log | What changed, when, and which records were updated | Brand owner |
The list is not a suggestion about which sections are nice to have. Its value is that each section names a producer, so gaps become visible. A file where the risk assessment has no author, or where the change log is empty after two production runs, is a file that will not survive a serious review.
The responsible person, described as a role
The role is an address and a function, not a rubber stamp. In practice it means an entity established in the Union that can be contacted by authorities and by customers, that holds or can obtain the technical documentation, and that can act on a safety issue, including a recall. That combination is why the role usually lands on the importer of record or on a brand owner with a European establishment, and why a factory address outside the Union cannot fill it.
Two failure modes are common. The first is a name on a document with no authority behind it: a forwarding agent or a fulfilment provider listed as the contact, without any arrangement for handling a technical question. The second is a name with no file: the operator exists, but nobody has assembled the documentation, so the first serious request produces a scramble.
Where the file lives and who keeps it current
The file can be held electronically, and it should be held somewhere the named operator can reach within the response time the framework expects. That rules out a folder on a supplier's local drive in another time zone. It also rules out a file that only exists as a PDF bundle assembled once for a trade fair.
Keeping it current is the harder half. A warmer has a small number of change points that matter: the heating element supplier, the adhesive that bonds it, the NTC thermistor position, the air gap above the element, the control board revision, the cell and the pack assembly inside the battery compartment, the firmware that governs the OTP behaviour, and the artwork on the shell and the box. Each of those should appear in the change log with a date and a note about which records were re-issued. When the log is maintained, an audit becomes a reading exercise; when it is not, an audit becomes an archaeology exercise.
A named operator ≠ a certified product
The boundary to state plainly: naming a responsible person does not certify the product, and holding a technical file does not demonstrate that the product is safe in absolute terms. The framework is about accountability and documentation; the safety evidence still has to come from testing and from design, and the file is where that evidence is kept rather than a substitute for it.
The second boundary is that this framework is not a marking scheme. A CE-style declaration and a general safety file are related but distinct artefacts, and a supplier who offers one as evidence of the other is conflating two different questions. For the market-access schemes in Asia, see PSE, KC and CCC; for the material documents, see REACH SVHC documents to request. The certification wall reality check explains why the folder itself proves nothing.
Five questions for the supplier
- Which entity will be named as the Union operator for this product, and what is the written arrangement with them? A name plus an arrangement is verifiable; a name alone is not.
- Can you deliver the eight file sections above, and which of them will you author versus which fall to us? The split should be agreed before the first shipment.
- Who signs the risk assessment, and what competence do they hold for a heated battery product? The signature should belong to someone who can defend the content.
- How is the change log maintained, and can you show the entries for the last two production runs? An empty log is a finding in itself.
- What is the response time for producing the file if an authority or a retailer asks? Ask for the process, not a promise.
Next step
Decide the Union operator before the packaging is finalised, because the name and address usually have to appear on the product or its packaging, and changing it later means new artwork. Then assign the eight file sections to named owners on both sides and put the change-log rule into the supply agreement. The certification document matrix by market can hold the resulting record, and three quote comparison worksheet helps when two suppliers propose different arrangements. To work through a specific programme, start at contact.
Written for the Emberly heating-element programme. Specifications are illustrative; confirm every figure against a supplier test record.