Menu

CE marking

CE Marking and the 2027 Machinery Regulation: The Deadline That Does Not Move

Notes · Testing, safety and certificationNovember 19, 202621 min readSenova Systems Research

On Wednesday 20 January 2027, Regulation (EU) 2023/1230 applies in full and Directive 2006/42/EC is repealed, a hard cut-over, unit by unit, with no grace period for new machines built to the old Directive. The Regulation adds essential requirements the Directive never had: protection against corruption, software and update integrity, self-evolving behaviour, and AI in safety functions, and for the six Annex I Part A categories, a notified body is always mandatory. Example Labs' cobot cell costs €6,625 in testing without the AI safety function and €16,625 with it, and the notified-body route lands February–May 2027, after the deadline.

First, a simple picture

A driving licence, and a new traffic law.

A driving licence is not a certificate the government gives you. It is your own declaration that you can drive, and the test certificate, the eye test, and the logbook are the evidence behind it. If the traffic law changes on a fixed date, the licence does not change, but the evidence behind it has to meet the new law, and a car you drive after that date has to comply with the new law, not the old one.

CE marking works the same way: it is the manufacturer's own declaration that the product meets the law, and the technical file is the evidence behind it. On Wednesday 20 January 2027, the law changes, and the evidence behind the mark has to meet the new law.

What CE marking is, and what it is not

CE marking (Conformité Européenne) is a mark the manufacturer puts on a product to declare that it meets all the EU laws that apply to it. It is not a certification issued by a testing house. It is the manufacturer's own declaration, and the technical file is the evidence. The EU charges no fee for the mark itself. The costs are the testing, the lab, and, where the law requires it, the notified body, an independent organisation designated by an EU country to assess the conformity of certain products before they can be placed on the market.

Example Labs is a made-up company we use for worked examples.

The mark covers every law that applies to the product, and a connected machine can fall under several at once. Example Labs' cobot cell falls under six: the Machinery Regulation, the EMC Directive, the Low Voltage Directive, the Radio Equipment Directive, RoHS, and, from 11 December 2027, the Cyber Resilience Act. One machine, six acts, and one single declaration of conformity for all of them, the Regulation's new format, defined in Annex V, replaces the old habit of a separate declaration per act.

The mark is also not a quality stamp, and it is not a safety guarantee. It is a legal declaration. The technical file is what makes it true, and the technical file is what a market-surveillance authority asks for when something goes wrong. If the file does not hold the evidence, the mark does not hold either.

The deadline: 20 January 2027, and the one nuance

Machinery Regulation (EU) 2023/1230: the dates

DateWhat happens
14 June 2023Adopted (published 29 June, in force 19 July 2023)
20 January 2024Notified-body rules (Articles 26 to 42) apply
20 October 2026Penalty rules (Article 50(1)) apply
20 January 2027Applies in full; Directive 2006/42/EC repealed; every machine placed on the market must comply

Regulation (EU) 2023/1230 was adopted on 14 June 2023, published on 29 June 2023, and entered into force on 19 July 2023. It applies from 20 January 2027, and from that date it repeals Machinery Directive 2006/42/EC (Articles 51(2) and 54). The Official Journal first printed 14 January 2027; a corrigendum of 4 July 2023 changed this to 20 January 2027, so if a document you hold says 14 January, it is reading the uncorrected text. The Regulation is directly applicable in every Member State, and in Northern Ireland, from 20 January 2027, when the Directive is repealed. Unlike the Directive, which had to be transposed into 27 national laws, the Regulation needs no national transposition: the same words apply identically everywhere in the EU.

The switch is a strict deadline rule, not a gradual phase-in. There is no option to apply the new Regulation early, and there is no grace period for new machines built to the old Directive. Every machine placed on the market or put into service from 20 January 2027 must comply with Regulation 2023/1230. The pipeline file's "hard cut-off, no parallel period" is right for machines placed on the market from that date, and there is exactly one nuance, and it is the only one: machinery placed on the market in conformity with the Directive before 20 January 2027 may still be made available afterwards (Article 52(1)).

Certificates issued under Article 12 of the Directive remain valid until they expire (Article 52(2)), but they only support units placed on the market before the deadline. New EU type-examination certificates under the Regulation are valid for a maximum of five years (Annex VII No 6.1). Some provisions apply earlier: the rules on notified bodies (Articles 26–42) since 20 January 2024, and the rules on penalties (Article 50(1)) since 20 October 2026. Between entry into force and the date of application there is a transition period of about three and a half years, and that period is now nearly over.

