Case Study on CE Marking Requirements and Compliance Process

A product can look ready for launch and still be weeks away from legal sale in the European market.

That was the risk facing a manufacturer preparing to release a portable indoor air quality monitor. The hardware worked. The enclosure looked final. The supply chain was in place. Sales teams had early interest from distributors. Yet the compliance evidence did not support the product claims, user manual, labels, or intended markets.

This case study shows how the manufacturer moved from an uncertain compliance position to a controlled approval process. The company name and nonessential details are anonymised, and the timings are rounded. The case is presented for practical learning and is not legal advice.

The product and the compliance challenge

The manufacturer, called X Instruments in this case study, developed a portable indoor air quality monitor for homes, schools, and light commercial spaces. The device measured carbon dioxide, temperature, humidity, and particulate levels. It used a rechargeable lithium-ion battery and connected to a mobile app through Bluetooth.

The planned sales route included online sales, distributors in several EU countries, and later sales in Great Britain. That meant the product needed a defensible conformity process before it could carry the CE mark for the EU market, with separate planning for the UK regime.

At the start of the project, the team believed compliance would be simple. The Bluetooth module came from a well-known supplier. The battery pack had documentation. The plastics supplier had material declarations. The engineering team had used similar sensors before.

That confidence hid several gaps.

The product was not just a collection of compliant parts. Once X Instruments combined the module, battery, enclosure, charger input, firmware, labels, and instructions into one finished product, X Instruments became responsible for the conformity of that finished product.

The first internal review found five major problems:

Area reviewed	Initial issue	Commercial risk
Legal scope	The team had not confirmed all EU legislation that applied	Wrong conformity route or missing evidence
Radio function	Bluetooth documentation covered the module, not the finished device	Final product could fail radio or EMC assessment
Instructions	Safety and disposal information was incomplete	Delayed distributor acceptance
Labelling	Importer and traceability details were missing from mock-ups	Customs or market surveillance problems
Technical file	Test reports, risk notes, and supplier declarations sat in separate folders	No clear proof of conformity

The goal was not only to “pass testing.” The goal was to build a product file that showed why the device met the applicable requirements when placed on the market.

The first mistake was treating the CE mark as a test certificate

X Instruments early plan focused on booking a test lab near the end of development. That approach is common, but risky.

The CE mark is not a certificate issued by a laboratory for most products. It is the manufacturer’s declaration that the product meets all applicable EU requirements. Test reports can support that declaration, but they are only part of the evidence.

For this product, the team had to answer a wider set of questions:

• What EU laws applied to the finished device?

• Which harmonised standards were suitable?

• Could the company use internal production control, or did it need a notified body?

• What warnings and instructions were needed?

• What supplier evidence was reliable enough to keep?

• Who would act as the EU importer?

• How would Aster control changes after launch?

  
  

The team also needed to consider Great Britain separately. Planning for ce and ukca marking early helped avoid redesigning labels and declarations later.

This changed the project from a late-stage lab booking into a staged compliance process.

Step one was defining the product without assumptions

The compliance lead started by writing a plain product definition. This sounds basic, but it shaped every later decision.

The definition covered:

• The intended user

• Normal conditions of use

• Reasonably foreseeable misuse

• Power input and charging method

• Battery type and capacity

• Wireless technology and frequency band

• Accessories included in the box

• Markets where the product would be sold

• Languages needed for instructions

• Environmental conditions for storage and use

  
  

This step resolved one early confusion. The device did not ship with a mains charger. It shipped with a USB-C cable and instructions to use a suitable external USB power source.

That choice reduced some design scope, but it did not remove all safety obligations. The product still needed clear charging instructions and protection against risks linked to battery use, heat, incorrect charging, and foreseeable consumer behaviour.

The team also confirmed that the app was not part of the CE-marked physical product in the same way as the device hardware, but firmware and app behaviour still mattered. For example, the app could trigger settings, updates, alerts, and user instructions. If software changes affected radio performance or safety information, the technical file had to reflect them.

Step two was mapping the applicable requirements

Once the product definition was clear, X Instruments mapped the main EU requirements.

For a Bluetooth-enabled electronic measuring device, the key route centred on the Radio Equipment Directive 2014/53/EU. That directive covers radio equipment and includes requirements for health and safety, electromagnetic compatibility, and effective use of radio spectrum.

The team also considered substance restrictions under RoHS Directive 2011/65/EU. RoHS is a common issue for electronic products because it limits certain hazardous substances in electrical and electronic equipment.

Other obligations sat around the CE process, even where they did not drive the CE mark directly. These included battery documentation, waste electrical and electronic equipment duties, packaging obligations, REACH considerations for chemical substances, and distributor or importer responsibilities.

The legal review created a short matrix.

