Skip to content
Inovasense

Market Surveillance Inspection

A Market Surveillance Inspection is an official investigation by a national authority into whether a CE-marked product complies with EU legislation — covering technical file review, product testing, and enforcement actions including market withdrawal and recall.

Market Surveillance Inspection — What Authorities Check and Why

A Market Surveillance Inspection is the specific process by which a national market surveillance authority (MSA) investigates whether a product on the EU market complies with applicable legislation. It is the operational mechanism through which the EU’s market surveillance system translates into concrete action against individual products and manufacturers.

Understanding what happens during an inspection — and what authorities look for — is essential for any hardware manufacturer or importer with products on the EU market. A well-prepared manufacturer can navigate an inspection without disruption; an unprepared one may face market withdrawal, recall orders, and significant financial and reputational consequences.

How an Inspection Is Triggered

Market surveillance inspections are initiated through several routes:

TriggerDescription
Proactive samplingAuthority purchases and tests products from the open market as part of regular surveillance campaigns
ComplaintA competitor, consumer, or safety organisation files a complaint about a specific product
RAPEX / Safety Gate notificationAn authority in another member state has found a similar product non-compliant and triggered an EU-wide alert
Customs referralCustoms authorities have flagged a product at the border for potential non-compliance
Whistleblower reportAn employee or supply chain participant raises a concern
Media reportA high-profile safety story triggers targeted authority investigation

Proactive sampling campaigns are increasingly common and are coordinated across member states — particularly for product categories identified as high-risk (consumer IoT, radio equipment, children’s products).

Phase 1: Initial Product Evaluation

When a market surveillance authority decides to investigate a product, the first step is typically a preliminary evaluation of the product on the market:

Documentation Check

Authorities verify whether the basic market-entry documentation requirements are met:

  • CE mark present? — Is the CE mark physically affixed to the product or packaging, with the correct dimensions and format?
  • EU Declaration of Conformity accessible? — Is the DoC available to authorities (either supplied with the product or accessible via a link/QR code)?
  • Manufacturer/authorised representative identified? — Name and address visible on the product or packaging?
  • Product identification — Model number, serial/batch number, or other identifier present?

Missing or incorrect CE marking documentation is a finding in itself — even if the product is technically safe.

Risk Assessment

Based on the product category and any available information, the authority performs a preliminary risk assessment to determine whether a deeper technical investigation is warranted and at what urgency.

Phase 2: Technical File Request

If the initial evaluation raises concerns, or as part of a systematic investigation, the authority issues a formal request for the technical file — the complete documentation package that the manufacturer must maintain for 10 years.

What Authorities Request

DocumentWhat Authorities Examine
General product descriptionDoes it match the product on sale? Have there been undisclosed design changes?
List of applicable directives and standardsAre all applicable directives identified? Are the cited standards harmonised and current?
Design drawings and schematicsDo they correspond to the actual product sold?
Bill of MaterialsAre all components identified? Do any components have certification issues?
Risk assessmentHas the manufacturer systematically identified and mitigated hazards? Is the assessment credible?
Test reportsDo test reports cover all applicable standards? Are tests performed by accredited labs? Are they for the exact product model and configuration?
EU Declaration of ConformityIs it complete, signed by an authorised person, and consistent with the product and standards applied?

Response Deadline

The manufacturer must provide the technical file within the deadline specified in the request — typically 10 business days for an initial response under most EU directives, though some directives allow shorter or longer periods depending on the urgency.

Critical: An incomplete, inconsistent, or missing technical file is treated as evidence of non-compliance — independent of whether the product itself would have passed physical testing.

Phase 3: Laboratory Testing

If the documentation review is insufficient to confirm compliance — or if the preliminary evaluation indicates a likely technical issue — authorities commission accredited laboratory testing of the product:

Testing Process

  1. The authority purchases or seizes reference units of the product from the market.
  2. Units are submitted to an accredited test laboratory designated by the authority.
  3. The lab performs testing against the standards cited by the manufacturer in their DoC or, if none are cited, against applicable standards.
  4. A test report is issued.

What Is Tested

