▶ Watch the video on YouTube

A round of improvements across chat, Experience Designer for Shopware, the Shopware integration, data sync and the Nuxt module.

Agent questions wait for you in the thread

When the agent asks a question, needs a tool approved or proposes a plan, it now shows up as the last message in the conversation instead of sliding up over the message box. This works the same in Studio, Experience Designer and the chat hub. If you are scrolled up reading the agent's reply, nothing jumps: a "Waiting for your answer" note appears on the scroll-to-end button, and it disappears once the question is in view.

Questions with several steps now list each step by its title. Open any step directly, so you can read the second question before you answer the first. Answered steps show a check, and long questions no longer scroll inside a small box, so their titles are never cut off.

Experiences on your storefront match the preview

Experiences you publish with Experience Designer for Shopware no longer pick up styling from your shop's theme, so shoppers see exactly what you designed. Link clicks inside an experience are reported to Google Tag Manager, and adding a product to the cart from an experience is tracked as an add-to-cart event. This needs a current browser (Chrome 111, Safari 16.4 or Firefox 123 and later).

Shopware connection status loads on large shops

On shops with many sales channels, the connection status on the integration page could stay on "Loading" for good. It now runs only a quick connection check and shows up right away, however large your setup is. Languages, currencies and sales channels load only in the screens where you edit them.

More improvements

• Steadier syncs across subshops - Product and category syncs keep going when an item is missing from one subshop instead of stopping, and records show the right language's names.

• Sample Experience link - Opening the sample Experience from the Shopware extension takes you to Experience Designer, even when no sample slot is saved yet.

• Larger menu trees - Menu trees load up to 1,250 records before they are cut off, up from 1,000.

• Nuxt: disabled search stays quiet - useFronticSearch makes no requests while enabled is false, and refreshes its results once you turn it back on.

• Nuxt: types in server code - Types generated from your Frontic data model and the frontic:fetch:error hook now work in API routes and server utilities too.