Configured Commerce STS release highlights
1 min
Subscribe to updates on this page using the notification and RSS feed options.
- Accessible Admin Console reordering – Reorder any list in the Admin Console using just the keyboard, with screen-reader announcements that confirm each move, so merchandising and operations teams can work with controls that meet modern accessibility standards. Keyboard reordering and translated announcements now cover product images, list columns, export columns, promotion rule groups, multi-value settings, user roles, and product relationships.
- Unified multilingual catalog URLs – Gives multilingual sites one clean, consistent URL structure for cleaner search-engine indexing and simpler navigation, with no language prefix on every root path and no duplicate language tokens in brand URLs. Enable the new Use Home Page Url Segment Across Catalog Pages setting (Catalog → URL Mapping) to extend the home page URL segment across catalog, product, brand, and search pages. See Translate URLsTranslate URLs. (Enabled for new websites; existing websites keep their current behavior.)
- Self-service .well-known file hosting – Cuts verification-file publishing from a developer sprint cycle to a direct upload, removing deployment bottlenecks for mobile app and third-party service setup. Implementers upload app-site association, domain verification, and mobile link verification files directly to /userfiles/_system/.well-known, and Spire serves them at /.well-known/<filename> without requiring a code change or a production release. See Media libraryMedia library.
- Content Security Policy (CSP) controls – Lets security teams test stricter browser policies safely in observation mode before enforcing them, without risking storefront downtime or broken checkout flows. The storefront and Admin Console now have separate, configurable policies, each with a report-only mode (Content-Security-Policy-Report-Only and Admin Content-Security-Policy-Report-Only) that surfaces blocked scripts and connections before strict rules apply. See Set security headersSet security headers.
- Search v3 reliability improvements – Protect the shopper search experience during outages and high-demand periods. If Commerce Search v3 ever experiences downtime, storefront search now automatically fails over to Elasticsearch, so shoppers can keep finding and buying products without requiring emergency manual intervention from your team (see Rate limitsRate limits for more details). Optimizely has also improved how the Search Service manages its internal resources, keeping memory usage and performance stable during sustained, high-volume shopping periods. This reduces the risk of slowdowns as demand grows. see Commerce Search v3Commerce Search v3.
- Spreedly Checkout SDK migration – Stay ahead of Spreedly's iFrame retirement with a seamless, zero-touch migration. Payment Service card capture has transitioned from Spreedly's legacy iFrame to the Spreedly Web Checkout SDK. Configured Commerce instances using the Payment Service must upgrade to version 5.2.2609+ by December 31, 2026, ahead of Spreedly's retirement of the legacy iFrame in Q1 2027. All existing merchant and gateway configurations, including 3DS/SCA setup, carry over automatically, no manual reconfiguration required.
Important Configured Commerce instances that use the Payment Service must upgrade to version 5.2.2609+ by December 31, 2026 (end of Q4 2026). If you do not upgrade by this date, card capture and payment processing may stop working.
See [NOTICE] Payment Service customers must upgrade to 5.2.2609for more details.