Requirement area	Why it mattered for the device	Evidence needed
Radio performance	The device used Bluetooth in the 2.4 GHz band	Radio test report and module evidence
EMC	The device had sensors, a display, charging circuitry, and radio operation	EMC testing on the finished product
Electrical safety	The device charged through USB and used a lithium-ion battery	Safety assessment, design review, relevant test evidence
RF exposure	The product operated near users	RF exposure assessment
RoHS	The product was electronic equipment	Supplier declarations and technical documentation
User information	Consumers needed safe charging, use, disposal, and radio details	Manual, warnings, translations, label review
Traceability	Authorities need to identify the product and responsible operators	Model number, batch details, manufacturer and importer information

The team then selected harmonised standards. Examples included radio standards for Bluetooth equipment, EMC standards for radio devices, electrical safety standards suited to the product type, RF exposure assessment standards, and RoHS documentation standards such as EN IEC 63000.

Using harmonised standards gave X Instruments a clearer route to show conformity. It also supported the decision that a notified body was not needed, provided the standards covered all relevant essential requirements and the company applied them properly.

Step three was finding design issues before final testing

X Instruments booked a pre-compliance review before final tooling. This decision saved time.

The review did not replace formal testing. It gave the engineering team a controlled way to find weak points while changes were still possible.

The pre-compliance checks found three issues.

The first issue involved emissions during USB charging. The device passed early checks when running on battery power, but noise increased when connected to a long USB cable. The cause was linked to the charging circuit and cable behaviour.

The second issue involved electrostatic discharge. The device had a plastic enclosure, but the display opening and charging port created paths where static discharge could affect operation. The unit recovered, but the screen froze during one test condition.

The third issue involved the label. The first mock-up used a very small CE mark and placed key information on a removable sleeve. That would not give reliable traceability once the product was unboxed.

The engineering and product teams made several changes:

• Added filtering to reduce charging-related emissions

• Revised grounding and PCB layout around sensitive components

• Changed the enclosure detail around the charging port

• Added firmware recovery behaviour after disturbance events

• Moved permanent traceability data onto the device body

• Increased symbol size and spacing on the rating label

  
  

The team also revised the user instructions. The manual now described charging conditions, temperature limits, disposal symbols, cleaning instructions, radio function, troubleshooting, and product identification.

This stage changed the company’s view of compliance. Instead of seeing it as a hurdle at the end, the team began using it as a design control tool.

Step four was building the technical file while the product was still moving

The technical file became the central record. It had to support the Declaration of Conformity and show how X Instruments reached its conclusions.

A good technical file is not a pile of unrelated PDFs. It should tell a clear story. If a market surveillance authority asks for evidence, the manufacturer should be able to provide it within the required time and explain the reasoning behind it.

X Instruments file included:

• Product description and intended use

• Photos and drawings of the finished device

• Bill of materials at controlled revision level

• PCB and assembly details

• Firmware version control record

• Critical component list

• Battery and radio module documentation

• Risk assessment and design decisions

• Standards list and applicability notes

• Test plans and test reports

• RoHS supplier declarations and material evidence

• Label artwork and packaging proofs

• User manual and translations

• EU Declaration of Conformity draft

• Change control procedure

  
  

The team assigned document owners. Engineering owned design evidence. Quality owned change control and supplier records. Regulatory owned the standards matrix, declaration, and technical file index. Product owned the manual and packaging content, with regulatory approval before release.

This prevented a common failure. Many companies gather documents at launch, then lose track of which version matches the product. X Instruments tied the file to product revision levels. If the antenna layout, battery, enclosure, firmware, or charger instructions changed, the team had to decide whether the compliance evidence still applied.

Step five was formal testing on the finished configuration

After design updates, X Instruments sent production-intent samples for formal testing.

The key point was that samples matched the intended production configuration. That included the final enclosure material, display, PCB layout, antenna position, firmware version, battery, USB-C cable, labels, and normal packaging.

The lab tested the device against the agreed standards plan. The scope included radio performance, EMC behaviour, safety-related checks, and RF exposure assessment. RoHS evidence came through supplier documentation and controlled material declarations rather than destructive testing of every part.

The device still produced one minor observation around user instructions. The lab recommended clearer wording for charging only from a suitable limited power source. X Instruments updated the manual and added a related warning in the quick-start guide.

The final test reports supported the compliance route. The product did not need a notified body under the chosen route because X Instruments had applied suitable harmonised standards for the relevant essential requirements and documented that decision.

That conclusion mattered. A company should not guess on notified body involvement. If harmonised standards are incomplete, not applied, or not suitable for every relevant essential requirement, the route can change.

Step six was preparing the Declaration of Conformity

The EU Declaration of Conformity was the formal statement that the product met the applicable legislation.

X Instruments prepared the declaration only after the evidence had been reviewed. It included the manufacturer’s details, product identification, legislation, standards, and authorised signature. The product model and revision matched the label and technical file.

The team avoided vague wording. The declaration did not claim every possible standard. It listed the legislation and standards that applied to the product and that the company could support with evidence.

X Instruments also prepared a UK Declaration of Conformity for Great Britain. The UK file used the relevant UK regulations and designated standards. For practical reasons, the company aligned label planning early so the product artwork could support both EU and UK requirements where allowed.