From today, 19 November 2026, the deadline is 62 days away.

What is actually new

What the Machinery Regulation (EU) 2023/1230 adds that catches a 2009 design

ChangeWhereWhat it asks
Protection against corruptionAnnex III, 1.1.9Connecting another device must not create a hazard; software and data protected against tampering
Software and update integrityAnnex III, 1.2.1Control systems safe and reliable, including against malicious attempts, with software logs
Self-evolving behaviourGeneral principles, 1.1.6, 1.2.1Risk assessment covers the machine's intended evolution and varying autonomy
AI in safety functionsAnnex I, Part ASafety components with self-evolving behaviour need a notified body

The essential health and safety requirements (EHSRs) have moved from Annex I to Annex III, with the same chapter structure, plus new or extended sections. The Directive was written in 2006 for machines that could not be hacked, updated, or taught. The Regulation is written for machines that can. Five changes matter:

1. Protection against corruption (Annex III, point 1.1.9). Cybersecurity is now an essential health and safety requirement, not a nice-to-have, and not a separate law. Machinery must be designed and constructed so that the connection to it of another device does not lead to a hazardous situation, and control systems and software must be secured to prevent tampering or unauthorised modifications. If someone can hack your system and mess with safety functions, that is a direct safety risk, through a USB stick, through Wi-Fi, or through a rogue firmware update. Compliance will be guided by emerging harmonised standards, including prEN 50742 (currently under development for protection against corruption) and the widely recognised IEC 62443 series for industrial automation cybersecurity. Several major industry associations, CECE, CECIMO, EGMF, and FEM, formally requested a postponement of these cybersecurity provisions to align the timeline with the Cyber Resilience Act, but as of late 2025 no final decision from the European Commission is pending, and the machinery cybersecurity requirements apply from 20 January 2027 regardless.

2. Software and update integrity (Annex III, point 1.2.1). The safety and reliability of control systems now explicitly includes malicious attempts, and software logs. The risk assessment must address the risks that may arise during the product's lifecycle due to an intended evolution of its behaviour, and the technical file gains two points: safety software source code or logic (point m) and sensor-fed or autonomous systems (point n). Machinery must also be designed so that users can test safety functions where necessary (point 1.1.2(e)). This is the article that makes Article #11's OTA update a compliance question, not just an engineering one: the update must be signed, the bootloader must verify it, and the trial-then-confirm must revert a bad build, because the Regulation now requires the integrity to be demonstrable, not just present.

3. Self-evolving behaviour (General Principles point 1, 1.1.6, 1.2.1). Machines whose behaviour evolves through machine learning are addressed directly rather than left to interpretation. The risk assessment must account for things like evolving logic and unpredictable behaviour, and the risk assessment must cover the risks that may arise from the machine's intended evolution to operate with varying levels of autonomy. Software that performs fixed automated functions is not thereby exempt from machinery safety obligations: the requirements specifically addressing self-evolving behaviour apply where that characteristic is relevant, and the other applicable requirements still need to be assessed.

4. AI in safety functions, Annex I, Part A, and the notified body. The old Annex IV high-risk list becomes Annex I, split in two. For the six categories in Part A, involving a notified body is always mandatory from 20 January 2027, even if harmonised standards are applied in full (Article 25(2)). Part A includes removable mechanical transmission devices and their guards, vehicle servicing lifts, portable cartridge-operated fixing and other impact machinery, and, new, safety components with fully or partially self-evolving behaviour based on machine learning, and machinery with embedded AI systems ensuring safety functions. For the 19 categories in Part B, essentially the old Annex IV list, self-assessment remains possible, but only if harmonised standards or common specifications covering all relevant requirements are applied in full (Article 25(3)), and only standards cited under the Regulation count. If your machine has AI or machine learning, especially for anything safety-related, it is now considered high-risk, and there is no more self-declaring CE compliance for it. One more thread, for the file: since the AI Digital Omnibus of July 2026 (Regulation (EU) 2026/1744), the AI Act's high-risk requirements are being folded into the Machinery Regulation's own Annex III by delegated acts, applicable by 2 August 2028, instead of running as a parallel regime.

