E-Commerce Nov 19, 2026

EU AI Act Transparency: What Your Store's Chatbot Must Disclose

EU AI Act Transparency: What Your Store's Chatbot Must Disclose

Time to read: 11 minutes

Content

  1. What Article 50 requires, and since when
  2. The AI feature transparency register
  3. Provider or deployer: building vs buying a chatbot
  4. Worked example: a cosmetics retailer's register
  5. Designing the disclosure: first interaction, wording and accessibility
  6. Generated images and product content: marking, deep fakes and editorial control
  7. What to require from AI vendors
  8. A transparency acceptance check before release
  9. FAQ
Bookmark

Since 2 August 2026, Article 50 of the EU AI Act requires AI systems that talk directly to people to tell them they are dealing with AI, at the latest at the first interaction, unless that is obvious. That duty sits with the provider: the company that develops the system, or has it developed, and puts it into service under its own name. A store that builds its own assistant on a model API, or has an agency build one, is likely its provider. A store that switches on a vendor's chatbot is usually a deployer: the notice is the vendor's to build, and yours to check. Two more duties reach retail. Providers of tools that generate images, audio, video or text must mark the output in a machine-readable way, and deployers must label deep fakes, which the Commission's guidelines say can include an AI product image that misrepresents the real product. Map every AI feature to a role and a duty, then test the notice on mobile and desktop.

This is plain-language guidance, not legal advice. Confirm your role and obligations with your counsel.

What Article 50 requires, and since when

Article 50 applies from 2 August 2026 (Article 113). The paragraphs that matter in a store:

ParagraphWhose dutyWhat the Act saysStore example
50(1)ProviderSystems "intended to interact directly with natural persons" must inform them "that they are interacting with an AI system, unless this is obvious" to a person "who is reasonably well-informed, observant and circumspect"Chat assistant, voice bot
50(2)ProviderOutputs of systems generating "synthetic audio, image, video or text content" must be "marked in a machine-readable format and detectable as artificially generated or manipulated"Image or text generator
50(4), first subparagraphDeployerDeep fakes: "disclose that the content has been artificially generated or manipulated"Realistic AI people in campaign images
50(4), second subparagraphDeployerAI text "published with the purpose of informing the public on matters of public interest" must be disclosed, unless it had "human review or editorial control" and someone "holds editorial responsibility"Possibly an AI-written guide with health or safety claims
50(5)BothInformation "in a clear and distinguishable manner at the latest at the time of the first interaction or exposure", conforming to "the applicable accessibility requirements"Every notice

Article 50(3), on emotion recognition and biometric categorization, rarely fits a shop. One date moved: the Digital Omnibus on AI, Regulation (EU) 2026/1744, published in the Official Journal on 24 July 2026, added Article 111(4). Providers of generative systems "placed on the market before 2 August 2026 shall take the necessary steps in order to comply with Article 50(2) by 2 December 2026." The other Article 50 duties did not move; the Commission's guidelines on Article 50 (C(2026) 7702, 5 November 2026) say a partly interactive, partly generative system must give the 50(1) notice from 2 August 2026. Fines for Article 50 breaches can be up to EUR 15 million or 3% of worldwide annual turnover, whichever is higher; for SMEs and small mid-cap enterprises (SMCs), whichever is lower (Article 99(4), (6) and (6a), the last added by the Digital Omnibus). Article 50 applies alongside, not instead of, the high-risk rules (Article 50(6)), and the guidelines note that a system can fall under Article 50 without being high-risk. Ask counsel if any feature might be on the Annex III list.

Article 50 datesTimeline of Article 50 dates: the Digital Omnibus on AI published on 24 July 2026, Article 50 applying from 2 August 2026, the Commission's guidelines of 5 November 2026, and the 2 December 2026 deadline for Article 50(2) on generative systems placed on the market before 2 August 2026.Article 50 datesAct, Digital Omnibus and guidelines24 July 2026: DigitalOmnibus on AI publishedRegulation (EU) 2026/1744 in theOfficial Journal; it added Article111(4)2 August 2026: Article 50appliesArticle 113; the other Article 50duties did not move5 November 2026: CommissionguidelinesC(2026) 7702 on Article 50; theguidelines are non-binding2 December 2026: Article50(2) deadlineArticle 111(4): generative systemsplaced on the market before 2 August2026

The AI feature transparency register

