Vacuum appliance standards, connected-device cybersecurity and lithium battery rules in one product.
A robot vacuum is three certifications in one: a vacuum cleaner under the appliance standards (EN 60335-2-2), a WiFi-connected radio product (RED, FCC ID) and, since the connected-product rules arrived, a cybersecurity subject (EN 18031 in the EU, PSTI in the UK).
The dock adds scope too: mains electronics, sometimes a second battery, and its own EMC profile. Quoting only the robot body is the most common first-quotation mistake in this category.
| Market | Typical requirements | Notes |
|---|---|---|
| European Union | CE: LVD with EN 60335-1 + EN 60335-2-2; EMC; RED for WiFi models (with EN 18031 cybersecurity); RoHS | Connected radio models trigger the RED cybersecurity articles |
| United Kingdom | UKCA equivalents; PSTI security requirements for consumer connectable products | PSTI statement of compliance is separate from UKCA marks |
| United States | FCC ID for WiFi models (Part 15 Subpart B for non-radio); retailer safety reports; UN38.3 | App-connected models are radio products - plan the FCC ID route |
| Battery & dock | UN38.3 pack tests, cell safety, dock EMC and safety | The dock is mains equipment and needs its own scope lines |
Launching a WiFi robot vacuum into the EU, UK or US? Send the product and dock specifications - we will scope appliance safety, radio and cybersecurity as one project.
Vacuum cleaners fall under EN 60335-2-2 (household vacuum appliances), read together with the general part EN 60335-1. Robot-specific mechanics (sensors, brushes, drop protection) are assessed within that framework.
If it connects via radio and is placed on the EU market, the RED cybersecurity articles apply to connected radio products. The UK adds PSTI for consumer connectable products. Both are legal requirements now, not voluntary labels.
It should be. The dock is mains-powered equipment with its own EMC and safety scope and often contains the charging electronics and a second battery. Including it from day one prevents the most common mid-project scope change.