Case Study on CE Marking Requirements and Compliance Process
Updated: 5 days ago
A product can appear ready for launch yet still be weeks away from legal sale in the European market.
This was the risk faced by a manufacturer preparing to release a portable indoor air quality monitor. The hardware functioned correctly. The enclosure appeared final. The supply chain was established. Sales teams had garnered early interest from distributors. However, the compliance evidence did not substantiate the product claims, user manual, labels, or intended markets.
This case study illustrates how the manufacturer transitioned from an uncertain compliance position to a controlled approval process. The company name and non-essential details have been anonymised, and the timings have been rounded. This case is presented for practical learning and does not constitute legal advice.
The Product and the Compliance Challenge
The manufacturer, referred to as X Instruments in this case study, developed a portable indoor air quality monitor intended for homes, schools, and light commercial spaces. The device measured carbon dioxide, temperature, humidity, and particulate levels. It operated using a rechargeable lithium-ion battery and connected to a mobile app via Bluetooth.
The planned sales route encompassed online sales, distributors across several EU countries, and subsequent sales in Great Britain. This necessitated a defensible conformity process before the product could display the CE mark for the EU market, with separate planning required for the UK regime.
Initially, the team believed compliance would be straightforward. The Bluetooth module was sourced from a reputable supplier. The battery pack had appropriate documentation. The plastics supplier provided material declarations. The engineering team had experience with similar sensors.
This confidence concealed several critical gaps.
The product was not merely a collection of compliant components. Once X Instruments integrated the module, battery, enclosure, charger input, firmware, labels, and instructions into a finished product, X Instruments assumed responsibility for the conformity of that complete product.
The first internal review identified five major issues:
| Area Reviewed | Initial Issue | Commercial Risk |
|---------------|---------------|-----------------|
| Legal Scope | The team had not confirmed all EU legislation that applied | High |
| Conformity Route | Wrong conformity route or missing evidence | Medium |
| Radio Function | Bluetooth documentation covered the module, not the finished device | High |
| Instructions | Safety and disposal information was incomplete | Medium |
| Labelling | Importer and traceability details were missing from mock-ups | High |
The objective was not merely to “pass testing.” The goal was to construct a product file that demonstrated why the device met the applicable requirements when introduced to the market.
The First Mistake: Treating the CE Mark as a Test Certificate
X Instruments' initial plan centred on scheduling a test lab near the conclusion of development. While this approach is common, it is fraught with risk.
The CE mark is not a certificate issued by a laboratory for most products. It represents the manufacturer’s declaration that the product complies with all applicable EU requirements. Test reports can support that declaration, but they constitute only a portion of the evidence.
For this product, the team needed to address a broader array of questions:
What EU laws applied to the finished device?
Which harmonised standards were appropriate?
Could the company utilise internal production control, or was a notified body necessary?
What warnings and instructions were required?
Which supplier evidence was reliable enough to retain?
Who would act as the EU importer?
How would X Instruments manage changes post-launch?
The team also had to consider Great Britain separately. Early planning for CE and UKCA marking helped avoid the need for redesigning labels and declarations later.
This shifted the project from a late-stage lab booking into a structured compliance process.
Step One: Defining the Product Without Assumptions
The compliance lead commenced by drafting a straightforward product definition. Although this may seem basic, it shaped every subsequent decision.
The definition encompassed:
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 required for instructions
Environmental conditions for storage and use
This step resolved an 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.
This decision reduced some design scope, but it did not eliminate all safety obligations. The product still required clear charging instructions and protection against risks associated with 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 manner as the device hardware. However, firmware and app behaviour remained significant. For instance, the app could trigger settings, updates, alerts, and user instructions. If software changes impacted radio performance or safety information, the technical file had to reflect those modifications.
Step Two: Mapping the Applicable Requirements
Once the product definition was clarified, X Instruments mapped the primary EU requirements.
For a Bluetooth-enabled electronic measuring device, the key route centred on the Radio Equipment Directive 2014/53/EU. This directive governs radio equipment and encompasses requirements for health and safety, electromagnetic compatibility, and effective use of radio spectrum.
The team also considered substance restrictions under the RoHS Directive 2011/65/EU. RoHS is a prevalent issue for electronic products as it restricts certain hazardous substances in electrical and electronic equipment.
Other obligations surrounded the CE process, even when they did not directly influence the CE mark. 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 generated a concise 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 needed to identify the product and responsible operators | Model number, batch details, manufacturer and importer information |
The team subsequently selected harmonised standards. Examples included radio standards for Bluetooth equipment, EMC standards for radio devices, electrical safety standards appropriate to the product type, RF exposure assessment standards, and RoHS documentation standards such as EN IEC 63000.
Utilising harmonised standards provided X Instruments with a clearer path to demonstrate conformity. It also supported the determination that a notified body was unnecessary, provided the standards encompassed all relevant essential requirements and the company applied them correctly.
Step Three: Identifying Design Issues Before Final Testing
X Instruments scheduled a pre-compliance review prior to final tooling. This decision proved time-saving.
The review did not replace formal testing; rather, it offered the engineering team a controlled method to identify weaknesses while changes remained feasible.
The pre-compliance checks uncovered three issues.
The first issue pertained to emissions during USB charging. The device passed initial checks when operating on battery power, but noise levels increased when connected to a lengthy USB cable. The cause was linked to the charging circuit and cable behaviour.
The second issue involved electrostatic discharge. Although the device had a plastic enclosure, the display opening and charging port created pathways where static discharge could disrupt operation. The unit recovered, but the screen froze during one test condition.
The third issue related to the label. The initial mock-up featured a very small CE mark and placed key information on a removable sleeve. This would not provide reliable traceability once the product was unboxed.
The engineering and product teams implemented several changes:
Added filtering to reduce charging-related emissions
Revised grounding and PCB layout around sensitive components
Altered the enclosure detail surrounding the charging port
Incorporated firmware recovery behaviour after disturbance events
Transferred 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 detailed charging conditions, temperature limits, disposal symbols, cleaning instructions, radio function, troubleshooting, and product identification.
This stage transformed the company’s perspective on compliance. Instead of viewing it as a hurdle at the end, the team began to utilise it as a design control tool.
Step Four: Constructing the Technical File While the Product Was Still in Motion
The technical file became the central record. It had to support the Declaration of Conformity and demonstrate how X Instruments reached its conclusions.
A comprehensive technical file is not merely a collection of unrelated PDFs. It should narrate a coherent story. If a market surveillance authority requests evidence, the manufacturer must be able to provide it promptly and elucidate the rationale 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 designated document owners. Engineering was responsible for design evidence. Quality managed change control and supplier records. Regulatory oversaw the standards matrix, declaration, and technical file index. Product managed the manual and packaging content, with regulatory approval required prior to release.
This approach mitigated a common failure. Many companies compile documents at launch, subsequently losing track of which version corresponds to the product. X Instruments linked the file to product revision levels. If the antenna layout, battery, enclosure, firmware, or charger instructions changed, the team had to determine whether the compliance evidence remained applicable.
Step Five: Formal Testing on the Finished Configuration
Following design updates, X Instruments dispatched production-intent samples for formal testing.
The key point was that samples matched the intended production configuration. This included the final enclosure material, display, PCB layout, antenna position, firmware version, battery, USB-C cable, labels, and standard packaging.
The lab evaluated the device against the agreed standards plan. The scope encompassed radio performance, EMC behaviour, safety-related checks, and RF exposure assessment. RoHS evidence was obtained through supplier documentation and controlled material declarations rather than destructive testing of every component.
The device yielded one minor observation regarding user instructions. The lab recommended clearer wording for charging exclusively from a suitable limited power source. X Instruments updated the manual and included a related warning in the quick-start guide.
The final test reports substantiated the compliance route. The product did not necessitate a notified body under the chosen route because X Instruments had applied suitable harmonised standards for the relevant essential requirements and documented that decision.
This conclusion was significant. A company should not speculate regarding notified body involvement. If harmonised standards are incomplete, improperly applied, or unsuitable for every relevant essential requirement, the route may change.
Step Six: Preparing the Declaration of Conformity
The EU Declaration of Conformity served as the formal statement confirming that the product complied with the applicable legislation.
X Instruments prepared the declaration only after reviewing the evidence. It included the manufacturer’s details, product identification, legislation, standards, and authorised signature. The product model and revision aligned with the label and technical file.
The team avoided vague language. The declaration did not assert compliance with every possible standard. It enumerated the legislation and standards applicable to the product, which the company could substantiate with evidence.
X Instruments also prepared a UK Declaration of Conformity for Great Britain. The UK file utilised the relevant UK regulations and designated standards. For practical reasons, the company aligned label planning early so that the product artwork could accommodate both EU and UK requirements where feasible.
The compliance lead created a release checklist prior to mass production.
Release Check
| 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 standard production release gate.
The Results of the Compliance Process
X Instruments' final outcome was not merely a product bearing a mark on its label. The company established a repeatable process for future electronics projects.
The overall project timeline appeared as follows:
| 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 entire process spanned approximately 14 weeks. This duration was contingent on lab availability, sample readiness, document quality, and the speed at which engineering changes could be implemented.
The most beneficial outcomes were practical:
The team rectified emissions and electrostatic discharge issues prior to mass production.
The final label displayed permanent traceability information.
The manual provided clearer charging, use, disposal, and radio information.
The technical file aligned with the released product revision.
The company established a change control process for future hardware and firmware updates.
Distributors received clearer declarations and product information before placing orders.
The most significant commercial advantage stemmed from diminished uncertainty. X Instruments could address distributor inquiries with evidence rather than mere assurances. If a market authority requested documentation, the company possessed a controlled file ready for presentation.
What Went Wrong Before the Process Improved
The project also illuminated areas where manufacturers frequently squander time.
X Instruments' initial error was placing excessive reliance on supplier documents. Supplier evidence is important, but it does not absolve the manufacturer of responsibility for the finished product.
The second error involved treating wireless approval solely as a module issue. A certified or tested module can be beneficial, but final integration still influences antenna performance, EMC behaviour, user instructions, and product configuration.
The third error was postponing manuals and labels. Many teams regard instructions as packaging content. Compliance treats them as risk controls. A missed warning, incorrect symbol, or absent importer detail can delay release as significantly as a failed test.
The fourth error was inadequate version control. If test samples differ from production units, the reports may not substantiate the product presented to the market.
The fifth error was assuming that the same mark and declaration would suffice for every market. While the EU and Great Britain can often be planned concurrently, the declarations, legal references, and responsible operator details necessitate separate review.
A Practical CE Compliance Process Others Can Apply
X Instruments' case can be distilled into a straightforward process for numerous product teams.
Start with the Finished Product, Not Its Parts
List the final product precisely as it will be sold. Include accessories, firmware, packaging, instructions, variants, and intended countries. Compliance decisions based on an incomplete product definition lead to rework.
Confirm the Legal Scope Early
Identify all applicable EU legislation before testing. For electronic or connected products, this may encompass radio, EMC, electrical safety, RoHS, battery, environmental, and product safety obligations. Some duties directly support CE conformity, while others exist alongside it and still affect market access.
Choose Standards with Care
Harmonised standards can provide a presumption of conformity, but only when they apply to the product and its associated risks. Maintain a standards matrix that elucidates why each standard was selected and which requirements it addresses.
Test Before the Design is Locked
Pre-compliance testing can identify issues while the team can still modify the design. It is generally easier to incorporate filtering, revise layout, or alter enclosure details before tooling and production orders are finalised.
Treat Instructions and Labels as Compliance Evidence
Manuals, warnings, symbols, importer details, and traceability data are crucial. They should be reviewed with the same diligence as test reports.
Build the Technical File as the Project Progresses
Do not postpone until launch week. Establish the file structure early and incorporate evidence as it becomes available. Link every document to a product revision.
Control Changes After Launch
A compliant product can become non-compliant following a minor change. A new battery supplier, antenna alteration, enclosure material, firmware update, or cable substitution may necessitate a fresh review.
Key Lessons from the Case Study
The X Instruments project demonstrates that compliance is most effective when initiated prior to the finalisation of the product.
The first lesson is that CE conformity belongs to the manufacturer. Test labs, suppliers, and consultants can provide evidence and guidance, but the manufacturer ultimately signs the declaration.
The second lesson is that the finished configuration is paramount. A product must be evaluated as sold, rather than as a collection of separately approved components.
The third lesson is that documentation is integral to the product. The technical file, declaration, labels, and user instructions are not merely administrative tasks. They serve as proof that the company comprehended and managed the associated risks.
The fourth lesson is that early checks alleviate launch pressure. A pre-compliance review afforded X Instruments the opportunity to rectify design and labelling issues before production commenced.
The final lesson is that compliance must persist post-release. Products evolve. Regulations and standards can change. Suppliers may also change. A company requires a process that identifies those changes before they reach customers.
The practical takeaway is straightforward: integrate the compliance route into product development from the outset. A clear scope, appropriate standards, early testing, controlled documents, and meticulous release checks do more than facilitate a mark on the label. They safeguard market access, minimise rework, and instill confidence in the business that the product can uphold its declaration.
Comments