Keep one row per AI touchpoint, with these columns: vendor or custom build; your role (provider or deployer) and why; the Article 50 paragraph triggered, or "none" with the reason; the disclosure design (where, when, wording, accessible format); who handles machine-readable marking; human handover; logging; owner; and the latest test result. Start from this list:

TouchpointUsual Article 50 triggerWhat to record
Chat assistant (help desk or shopping)50(1); the guidelines name customer-support and e-commerce chatbotsWho provides it, where the notice shows, the handover
Voice or phone bot50(1)The spoken notice at the start of the call
AI product Q&A on product pages50(1) if customers type questions and get generated answers; 50(2) for its providerA notice beside the input field
Generated product or lifestyle images and video50(2) for the tool's provider; 50(4) if realistic and able to pass as realThe vendor's marking answer; your visible label
AI-written product descriptions50(2) for the tool's provider; 50(4) usually not (see below)Who reviews claims before publishing
AI email replies50(1) if the AI sends them; not if staff review and send themWho presses send
Virtual try-onNot 50(1): the guidelines list "AI-assisted product visualisation (e.g., virtual try-on, room staging, product rendering)" as outside itThe vendor's 50(2) answer

Record "none" for recommendations and search ranking too: the guidelines list "AI-enabled recommender systems" and "search and retrieval of information without generating or modifying content" outside Article 50(1).

Four Article 50 questions for each AI touchpoint in a storeFour questions asked in order for every AI touchpoint. A yes to question 1 leads to the provider's AI notice duty under Article 50(1); to question 2, the provider's machine-readable marking duty under 50(2); to question 3, the deployer's deep-fake label under 50(4); to question 4, the deployer's text disclosure under 50(4). If all four answers are no, there is no Article 50(1), (2) or (4) duty and the reason is recorded.Ask all four questions for each AI touchpoint.One touchpoint can trigger several duties.1 Does it talk withcustomers directly?50(1): AI notice atfirst interaction(provider's duty)Yes2 Does it generate image,audio, video or text?50(2): mark outputmachine-readably(provider's duty)Yes3 Realistic image, audio orvideo that could passas real?50(4): visibledeep-fake label(deployer's duty)Yes4 Text informing the publicon public-interest matters,without editorial review?50(4): discloseAI-generated text(deployer's duty)YesAll four no: no Article 50(1), (2) or (4) duty. Record why.
Ask the four questions in order for every AI touchpoint in the register. Each yes adds a duty, and the label says whose it is; only when all four answers are no do you record that these duties do not apply, with the reason. Provider duties sit with you if you built the system, or had it built, and run it under your name; otherwise with the vendor.

Provider or deployer: building vs buying a chatbot

A provider is a person or body "that develops an AI system ... or that has an AI system ... developed and places it on the market or puts the AI system into service under its own name or trademark" (Article 3(3)). A deployer is one "using an AI system under its authority" (Article 3(4)). For a store:

Still deciding what to build? Check whether an assistant can produce a valid cart (conversational commerce) and choose support automation by resolved journeys (helpdesk automation or AI agents).

Worked example: a cosmetics retailer's register

Fictional, illustrative example. A cosmetics retailer selling to EU consumers runs a vendor help-desk chatbot, a custom "shade finder" assistant an agency built on a model API, AI-generated lifestyle images with realistic people, and product descriptions drafted with AI and edited by staff.

TouchpointRole and reasonArticle 50Disclosure, handover, loggingOwner and result
Help-desk chatbotDeployer: vendor's product under the vendor's name, configured with our FAQ, not retrained50(1), vendor's dutyVendor's AI notice switched on; "Talk to a person" button; vendor logs handoversCX product owner. Mobile notice hidden by the keyboard; fixed in vendor settings, retest passed
Shade finderProvider: we had it developed and run it under our brand50(1); 50(2) for its text"AI assistant" label beside the input, first-message notice, handover to a beauty advisor, handovers logged; model vendor asked what it marksEcommerce product owner. Pass on desktop and mobile
Lifestyle imagesDeployer of the image tool; the tool vendor is its provider50(4): realistic people who could pass as real; 50(2) is the vendor'sVisible "AI-generated image" label on each imageContent lead. Open: vendor's marking answer pending
Product descriptionsDeployer of the writing toolNone under 50(4): descriptions carry no health, safety or sustainability claims; the regulatory team checks every claim before publishingNone needed; review recorded per productContent lead. Recorded

Designing the disclosure: first interaction, wording and accessibility

From the Commission's guidelines:

Designing the noticeWhat a chatbot notice needs: one prominent notice before the first interaction, plain wording near the input or output field, no reliance on terms and conditions or a generic label alone, and real text a screen reader announces when the chat opens.Designing the noticeTiming, wording, place, accessibilityOne prominent notice beforethe first interactionLikely to suffice in most instances;riskier contexts likely needreminders; say it is AI wheneveraskedPlain wording near theinput/output fieldSuch as “You are interacting with anAI system”; for voice, a spokenstatement at the startNot enough on their ownOnly terms and conditions, URLs ordocumentation; a generic “assistant”label; a site-wide AI noticeReal text, announced whenthe chat opensIf your store is an e-commerceservice under the EAA, the notice ispart of it

Article 50 does not require a route to a person. Add one anyway, and log it. In a multi-phase custom AI chatbot proof of concept for a US performance marketing agency, Dinarys built authentication and access control, fallback, logging, feedback and a validated-response layer; it is an agency PoC, not a consumer store chatbot or an AI Act project. For Oze's lending platform, Dinarys and Oze's internal team built a bank statement processing pipeline with asynchronous AI analysis, retry flows on failure and a manual template fallback for edge cases. Both plan in advance what happens when the AI cannot answer reliably.

Generated images and product content: marking, deep fakes and editorial control

Marking (50(2)) is the generator's provider's job; standard editing, such as grammar correction or minor cropping, is exempt. Ask each vendor how it marks and detects output.

Deep fakes (50(4)) are content that "resembles existing persons, objects, places, entities or events and would falsely appear to a person to be authentic or truthful" (Article 3(60)). For stores, the guidelines count "realistic AI-generated human avatars or personas" as persons and list as a deep fake "An AI-generated image of a product in advertisement or packaging that can affect the audience's perception and mislead as to the actual product appearance, characteristics or use". A real product shown against an AI-generated background is not one "as long as the ad is not likely to mislead". The label must be visible to people; metadata alone does not meet it. Evidently artistic or creative works need only a disclosure that "does not hamper the display or enjoyment of the work".

Text (50(4)) covers publications that inform the public on matters of public interest, which include "public health, environmental protection, consumer safety". The guidelines place "AI-manipulated text that is part of a company's advertisement or product descriptions (not including any claims related to e.g. health, consumer safety or sustainability)" outside it. For buying guides and claims, the review exception needs substantive review: spell-checking does not count, a substantive AI edit after sign-off voids it, and the person or function holding editorial responsibility should be named publicly.

Consumer law applies alongside: the guidelines point to the Unfair Commercial Practices Directive and the Consumer Rights Directive, whose information obligations apply "irrespective of whether the interaction is considered 'obvious'", and data protection law applies too.

What to require from AI vendors

Put these in the contract:

A transparency acceptance check before release

Run this for every AI touchpoint before it goes live and after each vendor or model change:

  1. The register row is complete: role with a reason, Article 50 paragraph or "none" with a reason, owner.
  2. In a fresh session on mobile and desktop, the notice appears at or before the first message, stays visible when the on-screen keyboard opens, and a screen reader announces it.
  3. Asked "Am I talking to a person?", the assistant says it is AI.
  4. The handover to a person works and is logged.
  5. Every realistic AI image in use carries a visible label, and the vendor's marking answer is on file.
  6. Public-interest text has a recorded human review and named editorial responsibility, or a disclosure.

One limit: the register records how you reached each decision; it does not settle open questions, such as when a white-label bot makes you its provider. The Commission's guidelines are non-binding, and only the Court of Justice of the EU can interpret the Act authoritatively.

If you want a second view before release, Dinarys' ecommerce consulting team can review your chatbot's disclosure, fallback and logging design. The legal assessment stays with your counsel.

FAQ

We use a vendor's chatbot. Is the notice our problem?

The Article 50(1) duty is the vendor's as provider, but the notice appears in your store. Check it is switched on and visible. If you retrain or rebrand the system, you may become its provider.

Do AI-written product descriptions need an "AI-generated" label?

Usually not under Article 50(4): the guidelines place product descriptions outside it unless they make health, consumer safety or sustainability claims. The tool's provider still marks output under 50(2).

Does a clause in our terms and conditions count?

No. The guidelines say disclosures only in terms and conditions, URLs or documentation are not enough on their own.

Let professionals meet your challenge

Our certified specialists will find the most optimal solution for your business.

Please enter valid name
Please enter valid company
Please enter a valid phone
Please enter valid E-mail
Message is too short

    Your message has been successfully sent. We will be in touch shortly! Success icon