Salesforce B2C Commerce Cloud 22.8

A new month means new candy for us in Salesforce B2C Commerce Cloud. But what will we find in that jar this month? Let us find out! 

Are you interested in last month’s release notes? Click here! Or are you looking for the official release notes?


A few changes are happening in “terms” used in Salesforce B2C Commerce Cloud:

  • master product/variation master: base product
  • master catalog/master product catalog: product catalog
  • master and child items: main items and secondary items
  • master document: main document

This update is in line with the inclusive language within the Salesforce ecosystem. Expect these changes to take effect in all communication slowly and inside the documentation!


Holiday Readiness Preparations

Summer has just begun, but Salesforce is already underway to ensure all merchant instances can handle the holiday period!

But nothing major in this release, just some database optimizations. Sign up for this Salesforce webinar series to prepare for the holidays!

New Sandbox clusters

With the steady growth of on-demand sandbox usage, Salesforce will add new clusters to ensure enough resources are available to support it.

This change will affect partner sandboxes as they will be moved to US03. Currently, this is US01.

The usage of the on-demand sandbox has been steadily growing. To meet the demand and while maintaining the availability and performance of the on-demand sandbox, new ODS clusters have been added to provide more resources overall to all ODS.

A change coming to this community is that the ODS you currently use will be moved to a new and dedicated cluster: US03. Salesforce engineers will make the move itself in batches. No actions are required from you, and your sandboxes should still work as they are after the move. The expected move is in batches and will be done in August on Friday evenings and Saturdays. More details will be posted here in the following days.

All new realms provisioned after this announcement (including realm zyfo and zyft that are being provisioned) will be on the new cluster US03. If your realms fall into this category, please note the following:

New Sandbox maintenance times

Everyone using the On-demand Sandboxes has known that maintenance always happens on a weekday (Thursday mornings for me). This has annoyed many developers, depending on the time zone. 

And for a good reason, it is in the middle of the week and during working hours for many. When you are ready to start your day and work on a ticket or a deadline is breathing in your neck, the last thing you need is your sandbox being unavailable!

Good news: The weekly maintenance is moved to Saturday between 02:00 and 08:00 UTC!

HTTPClient.send quota limit doubled

great power responsibility

Good news, but with a warning, for many developers who have done real-time integrations! The quote limit of external API calls you can do in a single request has doubled, going from 8 to 16.

But with great power comes great responsibility. Even though you can do more API calls now, it is not a good idea to take it to the limit.

As always, when implementing third-party integrations, keep in mind performance. Ask the question: “Does this really have to happen in real-time? Or can I do this async in a job?”

Any delay the third-party introduces will impact the storefront performance and user experience!

Salesforce Payment Information in Customer Import

The customer import (customer.xsd) has added additional site-specific data about payments.

Note: This information points to where the data is, not the actual data.

					<xsd:element name="customer-payment-profiles" type="complexType.CustomerPaymentProfiles" minOccurs="0" maxOccurs="1">
            <xsd:documentation>This element is for use with Salesforce Payments to track references of customer profiles between systems.</xsd:documentation>
					    <xsd:complexType name="complexType.CustomerPaymentProfiles" mixed="false">
            <xsd:element name="customer-payment-profile" type="complexType.CustomerPaymentProfile" minOccurs="0" maxOccurs="unbounded" />

    <xsd:complexType name="complexType.CustomerPaymentProfile" mixed="false">
            <xsd:element name="creation-date" type="xsd:dateTime" minOccurs="0" maxOccurs="1" />
        <xsd:attribute name="account-id" type="simpleType.Generic.NonEmptyString.256" use="required">
                The ID of the payment account used to create the customer payment profile.
        <xsd:attribute name="account-type" type="simpleType.PaymentAccountType" use="required">
                The type of the payment account used to create the customer payment profile.
        <xsd:attribute name="account-customer-id" type="simpleType.Generic.String.256" use="required">
                The ID of the customer payment profile in the payment account.

Verify Hostname Ownership

When uploading a custom hostname certificate, you are now required to verify ownership by adding a TXT record in the DNS configuration of that domain.

The value is shown in the Business Manager after uploading the certificate.

Business Manager

eCDN Interface Update

The workflow for creating zones gets an update:

  • Updated storefront zone creation UX workflow in Business Manager.

  • Zone is created using SSL for SaaS V2 (No USSL*) and configured and activated using CDN-API.

  • No need to refresh the entire page after zone creation.

  • Users can use the “Refresh” and “Verify Configuration” buttons to confirm that the zone has been verified/configured.

This is nothing “too exciting,” except if you have to configure about 50 zones. This minor update will speed up the process a lot!