5. Digital documents, allowed, not required. Instructions for use and the EU declaration of conformity may be supplied in digital form. Two conditions come with that: they have to stay accessible online for the expected lifetime of the machine and for at least ten years after it was placed on the market, and a buyer who asks for a paper copy has to receive one free of charge. Electronic signatures are valid. Digital is permitted, not mandatory, you may continue issuing paper documents. A note for the file: the proposed Omnibus IV package includes provisions that could make digital documentation mandatory in the future; as of July 2026, that proposal is still under debate and has not been adopted.

The substantial modification

This is the change that catches the most teams, because it does not look like a compliance event. Article 18 of the Regulation says that a natural or legal person who carries out a substantial modification of machinery is considered to be a manufacturer for the purposes of the Regulation, and is subject to the manufacturer obligations in Article 10. That person has to declare conformity on their own responsibility and apply the relevant conformity assessment procedure.

Article 3(16) defines a substantial modification as a change made after the machine was placed on the market that was not foreseen by the manufacturer and that creates a new hazard or increases an existing risk to the point where new or modified guards or protective measures are needed. A substantial modification is not only mechanical. Changes to software, control logic, or operating modes count if they create a new hazard or increase an existing one, changed safety-related PLC logic, or a bypassed interlock, is a safety function change. A software update or physical alteration is not automatically a substantial modification: assess the change against the legal definition and document its effect on safety. But the assessment has to happen, and it has to be documented, and if the update is a substantial modification, the updater becomes the manufacturer, with the manufacturer's obligations, including a new declaration of conformity and a new technical file. This is the article that makes Article #11's OTA update and Article #13's firmware architecture into compliance decisions: the update that changes a safety function is not a maintenance event. It is a manufacturing event.

The technical file: the evidence behind the mark

The technical file is the evidence. It holds the risk assessment, the design and manufacturing drawings, the descriptions and explanations needed to understand them, the list of the essential health and safety requirements that apply and how they are met, the standards applied, the test reports, the instructions, and, new in the Regulation, the safety software source code or logic, and the documentation for sensor-fed or autonomous systems. The file has to be kept available for ten years after the machine was placed on the market, and the digital documents have to stay accessible online for the machine's expected lifetime and at least ten years.

The file is what a market-surveillance authority asks for when something goes wrong, and the file is what the notified body reviews when the law requires one. A machine with a CE mark and no file is a machine with a declaration and no evidence. The mark does not survive the file.

The cost

The costs below come from one provider's 2026 guide (EcoComply, "CE Marking Costs 2026: Testing, Fees & Examples"), labelled as such, they are indicative ranges, not quotes, and your own quote depends on the product. The guide's service fee is €3,800 per product, with laboratory testing fees additional. Two things are missing from the table, and they are usually the expensive ones: your own engineers' time, and the delay.

A six-week slip on a product launch rarely shows up on a compliance invoice, but it is often the largest number in the whole exercise.

Product typeTypical rangeMain cost driver
Simple electronics (DC/battery)€400–€800EMC testing only
Standard electronics (AC-powered)€750–€1,500EMC and safety testing
Wireless products (RED)€1,500–€3,000+Radio testing across frequency bands, plus RED cybersecurity assessment against the EN 18031 series, required since 1 August 2025
Machinery€1,500–€5,000+Risk assessment, documentation; Regulation (EU) 2023/1230 applies from 20 January 2027
Notified Body fees (full assessment, audits, first-year surveillance)€5,000–€15,000+Notified Body, where required
Laboratory testing€500–€5,000+Accredited test lab

Radio equipment placed on the EU market since 1 August 2025 must meet the cybersecurity essential requirements in Article 3(3)(d), (e), and (f) of the Radio Equipment Directive, activated by Delegated Regulation (EU) 2022/30; testing against the EN 18031 series is an addition to the radio and EMC scope, not a substitute for it. A 2023 survey of more than 20 MDR notified bodies put the average application fee at €1,540, with hourly rates around €325 for QMS audits and €317 for technical file review, a different regime, but the shape of notified-body pricing.

And the wider market agrees on the order of magnitude: a simple AC/DC powered electronic device runs $4,000–$9,000 all-in (LVD, EMC, RoHS, self-declared); a complex wireless/IoT device $10,000–$25,000+; industrial machinery $15,000–$50,000+, with a notified body often required.

