CE Conformity Assessment for OEM Manufacturers

Who this guide is for

This article is for companies that develop, order or place electronic devices on the market under their own brand or business model.

Typical situations include:

• you have an idea for an electronic device and want to move from concept to prototype,
• you have a working prototype and are planning serial production,
• you have a design prepared by an external engineering office,
• you are transferring production from another supplier,
• you import or integrate an electronic device under your own brand,
• you sell a B2B, industrial, professional or consumer device,
• you do not have an internal compliance department, but you are formally responsible for the product.

In practice, this issue is not limited to small companies. Large organisations can also have fragmented responsibility: RD assumes one thing, procurement another, the supplier a third, and the sales team expects a finished product with CE marking. If nobody manages conformity from the beginning, the risk returns during testing, documentation review or market surveillance.

If you are moving from an idea or prototype to a product ready for production, it is worth aligning technical, manufacturing and conformity requirements at the same time. This process naturally connects with electronic product development and preparing the product for electronics manufacturing services.

CE is not a sticker at the end of the project

One of the most common misunderstandings is treating CE as the last step before sales. The product works, the enclosure is ready, the prototype passed functional tests, so now it is time to “do CE”. This way of thinking is understandable, but wrong.

CE marking means that the manufacturer declares the product’s conformity with the applicable requirements of European Union legislation. For electronics, this may involve several areas: electromagnetic compatibility, electrical safety, radio equipment, restrictions on hazardous substances, batteries, consumer product safety, environmental requirements or cybersecurity requirements for products with digital elements.

This means conformity assessment begins much earlier than in the laboratory. It begins with understanding the product:

• what it does,
• who will use it,
• where it will operate,
• how it is powered,
• whether it communicates wirelessly,
• whether it contains firmware or software,
• whether it has a battery,
• whether it is part of a larger machine or system,
• which market it will be sold in.

If these questions are not asked early, the project may move in a direction that is later difficult or expensive to defend. The issue may be a PCB layout vulnerable to EMC emissions, insufficient insulation distances, an unsuitable power supply, no space for a label, no firmware version control, missing component documentation or an enclosure that does not meet environmental requirements.

That is why CE should be treated as a design and evidence process, not as a formality after production.

In practice, the CE topic should appear when the product architecture, first technical assumptions and prototype plan are being created. We describe the broader path from concept to implementation in the guide: From idea to finished electronic device.

Who is the OEM manufacturer and who is responsible for the product

Electronic product projects often involve several parties: the customer, electronics designer, PCB supplier, EMS assembler, enclosure supplier, module manufacturer, test laboratory, component distributor and sometimes a final system integrator. This can create the false impression that conformity responsibility will somehow be distributed across all project participants.

In practice, it must be clear who places the product on the market as the manufacturer. If a company sells the device under its own brand, defines its intended use, decides on the construction and takes responsibility for making the product available to customers, it is typically the manufacturer in both the business and formal sense.

A design partner or EMS can help significantly. It can design electronics with EMC in mind, prepare production documentation, control BOM versions, provide traceability, support testing, cooperate with the laboratory and maintain process stability. However, this does not automatically mean it assumes the manufacturer’s responsibility for the Declaration of Conformity of the final product.

This distinction is critical. The EMS usually manufactures according to agreed documentation and process. The OEM is responsible for ensuring that the product as a whole is compliant, properly described, marked, documented and kept in conformity after changes.

OEM, EMS, importer and distributor: simplified responsibility map

The safest approach is to define the responsibility model at the start of the project. Who defines the requirements? Who selects the standards? Who maintains technical documentation? Who orders testing? Who signs the Declaration of Conformity? Who approves production changes? Without these answers, the project may work technically, but remain organisationally unready for the market.

Where to start with conformity assessment for an electronic device

The first step is not choosing a laboratory. The first step is describing the product and its use context. Only then can you reasonably identify which requirements may apply.

Minimum information worth collecting:

• product name and function,
• end user description,
• target market and country of sale,
• operating environment: home, industrial, vehicle, machine, field use, outdoor, humidity, temperature,
• power supply: mains, external power supply, battery, PoE, industrial installation,
• communication interfaces: wired, radio, Bluetooth, Wi-Fi, LTE, LoRa, NFC,
• presence of firmware, application, cloud connectivity or updates,
• mechanical elements and enclosure,
• product variants and configuration options,
• expected production volume,
• planned product lifecycle and change management.

This description is practical, not academic. If the product contains a radio module, conformity will be different than for a simple wired controller. If the product is mains powered, the safety requirements are different than for a low-voltage device supplied by an external adapter. If the product has firmware and network communication, you need to consider not only function, but also updates, configuration and potential cybersecurity requirements.

The earlier this information reaches the design and manufacturing partner, the easier it is to plan product architecture, prototypes, pre-compliance testing, documentation and implementation schedule.

