A new component has been added to the Builder which adds dynamic grid options (rowspan/colspan) to regular product tiles. This means you get the same maximum flexibility and creative layout options that were previously only reserved for special tiles, now available for your everyday product tiles too. This new Item Placeholder component is a perfect fit for creating visually appealing grids that better reflect your brand style and merchandising strategy. Dynamically adjust tile size in both rows and columns, mix and match layouts for a more engaging and personalized product grid and maximize impact without any limitations.

Designed to improve user experience and provide greater insights into product relationships and applications, two small features with great impact were added to the Items module in Tweakwise App > Catalog. You can now easily view related items belonging to the same group through the group code. By simply accessing the group code users can explore all related items, resulting in a more streamlined browsing experience. We have also introduced a new feature that provides clarity on how each item is being utilized within the platform. Users can now see whether an item is directly applied in the Builder or via the Pins module. This insight should help to understand the context in which products are used.

Our Shopware plugin was upgraded so that we are compatible with Shopware 6.7. Every year, Shopware releases a new major version with improvements in performance, accessibility, and developer experience. Back in June, Shopware released its version 6.7. Major versions don’t focus on new features. Instead, they provide the technical foundation for features that will be introduced in upcoming minor releases. For Tweakwise, it is required to keep up to date with these new major versions so that our product won't break your storefront in case you upgrade to the newest Shopware version.

📘

SW-Tweakwise 5.1.0 (Compatibility with Shopware 6.7)

Click this link to visit corresponding repository and update on Github. This version is now supporting Shopware v6.7.x. Both v4 (for Shopware 6.5 and 6.6) as v5 (for Shopware 6.7) of the plugin will be maintained.

We have implemented an optimization that fixes some form of app freezes we've been experiencing lately. The issue was (likely) caused by the items module where we would fetch all categories to which an item was linked at the same time. In some cases, this resulted in an awful lot of API requests at the same time which significantly slowed down the API in such extend that all users, regardless of the customer or instance, where affected. The implemented fix could temporary result into slower pages (when lots of categories are linked), and that no data is available (as it will appear a bit later).

• Backend API | We extended the existing Get item endpoint in the Backend API with attribute id in the attributes list. This makes follow-up requests to the API easier than previously when only the key and name were present in the list.
• Backend API | We added the possibility to filter on groupcode in the Get all items endpoint of the Backend API.
• Backend API | We added a new endpoint to the Backend API for checking item usage in builder and pins.
• Backend API | We implemented a new Organic component for Builder (see below) in the Backend API.
• Backend API | Via our items endpoint you could add values to derived attributes, like it was a feed attribute. We added validation on this so that its not possible anymore.
• Backend API | Updated existing category-related endpoints to include Landing Page information in their responses.
• Delivery API | The Delivery API has been extended with the option to serve organic product tiles in the builder, containing a flexible width and/or height. This feature will be introduced so that users are in full control of creating layouts in the builder, no matter on which item_types are configured.

Tweakwise App

• Tweakwise App | We have added the option to duplicate a configuration in the Tweakwise App > Suggestions module. In the context menu of each suggestion setup on the index page, there's now a button to create a copy.
• Tweakwise App | We have added a confirmation before leaving the page alert, after having made changes to a suggestion rule so users don't lose any unsaved changes. We resolved the problem where no suggestions could be created for a category having id 0 as well.
• Tweakwise App | The recently introduced priority list of categories in category suggestions was already made easier to use by adding a drag and drop functionality to change the order of the list.
• Tweakwise App | Fixed an issue where the GA4 module wouldn't open if the connected Google account no longer had access to the selected property.

Demoshop

• Demoshop | A tiny update regarding the JS Demoshop! When you're viewing suggestions in the JS demo page, the category and facet suggestions are actually clickable! Before this release they were shown but nothing happened when you clicked on them.

JavaScript