Timelines follow the same shape: a simple electronic device with a well-prepared technical file takes 4–6 weeks; a complex product requiring a notified-body audit takes 3–6 months or longer, and a complex medical device requiring a notified-body audit can take 12–18 months. One guide's phase breakdown: pre-compliance testing 2–4 weeks, engineering fixes 2–6 weeks, full certification testing 4–8 weeks, 9–20 weeks in total, depending heavily on first-pass success. Ask the laboratory for its rush-fee schedule before you book, and plan for the relaunch delay: fixing a design after a test failure means new samples, a new booking, and a new queue.

The other deadline: the Cyber Resilience Act

The Machinery Regulation is not the only clock. The Cyber Resilience Act (CRA), Regulation (EU) 2024/2847, entered into force on 10 December 2024, and it covers products with digital elements: hardware and software that can connect, directly or indirectly, to a device or network, plus their remote data processing. Its reporting obligations already apply, since 11 September 2026: manufacturers must report actively exploited vulnerabilities and severe incidents impacting the security of products with digital elements, an early warning within 24 hours of becoming aware, a fuller notification within 72 hours, and a final report within 14 days after a fix is available.

Reports go once through ENISA's Single Reporting Platform, operational since 11 September 2026, to the CSIRT of the member state of the manufacturer's main establishment and to ENISA. The reporting duty applies to all products with digital elements that fall within the scope of the CRA, including products placed on the market before 11 December 2027, and if the product was placed on the market before then, the manufacturer may not be able to investigate, because the tooling to scan old software versions may no longer exist, the build environments for old code may be impossible to recreate, and the staff with knowledge of old codebases may have left.

The CRA's main obligations apply from 11 December 2027: the essential requirements, the conformity assessment, and CE marking against the CRA. For a product already on the market, the main obligations apply only if it is substantially modified after that date, but the reporting duty applies to everything regardless. If your product is a radio product, the RED cybersecurity rules under Delegated Regulation (EU) 2022/30 have applied since 1 August 2025, and the CRA builds on that.

The two deadlines are 11 months apart, and the product you design and tool this year needs to be built to both.

DEMO

This machine is made up. Call it Example Labs' bench cell from Article #10: a UR5e-class cobot (6 joints, 5 kg payload, 850 mm reach, 20.7 kg arm weight, max tool speed ~1 m/s, pose repeatability ±0.03 mm, force/torque sensor accuracy 4 N) moving the sensor hub's battery pack across the bench, with a person at the bench, the arm path crossing chest height, and a Wi-Fi gateway that reports the cell's state to the customer's dashboard.

The demo's arithmetic is the article's own, verified before writing, on the published cost ranges cited above and on stated assumptions (the mid-points of each range); the machine and its compliance route are the worked example, not a measured project.

Step 1, Which laws apply. The cell is a machine, so the Machinery Regulation applies. It has electronics, so the EMC Directive applies. It is AC-powered, so the Low Voltage Directive applies. It has a Wi-Fi radio, so the Radio Equipment Directive applies, with the EN 18031 cybersecurity assessment that has applied since 1 August 2025. It is a product with digital elements, so the Cyber Resilience Act applies from 11 December 2027, and its reporting duty already applies, since 11 September 2026. Six acts, one declaration of conformity.

Step 2, The cost without the AI safety function. The arm's safety is speed-and-separation monitoring and the human gate from Article #10, the risky move is gated at Sheridan level 5, the person approves before the arm moves, and neither is a self-evolving machine-learning safety function. So no Annex I Part A category applies, and self-assessment is possible if harmonised standards cover all the requirements in full. The testing bill, at the mid-points of the EcoComply ranges: machinery €3,250, EMC and safety €1,125, wireless (RED) €2,250, €6,625 in testing and lab costs, or €10,425 with the €3,800 service fee. The range, not just the mid-point: €3,750–€9,500 in testing, €7,550–€13,300 with the service fee.

Step 3, The cost with the AI safety function. Example Labs adds a self-learning vision system that watches the person's hands and slows the arm, and the vision system is a safety function, because the arm's speed depends on what it sees. The machine now falls under Annex I Part A: machinery with embedded AI systems ensuring safety functions. A notified body is always mandatory, even if harmonised standards are applied in full. The testing bill becomes €16,625 (the same €6,625, plus a notified body at the mid-point of €5,000–€15,000, €10,000), or €20,425 with the service fee. The range: €8,750–€24,500 in testing, €12,550–€28,300 with the service fee. The notified body adds €10,000, 151% on top of the testing bill, and it adds the months that miss the deadline.