Organising input data like this is part of a good NPI process. At Inventronics, we describe this as a sequence of steps from project qualification through prototype, validation, documentation, pilot run and serial production. See: Product development process.

How to identify which requirements may apply

Not every electronic device is subject to the same requirements. That is why one of the first tasks for the OEM manufacturer is to identify the legislation and conformity areas relevant to the specific product.

The table below does not replace legal analysis, but it shows the typical way of thinking.

In practice, several areas are often analysed in parallel. For example, a small IoT device powered by a battery and communicating via Bluetooth may require consideration of RED, EMC, RoHS, batteries, user instructions, marking and cybersecurity. If the same device is used in an industrial environment, customer expectations around robustness, traceability, quality and version control also become important.

The worst scenario is discovering the applicable requirements after the PCB and enclosure are already finished. At that point, the change may mean redesign, another prototype series, repeated testing and a delayed production launch.

For products with firmware, network communication or updates, cybersecurity requirements should also be considered from the start. We cover this topic separately in the article: Cyber Resilience Act readiness for electronics manufacturers.

Harmonised standards: why they matter and why they should be considered early

Legislation defines general requirements, but it often does not tell the engineer exactly how to design a specific circuit, enclosure, power supply, interface or test procedure. In practice, harmonised standards play a major role because they help demonstrate conformity with the requirements.

For the OEM manufacturer, three points are important.

First, a standard is not only a document for the laboratory. The choice of standards influences the design. It may determine requirements for EMC immunity, emissions, insulation distances, temperature limits, testing approach, marking or user instructions.

Second, standards should be considered before the design is frozen. If the engineering team designs electronics without awareness of the target tests, the risk increases that the product will work functionally but fail testing or require expensive changes.

Third, the list of standards is part of the product’s conformity story. The manufacturer should be able to explain why specific standards were selected, what testing scope was performed and what evidence exists in the technical documentation.

A good design and manufacturing partner does not replace a compliance specialist or laboratory, but it should ask questions that influence the design: does the product have radio communication, what are the environmental limits, where is the power supply, how long are the cables, is the enclosure metal, are filters needed, are test points included and how will component changes be handled?

That is why the discussion about standards should not be separated from electronics design. Decisions about power supply, PCB layout, circuit separation, filtering, enclosure and testability are best made with a team that understands both development and later production. This scope is part of our electronic product development work.

Risk assessment as the foundation of documentation

Conformity assessment is not only about collecting test reports. The manufacturer should understand and document the risks associated with the product. In electronics, those risks may be technical, usability-related, environmental, quality-related and organisational.

Example risk areas:

• electric shock,
• overheating or fire,
• electromagnetic disturbances emitted by the product,
• product susceptibility to external disturbances,
• firmware malfunction,
• loss of communication,
• incorrect battery charging,
• incorrect assembly or component substitution,
• reasonably foreseeable misuse,
• missing instructions, warnings or markings,
• product version change without reassessing conformity impact.

In a mature process, risk assessment is not a separate document created after the fact. It should influence design decisions: component selection, circuit separation, PCB layout, enclosure, protections, production testers, quality control procedures and change approval.

Testing: what to plan before serial production

Final testing is important, but it should not be the first moment when the product meets conformity requirements. In electronic product projects, it is often worth performing earlier pre-compliance tests or at least reviewing the design for EMC, safety and manufacturability.

Tests that may be relevant for an electronic device include:

• EMC emissions,
• EMC immunity,
• electrical safety,
• radio testing for wireless devices,
• RoHS/material verification,
• temperature and load testing,
• environmental testing depending on the application,
• functional and production tests,
• firmware version and configuration control.

The greatest value comes from linking the test plan to project stages. A first prototype is tested differently than an engineering build, a pilot production run or a product ready for the Declaration of Conformity. If the schedule does not allow time for corrections after testing, the risk of delay is high.

From a production perspective, laboratory tests should not be disconnected from production tests. A product that passed testing as a prototype must later be manufactured repeatably, controlled and traced by production batch. This is one reason why conformity assessment should be connected with preparation for electronics manufacturing services.

CE technical documentation: what should be in the product technical file

Technical documentation is evidence that the manufacturer performed conformity assessment in an organised way. It is not a single certificate or one test report. It is a set of information that makes it possible to understand what the product is, which requirements apply, how it was designed, how it was tested and how it is manufactured.

Typical technical documentation for an electronic device may include:

• product description and intended use,
• product variants,
• electrical schematics,
• PCB layout and production files,
• BOM and information about critical components,
• firmware/software description and versions,
• risk assessment,
• list of applicable legislation,
• list of applied standards,
• test reports,
• user instructions,
• label and marking,
• material declarations and RoHS documentation,
• production control procedures,
• production test results,
• ECO/ECN change history,
• EU Declaration of Conformity.

