Composable Storefront Release Notes

These release notes include updates to Progressive Web App (PWA) Kit and Managed Runtime.

The latest PWA Kit release notes are published on the releases page on GitHub before they're published here. To stay informed about new PWA Kit releases, subscribe to GitHub notifications for releases. See Configuring your watch settings.
  • Release notes may be published before the relevant Github packages are updated. The release notes identify any applicable package version that a feature is available in.
  • For the general B2C Commerce release notes, see Salesforce Help.

Improve stability and performance for hybrid storefronts and ensure optimal shopper experience. See Hybrid Stability Upgrade for PWA Kit Version 3.8.0 or Hybrid Stability Upgrade for PWA Kit Version 2.x.

Personalization with Shopper Context is now pre-integrated into Retail React App version 5.0.0 or later. Support personalized shopping experiences and reduce implementation costs. With Shopper Context, you can use features such as tailored promotions, pricing, and product recommendations to increase conversion and shopper loyalty. See Personalize with Shopper Context.

Going even more global! To optimize performance by co-locating with backend instances in Hyperforce regions, you can now deploy your Managed Runtime environments to these regions:

  • sa-east-1 - South America (São Paulo)
  • eu-central-2 - EU (Zurich)
  • eu-south-1 - EU (Milan)
  • ap-southeast-3 - Asia Pacific (Jakarta)
  • me-central-1 - Middle East (United Arab Emirates)
  • il-central-1 - Israel (Tel Aviv)

Previously, you could view logs in Log Center for only production environments associated with primary instance group (PIG) instances. Now you can view logs for secondary instance group (SIG) and on-demand sandbox (ODS) instances. These new logs count towards log volume limits.

This feature is generally available from PWA Kit version 3.7. With the __server_timing query parameter you can monitor the performance of your PWA Kit site to support your optimization efforts. The parameter provides access to the Server-Timing HTTP header and logs, that offer metrics about parts of the server-side rendering process such as route matching, component loading, and fetch strategies. Performance metrics logs are also available in Log Center. See __server_timing.

Retail React App version 4.0 consumes the new versions of Commerce SDK React and Commerce SDK Isomorphic. These SDKs now satisfy Shopper Login and API Access (SLAS) guidance to pass channel_id as an argument when retrieving guest access tokens. See Guest Tokens.

Store locator is generally available with Retail React App version 4.0 or later and Commerce SDK React version 2.0.1 or later. With our store locator, your shoppers can find nearby storefront locations based on their ZIP code, city, and more. Easily extend your store information in Business Manager to customize the displayed location metadata on your site. See Boost In-Store Sales with Store Locator.

Product bundles are generally available with Retail React App version 4.0 or later and Commerce SDK React version 2.0.1 or later. Use product bundles to group multiple related products into one orderable product for shopper convenience and personalization. Shoppers can update bundle variants and quantities directly in their cart. For example, an online sports apparel store can offer a "Runner's Bundle" so shoppers can select shoe size, apparel size, and fitness tracker model directly in their cart. Product bundles can help you to reduce cart abandonment and improve inventory management. See Product Bundles.

Restrict access to a Managed Runtime environment to traffic coming from eCDN. Set a shared access control header across eCDN and environment to ensure that shoppers, bots, and crawlers don’t access your environment directly.

See the updated Launch Your Storefront Guide and the new upsertOriginHeaderModification API for details on how to configure Managed Runtime and eCDN to lock down your environment.

Quickly find logs generated by your PWA Kit site by searching on namespaces added as prefixes to logs in Log Center. The namespace pinpoints the specific part of your codebase where an error occurred, helping you to focus your troubleshooting efforts. See Debug Using Log Center.

Restrict access to your Managed Runtime environment to traffic coming from your third-party content delivery network (CDN). Set a shared access control header across your CDN and environment to ensure that shoppers, bots, and crawlers don’t access your environment directly.

See Access Control Headers and the projects_target_access_control_header_create API to learn how you can lock down your environment.

Drive conversion and shopper engagement and reduce implementation costs with our greatly improved product tiles available in the PWA Kit Retail React App. Product tiles now feature:

  • Promo callouts
  • Strike-through pricing
  • Product tile swatches for variant selection
  • Product badges
  • Use of the productSearch API with expansions, which offers improved performance over the combination of the productSearch and getProduct(s) APIs

