Smart pet hardware is electronics with an app attached, and that makes it a compliance product the moment it crosses a border. The four names you will meet — CE, RoHS, FCC and UKCA — are not interchangeable stickers; each answers to a different market and a different question. This guide maps them, explains who actually holds the files when you buy through a trading desk, and lists the three checks worth running before a deposit.
What each scheme covers, and where
| Scheme | Where it applies | What it addresses |
|---|---|---|
| CE | European Economic Area | Product conformity for goods placed on that market — safety and design requirements for electrical devices |
| RoHS | European Union | Restrictions on hazardous substances in electrical and electronic equipment |
| FCC | United States | How electronic devices behave on the radio spectrum — relevant to any WiFi- or app-connected pet device |
| UKCA | Great Britain — England, Scotland and Wales | The UK's product-conformity marking, used where CE alone does not apply post-Brexit |
Two honest footnotes. Rules move: schemes get revised, transition periods end, and Northern Ireland keeps its own arrangement — confirm the current requirement for your exact market before you commit, and the desk will help you check. And none of these names says your specific model is covered; files attach to models and configurations, not categories.
What the smart layer adds to the compliance picture
The smart layer — WiFi connectivity, app control, sensors — is what pulls these schemes toward your product. A manual comb raises few questions; a water fountain with an app is a radio transmitter to an FCC conversation and an electrical product to CE and RoHS. Plan the documentation for the connected version of your product, not the unconnected one, and make sure trial units and samples carry the same configuration as the production run.
Who holds the certificates when you buy through a desk?
The certificates stay with the supplying factory, and the desk's job is to help you compile CE, RoHS, FCC and UKCA documentation with that factory for the exact model and market you are buying into — support is included per project, written into the order rather than sold as an extra.
That division of labor is normal in this trade, and it protects you if you read it right. A desk presenting certificates as its own makes claims you cannot check against a factory; a desk compiling files with the supplying factory gives you a paper trail that runs to the source. Ask where each file came from, and expect the answer to name the factory.
Why "certified" on a listing is not an answer
A listing that says a product line is certified has told you about a category, not your order. Files attach to the exact model and configuration: the plug, the adapter, the radio module and sometimes the packaging version can all change what documentation applies. On OEM runs, your artwork and labeling enter the scope too. This is why the desk treats certification as a per-project question with a dated status — what exists, what is being compiled, what your market expects to see — rather than a yes-or-no flag.
Three checks before a compliance-sensitive order
First, file status before the deposit: ask for the documentation status of the exact model and configuration, and expect the answer within 24 hours — what exists, what is being compiled, and what your market expects to see. Second, market match: confirm the set matches where the goods will actually sell, including the plug and adapter conversation. Third, travel with the cargo: the files should be packaged with your order documents so they move when the goods move, under whichever term you chose — FOB Shenzhen, EXW or DDP.
Timing: where compliance sits in the order calendar
Documentation moves alongside production, not after it. On catalogue and trial runs the file check happens at quotation — the desk states per-model status in the first reply. On OEM runs from 1,000 pcs the artwork and labeling review runs parallel to the 15–25 working-day production window. On ODM projects the compiled set matures with the tooling: engineering, trial samples and files all land inside the 30–45 working-day span. The failure mode to avoid is finishing production with an open compliance question.
What certification support includes here
For every project, this desk helps you compile CE, RoHS, FCC and UKCA documentation with the supplying factory — requesting the right test files for the exact SKU, checking they match your target market, and packaging them with your order documents. Where a file does not yet exist for your variant, the desk says so and starts compiling it. The full scope lives on the certification support page.
Send the model, the quantity and the market. The reply within 24 hours opens with documentation status — before you talk price. If a channel requires certification held in your own name, say so in that email: the desk sets the route with the supplying factory and the testing behind it, plainly rather than reassuringly.
— PetAI Tech Global Sourcing Desk
