Party Categories created in the App (Tryton client) were not retrievable or editable via the API because the App did not expose the fields import-key and origin. These fields can now be set manually.

When navigating through variants on the PDP, non-available options are now also displayed. These are shown as crossed out but remain clickable, ensuring that all variants are always visible and accessible. This makes it easy to see which combinations are orderable or not, and to offer alternatives on the PDP if desired.

In the production environment of the CMS, the ‘go to page’ dropdown previously also displayed test domains. This has been adjusted: from now on, only production domains are shown, making it clearer and more user-friendly.

To further optimize the visibility of your online channel, we have extended the hreflang tags in the sitemap. Previously, only the language code was included (for example, nl or fr), but now the country code is also added (for example, nl-BE or fr-BE).

When completing a payment via Stripe, the PaymentIntent API is now used instead of the deprecated redirect_status parameter. The payment status is retrieved directly from Stripe.

Do you want to display the lowest price as a starting-from price on the product list page (based on the highest tier)? This was already possible in CloudSuite, but only for sales units. For those working with price units – for example, a box of 24 items where the price is calculated per piece – this was not yet available.

The CloudSuite API has been updated so that a Crimson HTTP 500 Internal Server Error now always returns a JSON response with a clear error message and a Sentry ID.

To make the ordering process easier, we have improved the order of product filters on the PDP. Previously, the filter order could differ between category pages and, for example, tag or brand pages, which could be confusing during ordering.

Until now, a quotation accepted in the webshop had to be manually converted into an order by the user through the checkout. A new configuration option has now been added where the integration takes the lead: after acceptance in the webshop, the option to manually convert the quotation disappears.

The logic for variant grouping on the PLP has been adjusted so that an inactive product is no longer selected as the main item.

Together with our partner DeliveryMatch, we are developing a new integration between our checkout and their Transport Management System (TMS). The first version (MVP) makes it possible to display various carriers (delivery options) in the checkout as soon as a customer enters their delivery address.

Exports could contain empty lines when a main record included multiple subrecords, for example when exporting products within a tree or an order. An option has now been added to remove these empty lines, making exports clearer and easier to read.

When a customer changes the delivery method – for example from home delivery to in-store pickup – the delivery date may also change. In some cases, an earlier date becomes available.

We have significantly enhanced our monitoring. This gives us deeper insights into each customer’s web traffic and allows us to detect anomalies or unusual patterns more quickly, such as unwanted bots and crawlers.

It is now possible to define the order of sorting options on the Product Listing Page (PLP). For example, you can place Sort by price directly under Popularity if this is the option most frequently used by your customers.

In the OCI form, you can now define which product ID is used: EAN, product key, or product code. Previously, the product code was always used by default, but this is now configurable per OCI user.

For enterprise domains, the country selector can now be skipped. Visitors are automatically redirected to the correct shop (e.g., EU or US) based on their IP address. If a country cannot be recognized, the default shop will be shown with the option to manually select a different shop or language.

Calculated levies and surcharges (such as Waste Management Contribution or Single Use Plastic) are now also clearly displayed in the order overview in My Account. This gives customers a complete and transparent overview of all charges in their order.

You can now control whether prices in the shopping cart are calculated based on the order date or the delivery date. This functionality only applies when the shopping cart is grouped by delivery date. Until now, when using delivery dates per cart line, the delivery date was always used to apply the correct price list.

The date that the shopping basket was last modified is now stored. This is useful for, among other things, abandoned baskets. The modification date is automatically updated with every change.

When you hover over a product with your mouse (for example, in the search results), a popover appears. This popover now includes a convenient link to future stock information.

In a cXML punchout to a procurement system, the product EAN was always used by default. Since not all CloudSuite customers can work with an EAN number, this is now configurable.

In the customer details, the Chamber of Commerce number has been moved from the General tab to the eCommerce tab.

Together with our partner DeliveryMatch, we are developing a new integration between our checkout and their Transport Management System (TMS). The first version (MVP) makes it possible to display various carriers (delivery options) in the checkout as soon as a customer enters their delivery address.

In the CloudSuite App, a new option has been added under the Action button: " Open Help". This button opens the correct page in the documentation for the section you are currently working on.

When an internal user is linked to multiple customers via a customer group, the system now only displays the orders of the customer you are logged in as.

Users now always see all delivery addresses linked to the customer in My Account, regardless of whether a specific address is assigned to their account.

You can now search by specific attribute values, such as a product's country of origin. For example, a search for "Spain" will immediately return all Spanish products. This improvement makes it easier for customers to find what they are looking for quickly.

We have expanded the Template Product functionality in the PIM system to support more content fields. This allows you to provide richer product data and ensure consistency across all related products.

The Mollie integration has been extended with support for Klarna: Pay later.

Soon, we’ll introduce a new overview page where you can instantly see which powerful modules and features are available in the CloudSuite platform. For each feature, you’ll see whether it’s already active in your environment and what additional possibilities you can unlock to further enhance your eCommerce setup.

As of this release, sales and service staff can not only view but also directly edit the shopping carts of end users. This opens up new opportunities to provide personalized support when placing orders—both online and offline.

In addition to the existing backorder overview in ‘My Account’, a new view is now available where products are sorted by expected delivery date instead of order date. This better supports situations where the arrival date of products is more relevant than the order date.

Starting with this release, the order message via the REST API also includes product codes (in addition to the import key/origin), making integrations with ERP systems easier and more efficient to set up.