Easily create a sitemap in Business Manager (BM) for your headless or PWA Kit storefront built on B2C Commerce. Sitemaps provide search crawlers with instructions on the pages to index and site hierarchy and they help to improve SEO ranking. See Improve SEO with a Sitemap.

PWA Kit now supports the collection of Active Data order metrics. Use this collection to understand customer behavior and optimize your merchandising and segmentation strategy. See Active Data.

Use Runtime Admin to manage environment variables. This feature is available as an alternative to managing environment variables by using the Managed Runtime API. Environment variables allow you to add variables into the application process running in an environment, without having to make code changes. See Environment Variables.

This feature is now generally available.

Troubleshoot errors in your site built with PWA Kit by using Log Center:

  • Search and filter many logs. Check historical logs.
  • Access a single user interface to view logs from Managed Runtime (MRT) and your B2C Commerce instance. Connect what's happening in your MRT environment with what's going on in your B2C Commerce instance.
  • Easily see MRT logs without using a CLI.

See Debug Using Log Center.

This feature is generally available from PWA Kit version 3.5. Check the releases page on GitHub for the latest available version of PWA Kit.

Enable a Shopper Login and API Access Service (SLAS) private client in your PWA Kit site so you can support these features with reduced implementation time:

  • Passwordless login
  • Password reset
  • Faster page load times

See Use a SLAS Private Client.

Get reduced page load times after redeploying your bundles. These Content Delivery Network (CDN) enhancements improve app performance:

  • HTTP/3 — We automatically use the HTTP/3 protocol for all browsers and clients that support it. HTTP/3 improves performance, especially for shoppers who use network-constrained devices, such as mobile.
  • Cross-region CDN caching — We automatically use cached responses across regions to improve the cache hit ratio and performance for sites with a global audience.
  • More CDN regions — We added more regions to the CDN, resulting in faster response times and shorter network hops if you use a stacked CDN setup.

Use Runtime Admin to enable server-side cookies. This feature is available as an alternative to enabling server-side cookies by using the Managed Runtime API. Using server-side cookies helps you enhance privacy and security and supports more tailored personalization and marketing. See Personalize with Cookies.

Use Runtime Admin to enable source maps. This feature is available as an alternative to enabling source maps by using the Managed Runtime API. Source maps are designed to greatly improve the development and debugging experience by enhancing error stack readability. See Debug Using Source Maps.

Use a third-party content management system (CMS) with Storefront Preview. For example, if you have a holiday sale banner managed by your CMS, use Storefront Preview to see how the banner will appear on your site during your specified time period. See Storefront Preview.

Preview how your Progressive Web App (PWA) Kit site will look based on one or more customer group IDs. For example, preview your site as it would appear to shoppers who get an employee discount. See Preview Your Storefront.

Projects can now deploy with Node 20! PWA Kit projects will need to upgrade to the latest 3.4.x version and follow the instructions in Upgrade Node Version.

Customers in Japan can now run their environment in the Osaka region, in addition to the existing Tokyo region. Your region can be changed via Environment Settings.

Source maps are now available in Managed Runtime. This feature is designed to greatly improve the development and debugging experience by enhancing error stack readability. Source Maps can be generated starting in PWA Kit 3.4.x, and can be enabled by toggling the enable_source_maps environment setting. See Debug Using Source Maps.

Use Active Data in your PWA Kit site to observe product performance metrics and set automated rules for merchandising. See Active Data.

Use the Storefront Preview feature to see how your PWA Kit site will look in different contexts such as specified source code, customer groups, or a particular date or time. For example, preview your site changes in a staging environment before deploying them to production. See Storefront Preview.

When you create an environment in Runtime Admin, you can now select a Commerce Cloud instance and sites to connect to the environment. This allows for deeper integration between your Managed Runtime environments and the Commerce Cloud platform. You can also use new Managed Runtime API endpoints to manage and track your environments’ connections to Commerce Cloud instances. For more information, see this documentation:

For release notes published before October 2023, see: