CE to UKCA: What Carries Over, What Must Be Added

Start with the conclusion: converting a CE report to UKCA, in the large majority of cases, is not a retest — it is "change the references + swap the declaration". UK and EU technical standards are essentially the same, and the test data in the CE-RED report you already hold is still usable. What you have to do is change the standard references from EN to BS EN, then issue a UK Declaration of Conformity (UK DoC), paired with the UKCA mark and UK Responsible Person information.

But this only works in one direction. UKCA cannot be used for the EU. The EU does not recognise UKCA; a product entering the EU still needs a separate CE. So the practical approach is: one set of test data, one file set for each side — the EU set is an EU DoC plus the CE mark, the UK set is a UK DoC plus the UKCA mark, and neither replaces the other.

There is also a premise to state up front: the UK currently still accepts CE under transitional arrangements, and the exact position is subject to the UK government's current rules. Policy can be adjusted, so confirm the rules in force today before deciding — don't take an article written two years ago as your basis.

CE and UKCA are now two systems, with the same technical basis

After Brexit, the UK moved the product regulations it had previously implemented under the EU framework back into domestic law, forming the standalone UKCA system. Product scope, compliance approach and technical standards all correspond; what changed is the legal basis: the EU side recognises CE and the EU DoC, the UK side recognises UKCA and the UK DoC.

Under the current transitional arrangements CE is still accepted in the UK, and many products entering the UK with CE are not in breach. That does not equal "CE can be used indefinitely": transitional arrangements are policy, not a commitment. If your export plan runs across years, or UK customers are already asking for UKCA documents, it is safer to build the UK set in advance. As for how long this applies and which products fall within scope, that remains subject to the UK government's current rules.

Break the relationship into three sentences:

• Technical standards: essentially the same. The same EN standards; the UK version is called BS EN, with corresponding test methods, limits and pass/fail logic.
• Legal system: separate. Two sets of regulations, two kinds of declaration, two marks, neither subordinate to the other.
• Mutual recognition: never automatic. The EU does not accept UKCA; the UK's acceptance of CE is a transitional arrangement, with conditions and an end point.

This is also why "conversion" works technically but cannot be handled casually on paper: tested items do not need retesting, but every page of references, every declaration and every mark has to be redone under the UK set.

Which CE reports convert directly, and which need checking first

"Convertible" is not a switch, it is a range. There is really only one criterion: whether the test data and conclusions in the report cover the standards required by UK regulation, and whether they cover the models you now sell. If both line up, conversion is paperwork; if either does not, you have to fill the gap.

Wherever the table says "assessment needed", do not decide on your own. Have a lab that works on UK routes read the original report and give a written conclusion: convertible, and which items to add before converting. This step takes little time and saves a lot of rework. For how a report is broken down and which pages change, see the report conversion map; the EU-side report structure is broken down item by item in the CE-RED knowledge base.

What actually changes for UKCA: four things, none optional

Many companies assume conversion means "swap EN for BS EN in the report", submit it, get it rejected, and only then find three items missing. Work through these four in order and you should largely avoid rework.

1. Standard references: EN to BS EN, across the whole text not just the cover

Report cover, test item tables, limit references, conclusion page, photo page annotations — every place a standard number appears has to be aligned. If you add one BS EN line on the cover while the inner pages still say EN, a reviewer will spot it within two pages. Likewise, if the report cites a version that has been withdrawn, explain that too; don't wrap old content in a new cover.

2. UK DoC: the declaring entity and the legal basis both change

The UK DoC is a standalone document, not an EU DoC with a different title. It must state the manufacturer's name and address, product identification and model, the UK standards cited, the UK Responsible Person's name and address, the signatory and the date of signing. The EU declaration cites EU regulations and EN standards; the UK one cites UK regulations and BS EN. The responsible entities and the responsible-person address differ, so mixing them means neither stands.

3. Labelling: the UKCA mark has size and proportion requirements

The UKCA mark is not a matter of pasting in whatever image you find; size, proportion and legibility are all specified, subject to the rules currently in force. Three places matter in practice: the product itself (where space is insufficient, on the packaging or accompanying documents as the rules allow), the packaging, and the instructions. When one product goes to both the EU and the UK, place CE and UKCA each according to its own rules — don't squeeze them into a single combined graphic, which neither side will accept.

4. UK Responsible Person: depends on the product and the route

Many routes require a contactable responsible person and address within the UK; whether one is needed, and in what form it appears, depends on the product category and the compliance route you take. This information is not a formality: when regulators, platforms or customers need to find someone, someone must be reachable. The common mistakes are listing an overseas headquarters address, a freight forwarder's address, or an email nobody answers — the file looks complete but is unusable in practice.

PSTI is a separate track — don't fold it into UKCA

PSTI governs the cybersecurity of connectable consumer products: default passwords, vulnerability disclosure mechanisms, and statements of the security update period. It runs parallel to UKCA — UKCA covers traditional items such as product safety, EMC and radio, while PSTI covers "is it secure once it is connected".

So keep the two apart in your mind: holding UKCA does not mean PSTI compliance; doing PSTI does not replace UKCA. For smart cameras, smart doorbells, connected speakers and smart watches, both have to be worked through, and the documents kept separately. If a product does not connect to a network, the PSTI track usually does not apply, but UKCA still does.

For detail, see UKCA and PSTI compliance essentials and PSTI cybersecurity requirements explained; clause-level content is in the UK UKCA / PSTI knowledge base. For products like the security camera solution, both tracks usually apply at the same time.

UKCA cannot be used for the EU: identical standards are not mutual legal recognition

This is where many companies get the calculation wrong: if the standards are the same, why can't a UK report be used directly for the EU? Because certification is a legal act, not a technical one. The EU CE system recognises conformity assessment and EU DoCs under EU law; UKCA is a product of UK law, and the EU has no obligation to recognise it.

The reverse holds equally. The UK's acceptance of CE under transitional arrangements is a unilateral UK policy choice; it does not mean the EU will accept UKCA. So keep the two sets of accounts separate:

In practice, build a "master data + dual declaration" structure: keep the report, raw test data, critical component list and product photos in one master file; issue the EU DoC and the UK DoC separately, each carrying its own mark and responsible person. When the product is revised, update both together — update only one and the other becomes an out-of-date document, and by the time a customer audit finds it, the delivery date is usually already at risk.

For the European market framework overall, see the EU CE/RED certification service and the CE marking guide; the UK entry point is the certification services overview.

When doing UKCA directly is the better call

"Convert wherever you can" is the cost-saving route, but in several situations doing UKCA directly is cleaner:

• The market is the UK only, with no EU plan in the near term. There is no need to carry a CE file set you won't use for a possible future; put the resources on the UK track.
• The report is too old, or the product has been revised. The items to add for conversion come close to a retest, conversion saves little, and adds the risk of version mismatch.
• A UK customer or channel explicitly requires a UKCA document chain. Do it early and submit early; don't start digging through reports after the order is agreed.
• You want to straighten out labels, instructions and the UK Responsible Person in one pass. A fresh set is clearer than patching old documents, and easier to extend to derived models later.
• Multiple derived models. Do the parent model once and set out the coverage of derived models in one go — less work than explaining them one by one afterwards.

The reverse also applies: if your main market is the EU, complete CE first and connect the UK set through conversion — that is the more economical sequence. The direction depends on your market structure, not on which mark sounds more "premium". For scheduling and how many items conversion needs, the assessment of the body you work with is what governs.

Eight common pitfalls, and a pre-flight action checklist

The following are nearly all document-level problems, not technical ones, but any one of them can leave goods sitting in the warehouse.

Pitfall 1: Adding BS EN only to the report cover

The standard numbers on the inner pages, the limit references and the conclusion page are all still the old ones. The reviewer matches them and it shows immediately; you then redo a round, which takes longer than changing it properly the first time.

Pitfall 2: Retitling an EU DoC as a UK DoC

The legal basis, standard numbers and responsible-person address do not match. This kind of document surfaces very quickly in platform reviews and customer audits.

Pitfall 3: Assuming UKCA lets you into the EU

The EU does not recognise UKCA. Declaring to EU customs with UKCA documents is the same as having no documents; you have to go back and add CE.

Pitfall 4: UK Responsible Person details blank or unusable

An address is listed but nobody can be reached there; or it is an overseas headquarters or a freight forwarder. The documents are formally complete but do not hold up in practice.

Pitfall 5: Model, trademark and address do not agree

One model on the report, another on the rating label, a third on the declaration; a trademark changed but not updated; a company address moved but not amended. This type of inconsistency is a frequent cause of rejection.

Pitfall 6: Treating PSTI as part of UKCA

Assuming that doing UKCA also covers cybersecurity. The two tracks are managed separately, and connected products need both prepared.

Pitfall 7: Treating the transition as long-term policy

Planning two years of exports on "CE still works" means last-minute document work when policy changes. The transitional arrangements are subject to the UK government's current rules, so leave margin in your schedule.

Pitfall 8: One file set shared by both sides, one updated and one forgotten

A critical component is changed and only the EU set is updated. The UK set still shows the old construction, and it shows the moment a customer asks for documents. Keep both sides updated and you save a great deal of explaining.

A pre-flight action checklist — work through it item by item and you can largely settle the question:

Converting CE to UKCA is not technically hard; what is hard is document discipline: references aligned through the whole text, declarations issued separately, marks applied to the rules, and a responsible person who can genuinely be reached. Get these four solid and conversion is a matter of days; get them wrong and it is rejection after rejection. If you want an item-by-item check for your product, the quick lookup tool can pull a checklist first; for experience with similar products, the case studies show paths you can compare against.