Role · Importer or distributor

You do not build it. You let it in.

Most EU AI Act importer and distributor obligations are checks made before a system reaches the market. Importers also keep the paperwork ten years.

No card · EU-hosted · 5 minutes to a first classification
Evidence · filed onceExample
Record · approved
Roles, responsibilities and authorities
One owner · one review date · hash-chained on approval
ISO 42001§5 Counts
ISO 27001§5 Counts
EU AI Act14Related · not counted
NIST AI RMFGOVERN 2.1Related · not counted

The record is credited only where it has been verified against both clause sets. The other clauses are signposted, and nothing is ticked on your behalf.

The reality

What the supply-chain roles miss.

What we hear

“We assumed the CE mark meant the checks were done.”

What the product does

A CE mark is the provider's claim. Article 23 makes verifying it, and the paperwork behind it, your duty.

What we hear

“We rebranded it, and nothing changed on our side.”

What the product does

Under Article 25(1)(a), your name on the product moves the whole provider set to you.

What we hear

“Nobody knew we had to keep the declaration for a decade.”

What the product does

Article 23(5) sets ten years from placing on the market, longer than most retention defaults.

What you get

A pre-market check that leaves a record.

01

The verification, as a form

Provider, authorised representative, CE date, declaration and placing date in structured fields: evidence, not memory.

02

Only the supply-chain duties

An importer gets the Article 23 set, never the Annex IV file that belongs to the builder.

03

The ten-year clock, held

Retention runs from the placing date, so the certificate, instructions and declaration outlive their folder.

04

Ready for the authority

When an authority asks, export the record instead of assembling it under pressure.

In practice

Where the checks actually bite.

Use case 01

A reseller importing a US vendor's high-risk system.

  • Art. 23 checks recorded before placing: assessment, documentation, CE, declaration.
  • Declaration and instructions kept for the ten-year clock.
  • No Annex IV: the technical file stays the provider's.
Evidence · filed onceExample
Record · approved
Roles, responsibilities and authorities
One owner · one review date · hash-chained on approval
ISO 42001§5 Counts
ISO 27001§5 Counts
EU AI Act14Related · not counted
NIST AI RMFGOVERN 2.1Related · not counted

The record is credited only where it has been verified against both clause sets. The other clauses are signposted, and nothing is ticked on your behalf.

Use case 02

A distributor putting its own brand on a bought model.

  • The branding question flips the role to provider under Art. 25(1)(a).
  • The obligation set switches to risk management, Annex IV, conformity, CE.
  • Caught at classification, not at audit.
ClassificationRecruitment assistant
Prohibited practicesNo — none of thoseArt. 5
Product lawNoArt. 6(1)
Annex III area4. EmploymentArt. 6(2)
Art. 6(3) exceptionIt profiles natural personsArt. 6(3)
Your roleWe use it as supplied — a finished tool somebody else providesArt. 3(3)–(8)
VerdictHighDeployerEvery step cites its article
Illustrative record · articles are real, the system is not
Use case 03

A reseller who believes a shipped system no longer conforms.

  • The decision not to make it available, recorded and dated.
  • Provider and authority informed, and that is evidenced.
  • A hash-chained trail of who knew what, and when.
Audit trailArt. 12 · Art. 72
29.09.2026 09:12Classified AI systemRecruitment assistant → High Risk
29.09.2026 11:47Updated obligationAssign human oversight person(s) → Complete
29.09.2026 11:51Uploaded evidenceOversight rota.pdf
29.09.2026 16:30Signed off the residual riskA. Morgan
SealedDaily anchor · 29.09.2026 · 4 rows
sha256sha256 fingerprint bf89cbac35190d9ad25aac7b61ef9fb6ad1f7033008ec179304d9db75eadbc26
Chained to the day before
Illustrative trail · the anchor is the real hash of these rows
Also included

The parts the supply chain reaches for.

Straight answers

Questions on importer and distributor obligations.

What is the difference between an importer and a distributor?

An importer places on the EU market a system bearing the name or trademark of a provider established outside the Union (Art. 3(6)). A distributor makes it available further down the chain, as neither provider nor importer (Art. 3(7)).

What must an importer verify before placing a high-risk system?

Article 23: that the provider carried out the conformity assessment, drew up the technical documentation, affixed the CE marking, supplied the declaration and instructions, and appointed an authorised representative where required. If you believe it does not conform, do not place it until it does.

How long must an importer keep the paperwork?

Article 23(5): a copy of any notified-body certificate, the instructions for use and the EU declaration of conformity, for ten years after placing on the market. That outlasts most retention defaults, so record it deliberately.

When does a distributor become a provider?

Under Article 25(1): put your name on a high-risk system already on the market, substantially modify it, or change a system's purpose so it becomes high-risk, and the provider set applies to you. Rebranding is the most common route.

Do we have duties after the system is sold?

Yes. While the system is your responsibility, storage and transport must not jeopardise conformity. Both roles must act on a system they consider non-conforming and give authorities the information needed to demonstrate conformity.