Quotas: Site Specific

This improvement is more for the engineering and performance team at Salesforce to make sure POD performance can be ensured.

Rather than having to manage/relax a quota at a “realm” level, quotas can now be addressed at the Site level (when applicable).

Change History for campaigns & promotions

The Change History feature is getting some more options! With this release, you can keep track (if you want to) of all modifications of:

  • Campaigns
  • Promotions
  • Coupons


Identify SCAPI requests in hooks

Until now, you had to do a custom header check to differentiate between OCAPI and SCAPI requests.

In this release, you get a new function/attribute on the Request global object that makes life a little bit easier:


When writing your hook logic, it’s important to keep in mind the context of the API that is calling the hook. Both OCAPI and SCAPI share the same hooks, so it’s possible to write a hook that is used for both. Use request.isSCAPI() to determine SCAPI or OCAPI usage, especially if you’re already using the calculate hook in the context of controllers and use transactions in that hook, as that breaks SCAPI. Direct access to the _sfdc_mercury HTTP header is deprecated.

New SLAS Identity Providers supported

SLAS does not allow you to hook in any external IDP at the moment. You need to ask the SLAS team to add support for these through a message on the community groups.

Newly supported IDPs are:

PWA Kit v2.1.0

The PWA Kit is under continuous development as some features are still missing and new use-cases are presented to the team every week that might require some changes.

This release can be found here.

What’s New

  • 🔥 Client side hot module replacement.


  • Replace Mobify references/links with proper PWA Kit values. #619
  • Add support for a custom build directory to pwa-kit-dev build#628
  • Introduce client-side hot module replacement. #630


  • Remove console logs from route component. #651


For the 22.8 release, I have not found any newly accepted bug fixes, but that might change a few weeks after this article is released. I found that an issue was fixed in 22.7, which I didn’t mention in last month’s release note article.

Updated Cartridges & Tools

sfcc-cartridge-overrides-vscode-extension (v1.0.1)

VS Code Extension to Display SFCC Cartridge Overrides

Fix issue with Workspace Detection Issues. Tested this solution with a few different workspace setups and it seems to resolve the following issues:

Fixes #1#2 & #3

commerce-sdk-isomorphic (v1.6.0)

The Salesforce Commerce SDK Isomorphic allows easy interaction with the Salesforce B2C Commerce platform Shopper APIs through a lightweight SDK that works both on browsers and NodeJS applications.

API Changes

Shopper Login New Endpoints

Endpoint NameDescription
getPasswordResetTokenRequest a reset password token
resetPasswordCreates a new password


More error handling has been added in the SLAS helpers

Bug fixes

SLAS helper loginRegisteredUserB2C no longer calls redirectURI when running server side


README updated to explicitly note lack of CORS support for SCAPI


The Hybrid Storefront plug-in cartridge (name tentative) provides Storefront Reference Architecture (SFRA) and SiteGenesis sites with a mechanism for redirecting pages to PWA Kit as part of a hybrid storefront strategy.

Not so much an update as this cartridge does not have an official release yet, but an important one exists if you want to implement a hybrid deployment using SFRA/SG in combination with the PWA Kit.

sgmf-scripts (v2.4.2)

This repository contains a collection of scrips that are useful for creating Storefront Reference Architecture overlay cartridges. All of the scripts are executable through CLI.


  • Added --fix option when linting js and scss files (#33)
  • Removed unused webdriverio (#60)

sfra-webpack-builder (v3.3.2)

Webpack can be cumbersome to setup, especially in multicartridge projects for SFRA. This plugin let you bundle all your js, scss and jsx files out of the box.

I don’t think anything has changed in this release besides updating the package version. But it might be good to put it on the list, so people know this one exists!

b2c-commerce-toolkit-for-grocery (v1.3.0)

This demo version of a grocery storefront includes store and time slot selection, grocery-specific shopping experiences for all key store pages, and edit order capabilities. A sample grocery data set and a few typical configurations are also included.


Removed some redundant code which is now part of SFRA

plugin_einstein_api (v0.0.4)

This is the repository for the plugin_einstein_api plugin. This plugin enhances the app_storefront_base cartridge by adding the Einstein API capabilities.

Einstein API is the API-led interface from Salesforce B2C Commerce Einstein, and can be leverage to include Einstein product recommendations in places that are not displayed through a content slot on the storefront, or even outside of the storefront.

What’s Changed

Bugfix/cart productlineitems by @adrien-monte in #8

New Contributors

@adrien-monte made their first contribution in #8

Commerce Cloud Quota Increase

Table of Contents