Minor releases introduce new features and improvements. Check out what’s new!

API's

• Delivery API | We've added a nrofitems field to the suggestion products and suggestion products grouped endpoints. This field contains the total number of products found for the given search term.
• Delivery API | We've significantly improved the performance of the Filter Wizard endpoint (Guided Selling funnel type) in the Delivery API. The average response time has been cut by nearly 40%, dropping from ~180ms to ~110ms. This optimization delivers the most dramatic improvement for the slowest requests.
• Delivery API | The origin name field now contains the value 'Product' if the instance has placed specific products on the builder and has not configured item types. If a customer already had item types configured, then it would've already said 'Product'.
• Backend API | On our docs website the Backend Api endpoint for Patch filter template attribute was in the wrong place and we resolved this.
• Backend API | From now on, we do not set some default values for filter template attributes when using POST or PUT. Previously we set some default values in our API, but we now want all the settings to be explicitly defined by the users input.
• Backend API | Some API validation logic was updated regarding Filter template attributes, which now makes it possible to set multiple choice options for the attribute type 'link'.
• Backend API | The maximum allowed length for categorykey has been increased from 64 to 128 characters.
• Analytics API | New events were added to the Analytics API, namely: add-to-cart, add-to-wishlist, page-impressions.

Tweakwise App

