Shopware chatbot: add Kyros to Shopware 6

You can add Kyros to Shopware 6, but not with one click. There is no Kyros plugin or app, and Shopware’s Administration has no field for custom scripts. For the floating chat bubble on every page, a self-hosted store therefore needs a small Twig template override in its theme or in a plugin, which is a job for your developer. Shopware cloud stores can’t use plugins; there, it would take an App. What you can place without development is the inline frame, using the HTML element in Shopping Experiences. Whether the HTML sanitizer leaves the code intact there, and whether it works the same way in Shopware cloud, isn’t clearly documented, so please test before you go live. Of all the platforms in our install guides, Shopware takes the most work.

What the chatbot answers in your store

You decide in Kyros what the assistant knows. You paste the URLs of the store pages it should know, one per line: shipping, payment, returns, FAQ, and individual product pages if you like. On top of that come Golden answers you write yourself, for example on delivery times. When an answer draws on your pages, numbered source links appear below it under “Further Links.” If your content has no answer, the assistant is instructed to say so.

Kyros is not connected to Shopware. The chatbot can’t see orders, customer accounts or your product catalog, only the pages you list. So it can’t answer “Where is my order?” on its own. That would take your own API, called by an Interactive Card (Beta) action.

Shopware AI: Copilot or chatbot?

Search for “Shopware AI” and you’ll likely end up at Shopware Copilot. According to Shopware’s documentation, it is a chat-based AI assistant that helps you manage your store. It runs only in the Administration (Shopware 6.7), with a limited free monthly quota; beyond that, there is Shopware Intelligence+. Copilot doesn’t chat with your shoppers, and the documentation describes no storefront chatbot (as of October 1, 2026). Chatbots for store visitors come as third-party extensions in the Shopware Store, or as embedded tools like Kyros.

If you want to install a chatbot with one click from the Shopware Store, a Store extension is the simpler route. And if it needs to look up orders without custom development, Kyros is not the right fit.

1. Copy the code in Kyros

1. Open your assistant’s Deploy section and click “Install the widget.”
2. Choose “Floating bubble” for a chat on every page or “Inline frame” for a chat in a fixed spot. Kyros has no Shopware-specific guide; use the HTML code.
3. Under “Website access,” you set which domains the chat can open on; add your store’s domain there, and temporarily your staging domain for testing. On other domains the chat button still shows, but the chat window won’t load.
4. Under “Code expiry,” you can set whether and when the signed code expires.

The floating bubble code looks like this; your values for id and sig are in Kyros:

<script src="https://kyros.omniratio.de/api/widget?id=…&sig=…&type=chatbot"></script>

2a. Chat bubble via a Twig template (self-hosted store)

Shopware’s developer guide “Add JavaScript as Script Tag” describes how an external script gets into the storefront through a template. Your developer extends the meta.html.twig template in your theme or plugin and adds the Kyros script to the layout_head_javascript_hmr_mode block after {{ parent() }}:

{% sw_extends '@Storefront/storefront/layout/meta.html.twig' %}

{% block layout_head_javascript_hmr_mode %}
    {{ parent() }}
    <script src="https://kyros.omniratio.de/api/widget?id=…&sig=…&type=chatbot"></script>
{% endblock %}

As an alternative, the guide names the base_body_script block in storefront/base.html.twig for body-level scripts, explicitly only when technically necessary. According to Shopware, you need a running plugin and full file access. Afterwards, clear the cache, either in the Administration under Settings › System › Caches & Indexes or with php bin/console cache:clear, and check the bubble on a staging environment first.

2b. Inline frame via Shopping Experiences (no development)

1. In the Administration, open Shopping Experiences and the layout of the page where the chat should appear, for example your help or contact page.
2. Add an element from the “HTML” block category and paste the inline frame code into it.
3. Save, then check the page in your store: does the chat appear in full?

The inline frame code looks like this; copy the complete code from Kyros:

<iframe src="https://kyros.omniratio.de/embed/widget/…?sig=…" width="100%" height="600px" allow="microphone; camera; autoplay" style="border: none; border-radius: 16px;"></iframe>

Please test: Since Shopware 6.5, an HTML sanitizer removes HTML code it considers unsafe. The Shopping Experiences documentation advises configuring or disabling the sanitizer accordingly, or tags and attributes may be removed. The 6.6.1.0 release notes, on the other hand, say the new HTML element does not conflict with sanitization. The sources also disagree on the version: the release notes say 6.6.1.0, the user documentation 6.4.0.0. In a self-hosted store, your developer configures the sanitizer in config/packages/z-shopware.yaml; Shopware strongly advises against switching it off entirely. Cloud stores currently can’t adjust it. A <script> in the HTML element is no substitute for the chat bubble: whether it runs on the storefront isn’t documented.

2c. Shopware cloud

According to Shopware’s developer documentation, plugins are not compatible with cloud stores; there, you extend the store with an App. Apps can customize the storefront, including changing templates and adding custom JavaScript. There is no Kyros App. For the chat bubble, a developer would therefore have to build a custom App for your store. For the inline frame: check whether the Shopping Experiences HTML element is available in your cloud store and lets the code through.

Check before going live

• Cookie consent: Shopware’s cookie consent manager doesn’t block scripts by itself. According to Shopware, registering a cookie there mainly lists it in the manager. If Kyros should load only after consent, your developer has to build that.
• Content Security Policy: Shopware sets default policies through the shopware.security.csp_templates container parameter. If your site sends a Content Security Policy, it must allow content from kyros.omniratio.de, or the browser blocks the widget. The developer tools console shows what is blocked.
• Test on every device: Check the bubble or inline frame on a phone and on desktop, including alongside your cookie banner.