For a typical IoT radio device under the RED Delegated Act, an authority might commission:

  • RF spectrum testing — Is the radio transmitting on correct frequencies within allowed power limits? (ETSI EN 301 893, EN 300 328, etc.)
  • EMC testing — Does the device cause harmful interference? Does it withstand interference? (ETSI EN 301 489)
  • Electrical safety testing — Is the device electrically safe? (IEC 62368-1 or IEC 60950-1)
  • Cybersecurity testing — Does the device have default unique passwords? Does it validate software integrity? (EN 303 645, EN 18031-1)
  • SAR testing — For devices worn close to the body, is the specific absorption rate within limits?

If the Product Fails Testing

If laboratory testing reveals non-compliance, the authority moves to enforcement. The manufacturer is notified of the findings and given an opportunity to respond — but the burden of proof is on the manufacturer to demonstrate compliance.

Phase 4: Enforcement Actions

Enforcement actions range in severity based on the degree of non-compliance and the associated risk:

Administrative Compliance Dialogue (Minor Non-conformity)

For minor documentation deficiencies (e.g., missing information in the DoC, incorrect standard reference), authorities may:

  • Issue a non-conformity notice and allow a defined period for correction
  • Request updated documentation
  • Verify corrections before closing the case

Corrective Actions Without Market Restriction

For non-conformities that can be addressed without product recall:

  • Updated labelling or documentation
  • Firmware update to address a software-level gap
  • Supply of additional user safety information

Market Restriction Measures

For significant non-conformity:

MeasureDescription
Prohibition on further salesAuthority prohibits placing additional units on the market pending correction or investigation
Market withdrawalAuthority orders removal of all non-compliant product from distribution channels (not yet in consumer hands)
Market recallAuthority orders retrieval of units already in consumer hands — the costliest enforcement outcome

Public Notification

For serious risks, authorities publish:

  • Safety Gate (RAPEX) notification visible across all EU member states
  • National public safety warnings on authority websites
  • In severe cases, media releases

A public safety notification is visible to competitors, customers, and the press — with significant reputational consequences independent of any financial penalty.

Financial Penalties

Financial penalties are set by national law rather than uniformly by EU regulation, but can be substantial. Some member states impose penalties of hundreds of thousands of euros for systematic compliance failures or for endangering consumers.

What Manufacturers Must Prepare in Advance

The best outcome of a market surveillance inspection is that the manufacturer provides a complete technical file promptly, the authority is satisfied, and no enforcement action is taken. Achieving this requires preparation long before any inspection occurs:

Technical File Readiness Checklist

  • Technical file is complete and internally consistent (design docs match DoC, test reports correspond to actual product variant)
  • All applicable directives and currently valid harmonised standards are identified
  • Test reports are from accredited laboratories and cover all applicable standards
  • Test reports are for the precise product variant being sold (not a different model or hardware revision)
  • Risk assessment is documented and credible
  • EU Declaration of Conformity is complete, signed, and up to date
  • EU Authorised Representative is designated (for non-EU manufacturers)
  • Product carries CE mark in correct format
  • Technical file is readily retrievable (not locked in a former employee’s laptop)

Post-Market Monitoring System

A manufacturer with an active post-market monitoring system — tracking field returns, customer complaints, and safety reports — is in a much stronger position during an inspection. It demonstrates that the manufacturer takes ongoing safety obligations seriously, which can be a mitigating factor in enforcement decisions.

  • Market Surveillance — The broader EU system within which inspections operate.
  • Technical File — The primary document requested during any inspection.
  • CE Marking — What inspections ultimately verify.
  • Declaration of Conformity — The formal document checked in the first phase of any inspection.
  • Post-Market Surveillance — The manufacturer’s own monitoring system; evidence of this can be a mitigating factor in inspections.
  • Notified Body — Third-party assessors whose involvement (where required) reduces inspection risk.

A market surveillance inspection is a realistic risk for any product with EU distribution — not a theoretical one. Inovasense builds technical files that are designed to withstand authority scrutiny: consistent across all documents, test reports from accredited labs, and covering all applicable directives without gaps. Our EU Compliance services include technical file audit, DoC review, and post-market monitoring process design.

Official References