• Tweakwise App | We've implemented a retry-logic for Google Analytics tasks. Sometimes the Google servers are not reachable when running these tasks, which then resulted in failed reports and task. With this improvement we implemented retry logic when trying to reach Google Analytics, that way we should be able to reduce the failures.
• Tweakwise App | Fixed a minor bug where dragging a content item within a builder would not show its "ghost" properly. And you're now able to open the page of an item or attribute in a new tab from the builder tile.
• Tweakwise App | All (new) data tables now display clear error message when a request fails, e.g. request time-out so users are not presented with non-relevant data in case they miss the error toast notification.
• Tweakwise App | Since upgrading to a new UI library recently, we got the option to easily add some transition animations to the UI for a more seamless experience - disclosures and dropdown menus/select boxes are now animated.
• Tweakwise App | In case an instance has image characteristic set up (attribute Use as 'Image') we now show the correct, potentially derived, image value in Builder Tiles, the Items module and item lookups (select boxes) across the App. Item edit (/create) page now shows no image in this case with another explanation for the characteristic. This is to prevent confusion when creating a new item/visual/.. in what the final, published image, is going to be.
• Tweakwise App | When an attribute has been selected (Use as) SKU, item records with empty SKU-values would not show up in the preview tab of rules. This issue was fixed, all items do show up in the preview tab no matter if SKU is empty or not.
• Tweakwise App | We have implemented some performance improvements for our search functionality in Tweakwise App > Catalog > Items, especially resulting in faster response times for instances with lots of items.
• Tweakwise App | Fixed an issue where items with special characters in their id (e.g. #) were not able to be opened. Also, when pressing enter with opened attribute selection dropdown (in items edit page, attributes tab) rows would be deleted via an auto-focus on the delete button. This has been solved as well.
• Tweakwise App | We added a new validation rule for One-way synonyms where a keyword can not appear in the list of terms too. Also potential API error messages while importing synonyms are displayed to users in notifications, instead of 'something went wrong'.
• Tweakwise App | Fixed a bug where clicking on 'Create new attribute' in some forms (e.g. Items edit form) would break the select component. Also fixed a small bug where labels for Radio group form components would not show up properly.
• Tweakwise App | Fixed a bug where showing Builder statistics would result in an error.
• Tweakwise App | In the publish process, we've updated our retry logic in order to reduce any potential publish failures during a small availability interruption in our Deployment API.

Demoshop

• Demoshop | The sort-by option is now preserved and not automatically removed when filtering. It will only be reverted to default when the 'remove all filters' is clicked.
• Demoshop | Fixed a bug where smart filter badges in front of respective facet values would not show up. We also changed Pins label from 'Content merchandising' to 'Product Pin'.

Tweakwise JS

• Tweakwise JS | We've fixed a problem where a part of the 'no results' page wasn't translated properly. Also some French translations were updated.
• Suggestions JS | For category search suggestions (e.g. 'T-Shirts in Clothing') we have added missing translations for the word 'in'. As with other translations it's possible to overwrite this in the config.
• Suggestions JS | There is now a new configurable option resultsButton.showResultsCount (boolean) that shows the number of results for a given suggestion. This feature is opt-in because an instance may have redirects configured for some terms and the amount of products may not match with what is on that redirected page.

Plugin Studio

• Plugin Studio | Fixed a bug in the Plugin Studio where a product tile sometimes wouldn't load.
• Plugin Studio | Added an 'auto initialization' toggle to the Search & Merchandising settings page to make it easy to prepare an instance for a manual configuration. In case you opt-in for manual configuration, disabling this setting will prevent Search & Merchandising from automatically initializing on page load.
• Plugin Studio | In the Tile Editor it is now possible to use string values (e.g. SKU) beginning with zero without losing these leading 0s after automatic conversion to a number.

Minor releases introduce new features and improvements for our Shopware plugin. Check out what’s new!

• SW-Tweakwise 5.1.0 | An new setting is introduced for the feed to respect Shopware settings to hide products after clearance. When enabled, products and variants will then be excluded from the feed after clearance. To achieve this, it is neccessary to set the option in the Tweakwise feed-settings in Shopware as well as in the product settings of Shopware. With this additional toggle in the Tweakwise feed-settings, we prevented this change to be breaking. This change was already released for the 4.x version of the plugin.
• SW-Tweakwise 4.5.1 | A small bugfix was done to make sure the sold out products are also excluded in the feed when you use the non-grouped approach.

📘

Reminder

The 4.x version of the plugin is compatible with Shopware v6.5 and v6.6. The 5.x version of the plugin is compatible with Shopware 6.7. Click this link to visit corresponding repository and update on Github.

We’ve expanded the Plugin Studio with two new configuration pages that make it easier to customize the behavior and some look & feel of your JavaScript implementation. You can now directly configure settings for the Suggestions and Recommendations modules; similar to how configuration has already been available for Search & Merchandising. These new pages allow you to fine-tune how Tweakwise interacts with your platform without modifying code, ensuring faster implementation and consistent results.

Suggestions JS settings Page

The Suggestions module settings page enables you to define how product and category suggestions behave and appear in your frontend, when implemented via Javascript. This page contains default settings for the implementation of the Suggestions module.

Although the contents of your suggestions are setup in Tweakwise App > Search > Suggestions, the way how the overlay behave is configured in Plugin Studio. You can set latency to control when results appear after typing, and choose the keyboard layout for search optimization. It also allows you to include or exclude products based on specific parameters, enable grouped products, and customize the product tile and language for display. These default settings determine the behavior and appearance of the Tweakwise Suggestions module and can still be overridden programmatically if needed.

Recommendations JS settings page

The Recommendations module settings page lets you manage how product recommendations are displayed and filtered on your platform. You can choose how recommendations are presented visually, with options for product tile design, language, and layout type per device (carousel or grid), limit results to specific categories, and include or exclude products based on custom parameters. Additionally, you can pass extra data to external components and specify a source name for better tracking. All these defaults can be overridden programmatically for advanced customization.

📘

All settings defined in the Plugin Studio act as defaults. You can still override them programmatically for advanced use cases, providing the flexibility needed for tailored implementations.

Minor releases introduce new features and improvements for our Magento plugins. Check out what’s new!

Magento2Tweakwise

• Magento2Tweakwise 8.7.1 | Added 'Show More/Less' functionality to color and size swatches for a cleaner display on product listings.
• Magento2Tweakwise 8.7.1 | Moved the itemclick tracking logic to ensure it functions correctly across all module configuration settings.
• Magento2Tweakwise 8.7.1 | Fixed a issue where special characters were not correctly handled in the in-filter search.
• Magento2Tweakwise 8.7.1 | Resolved a bug with category redirects when the category URL was changed.
• Magento2Tweakwise 8.7.1 | Fixed an issue where removed filters would sometimes remain in the URL.
• Magento2Tweakwise 8.7.1 | Corrected a bug where a category could be hidden if it was the only category returned.
• Magento2Tweakwise 8.7.1 | Fixed an issue preventing the page parameter from being correctly saved in the browser history on the first request.
• Magento2Tweakwise 8.7.1 | Added an alias to a function to maintain compatibility with Magento Commerce (Adobe Commerce).

Magento2TweakwiseExport

• Magento2TweakwiseExport 7.7.0 | Added a new setting to control how created/updated dates are exported. You can now select to export all dates (default), only the earliest date, or only the latest date.
• Magento2TweakwiseExport 7.7.0 | The Attribute Set is now included in the export data.
• Magento2TweakwiseExport 7.7.0 | Fixed an issue with incorrect prices being exported for grouped and bundle products when using special prices.
• Magento2TweakwiseExport 7.7.0 | Resolved a bug that resulted in the wrong store view being used in the category URLs in the export.

Magento2AttributeLanding 6.0.1

• Magento2AttributeLanding 6.0.3 | Fixed an SQL error that occurred when changing the category URL suffix setting for landing pages.

Magento2TweakwiseHyva

• Magento2TweakwiseHyva 4.4.0 | Added 'Show More/Less' functionality to color swatches, aligning with the core module update.
• Magento2TweakwiseHyva 4.4.0 | Moved the itemclick tracking logic to ensure it functions correctly across all module configuration settings.
• Magento2TweakwiseHyva 4.4.0 | Fixed an error that occurred when activating Personal Merchandising.
• Magento2TweakwiseHyva 4.4.0 | Resolved an error that would prevent default functionality from working correctly if an error occurred while selecting a filter.

As part of our ongoing evolution of the attribute model in Tweakwise, and to support the fact that you can now create new attributes directly in the App (rather than only via feed/external import), we are introducing a streamlined model: the previous distinction between Feed and External attribute types is removed, and both are now treated as one type: Standard. This change simplifies the internal logic and the user experience, and removes legacy distinctions that no longer reflect how attributes are created or managed.

With the ability to create attributes directly in the App (in addition to import), the old notion of Feed vs External no longer mapped cleanly to how customers actually set up attributes. Rather than adding a new type (such as 'App' or 'API'), we simplified logic by merging Feed and External into a Standard attribute. Many parts of our backend logic and UI had special cases (added complexity) for External attributes, which now has been removed. No action is required for users. All existing attributes are migrated behind the scenes: filters, facets and characteristics continue to work as before.

When you see Standard attribute, you now know it covers all attributes created via feed, external feed, API or App. This way the terminology is aligned across UI, API, documentation and internal logic, and lays the groundwork for further advancements without being tied to legacy types.

Minor releases introduce new features and improvements for our Magento plugins. Check out what’s new!

• Magento2Tweakwise 8.7.0 | Moved the analytics setting to the General section, as it’s not dependent on personal merchandising.
• Magento2Tweakwise 8.7.0 | The Suggestions endpoints will now be used as the default endpoint for search suggestions, instead of the old Autocomplete endpoints.
• Magento2Tweakwise 8.7.0 | Fixed an issue where the wrong URL was used for ALP pages when filtering by swatch.
• Magento2Tweakwise 8.7.0 | Resolved an issue where product images were missing when the Tweakwise API was not configured for images, ensuring the correct image is shown when grouped products are disabled.
• Magento2TweakwiseExport 7.6.1 | We’ve reverted some poor performing changes to the export.
• Magento2TweakwiseExport 7.6.1 | PHP 8.4 is fully supported, so you can run the latest version with confidence.
• Magento2TweakwiseExport 7.6.1 | Resolved an issue in grouped export where the wrong group code was exported for certain products.
• Magento2TweakwiseExport 7.6.1 | Fixed a type error.

We’ve added some powerful new features to the Item Management module, making it easier than ever to organize and control your catalog. With these latest improvements, you can now not only search and filter items more precisely, but also control their publication status and handle bulk updates with ease. Whether you want to trace back changes across systems, work with draft or inactive items, or import and export larger sets of data, this release makes managing your catalog more flexible and efficient than ever before.

1. Filter by "Last Updated By": You can now filter items based on the system that last updated them: App, API, or Feed. This makes it much easier to track changes and trace back how specific items ended up in your catalog. The filter also works seamlessly with the existing Type filter, allowing you to combine filters for even more precise results.
2. Item statuses: Items can now be marked as active or inactive. This means that you can work on draft or concept items without publishing them live right away. Perfect for temporarily disabling products from your shop or keeping visuals as work-in-progress in your catalog. The status is clearly indicated not only in the Items module, but also throughout the platform, for example when pinning an item in the Builder.
3. Import & Export: We now offer the ability to import and export (small chunks of) items directly from the Items module too. This feature is designed for bulk updating and inserting items and attributes, which is especially useful when working with visuals. The process is based on simple .csv files and comes with limits on file size and page size to keep things running smoothly. Import and export are meant for updating and adding records, not for deleting them. For that, you should continue using the module itself.

Minor releases introduce new features and improvements. Check out what’s new!

API's

• Backend API | Item status (active/disabled) is now fully supported across all endpoints. You can read, create, update, and filter items by their status consistently via the API.
• Backend API | We added the option to filter Get All Items on 'updatedBy' (Feed/Api/App).
• Backend API | Fixed a bug where it was not possible to add an item with a NULL value in attributes.
• Backend API | A new endpoint was released in the Backend API for patching filter template attributes. With a patch you only have to provide the information you want to update.
• Backend API | Support was added for filtering on multiple product sources for items.
• Delivery API | You can now reliably filter on values that contain special characters like < and >.

Tweakwise App

• Tweakwise App | We've seen people struggling using the app when working with different instances. In the renewed parts of the app we are able to detect this better. To prevent that we're forcing an instance, a modal is shown that lets you decide what you want to do, continue or move to the other instance.
• Tweakwise App | Fixed a bug in the suggestions module where users got stuck and validation errors were not visible.
• Tweakwise App | Error feedback has been improved in the attribute modal in Tweakwise App > Catalog > Items when configuring an attribute as 'Use as' characteristic.
• Tweakwise App | The attribute lister page was quite messy when titles like URL-name and API-name were very long. We added these fields as columns to make it more predictable in the width. As the table might become wider, we implemented horizontal sticky behavior. In case there is no room to show everything a scrollbar is shown, the main fields are sticked to the left and right to have all the context always available.
• Tweakwise App | We added a validation summary to all forms in our new Item Management feature to give way better feedback after a submit action. Sometimes it was not fully clear when a form stalls on errors. Now most of the errors are generic an predictable.
• Tweakwise App | We added a useful 'Last Updated By' filter in Tweakwise App > Catalog > Items as part of the new Item Management feature, so it becomes way easier to find your manual created/updated items.
• Tweakwise App | Disabled items in Pins are now handled properly. They remain visible during pin configuration but are clearly marked as inactive. At publish time, disabled items are excluded from outputs, and once re-enabled, they automatically reappear in the curated pins.
• Tweakwise App | We fixed a bug where the context menu to edit an External Data Component in the Builder would not show up.
• Tweakwise App | A fix was made for Tweakwise App > Connectivity > Tasks in which your selected language reverted back to English on page refresh while running a task/job. Now it keeps using the language you selected.
• Tweakwise App | We extended the timeout from 30 minutes to 60 minutes in 'the Backup Database step' in the publish, which should solve some timeout issues at certain customers.
• Tweakwise App | We introduced tracking of attribute ownership. We now record which service (Feed Import, External Attribute Import, GA4 task, or Backend API, etc.) last modified an attribute’s metadata. This helps protect items and attributes created manually in the App from being deleted during feed imports.
• Tweakwise App | When a task is skipped due to concurrency, the log message now includes the blocking task’s ID (and type/name if available) for easier troubleshooting.
• Tweakwise App | Tweakwise App has been extended with a settings module, which will be the location for setting up instance specific 'admin' settings.
• Tweakwise App | On some attributes components throughout Tweakwise App we added an instant link to the selected attribute, making it easier to navigate to relevant parts of your catalog configuration.

Insights

• Search Word Analysis Report | We added an option to the Search Word Analysis Report (enabled by default) which results in 'showing search words that never returned results' only. Besides that, we changed the chart on the detail view page to show with(out) results and redirects.
• E-commerce Report | We added a filter (always on, not interactive) on no-results to only show results that never returned results; we changed the Click Distribution data source to make it filterable with date slicer and fixed a small bug regarding the date slicer in case GA4 data was missing while the report was enabled.

Plugin Studio

• Plugin Studio | Plugin Studio had a small issue that changed the tile configuration when going into the settings of a module and back.

Minor releases introduce new features and improvements for our Shopware plugin. Check out what’s new!

• SW-Tweakwise 5.0.4 | Fixed an issue for cross-sells based on last added product to the shopping cart which doesn't have a product number, like promotions.
• SW-Tweakwise 5.0.3 | Fixed issue in compiled JavaScript.
• SW-Tweakwise 5.0.2 | The JavaScript plugins for add-to-cart and add-to-favorites are now working correctly in frontend again.
• SW-Tweakwise 5.0.1 | It is now possible again to choose Tweakwise as the layout type of product listings. Some translations are fixed for the Tweakwise CMS elements group.
• SW-Tweakwise 5.0.1 | Fixed a small bug which ensures the Tweakwise searchbar is shown when choosing Plugin Studio as the way of integration.
• SW-Tweakwise 4.5.0 | An new setting is introduced for the feed to respect Shopware settings to hide products after clearance. When enabled, products and variants will then be excluded from the feed after clearance. To achieve this, it is neccessary to set the option in the Tweakwise feed-settings in Shopware as well as in the product settings of Shopware. With this additional toggle in the Tweakwise feed-settings, we prevented this change to be breaking.
• SW-Tweakwise 4.4.2 | Fixed an issue for cross-sells based on last added product to the shopping cart which doesn't have a product number, like promotions.
• SW-Tweakwise 4.4.1 | Showing sibling categories in category filters is now working correctly in Shopware 6.5 installations as well

📘

Reminder

The 4.x version of the plugin is compatible with Shopware v6.5 and v6.6. The 5.x version of the plugin is compatible with Shopware 6.7. Click this link to visit corresponding repository and update on Github.

We’ve introduced a big addition to the Items module: Item Management! With this release, you can now create, edit, delete, and copy items in Tweakwise App > Catalog > Items without the need of a an XML feed or Backend API. This gives you control over your items, directly in Tweakwise. This allows you to all sorts of neat stuff like quickly/temporarily edit a product attribute, for example the stock of a product (so you don't have to wait a full import cycle); or create & manage visuals without a complicated workflow.

The id will remain the unique identifier for an item. When creating an item, we will prefill it with a random value. New items created in the module persist until manually deleted, or adopted by the XML feed import. Validation is in place, for example to check if an item already exists. In the attributes tab you can assign attributes and (multiple) attribute values to the item. If an attribute or attribute value does not exist, it can be created on the spot. If an attribute or its value does not exist, it can be created without switching workflows, as multiple attribute values can be assigned simultaneously. In the categories tab you can even assign an existing category (or multiple) to the item you're creating or modifying. Only existing categories can be connected, as category-management is not yet available via Tweakwise App.

Good to know:

• Feed imports & Backend API still remain the primary way of getting data into Tweakwise.
• Feed imports & Backend API operations have priority over any manually created/edited items. If you edit an item that is also contained in the feed, it will be overwritten in the next import chain. If you delete an item that is also in the feed, the item will be added in the next import chain.
• Some fields in the general tab are characteristics, like image. If a derived attribute is set as characteristic for this field and it does not use the default fields, make sure that derived attribute will handle your manual case correctly.
• It is not possible to create categories through this module, that should still be done using the regular workflow.