Step 4, The clock. From today, 19 November 2026, the deadline is 62 days away. The self-assessment route takes 4–6 weeks: starting now, it lands 17–31 December 2026, before the deadline. The notified-body route takes 3–6 months: starting now, it lands 19 February–19 May 2027, after the deadline. The machine placed on the market from 20 January 2027 must comply with the Regulation, and the AI safety function is the thing that pushes the machine into the notified-body route. So the demo's decision is not "do we add the AI safety function", it is "do we ship the machine without it before the deadline, and add it as a later release with the notified body, or do we delay the whole machine by three to six months and ship it with the AI function?" The honest fork, stated plainly: ship the non-AI cell before 20 January 2027, self-assessed, and take the notified-body route for the AI version as a second release, or delay the whole cell, miss the deadline, and ship nothing until the notified body has done its work. And if the team ships the AI version without the notified body, the machine has a CE mark and no evidence, and the mark does not survive the file.

Step 5, The update that makes Example Labs the manufacturer. Six months after the cell ships, Example Labs pushes an OTA update that changes the safety-related PLC logic, the arm's speed limit in the shared zone drops from 250 mm/s to 150 mm/s after a near-miss. The update was not foreseen by the manufacturer, and it changes a safety function. Under Article 3(16) and Article 18, that update is a substantial modification, and Example Labs, the updater, becomes the manufacturer for the purposes of the Regulation, with the manufacturer's obligations: a new declaration of conformity, and a new technical file. The update that changes a safety function is not a maintenance event. It is a manufacturing event, and the OTA architecture from Article #11, with its signed images and its trial-then-confirm, is what makes it a safe one.

Without the AI safety function10425 €With the AI safety function20425 €
The worked example's cobot cell: conformity cost with and without one AI safety function (in-service estimate)

The decision test

Four questions. They sort the machines that ship on 20 January 2027 from the machines that do not:

  1. Which laws apply, and is the technical file built for each of them? One machine, six acts, and the file holds the risk assessment, the design drawings, the standards applied, the test reports, the safety software source code or logic, and the documentation for the sensor-fed or autonomous systems. If the file was built for the Directive, it was built for a law that is repealed, and the file has to be rebuilt for the Regulation, not relabelled.
  2. Does the machine have an AI safety function, and is the notified body booked? No, and self-assessment is possible, if harmonised standards cover all the requirements in full. Yes, and the machine is in Annex I Part A, the notified body is always mandatory, and the route takes 3–6 months, which lands after the deadline if it starts now.
  3. Is the software and update integrity demonstrable, and is the substantial modification assessed before the update ships? No, and the update that changes a safety function makes the updater the manufacturer, with no new declaration and no new file. Yes, and the update is signed, the bootloader verifies it, the trial-then-confirm reverts a bad build, and the modification is assessed against Article 3(16) and documented before it ships.
  4. Is the reporting duty already live, and is the support period declared? No, and the CRA's reporting obligations have applied since 11 September 2026, with a 24-hour early warning, a 72-hour notification, and a 14-day final report, for products already on the market. Yes, and the vulnerability reporting process exists now, the support period is declared, and the product is built for the main obligations that apply from 11 December 2027.

If the answers are yes, yes, yes, yes, the machine ships on 20 January 2027, and the review is a final check, not a rescue. If any answer is no, the job is a compliance review, and the honest thing is to do it now, with 62 days to the deadline, not after the deadline, when the machine is already on the market and the file is already wrong. And if the answer to question 2 is "we have an AI safety function, but we haven't booked the notified body", the problem is not the AI.

The problem is that the route was never chosen, and the review starts by choosing it.

"But we already have CE marking", and two more fair doubts

"But we already have CE marking." The mark is a declaration, not a certificate, and the declaration is only as good as the file behind it. If the file was built for Directive 2006/42/EC, it was built for a law that is repealed on 20 January 2027. The machine placed on the market before that date may still be made available afterwards, but the machine placed on the market from that date must comply with the Regulation, and the file has to hold the new evidence: the cybersecurity requirement, the software and update integrity, the self-evolving behaviour, the safety software source code or logic, and the sensor-fed or autonomous systems. A mark on a machine whose file was built for the old law is a declaration with no evidence, and the mark does not survive the file.