• Tweakwise JS | The in-filter search in the Search & Merchandising JS package has been made a bit better. It now ignores all diacritics (á, é, ë, etc.) or special characters, so it's easier to find terms with them. There is no need for any configuration, this is now how the search works for everyone. So, 'crème brûlée' now will be found while searching for just 'brulee'.
• Event Tag | We updated the Event Tag so that it automatically tracks user sessions. Whenever the tag is loaded for the first time, a new session is created. This session is automatically sent along with every event, like a purchase. If the user is inactive for 30 minutes, the session expires and a new one is generated when the user re-visits the page or continues where he/she left off.

Plugin Studio

• Plugin Studio | Fixed a bug where certain numbers (typically those ending with a 0 after the decimal point) were not formattable (delimiter, separator,..).
• Plugin Studio | Fixed a bug related to tiles, where an element had the value of just a (space character), the text "NaN" would show instead. This no longer happens.

Guided Selling, designed to help customers find the most suitable products in just a few logical steps instead of filtering, is now supported in the Tweakwise Demoshop. You can now explore the Guided Selling funnel experience directly in the Demoshop, which makes it easier than ever to demonstrate how Guided Selling can simplify product discovery, showcase its personalization and filtering logic in real time and inspire everybody with a hands-on example of its potential.

Guided Selling bridges the gap between online product discovery and the in-store sales experience. By guiding users through a series of dynamic questions and filters, Guided Selling simplifies complex assortments, boosts conversion, and enhances the shopping experience.

• SW-Tweakwise 4.4.0 | Besides the property 'Selected option', which contains the chosen options for a specific variant in one attribute, we have introduced the multi-value property 'Selected options' in the feed. This property will store the selected options of a variant as separate attributes.
• SW-Tweakwise 4.3.0 | Added an option to show sibling categories in the category filter on the merchandising pages (by adding the parent category in navigation.cid).
• SW-Tweakwise 4.2.3 | Added missing getters and setters in feed generation events.
• SW-Tweakwise 4.2.3 | The last generation date is now instantly updated when you click the refresh button in the feed admin, like it already worked for 'status' and 'renewal date'.
• SW-Tweakwise 4.2.2 | Added some missing Dutch translations in the admin of the plugin.
• SW-Tweakwise 4.2.2 | Adding products to your wishlist/favorites is now working (again) when using grouped products.
• SW-Tweakwise 4.2.2 | When you have non-string custom fields in your products (like prices), this will now not result in an error when generating the feed.
• SW-Tweakwise 4.2.2 | No error will show up in the browser console when you do not have activated the wishlist in Shopware.

📘

SW-Tweakwise 4.4.0

Click this link to visit corresponding repository and update on Github.

As part of our ongoing commitment to inclusive digital experiences, the Tweakwise Search & Merchandising JavaScript module has been updated to align with the latest web accessibility (a11y) practices. Accessibility in web development means designing interfaces that are usable by everyone including people relying on screen readers, keyboard navigation, or visual support tools. These enhancements are designed with WCAG 2.2 AA compliance in mind, supporting the European Accessibility Act, which took full effect on June 28, 2025.

This update ensures that Search & Merchandising JS functions optimally with assistive technologies. One of the biggest changes is that the entire module is now fully operable with a keyboard: users can navigate, select filters, interact with carousels, and more, without ever using a mouse. We’ve also added descriptive alt texts for icons and images, and proper ARIA roles and labels to make the experience compatible with assistive technologies. Smaller but meaningful improvements include better visual contrast (e.g., making filter count text easier to read) and eliminating tab traps that previously hindered smooth navigation.

While the core experience remains unchanged for most users, it’s now significantly more accessible for those using screen readers or keyboard navigation. Do note that accessibility can also be influenced by customizations in styling and structure of the Tweakwise JS implementation, which may vary per customer setup. We’re still working on a few follow-ups, so please let us know if you encounter anything unusual - your feedback is invaluable as we continue to improve.

📘

European Accessibility Act/WCAG 2.2 AA

In January 2013, a European Accessibility Report was created that prompted a legislative change (law), which was adopted by the EU member states in 2019. By June 2022, member states had to implement the changes in their own legislation. June 28, 2025, marks the official start date of the European Accessibility Act.

In the Netherlands, (semi-)government websites must already meet certain accessibility requirements. The main change in 2025 is that the legislation will apply to many more organizations, including e-commerce businesses.

