Caesar AI Atlas
RegulatoryIntermediate

Placing on the Market vs Putting into Service

A side-by-side comparison of Placing on the Market and Putting into Service. Understand how first EU market availability differs from first operational use for an intended purpose.

Quick Verdict: Use Placing on the Market for first EU market availability; use Putting into Service for first intended use by a deployer or provider in the Union.

At a Glance

Placing On The Market

Placing On The Market defines first making available of an AI system or general-purpose AI model on the EU market.

Key Characteristics
  • First making available on the EU market
  • Can apply to AI systems or general-purpose AI models
  • Regulatory obligations may attach at or before this point
Watch Out For
  • Not the same as every later supply or distribution event
  • Timing matters for pre-market evidence and provider obligations

Context: Most relevant when assessing market-entry obligations before an AI system or GPAI model is made available in the EU.

VS
Putting Into Service

Putting Into Service defines supplying an AI system for its first use by a deployer or for the provider's own use in the Union.

Key Characteristics
  • Supplying an AI system for first intended use
  • Can be for a deployer or for the provider's own use
  • Marks an operational lifecycle point
Watch Out For
  • Not the same as general market availability
  • Use must be tied to the intended purpose in the Union

Context: Most relevant when assessing obligations tied to first operational use of an AI system in the EU.

Key Differences

AspectPlacing On The MarketPutting Into Service
Regulatory purposePlacing on the market identifies the first making available of an AI system or GPAI model on the EU market.Putting into service identifies the first use of an AI system for its intended purpose in the Union.
Trigger pointTriggered by first EU market availability.Triggered by first operational use by a deployer or the provider itself.
Required evidenceEvidence should support compliance before or at market entry.Evidence should support readiness for intended operational use.
Responsible actorMost closely linked to the actor making the system or model available on the EU market, often the provider.Linked to the actor supplying or using the system for first intended use, including provider or deployer contexts.
Audit implicationAuditors should check whether pre-market obligations were satisfied before the first market event.Auditors should check whether operational-use controls were ready before first intended use.
Caesar AI Note

In practice, product teams should build separate gates for market release and operational activation, because a system can be commercially available before a specific deployer starts using it.

Notes

Common Mistakes

1

Using market launch and first operational use as interchangeable milestones.

2

Waiting until first deployment to prepare evidence needed before market placement.

3

Ignoring provider's own use when assessing putting into service.

When to Use Each

placing-on-the-market

Use Placing on the Market when the issue is first EU market availability of an AI system or general-purpose AI model. It is the right term for pre-market checks, provider evidence, and CE-related workflows where applicable.

putting-into-service

Use Putting into Service when the issue is first intended operational use in the Union. It is the right term for deployment-readiness, use-context controls, and evidence tied to actual operation.

Compliance Note

Under the EU AI Act, these lifecycle triggers help decide when obligations must be satisfied. Treating them as the same can cause teams to prepare evidence too late or assign responsibility to the wrong actor.

FAQ

Is putting into service the same as placing on the market?+

No. Placing on the market concerns first EU market availability, while putting into service concerns first intended use in the Union.

Can both happen close together?+

Yes. They can occur close in time, but the legal concepts still answer different lifecycle questions.

Why should governance teams separate these triggers?+

Separate triggers make it easier to assign owners, prepare evidence, and confirm that obligations are satisfied before the relevant lifecycle event.

Recently Viewed

No recently viewed comparisons yet.