EU AI Act Compliance

Automation

Flow Builder action, Rule Builder condition, notifications and the CMS element.

Beyond plain labelling, the extension brings three additions that slot into Shopware features you already know. They're optional – use them if they fit the way you work.

1. Rule condition: "Product has AI image with status"

Shopware rules let you group products dynamically or steer actions (dynamic product groups, discounts, that kind of thing). This extension adds a new condition:

Product has an AI image with a given status.

With it you can build a product group containing every product with AI-generated images – to highlight them in a campaign world, for instance.

How to use it:

Step 1: Open Settings → Rules and create a rule or edit an existing one.

Step 2: Add the condition "Product has AI image with status".

Step 3: Pick the status you want and save.

2. Flow action: "Set AI media status"

The Flow Builder automates processes in Shopware ("when X happens, do Y"). The extension adds a new action:

Set AI media status – sets the AI status for the images of the product concerned, automatically.

So you can decide that on a given trigger the images of a product get a status, with nobody having to click anything.

How to use it:

Step 1: Open Settings → Flow Builder and create a flow or edit an existing one.

Step 2: Choose "Set AI media status" as the action.

Step 3: Pick the status you want and save.

The extension can also fire an event when too many media are unlabelled (a coverage gap). Use that event in the Flow Builder to send yourself a notification, for example. You switch the underlying check on in the configuration.

3. CMS element: "AI Transparency Info"

For Shopping Experiences the extension ships its own element: "AI Transparency Info". Use it to add an explanatory block for your customers – to describe your shop's AI policy, for example.

How to add it:

Step 1: Open Content → Shopping Experiences and edit a page.

Step 2: Drag the "AI Transparency Info" element where you want it.

Step 3: Enter a heading and an explanatory text.

Step 4: Save the layout.

When is each one worth it?

  • Rule condition: when you want to group or highlight AI products on purpose.
  • Flow action: when you want labelling to happen without manual steps.
  • CMS element: when you want to explain your AI policy transparently on a content page.

Once folder defaults, the metadata scan and a flow are in place, day-to-day labelling mostly runs by itself – you only step in for the cases in the review queue.

Was this page helpful?