Note: As we mainly focused on the Search & Merchandising JS in this release, we will follow up on this topic regarding other solutions, like Suggestions JS, Recommendations JS, Guided Selling JS and our Magento storefront plugins. Web accessibility for our Shopware plugin will be fully covered via our JavaScript solutions.

We’re excited to announce that our OpenAPI specification for the Frontend API has been significantly improved and is now fully valid and compliant with industry standards. This means developers can confidently use the specification to automatically generate API clients in a wide range of programming languages, streamlining the process of connecting to our API and reducing the risk of errors. For example, developers can take advantage of tools like OpenAPI Generator to quickly create ready-to-use API clients, saving time and ensuring consistency across different projects.

These improvements make it much easier and faster for teams to integrate with our services, whether they are building new features or maintaining existing applications. By providing a clear and accurate API specification, we’re making our platform more accessible and developer-friendly.

• Magento2Tweakwise 8.4.4 | A new setting for visual item types was added for enabling or disabling visuals. This new behavior prevents the default product tile layout from being overwritten, as we encountered some issues with this. When enabling Personal Merchandising or Visuals, the product tile layout may be replaced. To maintain a custom layout (built by yourself), you can override the default layout file with your own version.
• Magento2Tweakwise 8.4.5 | Fixed an issue where the category URL ended with a trailing slash, even though this was not configured.
• Magento2Tweakwise 8.4.5 | Fixed an issue where the 'clear filters' URL was incorrect in situations that the filter URL segment included the category URL.
• Magento2Tweakwise 8.4.5 | Fixed an issue where HTML was displayed as plain text on a button.
• Magento2Tweakwise 8.4.5 | Fixed a tiny bug where an analytics request from the Hyvä-theme was not processed correctly.
• Magento2Tweakwise 8.4.5 | Fixed an issue where a dot (.) in the personalisation profileKey caused analytics requests to be ignored by Tweakwise.
• Magento2Tweakwise 8.5.0 | Regarding our Event Tag integration, the purchase event now includes a revenue value, allowing for more accurate reporting. We also added the item_click event to track which products users click on.
• Magento2Tweakwise 8.5.0 | Introduced a compatibility adjustment for Magento 2.4.8. As full support is still being tested, more updates will follow.
• Magento2Tweakwise 8.5.0 | A wrong type declaration has been fixed to prevent potential runtime errors.
• Magento2Tweakwise 8.5.0 | Fixed an error that occurred when Tweakwise was configured for swatches, but no swatch attributes existed in Magento.
• Magento2TweakwiseHyva 4.4.0 | Just like in the main module, the item_click event is now supported.
• Magento2TweakwiseHyva 4.4.0 | The swatch mismatch error mentioned above has also been resolved for the Hyvä storefront.
• Magento2TweakwiseExport 7.4.0 | The SEO-Url of categories is included in the export data, required for a smooth interaction with the new/upcoming Magento Tweakwise JS plugin. By having category-urls available within Tweakwise, it is possible to refer category-suggestions and category-filters to their corresponding SEO-friendly urls instead of making use of query-parameters.
• Magento JS 1.1.0 | Added support for analytics events to track purchases, product views, and search events. Item click events were already supported. Meanwhile, fixed a small issue where the add to cart functionality could fail under certain conditions.

• Backend API | We have added the possibility to overwrite the order of category suggestions via the Backend API. From now, GET/POST/PUT /suggestions/autocomplete endpoints have a new PrioritizedCategories property.
• Backend API | Fixed a minor Google Analytics 4 metrics incompatibility validation bug.
• Analytics API | The session start event was added to the Analytics API. Having this event will, for example, allow us to say something about bounce rates on our customers’ websites when implemented.

Tweakwise App