In practice, technical documentation is strongest when it is created together with the project. If it has to be reconstructed years later or after a supplier change, decisions, reports, file versions, justifications and approval records are often missing.

If you are preparing an RFQ for a design partner or EMS, part of this information should be collected already at that stage. It helps assess scope, risks, missing data and a realistic implementation path. See the guide: How to prepare an RFQ for electronics design and manufacturing.

Serial production and maintaining conformity

Conformity assessment does not end on the day the Declaration of Conformity is signed. An electronic product lives: components, suppliers, firmware, PCB batches, substitute availability, customer requirements and sometimes standards themselves change.

For the OEM manufacturer, the following are especially important:

• BOM version control,
• approval of substitute components,
• assessment of the impact of changes on EMC, safety, radio and product function,
• firmware version control,
• batch traceability,
• retention of production test results,
• ECO/ECN procedure,
• decision rules for when a change requires retesting or laboratory consultation.

This is an area where the EMS partner can provide significant value. A stable production process, traceability, change control and batch documentation help maintain conformity over time. Without this, a product may formally pass testing as a prototype, while serial production begins to drift away from the assessed version.

In serial production, conformity depends not only on the design, but also on process discipline: BOM control, firmware versions, testing, traceability and change approval. That is why OEM projects need an EMS partner that understands both electronics assembly and the consequences of changes for the final product. See: Electronics Manufacturing Services.

Typical OEM mistakes when launching electronics

The most common mistakes usually do not result from bad intent. They come from not realising that conformity is part of the product project.

Typical problems include:

• treating CE as a final task,
• not identifying applicable directives and regulations at the start,
• assuming that a CE-marked module makes the entire device compliant,
• no list of standards before freezing the design,
• no budget or time for testing,
• technical documentation not collected during the project,
• missing instructions, warnings or correct marking,
• no change control after the first production batch,
• substituting components without assessing conformity impact,
• signing a Declaration of Conformity without sufficient evidence.

Each of these mistakes can cost more than organising the process earlier. The cost is not only redesign. It may also be delayed sales, a blocked shipment, a customer dispute, loss of credibility or repeated testing.

If the project is already past the prototype stage and problems have appeared with testing, documentation, manufacturability or transfer to serial production, a structured technical diagnosis may be the right first step. This scenario is addressed by Rescue NPI 60.

How a design and manufacturing partner can help

A good design and manufacturing partner should not promise to “take care of CE” without understanding the product. It should help the OEM move through the project in a way that creates a real path to conformity and serial production.

Support may include:

• organising product requirements,
• identifying questions needed for conformity scoping,
• designing electronics with EMC, safety and manufacturing in mind,
• preparing prototypes for testing,
• supporting pre-compliance testing,
• cooperating with the laboratory,
• preparing production documentation,
• controlling BOM and substitutes,
• maintaining batch traceability,
• maintaining firmware and process versions,
• supporting data collection for the technical file.

The greatest value appears when the conformity discussion starts before construction decisions are frozen. At that point, architecture, components, enclosure, power supply, testers and process can still be selected in a way that reduces the risk of later rework.

It is also worth checking whether the partner has real capabilities in the areas relevant to the product: design, assembly, testing, traceability, quality and technical documentation work. Learn more about Inventronics on the pages: Certifications, About us and Electronics Manufacturing Services.

Checklist of questions for the OEM manufacturer

Before starting the project or moving from prototype to serial production, it is worth answering the following questions.

When to discuss CE with your EMS partner

As early as possible. Not because every project needs full testing immediately, but because conformity requirements influence technical decisions.

The discussion is most valuable:

• at the product concept stage,
• before selecting modules and architecture,
• before the first PCB layout,
• before freezing the enclosure,
• before the prototype series,
• before laboratory testing,
• before production transfer,
• before approving substitute components.

If the product is already finished, the discussion still makes sense, but its nature changes. Instead of designing with foresight, the team has to assess the risks of the existing construction and decide whether the documentation, testing and production process are sufficient for responsible implementation.

Summary

CE conformity assessment for an electronic device is not a single document or the last step before sales. It is a process that connects legal requirements, design decisions, testing, technical documentation, production and change control.

The OEM manufacturer does not need to know every standard and every test scenario alone. However, it must understand that, as the product owner, it should take care of the right questions, responsibilities, documentation and evidence. A design and manufacturing partner can help, but it does not replace a conscious process on the manufacturer’s side.

The greatest risk appears when conformity is addressed only at the end. The greatest savings appear when CE is treated as part of the project from the beginning: from concept, through prototype, to serial production and product maintenance on the market.

Talk to Inventronics about the technical path to production and the data needed for conformity assessment. We can help organise requirements, risks, production documentation and change processes before they become costly problems.

FAQ