"But the notified body is too expensive." The notified body adds €5,000–€15,000 where the law requires it, and where the law requires it, there is no cheaper route. The expensive thing is not the notified body. The expensive thing is the six-week slip on a product launch, the relaunch delay when a design fails a test and needs new samples, a new booking, and a new queue, and the machine that cannot ship on 20 January 2027 because the route was never chosen. The notified body is a cost. The delay is the largest number in the whole exercise, and it rarely shows up on a compliance invoice.

"But our machine has no AI, so none of this applies to us." The AI categories are the headline, not the whole Regulation. The cybersecurity requirement applies to any machine with a digital interface, a USB port, a Wi-Fi radio, a firmware update. The software and update integrity requirement applies to any machine with software. The digital documentation rules apply to any machine with instructions. The substantial-modification rule applies to any machine whose software is updated after it ships. The machine with no AI still has a USB port, still has firmware, and still gets updated, and the Regulation was written for that machine too.

Sources

  1. Regulation (EU) 2023/1230 of the European Parliament and of the Council of 14 June 2023 on machinery (via MAAK Law, Proxom, Nemko, CE-Copilot, Intertek, Fabrico, Seeta Labs
    What we used

    All checked against the official text on EUR-Lex, Nov 2026), adopted 14 June 2023, published 29 June 2023, entered into force 19 July 2023, applies from 20 January 2027 (corrigendum OJ L 169, 4.7.2023, corrected the first printed 14 January 2027 to 20 January 2027), repeals Directive 2006/42/EC (Articles 51(2) and 54); directly applicable in all Member States and Northern Ireland, no national transposition; notified-body rules (Articles 26–42) since 20 January 2024, penalty rules (Article 50(1)) since 20 October 2026; machinery placed on the market in conformity with the Directive before 20 January 2027 may still be made available afterwards (Article 52(1)); certificates issued under Article 12 of the Directive remain valid until they expire (Article 52(2)); new EU type-examination certificates valid for a maximum of five years (Annex VII No 6.1)

  2. MAAK Law, "New Machinery Regulation (EU) 2023/1230"
    What we used

    (published 23 December 2025, last updated 18 November 2026), Annex III now holds the essential health and safety requirements, with new rules on cybersecurity (point 1.1.9) and on self-learning machinery (point 1.2.1); Annex I Part A machinery, including safety components with self-learning behaviour, needs a procedure involving a notified body (Article 25(2)); a substantial modification after placing on the market can make the person who carries it out the manufacturer (Articles 3(16) and 18)

  3. Proxom Engineering, "Machinery Regulation vs Machinery Directive: 2027 Changes"
    What we used

    (checked against the official text on EUR-Lex on 3 November 2026), eight changes that matter, including: software that performs a safety function and is placed on the market on its own is now a safety component; Part A machines can no longer be self-certified, even with harmonised standards; new essential requirements on protection against corruption (1.1.9), control system reliability including malicious attempts and software logs (1.2.1), self-evolving behaviour, and autonomous mobile machinery; the technical file gains safety software source code or logic (m) and sensor-fed or autonomous systems (n); digital instructions and a digital declaration of conformity are allowed, with paper on request; a new declaration of conformity format, one single declaration for all EU acts that apply; Part A (6 entries) third-party assessment always required, Part B (19 entries) self-assessment only if harmonised standards or common specifications covering all relevant requirements are applied in full

  4. Nemko Digital, "Guide to the 2027 EU Machinery Regulation"
    What we used

    The Regulation becomes mandatory on 20 January 2027, superseding the Machinery Directive, introducing critical new requirements for cybersecurity, AI, and lifecycle management; Section 1.1.9, the connection of another device must not lead to a hazardous situation, and control systems and software must be secured to prevent tampering or unauthorised modifications; the Cyber Resilience Act becomes fully applicable on 11 December 2027; compliance guided by prEN 50742 (under development) and the IEC 62443 series; industry associations CECE, CECIMO, EGMF, and FEM formally requested a postponement of the cybersecurity provisions, but as of late 2025 no final decision from the European Commission; if an AI system performs a safety function, the machine is classified as high-risk under Annex I and a third-party Notified Body is mandatory

  5. Intertek, "Essential Safety Requirements: What You Need to Know About the New EU Machinery Regulation" (3 July 2025)
    What we used

    AI in machinery is high-risk: no more self-declaring CE compliance, a third-party Notified Body must be involved, and the risk assessment must account for evolving logic and unpredictable behaviour; cybersecurity is no longer optional, protect software and control systems from tampering, include cybersecurity in the risk analysis and technical file, show that safety cannot be compromised through a USB stick, Wi-Fi, or rogue firmware update; digital documentation is in, operating instructions, Declaration of Conformity, and technical documentation may be provided digitally, with paper on request

  6. CE-Copilot, "EU Machinery Regulation 2023/1230: What Changes in 2027"
    What we used

    A hard cut-over, unit by unit: the switch is a strict deadline rule, not a gradual phase-in, with no option to apply the new Regulation early and no grace period for new machines built to the old Directive; Part A includes safety components and machinery with fully or partially self-evolving behaviour based on machine learning; for the AI safety functions there is a second track, since the AI Digital Omnibus of July 2026 (Regulation (EU) 2026/1744), the AI Act's high-risk requirements are being folded into the Machinery Regulation's own Annex III by delegated acts, applicable by 2 August 2028; the machinery cybersecurity requirements apply from 20 January 2027 regardless; instructions may be supplied in digital form

  7. Fabrico, "Machinery Regulation 2023/1230: Applies 20 January 2027"
    What we used

    No transition period after 20 January 2027; under Article 18, anyone who substantially modifies a machine is treated as its manufacturer; Article 3(16) defines a substantial modification as a change made after the machine was placed on the market that was not foreseen by the manufacturer and that creates a new hazard or increases an existing risk; changes to software, control logic, or operating modes count; instructions may be digital, provided they stay accessible online for the expected lifetime of the machine and at least ten years after it was placed on the market, and a paper copy is supplied free of charge to a buyer who asks for one

  8. Seeta Labs, "How AI will impact the new EU Machinery Regulation 2023/1230"
    What we used

    The safety-component definition includes qualifying digital components and software independently placed on the market (Article 3(3)); digital instructions are permitted subject to Article 10(7), including access, download and retention requirements, a free paper copy on a request made at purchase, and essential paper safety information for non-professional users; Article 20 provides a presumption of conformity for the requirements covered by cited harmonised standards or applicable common specifications, not a blanket presumption covering every risk of a product; the Regulation addresses future updates or developments of software installed in machinery during the risk assessment

  9. Vantia, "Declaration of Conformity: Machinery Reg 2023/1230 Guide"
    What we used

    The format moves to Annex V; machinery falling under the Regulation must reference Regulation (EU) 2023/1230, not Directive 2006/42/EC; notified body details (name, identification number, certificate reference) where applicable; digital format is permitted, not mandatory; electronic signatures are valid; the proposed Omnibus IV package could make digital documentation mandatory in the future, as of July 2026, still under debate, not adopted; Section 1.1.9 introduces cybersecurity as a core essential health and safety requirement

  10. EcoComply, "CE Marking Costs 2026: Testing, Fees & Examples"
    What we used

    CE marking service €3,800 per product, laboratory testing fees additional; simple electronics (DC/battery) €400–€800 (EMC testing only); standard electronics (AC-powered) €750–€1,500 (EMC and safety testing); wireless products (RED) €1,500–€3,000+ (radio testing across frequency bands, plus RED cybersecurity assessment against the EN 18031 series, required since 1 August 2025); machinery €1,500–€5,000+ (risk assessment, documentation; Regulation (EU) 2023/1230 applies from 20 January 2027); Notified Body fees (full assessment, audits, first-year surveillance) €5,000–€15,000+; laboratory testing €500–€5,000+; radio equipment placed on the EU market since 1 August 2025 must meet the cybersecurity essential requirements in Article 3(3)(d), (e), and (f) of the Radio Equipment Directive, activated by Delegated Regulation (EU) 2022/30; a 2023 survey of more than 20 MDR notified bodies put the average application fee at €1,540, with hourly rates around €325 for QMS audits and €317 for technical file review; two things are missing from the table and are usually the expensive ones, your own engineers' time, and the delay

  11. EatHealthy365, "The Cost of Meeting CE Certification Requirements" (2026 guide)
    What we used

    Simple AC/DC powered electronic device $4,000–$9,000 all-in (LVD, EMC, RoHS, self-declared); complex wireless/IoT device $10,000–$25,000+; industrial machinery $15,000–$50,000+, with a notified body often required; a simple electronic device with a well-prepared technical file might take 4–6 weeks; a complex medical device requiring a Notified Body audit could easily take 12–18 months

  12. OPD Design, "CE FCC Certification Guide for Hardware Products" (2026)
    What we used

    CE (EMC + LVD) simple electronics $6,000–$12,000; CE (RED) wireless device $12,500–$24,000; pre-compliance testing 2–4 weeks, engineering fixes 2–6 weeks, full certification testing 4–8 weeks, total 9–20 weeks depending on first-pass success

  13. European Commission, "Cyber Resilience Act, Reporting obligations" (digital-strategy.ec.europa.eu)
    What we used

    As of 11 September 2026, manufacturers are required to report actively exploited vulnerabilities and severe incidents impacting the security of products with digital elements; ENISA's Single Reporting Platform is operational as of 11 September 2026; open-source software stewards are subject to reporting obligations from 11 December 2027 (Article 24(3), Article 71(2))

  14. Conformery, "CRA compliance checklist for connected hardware makers" (published 13 November 2026)
    What we used

    The facts come from Regulation (EU) 2024/2847: entered into force 10 December 2024; reporting obligations apply 11 September 2026 (actively exploited vulnerabilities and severe incidents); main obligations apply 11 December 2027 (essential requirements, conformity assessment, CE marking against the CRA); the reporting duty is already live, so you need a reporting process now; the full product requirements apply to products placed on the market from 11 December 2027; if your product is a radio product, the RED cybersecurity rules under Delegated Regulation (EU) 2022/30 have applied since 1 August 2025, and the CRA builds on that

  15. Captaincy, "The Cyber Resilience Act has applied since 11 September 2026"
    What we used

    Article 14 applies since 11 September 2026: 24 hours from becoming aware of an actively exploited vulnerability to file an early warning, 72 hours to file a proper notification, 14 days after a fix is available to file a final report; the manufacturer obligations, secure-by-design, CE marking, the support-period declaration, wait until 11 December 2027; for a product already on the market, the main obligations apply only if it is substantially modified after that date (Article 69(2)), though the reporting duty applies to everything regardless (Article 69(3))

