CE, FCC, UKCA and RoHS: Document Request Checklist

What the term actually covers

A market-entry file is not a single certificate. For a neck massager with a motor, a controller, a battery and a skin-facing shell, the relevant file families are an electromagnetic-compatibility and low-voltage set for the EU, an equivalent set for the UK market, an emissions file where the product radiates intentionally, and a restricted-substances declaration for materials. Each family is issued against a specific model and a specific revision.

The checklist discipline is to ask for the file families by name and to check that each one names the same model reference as the quotation and the sample. A report issued for a different model is not evidence for this one, whatever its logo.

A second habit belongs beside the file list: version control. Every document carries a revision, and a quotation can drift away from the revision the documents describe. A buyer who records the revision beside each file can see the drift; one who only records the model number cannot.

Which market asks for which file

Ask the factory for the file families that apply to the destination, and separate them by market. The EU set and the UK set are separate documents with separate mark conventions. A restricted-substances declaration sits on the materials line. If the product includes a radio module, a separate radio file is expected on top of the main set.

The buyer's job is not to interpret the clause text. The buyer's job is to assemble the file matrix, name an owner for updates, and route any unclear applicability as a written question to the testing laboratory. This article names the families only.

Comparison table

A document list is not the same as a conformity conclusion

A list of file families ≠ proof that a product conforms. Naming a regime and a file family describes the paperwork a market expects. It does not state that the sample passed, that the production batch will pass, or that the product is suitable for a particular sale. Applicability, clause text and transitional dates must be confirmed with the laboratory or the authority.

The second boundary is between the factory and the party placing the product on the market. The factory supplies the technical file and the test reports. The duty to keep that file current and to name a responsible party where required sits with the party that places the product on the market. Both sides need to know which one they are.

A third boundary is between the main file and the component files. A report for the cell does not cover the shell; a report for the radio module does not cover the motor drive. Ask which file covers which part, and read an unclear answer as an open question rather than an assumption.

The second-order question is the file's currency. A report issued before the current firmware, the current shell or the current cell is already describing a different product, and the buyer has no way to see that from the model number alone. Ask for the issue date against the revision date of the drawing, and read a gap between them as an open question rather than a closed item.

The third-order question is the test laboratory's scope. A laboratory may be competent for one product family and not for another, and the question is not whether the logo is familiar but whether the laboratory's scope covers this type of product. Ask which laboratory issued each file and whether its scope covers the category. A buyer who cannot name the laboratory cannot check the scope.

Reading a report against a drawing

The test report and the drawing should describe the same revision, and the buyer can check this by comparing two fields: the model reference on the report and the drawing revision it cites. A report issued before the current shell, the current firmware or the current cell describes a product that has since changed. Ask for the issue date on each report and the revision date on each drawing, and read a gap between them as an open question rather than a closed item.

The same check runs backwards. A drawing revision that post-dates the report means the drawing was changed after the test was run, so the test no longer describes the part on the line. Ask which revision was tested and which revision will ship, and ask the laboratory to confirm the scope covers this product family. A buyer who can name both revisions can see drift; one who cannot will accept a report that describes an earlier unit.

Questions to ask a supplier

1. Which file families apply to the exact model quoted, and against which revision?
2. Who issued each document, and when was it issued?
3. Does the model reference on each document match the drawing and the sample?
4. What change, a new motor, a new cell, a new firmware or a new shell, would trigger a re-test?
5. Who owns the file, and what is the update process before the next shipment?

A useful control is the cross-read. Read the model reference on the certificate against the drawing, the sample and the quotation in one pass, and read any difference as an open question. The check takes minutes, and it catches the error that no logo can prevent.

Common mistakes buyers make

• Accepting a certificate whose model number does not match the quotation. Read the reference against the drawing.
• Assuming one market's file covers another. The EU and UK sets are separate documents.
• Reading a supplier summary as the underlying report. Request the file, not the paragraph.

Each is caught by building the file matrix per model, naming an owner for updates and keeping the matrix with the purchase order.

Next step

Send this document request with your RFQ and ask for the file families by name, via contact.

Related reading

• Neck Massager Retail Brand Case Study
• Neck Massager Private Label Case Study
• Marketing Claims in This Category: A Compliance View
• Neck Massager Quote Comparison Sheet: Comparing Suppliers Fairly

From the Serenivo comfort-product notes. Descriptive material only; no health or medical outcome is stated or implied.