EU Market Surveillance Regulation Compliance

Start with the product and the route to the EU market. Regulation (EU) 2019/1020 applies to products covered by Union harmonisation legislation, and Article 4 applies only to the listed product laws or other legislation that explicitly relies on Article 4. For those products, placement on the EU market requires an economic operator established in the Union who can perform the Article 4 tasks.

The Article 4 operator can be an EU manufacturer, an importer where the manufacturer is outside the Union, an authorised representative with a written mandate, or an EU fulfilment service provider for products it handles when none of the first three exists in the Union. The operator's name, registered trade name or trademark, contact details, and postal address must be indicated on the product, packaging, parcel, or an accompanying document.

Do not separate online sales from MSR compliance. Article 6 treats products offered online or through other distance-sales channels as made available on the market when the offer is targeted at end users in the Union. The grounding guidance points to a case-by-case assessment, including dispatch areas, language used for the offer or ordering, and payment methods.

For direct-to-consumer shipments from outside the EU, the compliance record should show how the Article 4 operator was arranged before the offer was made to EU end users. If an authorised representative is the route, keep the written mandate and confirm the representative has the means to perform the Article 4 tasks.

Article 4 does not require every Article 4 operator to hold the whole technical file at all times, but it does require a workable readiness model. Where the applicable product legislation requires an EU declaration of conformity, declaration of performance, and technical documentation, the Article 4 operator must verify that they have been drawn up, keep the declaration available for the required period, and ensure that technical documentation can be made available to market surveillance authorities on request.

The practical file should therefore separate three records: the existence check, the custody or access route, and the response package for authorities. That package should identify who can supply the declaration, who can supply the technical documentation, which language can be used for the requesting authority, and how the manufacturer or client will support follow-up questions.

Economic operators must cooperate with market surveillance authorities on actions that eliminate or mitigate product risks. Market surveillance authorities can require documents, technical specifications, compliance data, supply-chain details, website ownership information, samples, inspections, and action to end non-compliance or eliminate risk.

When a product is non-compliant or presents a risk, the MSR corrective-action record should be specific enough for authorities and internal teams to follow. Article 16 lists possible measures including bringing the product into compliance, preventing further availability, withdrawal, recall, public warnings, prior conditions for sale, and alerts to end users at risk. For serious risks, rapid notification and Safety Gate pathways may become relevant.

MSR compliance should be ready before import, not after a customs problem appears. Articles 25 to 28 cover controls on products entering the Union market. Designated authorities perform controls for release for free circulation on a risk-analysis basis, exchange risk-related information, and may suspend release where documentation, marking, labelling, CE marking, Article 4 contact details, or other compliance indicators raise concerns.

If release is suspended, market surveillance authorities are notified. If the product presents a serious risk or may not be placed on the market because it is non-compliant, authorities can prohibit placement on the market and require that release for free circulation is not authorised. The business record should therefore connect import declarations, product identifiers, Article 4 contacts, documentation packs, and any authority correspondence.

A useful MSR compliance pack is short, current, and product-specific. It should not be a generic legal memo. It should let product, logistics, marketplace, legal, quality, and support teams answer three questions quickly: who is the EU-facing operator, where is the conformity evidence, and what happens if an authority or customs office asks for action.

Use version control for records that change with product design, supplier changes, firmware updates, packaging changes, marketplace expansion, new fulfilment arrangements, import routing, authority findings, or corrective actions. Keep unsupported national penalty assumptions out of the product record unless a current Member State source has been checked separately.