• Tweakwise App | In the Google Analytics 4 reports, it is now possible to use custom created dimension instead of a standardized list. This does mean that all dimensions as available in GA4 are also available to use as Tweakwise data. Meanwhile some validation-logic to the Google Analytics 4 module has been changed. We do show relevant validation error messages in case dimensions and metrics are not compatible.
• Tweakwise App | In addition to setup exclusions for Category suggestions, it is also possible to prioritize certain categories in your category suggestion group by hand, so these categories will pop up in your category suggestions result set with more priority. Also changes were done in the regular algorithm. Category suggestions that exactly match the search term, will be pushed to the top of the suggestions.
• Tweakwise App | We have re-arranged the elements in the Suggestion groups headers and color-coded different groups' labels, so it's easy to recognize at first look.
• Tweakwise App | The attribute filter is now a required field for setting up facet suggestion groups, solving the problem of having a saved breaking configuration.
• Tweakwise App | We fixed the way how to edit already placed tiles in your Builder templates. In case there is a second step in the tile's edit modal (e.g. Basic and Advanced tiles), you go directly there and all fields are properly filled with current values, making it easy to make tiny modifications.
• Tweakwise App | When sorting facets in a Filter template detail page, you are no longer randomly redirected to the Facet detail page after dropping the dragged item as this side-effect is now prevented.
• Tweakwise App | We fixed a small issue where you could not save the concatenate derived attribute when the attributeName has [] in its name.
• Tweakwise App | Added validation to the feed import for when there are 'HTML tags' present in the values of attributes. The import will now continue to work, but a warning will be shown.
• Tweakwise App | Applied a more consistent UX/UI to the disclosures in the App. For example, the arrow indicating that something is collapsed is now always on the left side.
• Tweakwise App | We've changed the way we search for suggestions (search phrases, facets, categories), more specifically: we ignore 'diacritics', special characters like éë etcetera. Previously, when searching for pokemon, you would not find category suggestions for categories containing 'Pokémon' in the name. This is now fixed and aligns with the rest of our search behaviors.
• Tweakwise App | We've enhanced how AI Embedding attributes are processed to ensure more reliable search results. Previously, products with multiple values for an AI embedding attribute could cause inconsistent search behavior. Now, the platform will consistently select a value from such attributes when creating AI embeddings, guaranteeing that search queries always return predictable and stable results.
• Tweakwise App | Added API attribute names in the list view of the Attributes module. Now you can see the name next to the URL name.
• Tweakwise App | Fixed a bug where some category paths (e.g. in Suggestions module - Category Suggestions - Exclude/Prioritize categories list) would show the last category name twice.
• Tweakwise App | Fixed the layout of the GA preview so that no columns can overflow the table anymore.

Demoshop

• Demoshop | Pagination has been improved. It's now possible to directly go to the page you want by typing in the page number. Also you can quickly navigate to the first and last page of the response, instead of only browsing to next and previous pages.
• Demoshop | We've added a summary of the total amount of results on top of the lister page, like we already did with the amount of results on a search results page. The search results display options (for debugging purposes) are no longer visible in case the 'Weighted Search Algorithms' feature is not enabled.
• Demoshop | Fixed the layout of the JavaScript Demoshop so the header doesn't overflow on mobile and the documentation button does not overlap with filter button.

JavaScript

• Tweakwise JS | Loading attribute for images has been improved. Eager loading is enabled for the first row of items to increase page-load speed/LCP.
• Tweakwise JS | Fixed a bug in Suggestions that prevented the form to be submitted without any result.
• Tweakwise JS | Fixed a bug with JS integrations that was caused by a specific version of an external library we use, causing certain parts to not work in older Safari browsers.

Plugin Studio

• Plugin Studio | The UX for the deployment has been slightly improved. We have fixed some usability issues with the deployment process and are now showing a list of last (max 20) versions that have been previously deployed for a quick overview. Each version is tagged with a timestamp of when the change has been made and you can now see which version is currently active. Yet it is not possible to go back to an older version.
• Plugin Studio | An information message was added to the 'Browser History Mode' in Tweakwise App > Plugin Studio > Search & Merchandising > Advanced to prevent users from just changing the configuration and breaking their implementations.
• Plugin Studio | It is now possible to set a value for a hover image on your Product Tile. This makes setting up a tile easier and does not require extra development for a hover image. Simply select an attribute with image URL. By default the switch between base and hover image is only triggered by moving your cursor over the image itself, but can be customized so that the whole tile triggers the effect. Adding a transition can also easily be done with setting a custom CSS property via the CSS editor on the Image Element.