RED vs Market Surveillance Regulation radio equipment comparison

RED applies to electrical or electronic products that intentionally emit or receive radio waves for radio communication or radiodetermination, including products that need an accessory such as an antenna to do so.

MSR is not a second product-standard regime. It provides the market-surveillance and product-compliance framework that authorities use for harmonised non-food products, including online offers, responsible operators, authority cooperation, and controls on products entering the EU.

Write the scope memo in two layers: first the RED product-conformity conclusion, then any MSR enforcement or market-access facts that change who must respond.

RED allocates duties to the manufacturer, authorised representative, importer, and distributor. It also uses notified bodies where the selected conformity assessment route requires one.

MSR can add a responsible economic operator for products covered by Article 4, and the Blue Guide also treats fulfilment service providers, online intermediaries, market-surveillance authorities, customs, and ADCO cooperation as relevant actors.

Assign RED evidence ownership to product regulatory or engineering, then assign separate MSR response ownership for importer, fulfilment, marketplace, customs, and authority communications.

RED work starts before the radio equipment is placed on the EU market or put into service, and must be revisited when configuration, intended use, software, radio interface, antenna, charger category, or applicable standard changes.

MSR work starts when market-surveillance facts arise: an online offer targets EU end users, third-country goods enter free circulation, authorities ask for documents, border authorities suspend release, or corrective action is needed.

Use intake questions that distinguish launch readiness from authority-response readiness; many connected devices need both, but the trigger is different.

RED requires the Article 3 essential-requirement assessment, Article 17 conformity assessment, technical documentation, EU declaration, CE marking, required instructions and safety information, importer/distributor checks, and 10-year document retention. Common-charger and delegated cybersecurity duties apply only to covered categories.

MSR focuses on making surveillance effective: a responsible economic operator where Article 4 applies, cooperation with authorities, document availability, online and distance-sales visibility, customs-release controls, corrective measures, ICSMS entries, RAPEX alerts for serious risks, and mutual assistance.

Build one action tracker with two columns: RED evidence needed to show conformity, and MSR actions needed to answer authorities, border controls, or EU-wide corrective measures.

RED evidence should show Article 3 matrix, standards list, test reports, notified-body certificate if needed, cybersecurity evidence, EU DoC, and technical file.

MSR evidence should show the Article 4 responsible economic operator where required, EU-facing online offer records, fulfilment or importer route, authority document requests, customs suspension decisions, ICSMS/RAPEX references, and corrective-action follow-up.

Keep a shared evidence index, but tag each document as RED conformity evidence, MSR response evidence, or both.

RED is fully applicable for current radio equipment, with a 10-year retention duty for technical documentation and EU declarations. Specific additions have their own dates, such as RED cybersecurity from 1 August 2025 and common-charger requirements from 28 December 2024 for listed handheld devices and 28 April 2026 for laptops.

Regulation (EU) 2019/1020 replaced older market-surveillance provisions from 16 July 2021. In border-control cases, the Blue Guide notes a four-working-day authority reaction point after suspension notification, while further checks and corrective measures may continue.

Track RED product deadlines and MSR authority-response clocks separately, then surface the earlier launch blocker and the longest document-retention or follow-up duty.

RED escalation starts with the conformity file: missing technical documentation, non-conforming radio equipment, wrong CE or instructions, unsupported standards, missing notified-body input, or Article 40-43 risk and safeguard procedures.

MSR escalation can involve market-surveillance authorities, customs release decisions, ICSMS records, RAPEX alerts for serious risks, ADCO cooperation, mutual assistance, withdrawal, recall, prohibition, or destruction of non-compliant goods in limited border cases.

Escalation playbooks should name the RED conformity owner, the authority-response owner, the customs or marketplace contact, the corrective-action owner, and the customer-facing message.

RED evidence is reusable for MSR only when it proves the same product configuration, intended use, conformity route, standards, test results, and declarations that authorities ask to see.

MSR records can point back to RED evidence, but they add market facts that RED does not fully capture, such as online targeting, fulfilment routing, importer identity, customs suspension, EU-wide corrective action, and authority database references.

Reuse the technical file, declarations, test reports, and labels where they answer the authority request, but keep separate notes for market route, responsible operator, and enforcement status.

Treat RED as controlling when the open question is whether the radio equipment may be lawfully placed on the EU market: essential requirements, conformity assessment, CE marking, instructions, labels, EU declaration, or technical documentation.

Run an MSR workstream when the open question is market access or authority handling: who is the responsible economic operator, whether an online offer targets EU users, how customs or market-surveillance authorities should receive evidence, or how corrective action is coordinated.

Most launch gates start with RED. Add MSR when the supply chain, online listing, import route, or authority interaction creates a separate surveillance or enforcement task.