More in design notes

Human FactorsIEC 62366-1:2015+AMD1:2020 is the international standard for usability engineering of medical devices, recognised by FDA as a consensus standard, and FDA's guidance 'Applying Human Factors and Usability Engineering to Medical Devices' (2016, revised August 2026) sets what reviewers expect. The process: specify users and use environment, identify use-related hazards, design the interface to mitigate them, validate with representative users. Formative testing uses early prototypes with 5–8 participants per user group; summative validation uses the finalised, production-equivalent device with at least 15 participants per distinct user group. On average 85% of utilisation problems are found with 5 representative users, 95% with 10. Between 2012 and 2015 there were 423 medical device recalls resulting from UI software errors. Acceptance is the correct execution of a task without use errors or difficulties, a percentage of users completing a task in a time is not a pass mark, because the users who cannot complete it are the signal, not the noise.24 minComponent deratingYour board was designed at the ratings, and now the warranty claims are coming in, slow drift, not sudden death. Here is the derating table that makes the product last: the 50% rule, NASA's table, the tantalum numbers, and what MTBF actually means.19 minEMC/EMIEvery board is a radio station. The only question is whether it knows it is one. A 60 mm clock trace on a 2-layer board fails radiated emissions at its 5th harmonic by 1.7 dB; the same trace on a 4-layer board passes with 14.4 dB of margin. This piece shows the three ways a board radiates, the return path that decides most failures, and the stackup that fixes them.25 minPCB Design for Manufacture and TestThe average PCB project needs 2.9 respins at $46,000 each, and teams that simulate first need 3.0 spins to production against 4.6 for build-and-test teams. A board that works on a bench is not the same as a board a factory can build, test, and repair. The rules that close that gap, in plain words.14 minThe Profile That Doesn't TombstoneYour boards come back with tombstoned parts, cold joints, and voids, and the assembler says the profile is fine, because the oven's setpoints are fine and the board's temperatures are not. Here is the reflow profile as four zones, measured on the board, with the numbers.17 min