The compliance lead created a release checklist before mass production.

Release check	What X Instruments verified
Product identity	Model number, batch code, and revision matched the file
Marking	CE mark size, position, permanence, and traceability details were correct
EU operator details	Manufacturer and importer information were present where required
Instructions	Safety, radio, disposal, and charging information were included
Languages	Instructions matched the countries selected for launch
Test evidence	Reports covered the final configuration
Supplier records	RoHS and critical component evidence were controlled
Declaration	Signed declaration matched the product and legislation
Change control	Post-launch design changes needed compliance review

This checklist became part of the normal production release gate.

The results of the compliance process

X Instruments final outcome was not just a product with a mark on its label. The company gained a repeatable process for future electronics projects.

The rounded project timeline looked like this:

Stage	Time taken	Result
Product definition and legal scope	2 weeks	Applicable requirements confirmed
Standards plan and supplier evidence review	2 weeks	Test route and evidence gaps identified
Pre-compliance checks	2 weeks	Design issues found before final tooling
Design updates and manual revisions	3 weeks	Product and instructions corrected
Formal testing and report review	4 weeks	Evidence gathered for declaration
Declaration, label approval, and release gate	1 week	Product cleared for launch production

The full process took about 14 weeks. That timing depended on lab availability, sample readiness, document quality, and how quickly engineering changes could be made.

The most useful results were practical:

• The team corrected emissions and electrostatic discharge issues before mass production.

• The final label carried permanent traceability information.

• The manual gave clearer charging, use, disposal, and radio information.

• The technical file matched the released product revision.

• The company built a change control process for future hardware and firmware updates.

• Distributors received clearer declarations and product information before ordering.

  
  

The strongest commercial benefit came from reduced uncertainty. X Instruments could answer distributor questions with evidence instead of promises. If a market authority asked for documentation, the company had a controlled file ready.

What went wrong before the process improved

The project also showed where manufacturers often lose time.

X Instruments first error was relying too heavily on supplier documents. Supplier evidence matters, but it does not remove the manufacturer’s responsibility for the finished product.

The second error was treating wireless approval as a module issue only. A certified or tested module can help, but final integration still affects antenna performance, EMC behaviour, user instructions, and product configuration.

The third error was delaying manuals and labels. Many teams treat instructions as packaging content. Compliance treats them as risk controls. A missed warning, wrong symbol, or missing importer detail can delay release as much as a failed test.

The fourth error was poor version control. If test samples differ from production units, the reports may not support the product placed on the market.

The fifth error was assuming the same mark and declaration would cover every market. The EU and Great Britain can often be planned together, but the declarations, legal references, and responsible operator details need separate review.

A practical CE compliance process others can apply

X Instruments case can be turned into a simple process for many product teams.

Start with the finished product, not its parts

List the final product exactly as it will be sold. Include accessories, firmware, packaging, instructions, variants, and intended countries. Compliance decisions based on an incomplete product definition create rework.

Confirm the legal scope early

Identify all applicable EU legislation before testing. For electronic or connected products, this may include radio, EMC, electrical safety, RoHS, battery, environmental, and product safety obligations. Some duties support CE conformity directly. Others sit beside it and still affect market access.

Choose standards with care

Harmonised standards can give a presumption of conformity, but only when they apply to the product and its risks. Keep a standards matrix that explains why each standard was chosen and which requirements it covers.

Test before the design is locked

Pre-compliance testing can catch issues while the team can still adjust the design. It is usually easier to add filtering, revise layout, or change enclosure details before tooling and production orders are fixed.

Treat instructions and labels as compliance evidence

Manuals, warnings, symbols, importer details, and traceability data matter. They should be reviewed with the same care as test reports.

Build the technical file as the project moves

Do not wait until launch week. Create the file structure early and add evidence as it becomes available. Tie every document to a product revision.

Control changes after launch

A compliant product can become non-compliant after a small change. A new battery supplier, antenna change, enclosure material, firmware update, or cable substitution may require fresh review.

Key lessons from the case study

X Instruments project shows that compliance works best when it starts before the product is final.

The first lesson is that CE conformity belongs to the manufacturer. Test labs, suppliers, and consultants can provide evidence and guidance, but the manufacturer signs the declaration.

The second lesson is that the finished configuration matters. A product must be assessed as sold, not as a set of separately approved parts.

The third lesson is that documentation is part of the product. The technical file, declaration, labels, and user instructions are not admin tasks. They are proof that the company understood and controlled the risks.

The fourth lesson is that early checks reduce launch pressure. A pre-compliance review gave X Instruments time to fix design and labelling issues before production.

The final lesson is that compliance should continue after release. Products change. Regulations and standards can change. Suppliers change. A company needs a process that catches those changes before they reach customers.

The practical takeaway is simple: build the compliance route into product development from the start. A clear scope, suitable standards, early testing, controlled documents, and careful release checks do more than support a mark on the label. They protect market access, reduce rework, and give the business confidence that the product can stand behind its declaration.