Welcome to Intershop Commerce Management 14.
This Public Release Note contains information about the latest features of Intershop Commerce Management. In addition, it serves as a quick reference for the latest documentation.
With this release, security and stability have been further improved through technology updates. Furthermore, the CMS Management REST API (back office) has been extended to support customer segments in the Design View in the Intershop Administration Portal (IAP).
Please note that the product syndication feature is now deprecated. You can continue to use product sharing.
Refer to our feature list for more details about the new release:
Refer to the following page for information about system requirements:
This section lists the main entry points for ICM 14 project development.
For a list of all available ICM 14 documents, use the ICM 14 filter in our Knowledge Base.
For migrations to ICM 14 version, refer to:
Overview - Customization - Development Process - ICM 11+
Concept - Intershop Commerce Platform DevOps - CI/CD Development Process
Bug fixes for each release can be found in Product Releases | Fixed Issues.
New features:
A new REST API endpoint for managing and querying preview context in ICM is now available. It enables the Preview feature for the IAP Design View. See Reference - Preview Context Management REST API 1.0.0 (Beta).
Media asset upload: Content editors can now upload multiple images and other media files at once in the Content Upload section in ICM. See Commerce Management Help | Managing Content Files.
A new configuration option is now available to set the default assignment priority for CMS component assignments to Lowest (configurable as a global or channel preference). See Guide - 14.5.0 - Configure Pagelet Assignment Default Position.
A new REST API endpoint for assigning a product to a catalog category via the Product and Catalog Management API is now available. See Reference - Product and Catalog Management REST API 1.6.0.
Updates and improvements:
Basket merge now supports an optional bulk processing mode for improved performance when merging large baskets. See Guide - 14.5.0 - Migrate REST Endpoint for Basket Merge.
OCI and cXML Punchout users are no longer displayed in the user list of a customer in Intershop Commerce Management. This change avoids confusion for e-commerce managers caused by duplicate display names and invalid e-mail addresses.
The order submission service now retries on transient failures. Immediate export on order creation is no longer blocking; a slow or unavailable target system no longer delays the order creation response.
Advanced order search: The distinction between "Received (not verified)" and "Received (verified)" withdrawal statuses has been simplified to a single "Received" status in ICM and the PWA.
The STAGING$grant_live_user_privs stored procedure now grants UPDATE permission on the ReplicationTask table, preventing live/edit replication failures due to missing permissions.
Many deprecated com.intershop.beehive.core.capi.log.Logger method callers have been replaced with their non-deprecated equivalents. The deprecated Logger methods are now marked “deprecated for removal”. Migrating project code to use the non-deprecated methods is recommended. Migration documentation can be found in the respective Javadoc of the deprecated method.
The AddProductDataFeedPreparer, which allows creating product data feeds with DBPrepare, now supports using IDs, SKUs, and the application URL identifier instead of database object UUIDs, which may not be available during DBPrepare yet. For details, see Support Article - Creating and Updating Product Data Feed Configurations via DBPrepare.
Resolved issues:
Same-day delivery is now possible. Setting the desired delivery date to “today” was incorrectly rejected when MinimumDeliveryDays=0. The validation now only checks that the desired date is not before the current day (time-independent). All configurations that are currently “0” will be set to “1” automatically during DBprepare to preserve the current behavior during checkout. If a project allows same-day delivery, set the value to “0”.
Payment instruments that are not eligible for use as the preferred payment method can no longer be set as such. The REST client does not need to filter them.
A NullPointerException occurred when sending a PUT /customers/{id} request with an empty preferredPaymentInstrument object (no ID field). An empty object is now correctly treated as a deletion intent.
For other fixes, see Product Releases | Fixed Issues.
Fixed time-zone display in e-mails: The date/time is now displayed according to the application time zone. For details, see Guide - 14.4.4 - Date Formatting Uses Application Default Timezone or work item 119195.
A new property, intershop.urlrewrite.exclude.standard.configuration, allows projects to disable the standard URL rewrite rules and rely exclusively on custom configurations instead. The default value is false, which preserves the existing behavior. Setting it to true prevents the standard rules from being loaded.
For details, see Concept - URL Rewriting | Using Custom URL Rewrite Rules Only or ticket 118876.
Improved display of scheduled jobs in the SMC: Jobs whose next run time has passed but have not yet run can now be identified more easily and filtered by their operating state "Due".
Updated io.netty:netty-resolver to version 4.1.135.Final to fix the vulnerabilities CVE-2026-47691 and CVE-2026-45674.
The order withdrawal functionality introduced with 14.3 was extended:
The order delivery date can now be added manually in Intershop Commerce Management.
The order list in ICM allows to filter by order withdrawal status in the advanced search. See Concept - Withdrawal.
The storefront Order REST API was extended. It now returns order withdrawal information and has a query parameter which allows to filter by “withdrawal”. See Reference - Order REST API 1.10.0.
A minimum set of non-sensitive payment service information is now stored in plain text, including the service name, service ID, and the short name of the payment account (account identifier). This information remains usable even if the payment service is no longer available. This applies only for newly created orders. Legacy orders must be handled separately, see Guide - 14.4.0 - Preparing Historical Payment Data Before Deleting a Payment Service.
Improved cache behavior for product reviews. List requests that only contain the current user's own review and detail requests for an own review are no longer cached. See Guide - 14.4.0 - Changed Caching Behavior of Rating & Review REST API and Reference - Rating and Review REST API 1.2.0.
Updates and improvements:
ICM can now automatically create product feed JSON files that comply with the Agentic Commerce Protocol similar to sitemap.xml files. For details, see Concept - Agentic Commerce Protocol - Product Feed.
The Media Assets Management REST API has been extended and now supports upload, deletion, and simple search. See Reference - Media Assets Management REST API 1.2.0 (Beta).
ICM now provides a feature set to enable shops to be compliant with EU Directive (EU) 2023/2673 (providing an easy-to-use digital order withdrawal capability for B2C customers). It consists of a set of REST APIs, new persistent data with import capability, as well as a back office display and e-mail template. For details, see Concept - Withdrawal and Reference - Withdrawal REST API 1.0.0.
It corresponds to a two-step shop frontend process provided with PWA 11.1.0.
As part of the previously described feature set, a new order data field has been introduced: the delivery date. It can now be imported via the order status XML import. It is available through the storefront Order REST API. It is also visible in the order detail view in Intershop Commerce Management. For further details, see Reference - Order Fulfillment Status Import.
Technology changes:
OAuth support for Microsoft 365 SMTP service: A new managed service implementation provides the capability to send mails via Microsoft 365 using OAuth authentication instead of Basic Auth. See Concept - Mail Services.
ICM supports the Open Telemetry Agent, see GitHub: intershop/helm-charts - values.yaml Attributes in Section openTelemetry.
Several libraries have been updated. For details see Guide - 14.3.0 - Migration Library Updates.
Known issue:
A warning is logged, reporting a parsing failure ("java.base/java.net.URI$Parser.fail" with regard to "${FileNameFromJavaName(basePkg)}${slash()}${name}.java"). This has no effect on the app server. Only a warning message is produced. For details, see ticket 116940.
The following back office REST API improvements have been made:
The Media Assets REST API now also supports shared content. For details, see Guide - 14.2.3 - Content Sharing Toggles in Media Assets Management REST API.
The CMS Management REST API has been enhanced to help content editors work more efficiently.
Several storefront REST API improvements are included as well, for example:
The wishlist links now include additional information (public, shared, itemsCount, creationDate) that can be used to display the list of all wishlists/order templates without the need to fetch the item details. This improves performance and therefore end user experience. See Reference - Wishlist/Order Template REST API 1.4.0.
For an overview of all REST API updates, see Reference - Intershop Commerce Management 14 REST API.
Staging tasks can fail under certain circumstances. It is now possible to retry such tasks.
You can now invalidate the icm-as page cache during deployment, allowing for targeted cache refreshes only when the executionMarker changes and, optionally, limited to specific sites to avoid unnecessary invalidations during application server restarts. For details, see GitHub: intershop/helm-charts | Attributes in Section pageCacheInvalidation.
The pre-integrated custom fields for basket and order feature has been enhanced with e-mail support. All standard e-mail templates concerning orders now contain these fields, which are displayed depending on the configuration. See Concept - Pre-Integrated Custom Fields.
For further compatible changes, see Overview - ICM 14 Migration.
Product list performance improvement toggles
Two properties have been added that you can configure to limit the data retrieved and displayed in the back office product detail view to improve performance.
See Guide - 14.0.2 - Toggles for Product List Performance Improvement in the Back Office UI for details.
The following updates of back office REST APIs improve the management and integration of customer segments and content components:
The Customer Segment Management REST API has been introduced. Now, a list of all valid customer segments can be provided to back office applications.
The CMS Management REST API has been extended. It is now possible to add customer segment relations to content components.
For an overview of all available REST APIs valid for ICM 14, see Reference - Intershop Commerce Management 14 REST API.
Technology Changes:
Tomcat has been updated from version 10 to 11.
Slf4J update to version 2 incl. Logback update.
Several other libraries have been updated.
For details, see Guide - 14.0.1 - Migration Library Updates.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Website, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.