A CE mark is a self-declaration backed by a file. This checklist names what the file must contain and the red flags that mean it does not. Planning input, not legal advice.
For the EU, a powered litter box ships on the strength of a technical file, not on the mark alone. The buyer who can read the file negotiates from evidence; the buyer who accepts a certificate image inherits someone else’s assumptions. This page itemizes the request and the red flags, complementing the framework overview in the certification guide.
| Item | What it should show | Why it matters |
|---|---|---|
| Declaration of Conformity (DoC) | Importer or manufacturer identity, product identification, directives listed (EMC, LVD, RED where applicable), signature and date | The legal core of the marking |
| Test reports | Per directive, per product model, with sample identity and dates | Evidence the DoC rests on |
| Technical documentation | Circuit descriptions, label artwork, manuals, risk notes | Shows the product as assessed |
| Harmonized standards applied | Standard numbers and editions | The presumption-of-conformity route |
| Radio module evidence | Module certification and integration statement for WiFi models | RED scope for connected units |
Request the file at the RFQ stage, not after production, so gaps are the factory’s problem to close while options remain. Index the file per model and destination like the rest of the documentation in the test reports structure, and re-request on any platform or supplier change. The vetting questions in the vetting questionnaire surface most gaps before they cost anything.
Send your mechanism type, capacity and certification need — we match a verified factory and return a consolidated quotation.
Request a Quote