10 posts tagged with "2025 October"

Party Categories created in the App 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.

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.

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.