Account Manager 3.0: The B2C Commerce Account Manager 3.0 is available on August 27, 2025. This release delivers:
Account Manager 3.1: The B2C Commerce Account Manager 3.1 is available on September 24, 2025. This release delivers:
Account Manager 3.3: The B2C Commerce Account Manager 3.3 is available on October 22, 2025. This release delivers:
Account Manager 3.4: The B2C Commerce Account Manager 3.4 is available on January 14, 2026. This release delivers:
Account Manager 3.5: The B2C Commerce Account Manager 3.5 is available on February 11, 2026. This release delivers:
Security Update for the Audit History Logs: Starting with the 1.34.0 release, the full name and full email address for active audit history users are masked from administrators. Masking occurs when the active user isn’t part of the organization and they’re active in Audit History for a User, Organization, or API Client sessions. Masking is also used when organization users view their audit history on the start page. The mask improves security compliance.
Account Manager 2026 Deployment Schedule: Interested in when the next release is coming? The B2C Commerce Account Manager Deployment Schedule lists all of the planned release dates for 2026.
Email Notification of Changes to Inactive User Settings: As part of the Auto Disable Inactive Users feature, an email notification is sent to users when the Inactive User settings are activated or deactivated. An email is also sent when the Days Before Deletion settings are changed on the organization detail page. The email is sent to the email address entered in the Contact Users field on the organization detail page.
Enable Read Only Account Manager Access: The Read Only Account Administrator role is now available in Account Manager. The role provides users read-only access to view details about their organization, API clients, and users. The role doesn’t include permissions to make updates. The new role is useful for auditors who want to confirm compliance with their company policies. High-privilege roles such as Account Administrator or API Administrator override the new role.
Multi-Factor Authentication for all Account Manager Users: Starting May 1, 2022 and continuing on a rolling basis through the end of May, Salesforce will enable and enforce MFA for all users who login in directly to B2C Commerce applications.
Account Manager Tenant Scope: Account Manager can now add scopes (claims) to API clients, enabling them to provide a tenant context as required by the Salesforce Commerce API.
Improved User Interface for Multi Factor Authentication (MFA) Management: We improved the Organization Detail page in two ways. You can now use sliders to set password policy values. And you can easily view which roles have MFA enabled, instead of selecting checkboxes. This user interface is similar to that of the User Detail page.
Improved Scope Assignment for API Clients: Each API client requires a scope assignment, either a default scope or one or more allowed scopes that you specify. Account Manager now validates your scope assignments before saving the API client.
Account Manager 1.31.100: The B2C Commerce Account Manager 1.31.100 is available on September 8, 2022. This release delivers:
Account Manager 1.31.102: The B2C Commerce Account Manager 1.31.102 is available on October 5, 2022. This release delivers:
Account Manager 1.31.104: The B2C Commerce Account Manager 1.31.104 is available on October 26, 2022. This release delivers:
Account Manager 1.31.108: The B2C Commerce Account Manager 1.31.108 is available on February 8, 2023. This release delivers:
Account Manager 1.31.111: The B2C Commerce Account Manager 1.31.111 is available on March 8, 2023. This release delivers:
Account Manager 1.31.112: The B2C Commerce Account Manager 1.31.112 is available on April 5, 2023. This release delivers:
Account Manager 1.31.113: The B2C Commerce Account Manager 1.31.113 is available on May 3, 2023. This release delivers:
Account Manager 1.31.114: The B2C Commerce Account Manager 1.31.114 is available on May 31, 2023. This release delivers:
Account Manager 1.31.115: The B2C Commerce Account Manager 1.31.115 is available on June 28, 2023. This release delivers:
Account Manager 1.31.117: The B2C Commerce Account Manager 1.31.117 is available on July 26, 2023. This release delivers:
Account Manager 1.31.118: The B2C Commerce Account Manager 1.31.118 is available on August 23, 2023. This release delivers:
Account Manager 1.31.120: The B2C Commerce Account Manager 1.31.120 is available on September 21, 2023. This release delivers:
Account Manager 1.31.123: The B2C Commerce Account Manager 1.31.123 is available on October 4, 2023. This release delivers:
Account Manager 1.31.124: The B2C Commerce Account Manager 1.31.124 is available on October 25, 2023. This release delivers:
New Multi-Factor Authentication Methods: We've added two new multi-factor authentication methods: Webauthn Cross Platform (FIDO2) and TOTP. Account administrators can decide which Multi-Factor Authentication methods they want for their organization.
MFA Verifier Allows Non-Ascii Characters: You can now use non-Ascii characters, such as ü, in the MFA Verifier display name. Previously, using these characters prevented user updates.
Define Users to Receive Security Emails: Keep your organization secure by defining contact users for security emails. Assigned users receive an email whenever a partner account with administrative permissions is added to your organization. Partner accounts with admin permissions receive admin permissions for all organizations they're part of. For security reasons, we recommend creating a new, non-admin account for users with existing admin permissions.
Secure Your Organization By Removing Shared Users With Escalated Privileges: To prevent privilege escalation, partner accounts in your organization who received administration privileges in another organization are now automatically removed from your organization. Previously, these users would receive admin privileges in your organization. Whenever a partner account receives admin privileges in another organization, any assigned security contacts in your organization receive an email notifying them of the event and whether the user was removed.
Change Logs Show Executing User's Email Address: The change log now display the executing user's email address. Change logs can be found on the user detail page, API client detail page, organization detail page, and account information page.
Passwords Can Only Be Changed Through Self-Service: Passwords can only be changed by a user, through the self-service feature. Administrators can continue to initiate user password resets through the API, but they can't update the password.
Multi-Factor Authentication Options: The option to exclusively use the Salesforce Authenticator is being replaced with the option to select from a number of different multi-factor authentication (MFA) options. The Salesforce Authenticator is still the default form of authentication.
Account Manager 1.31.77: The B2C Commerce Account Manager 1.31.77 is available on October 26, 2021. This release delivers:
Account Manager 1.31.79: The B2C Commerce Account Manager 1.31.79 is available on January 12, 2022. This release delivers:
Account Manager 1.31.83: The B2C Commerce Account Manager 1.31.83 is available on February 2, 2022. This release delivers:
Account Manager 1.31.88: The B2C Commerce Account Manager 1.31.88 is available on March 2, 2022. This release delivers:
Account Manager 1.31.90: The B2C Commerce Account Manager 1.31.90 is available on March 30, 2022. This release delivers:
Account Manager 1.31.91: The B2C Commerce Account Manager 1.31.91 is available on April 20, 2022. This release delivers:
Account Manager 1.31.93: The B2C Commerce Account Manager 1.31.93 is available on May 18, 2022. This release delivers:
Account Manager 1.31.96: The B2C Commerce Account Manager 1.31.96 is available on June 15, 2022. This release delivers:
Account Manager 1.31.97: The B2C Commerce Account Manager 1.31.97 is available on July 13, 2022. This release delivers:
Account Manager 1.31.99: The B2C Commerce Account Manager 1.31.99 is available on August 10, 2022. This release delivers:
Account Manager 1.32.0: The B2C Commerce Account Manager 1.32.0 is available on January 10, 2024. This release delivers:
Account Manager 1.32.1: The B2C Commerce Account Manager 1.32.1 is available on February 7, 2024. This release delivers:
Account Manager 1.34.0: The B2C Commerce Account Manager 1.34.0 is available on March 6, 2024. This release delivers:
Account Manager 1.35.0: The B2C Commerce Account Manager 1.35.0 is available on April 3, 2024. This release delivers:
Account Manager 1.36.0: The B2C Commerce Account Manager 1.36.0 is available on April 24, 2024. This release delivers:
Account Manager 1.38.0: The B2C Commerce Account Manager 1.38.0 is available on May 29, 2024. This release delivers:
Account Manager 1.39.0: The B2C Commerce Account Manager 1.39.0 is available on June 19, 2024. This release delivers:
Account Manager 1.40.0: The B2C Commerce Account Manager 1.40.0 is available on July 17, 2024. This release delivers:
Account Manager 1.41.0: The B2C Commerce Account Manager 1.41.0 is available on August 14, 2024. This release delivers:
Account Manager 1.42.0: The B2C Commerce Account Manager 1.42.0 is available on September 4, 2024. This release delivers:
Account Manager 1.43.0: The B2C Commerce Account Manager 1.43.0 is available on September 24, 2024. This release delivers:
Account Manager 1.44.0: The B2C Commerce Account Manager 1.44.0 is available on October 23, 2024. This release delivers:
Account Manager 1.46.0: The B2C Commerce Account Manager 1.46.0 is available on Feb 12, 2025. This release delivers:
Account Manager 1.46.4: The B2C Commerce Account Manager 1.46.4 is available on March 5, 2025. This release delivers:
Account Manager 2.0.5: The B2C Commerce Account Manager 2.0.5 is available on April 2, 2025. This release delivers:
Account Manager 2.1.0: The B2C Commerce Account Manager 2.1.0 is available on May 7, 2025. This release delivers:
Account Manager 2.2.0: The B2C Commerce Account Manager 2.2.0 is available on June 4, 2025. This release delivers:
Update Your Account Manager Login Experience: As part of the Account Manager infrastructure upgrade, Salesforce is updating the Uniform URL path and attribute values for the Account Manager login page. This change doesn’t affect the domain name. You can still use https://account.demandware.com/ to access Account Manager.
Use the Simplified Account Manager Login Screen Flow: As part of the Account Manager infrastructure upgrade, Salesforce is simplifying the Account Manager login screen flow. Updates include changes to the forgotten password link location, Multi-Factor Authentication (MFA) verification, and Salesforce Identity Management (SFIDM) redirect steps.
Update Your Account Manager Login Experience: As part of the Account Manager infrastructure upgrade, Salesforce is updating the Uniform URL path and attribute values for the Account Manager login page. This change doesn’t affect the domain name. You can still use https://account.demandware.com/ to access Account Manager.
Auto Disable Inactive Users: Compliance with PCI DSS 8.1.4 requires that Account Manager user accounts are disabled when their accounts are inactive for 90 days. To support compliance with PCI DSS 8.1.4, Account Manager administrators can now set the number of inactive days before an account is disabled. When the setting is enabled, users with inactive accounts receive an email notification 10 days and 1 day before their account is deactivated. To keep an account active, users can log in to any Commerce Cloud application. To enable the setting, in Account Manager > Organization details, activate or deactivate the setting. The setting is disabled by default.
Removal Deprecated Role Assignments: Salesforce is removing deprecated roles from Account Manager, ensuring a cleaner and more streamlined user experience. This update will not affect the supported roles currently assigned to users, and no action is required from customers.
Identify Uninvited Account Manager Users with the External User List: You can now use the External User tab in Account Manager to view and manage uninvited users who still have access to your Business Manager instances. Account Manager administrators can decide to either revoke their access or invite them to join your organization.
Improve Administrator Invitation Transparency with User Details: We have made an improvement to the email notification process for user invitations in customer Orgs. With the new enhancement, email notifications now include the username of the person inviting a new admin, increasing transparency and aiding in the quick identification of responsible parties.
Disable Inactive Users by Default: To improve security, new Account Manager organizations now disable inactive user accounts after 90 days by default. You can turn this setting off or adjust the number of inactive days before an account is disabled in Account Manager Organization settings.
Invalidate User Session for Improved Security: To improve security, Account Manager user sessions are invalidated when an account is edited, reset, deleted, or the password is changed.
Update Your Allow List with New IP Addresses for Account Manager: With this release of Account Manager, the IP addresses for traffic coming to Account Manager are now changed. If you have allow listed old IP addresses, you can remove them from the allowlist.
Log in to Account Manager with SSO: The Account Manager login screen now supports Single Sign-On (SSO). This enhancement simplifies the login process for new users. To link their account with Account Manager and get auto-provisioned in Account Manager, new users, who connect to Commerce Cloud with SSO, click Link for Single Sign-on. This setup requires that Just-in-time user provisioning is enabled.
Multi-Factor Authentication Warning Message: To increase security for our customers, as of February 1, 2022, Salesforce requires all users to use multi-factor authentication (MFA) to access B2C Commerce products, including Account Manager. When logging into Commerce Cloud Account Manager, users who don't use MFA receive a warning message stating that they aren't using MFA.
Update OAuth Endpoints: Salesforce has disabled the /tokeninfo endpoint in Account Manager. Use the /dwsso/oauth2/introspect endpoint for token validation.
Purge API Clients from Account Manager: Account administrators can now purge an API client after the API Client’s status is set to disabled for seven days. The wait period prevents any unexpected business disruptions caused by an unintentional immediate purge of an API Client. Before the wait period ends, the purge option isn't active.
Replace Wildcard Tenant Filter: Starting with the Account Manager 1.31.118 release, the wildcard filter, realm_*, isn’t supported and is replaced with this set of filters:
Simplified Identity Federation for Existing Users: Account Manager now supports automatic activation and linking for new user accounts. This change improves the single sign-on (SSO) user experience by making it simpler and faster.
Create Multiple User Accounts with Subaddressing: Use a single email inbox for multiple user accounts and assign specific roles based on the subaddress. Enhance security and simplify partner management by creating customer-specific subaddresses with limited roles, giving partners a single email inbox with distinct, traceable accounts for each customer relationship. You can also create separate user accounts for different functions, such as development, testing, and administration. Before setting up this feature, confirm that your email provider supports email subaddresses.
Tenant-specific Rate Limiting for Account Manager OAuth Traffic: Commerce Cloud Account Manager now enforces a new tenant-specific rate limit for OAuth traffic. OCAPI Shop and Data API calls can generate OAuth traffic on a POD. The New rate limit is enforced on a per minute basis. This change provides all B2C Commerce users on the same POD an equal share for OAuth traffic.
Update OAuth Endpoints: Salesforce has disabled the /tokeninfo endpoint in Account Manager. Use the /dwsso/oauth2/introspect endpoint for token validation. In addition, Salesforce will deprecate the /dw/oauth2 endpoint starting June 30th, 2025. Use /dwsso/oauth2 for OAuth operations to ensure continued secure access.
Track API Client Activity with Last Authentication Date: The Account Manager API Client Detail page now displays the last authenticated date for API clients. This date represents the last time an API client successfully used valid credentials to acquire an access token. This enhancement allows administrators to monitor API client activity and pinpoint any inactive API clients. As a security best practice, Salesforce recommends disabling API clients that aren’t in use. In our ongoing efforts to enhance security, we’re planning to remove API Clients that haven’t authenticated in the last 6 months.
Upcoming Removal of Deprecated Roles in Account Manager: Salesforce is removing deprecated roles from Account Manager. To prevent any disruption in your organization's workflow, ensure you aren’t using the deprecated roles.
Update Your Allow List with New IP Addresses for Account Manager: During the January 2025 release of Account Manager, the IP addresses for traf fic coming to Account Manager will be changed. To make sure service is uninterrupted, we a dvise adding the new IP addresses to your allowlist before this release. After the new IP addresses are in effect, you can then remove the old IP address from the allowlist. Further instructions will be detailed in the January release notes.
Upgrade to Introspect Endpoint for Secure Token Management: Salesforce strongly recommends that you replace the /tokeninfo endpoint with the /dwsso/oauth2/introspect endpoint. The /tokeninfo endpoint requires that the token is passed as a URL parameter. Sensitive information within URLs can be logged in various locations, including the user’s browser, the web server, and any forward or reverse proxy servers between the two endpoints. The /dwsso/oauth2/introspect endpoint includes the UUID access token in the request body which isn’t logged or recorded. In addition, only authenticated clients can use this endpoint. As an added level of security, an API client can only introspect its own tokens and can’t share information outside of your organizations.
UUID Tokens Switched to JWT Access Tokens: As previously announced in June 2023, Account Manager no longer supports the use of UUID token formats. All new API Clients only support the JWT access token format.
Einstein and Data Usage in B2B Commerce: As an Einstein customer, it’s important for you to know what data is being used by B2B Commerce products. This table lists the data that is used by each B2B Commerce feature.
B2B Commerce for Visualforce: Review B2B Commerce for Visualforce bug fixes included in each generally available patch. Access help documentation, release notes, and developer documentation using PDFs.
B2B Commerce for Visualforce Patch Notes: Salesforce B2B Commerce for Visualforce patch notes contain high-level reviews of bug fixes included in each generally available patch for a Visualforce package. We update patch notes after a new patch becomes available for a package.
B2B Commerce for Visualforce Resources: Access PDF resources to view B2B Commerce for Visualforce help documentation, release notes, and developer documentation. As of Summer ’25, Salesforce maintains only patch notes for B2B Commerce for Visualforce.
Searches for Brand Names Containing Stop Words Are Now Returning Relevant Products: Storefront searches for brand names are now returning relevant products even if brand names, or part of brand names, are defined as stop words. Previously, when searching a brand name that contained a defined stop word, like "of" or "the", the relevant products were sometimes not found.
Content Indexing Not Failing Any More If Content Asset Exceeds Maximum Size: The content indexing is no longer failing if a content asset has a searchable text or HTML attribute that exceeds the maximum size for an indexable term, and has autocorrect set to true. Previously, the content asset wasn't indexed properly, and failed.
Storefront Search Considers Special Characters When Creating a Did You Mean Phrase: A defect in the suggestion processor has been fixed for search phrases with special characters. When creating a Did-You-Mean phrase, the term match-type is now considered instead of just comparing the complete phrase. Previously, the whole constructed phrase was compared to the original user input that could lead to wrong results because the previous processor removed special characters.
Select All Storefront Sites or Site Parameter for Job Flow Scope: When you create a job flow, you can now select from four options for flow scope: Organization, All Storefront Sites, Specific Sites, and Site Parameter. The two new options, All Storefront Sites and Site Parameter, allow you to more easily specify which sites to include in the scope.
Page Designer Code No Longer Tries to Use Global Variable $A: The code that Page Designer injects into the storefront no longer tries to use the global variable $A. Previously, if the $A variable existed, the Page Designer code assumed it was part of the Aura UI framework and tried to access it.
Query Parameters Correctly Returned for Request.getHttpQueryString(): B2C Commerce Script API dw.system.Request.getHttpQueryString() now correctly returns query parameters that are part of a short URL. Previously, the query parameters were not returned. This fix addresses a Release 20.1 regression issue.
Custom Object Import/Export Page Displays Correctly: The Custom Object Import/Export page displays as expected. Previously, if there were custom object import/export records that had been triggered from the same Business Manager module, a Technical Error page displayed. This fix addresses a Release 20.1 regression issue.
Get Ready for the Google Chrome 80 Cookie Change: Google Chrome 80, scheduled to be released in February 2020, introduces a new default cookie attribute setting of SameSite=Lax. Previously, the SameSite cookie attribute defaulted to SameSite=None. Also new with Chrome 80, when SameSite is set to None, cookies must be tagged with the Secure attribute indicating that they require an encrypted HTTPS connection. Other browser vendors are expected to make similar changes soon. To get ready for the changes, enable the global security preference Enforce HTTPS. Also, test to see if client-side JavaScript code requires adjustments and to make sure that third-party integrations work as expected.
OCAPI: Review the B2C Commerce OCAPI update in the 20.10 release.
Pricing and Promotions: Review the new B2C Commerce Pricing and Promotions features in the 20.10 release.
Storefront Toolkit: Review the B2C Commerce Storefront Toolkit update in the 20.10 release.
New Override Price Books Preference: Merchandisers can now define a hierarchical override model that lets store-level prices override parent price book prices. The feature is controlled by a new preference, Enable Price Books Override, which can be found in the new Pricing Preferences module. This feature is helpful for merchants with repeated price entries in store-level price books because reducing the total price entries can optimize storefront lookup prices.
Test Promotions Using the Promotions Tracing Tool: See which promotions are applied to a cart and which don’t apply and why. You can get the promotions tracing tool from the Storefront Toolkit. Promotions tracing is available only in non-production environments and only in the cart.
OCAPI Cross Device Activity Tracking: OCAPI supports correlating data across devices for guests and logged in customers, which applies to both client and server side activities.
Reports & Dashboards: Review the B2C Commerce Reports & Dashboards update in the 20.11 release.
Exception Not Thrown When Building a To-One Relationship: Under some rare, specific conditions, exceptions of type ORMMandatoryException: Can't unset mandatory to-1 relationship were thrown if the target object didn't change. This issue has been fixed, eliminating some errors that occur when customers place orders.
Select Categories as Promotion Qualifiers: Merchants can use a category as a promotion qualifier. Previously, when a merchant attempted to specify a category as a qualifier, they received a blank popup.
AppServer: Review the new B2C Commerce AppServer features and enhancements in the 20.1 release.
Cloud Utilities: Review the new B2C Commerce Cloud Utilities enhancement in the 20.1 release.
eCDN: Review the new B2C Commerce eCDN feature in the 20.1 release.
Jobs: Review the new B2C Commerce Jobs feature in the 20.1 release.
OCAPI: Review the new B2C Commerce OCAPI updates in the B2C Commerce 20.1 release. The OCAPI version remains 19.10.
Page Designer: Review the new B2C Commerce Page Designer features and enhancements in the 20.1 release.
Pricing and Promotions: Review the new B2C Commerce Pricing and Promotions enhancements in the 20.1 release.
Products and Catalogs: Review the new B2C Commerce Products and Catalogs enhancements in the 20.1 release.
Reports and Dashboards: Review the new B2C Commerce Reports and Dashboards features in the 20.1 release.
Search: Review the new B2C Commerce Search enhancements in the 20.1 release.
Visual Merchandising: Review the new B2C Commerce Visual Merchandising feature in the 20.1 release.
Visual Merchandising Infinite Scroll and Performance Updates: The visual merchandising page no longer reloads product tiles when you sort by dragging them, which improves rendering speed. Also, the visual merchandising page now supports infinite scroll, which lets you scroll through all products in a category. Previously, you clicked through multiple pages that showed 50 products per page.
variation-value Attribute Deprecated: The variation-value attribute within the <image-group> element in the B2C commerce catalog import is deprecated. If your imported XML file has a <variation-value> attribute in the image-group element, a warning message is returned. The warning cautions that one or more image groups are specified using the deprecated <variation-value> attribute.
OCAPI: Product Search Handles Commas: You can now use commas in product search refinement strings. Previously, including a comma caused product searches to fail and return no results. The fix is also implemented in prior versions.
Create a New Page by Copying an Existing Page: You can now make a copy of a Page Designer page and then edit that page to create one. The copy has all the same settings and content as the original except for the Page ID. Copying a page can improve your efficiency since you don’t have to start from scratch every time you create a page.
Target a Page or Component for a Campaign or Promotion: You can now assign the targeting rules of a campaign or promotion that’s already set up in Business Manager to a Page Designer page. The targeting rules for the campaign or promotion override Page Designer targeting capabilities.
Get Alerts When Two-Factor Authentication Not Enabled for Code Uploads: Business Manager now issues alerts if a production instance doesn’t disallow code uploads or a staging instance doesn’t require a client certificate to upload code. For security reasons, we request that customers disallow code uploads to production instances and require a client certificate for code uploads to staging instances. We recommend making these configuration changes as soon as possible and no later than April 1, 2020, when we mandate this configuration.
Changes to eCDN WAF Log Updates: The eCDN WAF log delivers more comprehensive data to provide additional insights into WAF rules that are triggered. We added fields about the firewall type and any actions performed by WAF and removed fields made obsolete. The new WAF fields enable you to self-diagnose your environment and investigate the reason a WAF rule triggered. In addition, we added a field that indicates whether assets were cached on the eCDN.
Import Process Fix: The customer Merge/Update process no longer overrides the existing credentials attribute <enable-flag> to a false value. Previously, you explicitly set the <enable-flag> as true in the import XML for the customer to be enabled after import. The change to the XML file is no longer required.
Merchants Can Assign Multiple Products to a Category: Merchants can assign more than products to a category. Previously, if a merchant used the Edit All option to assign more than ten products to a category, using Finish: Go to Batch Process, only the top ten products were assigned.
Generic Mapping Logs Enhanced: Updated logs and metrics for the Import and Export Generic Mapping feature provide a data source for troubleshooting generic mapping issues. And now there’s a generic mapping performance alert notification for support and engineering.
Price Refinements Support Values from Data Type Double: The price refinement bucket definition, and the related Import and Export and Business Manager screens now support values for the double data type instead of the integer data type. Previously, price refinement buckets supported values no greater than the integer data type.
New Total Price Entries Quota: We're enforcing a new quota on total price entries. Customers now receive a WARN error when they reach 290 million price entries and an ERROR when they reach 300 million price entries.
AppServer: Review the new B2C Commerce AppServer feature in the 20.2 release.
eCDN: Review the new B2C Commerce eCDN feature in the 20.2 release.
Data API Endpoints for Updating Orders: You can now use Data API endpoints to update orders in server-to-server use cases, such as when an order management system or payment provider initiates a change.
Improved Validation for OCAPI Settings: Validation now checks for duplicate settings, and when you include multiple JSON configuration documents, it validates the settings in all documents instead of only the first.
Undo a Replication Process: To undo a data or code replication process, click Undo next to the replication process listed on the replication process screen. Also, now you can rerun a failed Undo Replication process as long as no other replication process has been run yet.
Create Custom Attribute Editors Faster with Prebuilt Attribute Editors: Use the prebuilt editors as building blocks when you create custom attribute editors. We provide prebuilt editors for Category Picker, Link Builder, Page Picker, and Product Picker UI controls. When the merchant configures the component attribute, the prebuilt editor opens in a separate breakout window window.
Gift Certificate Report: The new Gift Certificate report in Reports and Dashboards provides metrics on gift certificate purchases and redemptions.
Promotions Apply to High Prices: Products, orders, and shipments with prices greater than 2,147,483,647 of any currency can receive promotions again.
Promotional Price Rounds to Site Currency Precision: Promotional prices displayed on a product listing or display page rounds to the precision of the site current. Previously, the price always rounded to two decimal places.
Einstein Complete the Set Recommender: The Einstein Complete the Set Recommender is now generally available (GA). Complete the Set is a new recommender type in the Einstein Configurator that creates recommendations for complementary products.
Cart Checkout: Review the new B2C Commerce Cart Checkout feature in the 20.3 release.
eCDN: Review the new B2C Commerce eCDN feature in the 20.3 release.
OCAPI: Review the new B2C Commerce OCAPI updates in the B2C Commerce 20.3 release. The OCAPI version is now 20.3.
Page Designer: Review the new B2C Commerce Page Designer features and enhancements in the 20.3 release.
Pricing and Promotions: Review the new B2C Commerce Pricing and Promotions features and enhancements in the 20.3 release.
Products and Catalogs: Review the new B2C Commerce Products and Catalogs enhancement in the 20.3 release.
More Consistent Error Handling for Shop API DELETE Resources: Calling certain Shop API DELETE resources on a nonexistent record ID now returns HTTP 404 (ProductItemNotFoundException) instead of HTTP 204 (Success) with a debug log entry. This behavior is more consistent with the overall pattern.
Promotions Apply to High Prices: Products, orders, and shipments with prices greater than 2,147,483,647 of any currency can receive promotions again.
Two New Promotion APIs: Two new promotion APIs expose the promotion tier index at order and product level in dw.campaign.Discount script API
Use Tax Class ID in Advanced Search: You can now use the Tax Class ID as an Extended Attribute search parameter in the Business Manager Advance Search screen.
Fail Order Process Optimization: The order failure process is optimized to reduce inventory lock times. This improvement increases order throughput in high-load situations by up to 400%.
Find a Page Designer Page Using Search Suggestions: You can now implement search suggestion support for Page Designer pages. When a customer starts to enter a search term on the storefront, the storefront application suggests related search terms. And the customer can select from a list of Page Designer pages applicable to the suggested search terms.
Changes to eCDN WAF Log Updates: We modified the eCDN WAF log in the 20.1 B2C Commerce release to deliver more comprehensive data and provide added insights into WAF rules that are triggered. We provided a legacy and a new version of the eCDN-WAF log. In this release, we phased out access to the legacy eCDN-WAF Log version.
Einstein Recommendations: Review the change to B2C Commerce Einstein Recommendations in the 20.4 release.
OCAPI: Review the new B2C Commerce OCAPI updates in the B2C Commerce 20.4 release. The OCAPI version is now 20.4.
Orders: Review the new B2C Commerce Orders feature in the 20.4 release
Page Designer: Review the new B2C Commerce Page Designer feature in the 20.4 release.
Products and Catalogs: Review the new B2C Commerce Products and Catalogs feature in the 20.4 release.
Reports and Dashboards: Review the new B2C Commerce Reports and Dashboards feature in the 20.4 release.
Search: Review the new B2C Commerce Search feature in the 20.4 release.
CSV Format Supported for Product Catalog Export and Import: You can now import and export your product catalog as a CSV file or as an XML format. You can choose which product attributes to include in the export, so that the file shows only the data that you need. Each CSV export contains data for a single site and a single locale. The CSV import supports multiple sites and locales.
New Jobs for Search Index Rebuild: New jobs trigger the rebuild of search indexes. As a developer, you can now trigger a search index rebuild via OCAPI to easily set up and test new instances.
Order Status No Longer Changes to Open: Viewing an order in Business Manager no longer changes the order status to Open. Instead, the order retains its status. If needed, you can manually change the status to Open. Previously, viewing an order automatically changed the order status to Open. EDIT: This feature has been rolled back and no longer impacts any customers.
Enter Text More Easily with a Larger RTE: The Rich Text Editor (RTE) window where you enter text to configure component attributes is larger now. If you need even more room, you can expand the RTE window to full size.
New On-Site Search Report: The On-Site Search report shows search metrics across all sites. Track KPIs over time, such as total number of searches, number of searches with or without results, number of searches per visit, and revenue per search. The report also includes a list of search phrases that returned results and search phrases that did not return results. You can filter by site, locale, device type, and customer registration.
Einstein Dashboard Improvements: As of March 31, 2020, Commerce Cloud Einstein will no longer email the CC Einstein Recommendations Performance Report.
AppServer: Review the new B2C Commerce AppServer feature in the 20.5 release.
B2C Commerce Business Manager Available in German: The language pack for Business Manager is now localized into 8 languages including French, Italian, Portuguese, Spanish, Japanese, Simplified Chinese, Korean and for the first time German. In addition, the B2C Commerce release notes and the release highlights in the Message Center are also available in German.
Localization: Review the update to B2C Commerce localization in the 20.5 release.
Orders: Review the B2C Commerce Orders change in the 20.5 release
Pricing and Promotions: Review the new B2C Commerce Pricing and Promotions features in the 20.5 release.
Products and Catalogs: Review the new B2C Commerce Products and Catalogs feature in the 20.5 release.
Reports and Dashboards: Review the new B2C Commerce Reports and Dashboards feature in the 20.5 release.
Search: Review the changes to B2C Commerce Search in the 20.5 release.
Visual Merchandising: Review the new B2C Commerce visual merchandising feature in the 20.5 release.
Extend Combining and Excluding Promotions with New Attributes: Three new attributes provide you with extended promotion exclusivity and combinability. To make grouping promotions easier, add promotions to Exclusivity Groups. Then set individual promotions or entire Exclusivity Groups as Combinable Promotions or Mutually Exclusive Promotions.
Control Product Qualification with New System Attribute: Control which products can qualify for your promotions. With this option you can prevent a product that already qualified for a higher-ranking promotion from qualifying for your current promotion. This attribute affects class-exclusive promotions only.
Coupon Stacking on Order Promotions: We've introduced a new promotion preference that controls whether multiple coupon codes can stack in a single order promotion. This setting impacts monetary discounts only. The preference defaults to prevent coupon stacking.
See Source Code Reports on the New Source Code Dashboard: Analyze which campaigns are driving orders and revenue in your storefront. The new Source Code dashboard offers a view of your source code activity in a streamlined set of reports.
Order Post-Processing APIs No Longer Available: With the release of Salesforce Order Management, you can no longer enable the order post-processing APIs, including the Gillian package, in the B2C Commerce platform. Customers who are currently using order post-processing can continue to use it until further notice. This change does not affect Commerce Cloud Order Management. If these APIs are already enabled on your production instance and you need access to these APIs on your sandboxes, please contact Salesforce Support. If you need access to these APIs on SIGs, contact Salesforce Support.
Search Index Rebuild Jobs Show Output in Traditional Job History Page: Jobs triggered by the configuration specified in Business Manager > Merchant Tools > Search Index Rebuild Schedule now output their history in the traditional Job History (Deprecated) page. Previously, the history was shown in the new Job History page. This change is temporary, output will move back to the Job History page in a future release.
AppServer: Review the new B2C Commerce AppServer feature in the 20.6 release.
Jobs: Review the new B2C Commerce Jobs feature in the 20.6 release.
Locales: Review the new B2C Commerce Page Locales Setting in the 20.6 release.
Orders: Review the B2C Commerce Orders change in the 20.6 release
Page Designer: Review the new B2C Commerce Page Designer features in the 20.6 release.
Products and Catalogs: Review the new B2C Commerce Products and Catalogs feature in the 20.6 release.
Reports and Dashboards: Review the new B2C Commerce Reports and Dashboards feature in the 20.6 release.
Order Export Element Sizes Increased: Version 20.6 of the order.xsd export schema increases the maximum length of product line item product names, address suites, and applied discount price book IDs.
Check Numeral System Settings for Locales: Locales now correctly display numbers as defined in Business Manager in the locale's Numeral System setting. Previously, in some cases, the locale used the locale's default Numeral System even though a different Numeral System was configured in Business Manager.
Create Templates for Product List and Product Detail Pages: With Page Designer’s new dynamic page feature, you can easily create rich, engaging templates for Product Detail or Product List pages. You can assign the template to multiple categories. When a Product List or Product Detail page is rendered in the storefront for one of the assigned categories, the template page is displayed, populated with the appropriate product information.
Preassign Components to Regions on Page Designer Pages: When developing a page type or component type, Page Designer developers can preassign components to regions. When a merchant creates the page in the Visual Editor, the preassigned components are already in the region. The merchant can remove or modify the preassigned components as necessary.
Jobs Automatically Resume After Unplanned Events: If an unplanned event, for example an app server crash, interrupts a job running on the new job framework, the job automatically resumes. The job step in progress during the interruption and all subsequent job steps are executed. If the B2C Commerce or custom code version changed since the job started, the job is restarted from the beginning. If you restarted the instance or if the app server is shut down as part of a maintenance operation, the job is not resumed or restarted.
Verify User Permissions for New Stricter WebDAV Zip Check: B2C Commerce supports an extension to the WebDAV protocol that allows a client to pack files and folders into a zip archive at the server. With this release, the permission check for creating WebDAV zip archives is stricter.
Set Access Restrictions for Uploading Code by August 1, 2020: For security reasons, you must disallow code uploads to production instances and require a client certificate for code uploads to staging instances. We mandated this configuration by April 1, 2020, but did not start proactive enforcement because of COVID-19. As of August 1, 2020, we will start proactive enforcement.
AppServer: Review the new B2C Commerce AppServer features in the 20.7 release.
Page Designer: Review the new B2C Commerce Page Designer features in the 20.7 release.
Pricing and Promotions: Review the new B2C Commerce Pricing and Promotions feature in the 20.7 release.
Products and Catalogs: Review the Products and Catalogs OCAPI update in the 20.7 release.
Missing Attributes Available for Data Product Endpoints: The attributes valid_to (online_to), valid_from (online_from), tax_class_id, localized_tax_class_id, primary_catagory, and classification_category (category data via categories expansions) are now available from the DATA GET Products OCAPI Endpoint. You can include the attributes in the DATA PUT/PATCH Products OCAPI Endpoints.
Create and Manage Dynamic Pages More Efficiently: Dynamic pages are typically implemented as Product List or Product Detail pages for which the content changes based on which category or product is rendered. With this version, you can create and manage these pages more efficiently.
Search for Pages Using Attribute Values: Developers can specify that component or page attributes are indexed and searchable. When attributes are searchable, users can find pages by searching for the attribute value. For example, users can search for the text configured for a rich text attribute.
Create Custom Page-Level Attributes: Developers can define attributes for page types. For example, a developer can create a page type that includes attributes for the Title, Image, and Description displayed in search results for the page. Or the developer can define page attributes for page tags that allow merchants to search, sort, and retrieve pages more easily.
Use Simplified, Consistent File Retention Rules: New file retention rules are available for files in the /Logs, /Securitylogs, /Impex, and /Temp folders. Previously, different folders, instances, and environments used different file retention periods or no retention period at all. The new retention logic will be enabled after the 20.7 release. Download and save files you want to retain for longer than the new retention period.
Basket: Review the new B2C Commerce Basket feature in the 20.8 release.
Change of Identity Management for Commerce Cloud GitHub Repositories: We're simplifying how users access the Commerce Cloud GitHub repository. Access is now direct via Commerce Cloud Account Manager. Previously, access required users to register a GitHub account. This change only affects resources that require Commerce Cloud accounts. Any resources that are publicly available can still be accessed using any GitHub account.
Jobs: Review the new B2C Commerce Jobs feature in the 20.8 release.
OCAPI: Review the new B2C Commerce OCAPI updates in the B2C Commerce 20.8 release. The current OCAPI version is now 20.8.
Page Designer: Review the new B2C Commerce Page Designer feature in the 20.8 release.
Pricing and Promotions: Review the new B2C Commerce Pricing and Promotions features in the 20.8 release.
Reports and Dashboards: Review the new B2C Commerce Reports and Dashboards feature in the 20.8 release.
Enhanced Flexibility with Promotions Proration Exclusivity and Combinability: You can now prorate select product promotions across all eligible products in a cart. This enhancement is available for amount and percent promotions. Enable this option using the checkbox that appears for applicable promotions.
Basket Product Duplication Considers Product Lists: When basket settings are configured to disallow or merge duplicate product line items, the system now considers product lists, such as wishlists, in addition to SKUs and inventory lists. When a shopper adds a product from a list to a basket, the system can only duplicate an existing product line item that was added from the same list.
High Scale Price Book Activation Moved to Admin Feature Toggle: Business Manager admins can use a feature toggle to enable or disable High Scale Price Books. The High Scale Price Books feature is intended for customers who import prices frequently and don't create or modify prices directly in Business Manager.
Enhanced Error Handling for In-Cart Promotion Evaluation: If an exception is thrown during an in-cart promotion evaluation, the evaluation is aborted and any calculated discount is returned. This enhancement lets shoppers proceed to checkout with all applied discounts. We also enhanced the validation process to reduce unexpected failures. All failures are logged in Log Manager.
New Product Attributes for Price Per Unit Feature: You can now display two new product attributes for shoppers on the product display and product list pages: unit quantity and unit of measurement. These attributes let shoppers compare the value between similar products of varying quantities.
Work with Per-Unit Product Pricing: Several OCAPI documents now include properties related to per-unit product pricing. The Data API and Shop API products and product_search resources consume and return these documents.
Improve Performance with the parentCategoryTree Element: The get category API now has the parentCategoryTree element. The element returns the entire parent category tree. With the parentCategoryTree element, you can improve performance by retrieving the category tree path on the breadcrumb instead of making recursive calls to get the tree.
ExportOrders Job Step Order Status Behavior Updated: Three parameters on the ExportOrders job step have changed. The Export Status default value is now Ready for Export, and the Created and Failed parameters have been deprecated.
AppServer: Review the new B2C Commerce AppServer features in the 20.9 release.
Business Manager: Review the new B2C Commerce Business Manager feature in the 20.9 release.
Feature Switches (Toggles): Review the new B2C Commerce Feature Switch (Toggles) features in the 20.9 release.
OCAPI: Review the new B2C Commerce OCAPI updates in the B2C Commerce 20.9 release. The current OCAPI version is now 20.9.
Page Designer: Review the new B2C Commerce Page Designer feature in the 20.9 release.
Easily View and Download Files: Use the new folder browser feature in Business Manager instead of a WebDAV client to view and download files such as log files. The folder browser lets you quickly and easily view and download files that you have WebDAV permissions for.
Inventory Quotas Increased: You can now create more Product Inventory Records and Lists. The Product Inventory Records quota increases to 50,000,000, and the Product Inventory Lists quota increases to 10,000. Reaching or exceeding 80% of either quota triggers a quota warning.
JavaScript in HTML Attributes Allowed Only with Strong Authentication: Beginning with this release, for security reasons, only Business Manager users with strong authentication, such as through multi-factor authentication with Account Manager, can embed JavaScript in HTML attributes. To make it easier to adjust to this change, a Business Manager user with strong authentication can temporarily allow users without strong authentication to include JavaScript in HTML attributes.
Check Configuration for Secure Code Uploads: Two-factor authentication (2FA) for code uploads to the staging instance is required. Direct code uploads to the production instance aren’t allowed. Starting August 10, 2020, we automatically make configuration changes to meet these requirements on instances not in compliance.
Create a Link to a Content Asset: Some component attributes allow you to configure a link, for example to a product, category, page, or external resource. We have expanded your options for that link to include content assets.
Use the 404 Error Caching Feature Switch: Customers with administrator access can now manage feature switches (toggles) for web tier caching of 404 error responses.
Use the Einstein Complete the Set Recommender For New Verticals: The Einstein Complete the Set recommender enables customers to promote complementary items to shoppers. Customers can already use the Einstein Complete the Set recommender for apparel and accessories. Now it’s available for home furnishing, cosmetic, and beauty products.
Use Rule Sets to Assign Dynamic Categories: With dynamic categories, you no longer need to assign each product individually to your categories. Create rule sets to define criteria for products. All matching products are assigned to that category. You can add up to five rules to a dynamic category, using AND and OR rules to expand or narrow the category's criteria.
Customize Payment Methods in Multiple Countries Using Payments Zones: Use payments zones to specify which payment methods can be used by shoppers in specific countries. A default payments zone, set to all currencies and countries, is automatically created after you assign a checkout method to a merchant account.
Review Salesforce Commerce API Metrics in Reports & Dashboards: The Salesforce Commerce API (SCAPI) report is now available in the Reports & Dashboards app, Technical dashboard. It provides insight into your site’s Commerce API requests. The report metrics are updated daily.
Use Flexible On-Demand Sandboxes: B2C Commerce on-demand sandboxes, an alternative to traditional POD-based sandboxes, are generally available as of August 21, 2019. On-demand sandboxes can be acquired quickly, have improved performance, and can be used as part of a CI/CD process. You control how many sandboxes you use and when you use them. A usage-based pricing model allows you the flexibility to keep just a few sandboxes running for an extended period or create many short-term sandboxes.
B2C Commerce 2026 Deployment Schedule: To uphold our commitment to customer trust and to make sure that our B2C Commerce releases meet our rigorous standards, we deploy the B2C Commerce major releases to customers in four phases. See the Deployment table for information about which instances are included in each major release phase.
Inclusive Terms Are Replacing Legacy Language: As part of our efforts to refine language in our products to more accurately reflect inclusivity, Salesforce is replacing terms deemed noninclusive. APIs and older API documentation aren’t included because changing terms in our code can break current implementations.
Managed Runtime Release Notes Archive: Managed Runtime is part of Salesforce’s Composable Storefront solution, which includes PWA Kit and the B2C Commerce API. Review the features and updates from past releases.
PWA Kit Release Notes Archive: The Progressive Web App Kit (PWA Kit) is part of Salesforce’s Composable Storefront solution, which also includes Managed Runtime and the B2C Commerce API. Review and features and updates from past releases.
20.10 Release: The B2C Commerce 20.10 release occurs September 22, 2020 through October 20, 2020.
20.1 Release: The B2C Commerce 20.1 release occurs December 5, 2019 through January 20, 2020.
20.2 Release: The B2C Commerce 20.2 release occurs January 21, 2020 through February 20, 2020
20.3 Release: The B2C Commerce 20.3 release occurs February 25, 2020 through March 24, 2020.
20.4 Release: The B2C Commerce 20.4 release occurs March 19, 2020 through April 21, 2020.
20.5 Release: The B2C Commerce 20.5 release occurs April 16, 2020 through May 28, 2020.
20.6 Release: The B2C Commerce 20.6 release occurs May 18, 2020 through June 25, 2020.
20.7 Release: The B2C Commerce 20.7 release occurs June 23, 2020 through July 23, 2020.
20.8 Release: The B2C Commerce 20.8 release occurs July 21, 2020 through August 20, 2020.
20.9 Release: The B2C Commerce 20.9 release occurs August 18, 2020 through September 24, 2020.
24.10 Release: The B2C Commerce 24.10 release occurs October 01, 2024 through October 31, 2024.
24.6 Release: The B2C Commerce 24.6 release occurs May 21 , 2024 through June 27, 2024.
24.7 Release: The B2C Commerce 24.7 release occurs June 25 , 2024 through July 25, 2024.
24.8 Release: The B2C Commerce 24.8 release occurs July 23 , 2024 through Aug 22, 2024.
24.9 Release: The B2C Commerce 24.9 release occurs August 20, 2024 through October 03, 2024.
Add Checkout Links to Facebook and Instagram: Meta retired on-site checkout on Facebook and Instagram in September 2025. To send shoppers to your website to complete purchases, add checkout links.
Audit Product Changes in a Live Storefront: View the change history for B2C Commerce objects, such as products, prices, and content assets, in a production instance. Previously, change history recorded events only in a staging instance.
Enhanced Category Assignment Control in Page Designer: Page Designer now offers merchants greater flexibility when assigning landing pages to categories. Previously, assigning a page to a top-level category automatically included all sub-categories, which often required custom development to override. With this new enhancement, merchants can now choose whether to include sub-categories when creating or editing page assignments. This feature allows for more targeted and personalized customer experiences without the need for developer intervention.
Copy Components in Page Designer: Create components once and reuse them across multiple pages by copying up to 10 components. You can paste a copied component into any region or component that accepts it. Copying components helps ensure consistent site-wide experiences when building Page Designer pages.
Customize User-Agent Logging for CSRF Security: Meet compliance requirements and strengthen security monitoring by customizing User-Agent logging strings during Cross-Site Request Forgery (CSRF) token validation. Previously, strings longer than 32 characters were truncated. Now, you can increase the number of characters to capture more detail. You can also turn off logging entirely or set the number of characters to less than 32 to balance storage efficiency with detail.
Push eCDN Log Events to More Storage Services: You can now use the CDN-API to send HTTP requests, Firewall, and Pageshield events to these destinations for immediate log visibility: AWS S3 bucket, Azure, Datadog, Google Cloud Storage, HTTPS, Kinesis, and Splunk.
Access eCDN Logs in Log Center: The log center includes eCDN error logs, including HTTP status codes 502-530, for proxy zones on B2C Commerce Production instances. Use these logs to monitor site performance and security.
Set Reply-To Header for Email Messages: Control where email replies are sent by setting the Reply-To header using the new addReplyTo method in the dw.net.Mail class. This allows recipients to reply to a different address than the sender, such as replying to a support team address when the From address is a no-reply address.
Add Unsubscribe Headers to Email for Mailing List Compliance: Add List-Unsubscribe and List-Unsubscribe-Post headers to emails sent using the dw.net.Mail class to support compliance with email provider guidelines, including Google Sender Guidelines. Use the new setListUnsubscribe and setListUnsubscribePost methods to integrate with externally-managed mailing lists and enable one-click unsubscribe functionality.
Configure Page Designer Fingerprint Caching with TTL Control: Configure how long Page Designer fingerprints are cached by setting the Time to Live (TTL) value. This enhancement enables fingerprint caching for pages and components with schedule-based and locale targeting visibility rules. A Page Designer fingerprint identifies which version of a page to display based on its visibility rules and targeting configuration.
Improve SEO with Host Header Override Rules: Support a single hostname across multiple realms by creating a Host Header Override Rule for sites that use an external content delivery network (CDN). This rule replaces unique hostnames with a common hostname to maintain the single-hostname setup. Maintaining a single hostname improves SEO for your site.
Merge Baskets Consistently with One Script: Use the same merge script across controller and REST API implementations by invoking the new dw.order.mergeBasket business hook. Invoke the hook by using either the transferBasket endpoint and the merge=true parameter or the HookMgr in a controller. The dw.order.mergeBasket business hook unifies discrepancies between controller and REST API merging strategies. Replace your previous merging methods with the new business hook.
Improve Image Performance with Modern Formats: Upload AVIF and WebP images to your store’s Dynamic Imaging Service (DIS) for smaller file sizes and faster loading times. Most major browsers support these modern image formats, which provide a better user experience and enhanced image quality.
Notify Shoppers When a PayPal Order Needs Reapproval: Create a localized, personalized message to inform shoppers when an approved PayPal order amount increases and requires reapproval. Previously, a default message appeared if a payment amount needed reapproval.
Find Pages Faster with Improved Page Designer List: The Page Designer page list now includes enhanced search, sort, and filter capabilities to help you quickly locate the pages you need to manage. These improvements reduce the time spent navigating through large page collections and improve merchant productivity.
Automatically Cache Non-Customized Pages for Better Performance: Page Designer now automatically caches pages that don't use custom serialization logic, improving runtime performance. When a page doesn't have a custom serialize() function, the system caches its content for a configurable period.
Set Up Page Shield Policies with Business Manager: Page Shield policies make PCI 4.0 compliance easier and ensure that only trusted scripts run on sensitive pages, such as cart and checkout. Previously, you could configure the policies only with the Content Delivery Network (CDN) Zones API.
Make Targeted Price Adjustments Within Individual High-Scale Price Books: Adjust prices within a specific price book without having to replicate all price books. Previously, you had to replicate all high-scale price books when moving from a staging to production or development instance. Now you can make targeted pricing changes to your production data for multiple regions.
25.10 Release: The B2C Commerce 25.10 release occurs between September 23 and November 04, 2025.
Enable Optional Request and Response Logging for HTTP Calls: Control request and response logging for outgoing service calls by enabling the Communication Log setting for individual services. When enabled, this feature logs request and response details including headers. This feature provides enhanced visibility into external service communications and helps you validate authentication headers and troubleshoot integration issues.
Help Shoppers Find More Product Options: The Show More feature helps shoppers find additional product options matching the search criteria, if there are more than three results displayed in the Shopping Agent search results. This feature allows shoppers to easily discover a wider variety of relevant products and compare them so they make the best purchasing decision.
Improve Guided Shopping with the New Agent Template for B2C Commerce: The new agent template includes more topics and actions for B2C Commerce shoppers. The Agent’s product search capabilities now include images, rich content, category and facet filters, and multiple languages. Also, visual components are available for carousels, product details, cart, and order confirmation.
Manage Cipher Suite Settings via CDN-API: Customers can now retrieve and update cipher suite settings for their zones via the CDN-API, ensuring better control over security configurations. This feature allows businesses to define which TLS ciphers browsers and devices can use when connecting to their storefronts, enhancing security and compliance.
Debug Page Designer Page Caching in the Browser Developer Console: Use the Page Designer component’s caching details to find and resolve page caching problems. Access the browser developer console from within Page Designer. For example, if you use Google Chrome, go to View | Developer | Developer Tools | Console.
Enhance eCDN Settings for Clearer Certificate Management: The Business Manager eCDN Settings page is improved to clearly distinguish between hostnames with and without custom hostname certificates, reducing customer confusion and improving usability.
Use Granular Replication to Target Specific Content Assets: Use the granular replication feature to select specific content assets for replication from staging to production. This feature allows for targeted updates, ensuring your production data remains current without full-scale overhauls.
25.2 Release: The B2C Commerce 25.2 release occurs January 23, 2025 through February 27, 2025.
Upgrade to eCDN with WAFv2 for Enhanced Security: Salesforce B2C Commerce now integrates eCDN with WAFv2, offering advanced security features to protect your zones. This update includes OWASP ruleset updates, managed rules, and exposed credentials checks, ensuring better threat detection and reduced false positives.
Augment the Customer Shopping Experience with an AI-Powered Assistant: Agentforce for Guided Shopping helps your store’s customers find the products they need to make informed purchase decisions. The generative AI-powered agent provides personalized, real-time guidance throughout the shopping journey, from product discovery to checkout and retrieving order details.
Configure PCI 4.0 Compliance with eCDN PCI Tools: The B2C Commerce eCDN PCI tools now include Page Shield. Page Shield helps you manage resources loaded by your website visitors. Your security team is notified with an alert when a script is changed or is flagged as malicious. You can also access policy violations via LogCenter and stream using logpush.
Stream Security Logs for Enhanced Monitoring: Log Center now supports streaming security logs to third-party aggregation tools like Splunk, Datadog, New Relic, Grafana Loki, or a generic HTTP connection. This integration enhances your monitoring and automation capabilities, ensuring better security and compliance.
25.3 Release: The B2C Commerce 25.3 release occurs February 25, 2025 through March 20, 2025.
Provide a Reason for Restarting Your Commerce Cloud Instance: B2C Commerce Control Center now requires you to enter a reason when you initiate the restart of a B2C Commerce instance. Reasons are recorded to help improve the reliability of our infrastructure.
Set Authorization Methods for Password-Protected Storefronts: Business Manager administrators now have more options for managing access to a password-protected storefront. Administrators can select, the authentication method that’s best suited for their storefront.
Business Manager UI in Polish: The Business Manager user interface is now available in Polish. To choose this new language, select the respective value in the dropdown in your user profile settings.
Ingest Engagement Events from B2C Commerce into Data Cloud: You can now ingest storefront engagement events, such as product impressions, wishlist activity, and page views, into Data Cloud using the Web and Mobile App connector. The connector works with B2C Commerce storefronts built on SFRA, Sitegenesis, or PWA. You choose which type of engagement data to send to Data Cloud.
Manage Routing Rules in Business Manager: Starting with Business Manager version 25.4, you can now manage routing rules for forwarding composable storefronts directly from the Business Manager UI. This update simplifies the process of managing routing rules, making it easier to optimize traffic and improve the performance of your composable storefronts. It reduces the need for manual configuration and provides a more intuitive interface for managing your zones.
Get Near Real-Time Segmentation with Data Cloud: B2C Commerce storefronts can now leverage customer segments created in Data Cloud on a near real-time basis, eliminating the need for batch activation. With up-to-date customer segments, your storefronts can provide timely, personalized, and targeted shopper experiences. This feature is generally available in the 25.2 release.
Optimize Your Site URLs for Better SEO: You can now change URL preference values from slash (/) to hyphen (-) and improve the redirection of product and content links.
25.4 Release: The B2C Commerce 25.4 release occurs March 25, 2025 through April 24, 2025.
Search and Select Sites Quickly in Business Manager: Use the new Select a Site feature to navigate through a large number of sites, and find the specific site you need. Select a Site is located in the Business Manager left navigation. Start typing the name of the site you are looking for, and the results field display matching results, including partial matches.
Control Store Inventory Indexing for Shop the Store: Pilot customers using the Shop the Store capability can now control indexing of store inventory data at the site level. Use the indexing on a site feature to select which store inventories are included in search and browse routines. This makes search results more useful for shoppers and improves their experience.
Update Currency Precision for Better Global Business: B2C Commerce updated the precision of several currencies to align with the latest international ISO standards. This ensures more accurate financial transactions and reporting for your global business.
Ensure Secure API Responses for Unauthenticated Requests: We've updated the authentication handling for the GET/sandboxes and POST /realms/usages ODS API responses. The responses now return a 401 unauthorized status code with a structured error response for unauthenticated requests. This change enhances security and aligns with standard HTTP practices.
Control Proration Logic for BOGO Promotions and Bonus Products: We have added two new preferences in Business Manager to give you more control over the proration logic for BOGO Promotions and Bonus Products. These preferences ensure consistent discount handling and proration across your promotions.
25.5 Release: The B2C Commerce 25.5 release occurs April 22, 2025 through May 22, 2025.
Ensure Accurate Custom Attribute Values with Language Fallback: We updated MultiValueCustomAttributes to respect your language fallback settings. Now, if a custom attribute is requested in a language without a translation, and fallback is disabled, no value is returned. This ensures data accuracy.
Ensure Accurate Page Previews with Enhanced Hostname Handling: To generate accurate preview links, Page Designer now considers all configured hostnames in the Alias file. This avoids Cross-Origin Resource Sharing (CORS) issues with AJAX calls, and ensures that your storefront previews are reliable, consistent, and reflective of the live storefront experience. Previously, Page Designer used only the https-host from the alias file in Business Manager to decide which hostname to use for the preview link.
Updates To OCAPI and SCAPI APIs: This release introduces several enhancements to the Open Commerce API (OCAPI) and the Storefront Commerce API (SCAPI) to improve performance, and enhance developer experience.
Enhance Business Manager Efficiency with the New User Interface: The new Business Manager user interface (UI) is now the Business Manager default UI. The new UI provides a modern and efficient interface for administrators, merchandisers, and other Business Manager users. If needed, you can switch back to the classic UI by updating the UI preference. In Business Manager, select My Profile > Preferred UI style: Classic.
Track Category Assignments in Change History: Use Business Manager's Change History to track assignments between storefront categories and sorting rules. This additional change history gives you a complete record of all changes. Now you can easily manage and audit your storefront configurations. Previously, category assignments to sorting rules were tracked in campaigns or AB-tests.
Optimize Page Designer Performance with Fingerprint Caching: Use a new caching mechanism for the fingerprint calculation in Page Designer. This change significantly reduces the load time for pages and components without visibility rules, enhancing the overall user experience.
25.6 Release: The B2C Commerce 25.6 release occurs May 15, 2025 through Jun 28, 2025.
Secure Your Business Manager Import Export Access: Use the new Access_Customer_and Customerlist_Impex permission to restrict access to the customers and customer list in the Business Manager Import and Export module. The new permission is a site-specific functional permission that enhances data security and compliance. Now, only authorized users can import and export data.
Access Control Center Audit Events in Log Center: As of June 2025, you can view Control Center audit events in Log Center, which offers a centralized location for log management. Access to audit events directly from Control Center will be phased out, but for backward compatibility, it will remain available until February 2026. After this date, the Audit Logs button in the Control Center UI will be removed, and Log Center will be the sole location to access these events.
Configure Brotli Compression Speed in Business Manager: Business Manager now offers Brotli Compression speed settings, which simplifies managing and optimizing static web assets. This update ensures smaller payloads and faster delivery times, enhancing the overall user experience.
Disable the Deprecated Storefront Toolkit: To enhance security and the user experience, we now disable the deprecated Storefront Toolkit by default for new sites and imported sites. For existing sites, the behavior remains unchanged, but we recommend transitioning to the new Storefront Toolkit for enhanced functionality and support.
Manage WS-Security Keys and Certificates in Business Manager: Now you can manage WS-Security keys and certificates directly in Business Manager, making it easier to maintain different keys across various environments. This update simplifies key management and enhances security.
Migrate V1 Zones to V2 Zone Configurations for Enhanced Security and Performance: Salesforce B2C Commerce now supports migrating deprecated proxy V1 zones to current V2 zone configurations in Business Manager. This update provides better security and performance, especially for ghost routing and traffic splitting scenarios.
25.7 Release: The B2C Commerce 25.7 release occurs June 24, 2025 through Jul 24, 2025.
Test and Refine Store Inventory Searches in Business Manager: Pilot and beta users of Shop the Store can lookup store inventory information in the Search Index Query Testing (SIQT) tool. You can add up to 10 store inventory list IDs to the inventory field in the SIQT tool. The increased number of inventory list IDs returns more accurate and relevant search results.
Speed Up Catalog Data Replication: Configure your data replication processes to replicate only catalog data and exclude static content such as images. This configuration reduces replication time, especially for large catalogs.
Filter Testing IP Addresses from Reports and Dashboards: Internal performance and load testing tools can contaminate the data you see in Reports and Dashboards, making it difficult to distinguish between generated traffic and actual customer behavior. You can now specify IP address ranges to filter out traffic from your internal testing tools, ensuring your analytics reflect genuine customer interactions.
Use 3rd Party IDP Logins and Social Logins with Hybrid Authentication: Hybrid Auth now supports all 3rd Party IDP logins and Social logins via PWA or SFRA when you configure SLAS as the 3rd Party IDP. This allows you to quickly and securely log in to your Hybrid storefront. This support is added for SLAS private and public clients.
Use Refresh Token Cookie TTL Overrides with Hybrid Authentication: Hybrid Auth now supports the ability to override refresh token cookie time to live (TTL), allowing you to control when a persistent session expires. You can configure different TTL overrides for guest shoppers and registered shoppers. When you use this feature, also apply the same refresh token cookie TTL override setting for PWA Kit.
B2C Commerce Intelligence JDBC Driver Now Generally Available: Access your B2C Commerce Intelligence data lakehouse directly through SQL queries with the new Commerce Intelligence JDBC Driver. This driver enables seamless connectivity to your B2C Commerce data for advanced analytics, reporting, and custom integrations to third-party Business Intelligence tools of your choice.
Script API JSON Web Encryption (JWE): The Script API for JSON Web Encryption (JWE) now supports both encryption and decryption operations. Previously, it only supported decryption. This enhancement enables developers to encrypt sensitive data before sending it to third-party services, improving security and expanding integration capabilities. Additionally, a new CertificateUtils API simplifies working with external certificates, including JSON Web Key (JWK) format certificates, making certificate management more straightforward.
Increase Flexibility with Relaxed Locking Rules for Inventory Import: Previously, inventory imports locked inventory globally for the duration of the import. Now, only the inventory list that’s currently being imported gets locked. The attempt to lock the inventory import has a timeout of ten seconds. After ten seconds, the import attempt is aborted if a different process locks the inventory list. This change enhances system flexibility and efficiency by minimizing locking contention when updating inventory imports and Data API concurrently.
Analyze Your B2C Store Performance Using the Metrics Dashboard: Use the Metrics Dashboard to monitor your B2C Commerce storefront performance, security, and resource utilization. The dashboard improves developer productivity, reduces mean-time to resolution, and streamlines troubleshooting. The metrics that you can monitor include metrics for application performance, sales, embedded content delivery network (eCDN), B2C Commerce API (SCAPI) and SCAPI hooks, and Managed Runtime.
Enhance Shoppers' Experience With Accurate Inventory Data for In-Store Pickup (Beta): Display near real-time, accurate, and reliable stock information to your shoppers by managing your in-store inventory with Omnichannel Inventory. Using this inventory information, shoppers can more reliably shop online and pick up purchases in store.
Elevate Store Search with the Upgraded Search Engine: Improve product search, sorting, and ranking with the latest search engine. Give shoppers more control over the search experience, with enhanced security and refinement calculations.
Simplify Product Category Assignments: Product categories are now displayed in alphabetical order, by Category ID. Previously, the order of categories varied, leading to an inconsistent experience.
Strategize Promotions More Efficiently with Discounts: Set the maximum number of product and order promotions and the maximum discount allowed per cart. This increased flexibility makes it easier for B2C merchants to plan promotion strategies.
25.8 Release: The B2C Commerce 25.8 release occurs from July 22, 2025 through August 21, 2025.
Get Better Predictability of Your Service Profile Import: Previously, when you imported a service profile with a circuit breaker turned on but no call or interval values set, the values were set to 120 calls and 20000 milliseconds by default. Now both values are set to 0 by default.
Manage SVG Images More Efficiently: Scalable Vector Graphics (SVG) files are now supported as thumbnails in Business Manager. You can quickly identify and select the desired SVG file without needing to open or preview each image individually.
Manage A/B Tests More Efficiently with the New User Interface: Use the quick filters in the new A/B test interface to sort and manage A/B tests. Find the best- performing segments by scanning visual indicators. The new interface also includes clipboard functionality so that you can copy test results for further analysis. Test data is displayed if at least one data point is available in every test segment.
Identify Concurrent Modification Issues During Order Export: An alert now appears in Business Manager to inform you if another process is concurrently modifying the order during the export process. The alert helps you proactively identify when processes lead to order export data being out of sync or exported twice. To minimize the risk of another process modifying orders during export, you can delay order exports.
Simplify Coupon Management by Sharing Coupon Codes Across Sites: Share system-generated coupon codes across multiple sites. If a customer redeems a shared code on one site, that code can't be redeemed on another site unless it’s set to be redeemed more than once. You can import and export shared coupon codes, and you can set site-specific redemption limits.
Service Credentials Are Encrypted During Import and Export: Service credentials are now encrypted, instead of masked, during a service export when using Site Import & Export under Site Development. You can also import service credentials back if needed using the same method. Previously, service credentials were encrypted only when exported via Import & Export under Operations.
Connect More Effectively to Sandboxes: Now when you log in to sandboxes using OAuth, you don’t experience Connection Reset errors. With these errors eliminated, you can more reliably authenticate, improving your user experience.
Establish Security Compliance with an Outbound Connections Allowlist: Gain greater security and control over outbound connections. The new Outbound Connections screen in Business Manager lists recently used endpoints that you can select from. You can also configure new endpoints and add them to your allowlist. Connections defined under Service credentials are automatically allowed from the B2C Commerce platform.
Identify Scalability Issues with Multi-Order Transactions: An alert now appears in Business Manager to inform you if a custom job is changing multiple orders per transaction. The alert helps you proactively identify the issue and appears hourly until you resolve the issue. Review the source code in your custom job script to make sure that the custom job only changes one order per transaction. After you resolve the issue, the alert disappears within a day.
25.9 Release: The B2C Commerce 25.9 release occurs between August 19, 2025 and September 25, 2025.
Enhance Product Discovery in Your B2C Store (Generally Available): Elevate your shoppers' experience by merging online and in-store experiences, connecting shoppers to your stores and boosting sales. Shoppers can now discover in-store products when searching the online store and pick-up from their preferred store location. This feature, which is now generally available, includes some changes since the pilot release.
Help Shoppers Find the Best Deals: Shoppers can now sort prices by quantity or size to find the lowest price for a product. Add Unit Quantity and Unit Measure for each product. Then with these new sorting options, shoppers can identify the most affordable products.
Add Adyen as a Salesforce Payments Option: Integrate your existing Adyen merchant accounts into Salesforce Payments for B2C Commerce. Unify payment processing by managing all your accounts natively within Salesforce.
Manage eCDN Rate Limits in Business Manager: You can now configure and manage embedded CDN rate limits directly in Business Manager. Previously, these settings were only accessible via the CDN Zones API. Use the intuitive interface to adjust rate limits quickly, optimize performance, and ensure compliance with traffic management policies.
Streamline Subdomain Management with Wildcard Custom Hostnames: You can now use a single wildcard configuration in eCDN to cover multiple subdomains. For example, setting up *.merchantsite.com manages hostnames like shop.merchantsite.com and blog.merchantsite.com. This reduces the overhead of managing multiple custom hostnames.
Automatically Recover Inventory Availability After an Interruption: Omnichannel Inventory now triggers a recovery when a data stream interruption is detected, thus preventing gaps in availability updates. The recovery uses one of the two simultaneous export slots. If you use custom processes for full Omnichannel Inventory availability exports, review potential resource contention.
Get Consistent Storefront Preview URLs: Storefront preview URLs from Business Manager are now reliable and reflect the live storefront experience. The preview URL is generated based on the vanity hostname defined as the SEO alias instead of using the generic hostname. This improved consistency also applies to previews generated from the list and detail pages for Product and Content in Business Manager.
26.1 Release: The B2C Commerce 26.1 release occurs between December 4, 2025 and January 29, 2026.
Help Shoppers Find Products Faster with Guided Questions: Streamline the shopping experience with intelligent, guided search options. The B2C shopping agent prompts shoppers with relevant search results and follow up questions, leading shoppers to find the right product faster. For example, if a shopper searches for running shoes, the agent displays a list of running shoes and then asks follow-up questions based on the surface type, such as trail, road, or track.
Guide Shoppers to Manually Add Coupons: The B2C guided shopping agent now helps shoppers manually apply coupons to the cart and clearly shows complex discounts in the cart summary and order confirmation pages. To enable the B2C Commerce Coupon Management agent topic, contact your Salesforce account executive.
Launch Agentforce for B2C Commerce from More Places in Your SFRA Storefront: Give your customers more ways to chat with the Shopping Agent for B2C Commerce by selecting different launch locations. Add agent access from an icon in the site header, from a shopper's search suggestions, or a floating icon at the bottom of each storefront page.
Access Site Controls from the Administration App: Access the Site Selector, Storefront Preview, and Toolkit controls directly from the Administration app in Business Manager. You no longer need to switch to the Merchant Tools app, making it easier to preview your storefront and complete other site management tasks.
Access Developer Documentation in a Unified Location: In response to your feedback, we have combined the developer documentation for B2C Commerce, B2C Commerce API (SCAPI), and Composable Storefront into a single table of contents. You can now find what you need faster without switching contexts between product guides. A centralized API reference page also provides a single starting point for technical specifications.
Track B2C Shopping Agent–Assisted Revenue for SFRA Storefronts: See the orders and revenue that are directly attributed to the B2C Shopping Agent on B2C Commerce Reports and Dashboards. Estimate the return on investment contributed by the agent, and make informed decisions on how to use agent capabilities. Shopping Agent data is available on the Home, Sales, Products, and Promotions tabs.
Exit Business Manager Sessions Without Auto Reauthentication: You are no longer automatically logged into Account Manager or Business Manager again to reauthenticate when you end a session. Previously, accounts linked to Salesforce were automatically reauthenticated, making it difficult to exit the application if you're using unified authentication.
Gain Instance-Level Control Over On-Demand Sandbox Availability: For flexible and cost-effective sandbox management, create schedulers for individual on-demand sandboxes (ODS). Instance-level schedulers control when an on-demand sandbox instance stops and starts, so you can configure sandbox availability based on usage patterns. Individual instance schedulers override any realm-level schedulers.
Launch the Shopping Agent from Two Places in Your PWA Kit Storefront: Give your customers more ways to chat with the Shopping Agent for B2C Commerce. A floating icon appears by default at the bottom of each page. You can also add an icon in the site header for agent access.
Ingest B2C Commerce Domain Data into Data 360 Using Apache Iceberg: Use the Apache Iceberg File Federation connector to ingest B2C Commerce domain data—including products, orders, customer profiles, and custom attributes for products and customer profiles—into Data 360.
Choose Which Page Designer Pages to Replicate: Replicate specific Page Designer pages instead of an entire library. Push critical content updates to production faster by running smaller, more targeted replications multiple times a day without the expense and complexity of a full data replication.
Component Icons Removed from Page Designer: Page Designer no longer shows component icons in the component palette, page structure panel, or the window for adding components. This change provides a cleaner, more streamlined interface.
Prefill Shipping and Payment Information to Streamline Checkout: In the createBasket and transferBasket endpoint of the ShopperBaskets API V2, set the new populateCustomerDetails query parameter to true to prefill a shopperʼs information during checkout. This setting invokes the new dw-order.populateCustomerDetails business hook, which populates the basket with the registered shopperʼs default or first saved address and payment information. You can also customize the business hook.
Specify Enhanced Domain Names In Account Manager: You can now configure Identity Federation with Salesforce Identity in Account Manager using supported enhanced domain names. You can specify the organization MyDomain subdomain name in Salesforce Core. The default domain suffix is my.salesforce.com. If the identity federation is allowed or enforced, you can change the value. For example, if you use a Salesforce Core sandbox, you can use sandbox.my.salesforce.com as the domain suffix.
Tenant specific Rate Limiting for Account Manager Remote Procedure Call (RPC) Traffic: Commerce Cloud Account Manager now enforces a new tenant specific rate limit for RPC traffic. OCAPI Shop and Data API calls generate RPC traffic on a POD. The New rate limit is enforced on a per minute basis. This provides all B2C Commerce users on the same POD an equal share for RPC traffic.
Switch to JWT Access Tokens: Starting Thursday, June 28 2023, Salesforce will no longer support the use of UUID token formats for API Clients in Commerce Cloud Account Manager. New API clients now only support the JWT access token format.
Allow Duplicate Terms in Search Phrases: B2C Commerce search now accepts long-tail search phrases with duplicate search terms. When an exact match for a given phrase is found, the suggestion processor returns highly relevant search results. Previously, duplicate words in long-tail search phrases were autocorrected to slightly different versions. Autocorrecting terms in the search phrase can result in irrelevant search results.
Updated API Client List Page: With the addition of two new columns and filters, the Account Manager API Client List page is now easier to use.
New Multi-Factor Authentication Error Message: During multi-factor authentication (MFA), when a user tries to Log in with an insecure Device, Account Manager displays the following prescriptive error message: Your log in request can't be completed. Set PIN, pattern or passcode to secure your mobile device and try again.
Gain Visibility into Instance Filters for All User Accounts: All users can view the instance filters that are applied to their Account Manager user roles in their account profile. Instance filters limit a role's scope to specific Business Manager instances. Previously, this information was visible only to account administrators.
Use the Last Log In Date to Track User Activity: The Account Manager User Detail page now displays the user's last log in date. Admins can use this date to track user activity and identify inactive users.
Ensure Account Access with One-Time Passwords as Multi-Factor Authentication Fallback: If service issues prevent the use of multi-factor authentication (MFA), you can log in using a time-based one-time password (TOTP) from a registered authenticator app. This fallback option ensures that you maintain access to B2C Commerce applications and works with your registered Salesforce or third-party party authenticator apps. To use this fallback option, make sure that you register at least one authenticator app that supports TOTP.
Link Account Manager Account for SSO without MFA: New Account Manager users can now use using their Account Manager username and password to link their account with Salesforce Identity or a third party IDM (for example, OKTA) for SSO/federation. Previously, users were required to use multi-factor authentication (MFA) to link to Salesforce Identity or a third party IDM for SSO/federation.
Add Description of API Clients: When configuring API clients, you can now add additional description and details about the API clients. The new description field is limited to 256 characters.
New Reminder to Remove Role-Tenant Filters: When you remove an organization from a user detail page, a warning is now displayed as a reminder to remove all role-tenant filters belonging to the organization. If the role-tenant filters are note removed, the user retains access to them.
Prevent Org Invitations to Deleted Users: You can no longer add deleted users to an organization. Attempts to add a deleted user returns the following error message: Only enabled users can be invited into an organization.
Improve Security and Authentication Success with API Client Public Key Validation: Account Manager now verifies the Client JSON Web Token (JWT) Bearer Public Key field in API client configurations to prevent authentication failures and improve system security. You can input a PEM-formatted certificate or a Base64-encoded RSA public key (for B2C Commerce only), with or without headers. The system checks for correct formatting and valid cryptographic material. You can still create API clients without JWT public keys if public keys aren’t needed for your use case.
Delegate User Management with the User Administrator Role: Secure your organization by granting the new User Administrator role to support staff who manage user accounts. This role permits users to add, invite, and delete users, reset passwords, and manage organization assignments without full administrative access. This least-privilege approach improves security and compliance by only giving users the permissions necessary for their specific duties.
Auto-Renew Up to 500 eCDN Certificates per Zone: Simplify your annual eCDN certificate renewal process by using Business Manager or CDN-API to auto-renew up to 500 certificates per zone. Previously, you could renew only 50 certificate at a time. When you create a CDN zone in a development, staging, or production instance, select eCDN Managed certificates.
Boost Web Store Speed with Argo Smart Routing: Salesforce now makes your web store even faster with Argo Smart Routing. Argo uses real-time global network data to route traffic around issues like brownouts, cable cuts, and packet loss, and move traffic along faster routes. This reduces HTTP time to first byte (TTFB) by an average of 30%, making your web store faster and more reliable for users. Argo is implemented for you. No action is required from you.
Code Profiler Wait Times Removed from CSV Report: Code profiler wait times, which include Wait Time Own and Wait Time Total, are no longer measured. These values have been removed from the B2C Commerce CSV report. The CSV report remains backward compatible.
Get Smarter Business Insights with Commerce Intelligence (Pilot): Take a deep dive into customer behavior and key business metrics with Commerce Intelligence dashboards powered by CRM Analytics and Data Cloud. Use the Product Intelligence dashboard to understand the best and worst selling products, categories, and their trends over time. Delve into customer insights like number of active customers, average order value, and segmentation with the Customer Lifetime Value dashboard.
Create Active Data Sorting Rules: The Search Index Query Testing (SIQT) tool now supports sorting rules with active data sorting attributes. Get consistent sorting results in a storefront and when testing an active data sorting rule. Previously, if a sorting rule with active data was used in SIQT, the sorting used text relevance and didn’t consider active data.
Customize Your Search Index Rebuild Schedule: Enhance your site’s search functionality by specifying on which days to rebuild your search indexes. Previously, you could schedule rebuilds only on a daily, weekly, or monthly basis.
Scheduled Backups Button Is Disabled: The Scheduled Backups button is no longer available. Instead, use a custom job to schedule backups of your production and development environments.
Migrate Your Zones to eCDN with WAFv2: Salesforce B2C Commerce now uses eCDN with WAFv2. WAFv2 brings advanced security features to safeguard all your zones, both existing and new. You can migrate your existing customer zones from WAFv1 to WAFv2 as a self-service option. You can configure eCDN WAFv2 settings directly through the Business Manager UI or CDN Zones API for new zones. In addition, eCDN with WAFv2 integrates ruleset enhancements that improve firewall security and reduce false positives, improving threat detection accuracy and minimizing disruptions to normal operations.
Get AWS SFTP Stability with Automatic Timeout Adjustment: B2C Commerce now boosts the efficiency of SFTP transactions on AWS by preventing prolonged connection times. To mitigate issues related to delayed server responses, the timeout setting for an AWS SFTP connection now has a minimum threshold of 10 seconds.
Enhance Global Collaboration with Time Zone-Specific Scheduling: Improve shared task coordination among your globally distributed teams by setting on-demand sandbox (ODS) schedulers to local time zones. This feature defaults to the user's local time zone upon login but provides flexibility to change and save this setting as needed.
Get Better Null Basket Handling for Seamless Shopping: We improved how null baskets are managed in the cache. If the storefront basket isn’t available or is null in the cache, it’s loaded from storage using the ORM primary key access. Only valid baskets are considered to make the shopping experience smooth and uninterrupted.
Enhance Origin Performance and Security with Advanced Protocols: Boost your content delivery with the integration of Early Hints, HTTP/3, and HTTP/2 to Origin. These protocols reduce performance lag and enhance security, ensuring faster and safer data transmission. To optimize your service delivery, configure these settings using CDN-API or Business Manager.
Search Engine Provides Better Performance: The search engine that provides results for OrderMgr.searchOrder(s) has been updated across multiple instances. This update is aimed at enhancing the performance of the search engine. No user impact or behavioral change is expected.
Experience a More Efficient Workflow with the Control Center Lightning UI: The updated Control Center UI now aligns with Salesforce Lightning Design System (SLDS) standards. This update enhances the user experience with a more consistent design. Users can still access the same workflows while enjoying a refreshed interface. The new Lightning UI is the Control Center default option and is widely used by the majority of customers. Except for the audit logs, this update removes all links to the Classic UI.
Search Response Times Are Quicker: B2C Commerce has improved the performance of the common category lookup in storefront search and search refinement. Based on internal testing, the search engine calculates search refinements two times faster. With improved search, your users experience faster storefront response times, providing a smoother browsing experience.
Faster Stores Page Performance: B2C Commerce has significantly improved the performance of the Stores page in Business Manager. Users now experience much faster load times when searching for stores and viewing search results. This enhancement makes it easier and more efficient for merchandisers to manage, search, and update stores within the Business Manager module. Previously, users encountered performance issues when displaying 200 results per page in the Business Manager store module.
Get Better SEO Search Results: In Business Manager, the Catalog URL rules now use the localizable display value for product attributes with the type Enum of String. The localizable display value improves readability and the SEO value of storefront URLs that use multiple languages. Previously, Product URL attributes used the non-localizable Value.
Use Bots for Product Recommendations: Offer your shoppers bots that provide multichannel conversational product recommendations and add products to the cart with the new Commerce Concierge for B2C Einstein Bot template. Create an enhanced bot from the template and connect your store to a new Einstein bot. You can also use the new Commerce Concierge bot blocks to add functionality.
Implement Enhanced Security Controls in Commerce Cloud: As announced in the 24.7 release notes, B2C Commerce now prevents traffic that doesn’t originate from Commerce Cloud eCDN from accessing hyphenated demandware.net host names, such as staging-xxx.demandware.net, to the Open Commerce API (OCAPI) or Storefront. Traffic through demandware.net doesn’t have eCDN controls in place, posing a potential risk to your data security. Origin Shielding for staging makes sure that all external traffic goes through the eCDN security layers before reaching your environment. The introduction of Origin Shielding for staging impacts Commerce Cloud customers who have implementations that involve direct calls to POD IPs.
Implement Enhanced Security Controls in Commerce Cloud: Commerce Cloud is implementing a new security measure that blocks traffic to staging instances that doesn’t originate from Commerce Cloud eCDN from accessing the hyphenated demandware.net hostname. This change rejects all calls using hyphenated hostnames, such as staging-, to access the Open Commerce API (OCAPI) or Storefront.
Import and Export Dynamic Categorization Rules: In Business Manager, easily import and export dynamic categorization rules, including the excluded product list. The Catalogs Import & Export feature now updates the catalog.xsd schema with detailed information on categorization rules and excluded products within the catalog tag structure. Previously, you couldn’t import and export the dynamic categorization rules.
Import External Coupon Redemptions: You can now update the status of a coupon redeemed outside of B2C Commerce using the new Coupon Redemption API (/organizations/{organizationId}/coupons/actions/redeem). To identify the source of redemption for an external coupon, use a custom reference ID or any custom string. You can also add an optional email address to the redemption for further tracking and communication. To update multiple coupon redemptions at one time, use the new ImportCouponCodeRedemptionsStep job step. This bulk import, which works only in merge mode, streamlines the process of managing multiple redemptions at scale.
Get Improved Search Index Performance: B2C Commerce has updated the search index rebuild process. The update decreases resource usage and improves performance, and an unchanged index is no longer published when no changes are detected. Previously, a redundant product update index task was executed following the index rebuild, and a new search index was published when no documents were altered.
LINK Marketplace Retirement: The LINK Marketplace is now retired. To help you extend B2C Commerce, we’ve migrated all apps from the LINK (B2C Commerce) marketplace to AppExchange – made up of cartridges and headless integrations. The AppExchange is now the sole Salesforce marketplace for B2C Commerce Integrations. B2C Commerce independent software vendor (ISV) partner cartridge code has been removed from Salesforce GitHub repositories, and the LINK Program has officially concluded.
Make Product and Price Book Updates with Granular Replication: Use the granular replication feature to select specific products and price table entries for replication from staging to production. This feature allows for targeted updates, ensuring your production data remains current without full-scale overhauls.
Successful Jobs Are No Longer Logged: To increase the efficiency of log volume, successful job steps for custom and global jobs with dedicated log files are no longer logged in the global job log file, or Log Center. You can still review successful job steps in the dedicated log file.
Enhance your Business Manager Workflow with the New User Interface: B2C Commerce Business Manager has a new user interface (UI). The UI is available as an Open Beta. This new user experience for our merchandising tool introduces a fresh design and enhanced usability based on extensive research, industry standards, and valuable feedback from our customers and partners.
Improve Search Results with Autocorrection: Enable search to process configured synonyms when autocorrecting or autocompleting a user’s search phrase. If the original phrase matches the synonym entries, search includes the synonyms. When search autocorrects a phrase, it considers both the original phrase and the autocorrected version. Previously, if a phrase was autocorrected or autocompleted, synonym group matching on the initial search phrase wasn’t considered.
View Available Meta API Versions in OCAPI Explorer: The Meta API call in the Open Commerce API (OCAPI) Explorer now returns the available Meta API versions instead of an empty JSON response. The OCAPI Meta API is accessible only through an on-demand sandbox. Going forward, if you have a new project or a major refactoring, use the B2C Commerce API (SCAPI) instead of OCAPI.
Validate OCAPI Version Numbers Strictly: You can now strictly validate version numbers with the Open Commerce API (OCAPI). OCAPI requests that include a version number with leading zeros, such as v024_05, are rejected. These requests return a 400 Bad Request response and an InvalidVersionException fault. Going forward, if you have a new project or a major refactoring, use the B2C Commerce API (SCAPI) instead of OCAPI.
Optimize Omnichannel Inventory Synchronization: Full inventory imports from Omnichannel Inventory Service to B2C Commerce can now run concurrently with delta streams, providing more flexibility in data synchronization and eliminating the need of the nightly full import schedule. Additionally, the conditions for assignment of inventory lists to sites for the import process is eliminated, resulting in a smoother setup process. To provide clear insights into the status of full imports, the Business Manager page for Omnichannel Inventory is also updated.
Optimize On-Demand Sandbox Resource Management with the Usage Dashboard: Take control of your on-demand sandbox (ODS) resource consumption with the Control Center Usage Dashboard now available for ODS administrators. This feature offers a comprehensive graphical overview of sandbox usage and credit spending over selectable time frames–daily, weekly, or monthly. Use the dashboard to make informed decisions about resource distribution and budget forecasts.
Optimize Sandbox Resources Dynamically: Enhance your development environment by dynamically adjusting sandbox resource profiles. To manage performance and costs effectively, switch between medium, large, and xlarge profiles as needed. Automatic restarts and status checks ensure seamless transitions.
Optimize Web Performance with Streamlined HTML: Enhance your site’s SEO and user experience by compacting HTML lines, especially at the beginning of documents. This update is an automated feature added to maintain high performance and search visibility. It requires no user action. The change addresses the discontinuation of Cloudflare’s automatic compacting.
Block Unauthorized Access to Orders: The Order Preferences Storefront Order Access Allowlist, released in 24.5 in test mode, is fully functional and available to your storefront in Production. When enabled, storefront access to orders without a matching customer ID is now blocked unless the accessing controller is included on the Allowlist. If you aren’t yet limiting Storefront Order Access at all, enable the Allowlist feature on the Limit Storefront Order Access setting.
Patch Product Variations with OCAPI and SCAPI: OCAPI Baskets API and SCAPI Shopper-Baskets API now support patching of variations within product bundles in a single call. This enhancement allows for more efficient and streamlined management of product bundles, making it easier for developers to update multiple variations within a bundle without the need for multiple API calls. The update also improves the overall developer experience and increases productivity for developers managing complex product bundles.
Log Users Views of Personal Identification Information: Configure Business Manager to make security log entries when a user views a shopper’s personal identification information (PII) in the Order module, Customer module, or Coupon module. When a user clicks a button, tab or field that displays a shopper’s PII, the security log updates with details about when, who, and what is viewed. For example, when the user views an order, the security log is updated with a timestamp, the user, and the order number viewed.
Prepare for Third-Party Cookie Restrictions: To prepare for third-party cookie restrictions introduced by Google in 2024, Salesforce B2C Commerce is introducing a new feature toggle that enables partitioned cookies. The partitioned cookie toggle is available in Business Manager with the default value set to disabled.
Stay Informed with Real-Time On-Demand Sandbox Notifications: The on-demand sandbox (ODS) Notifications feature now offers real-time alerts for any activity within your sandboxes, directly within the Control Center. This enhancement aids ODS administrators in maintaining vigilant security and comprehensive activity tracking, crucial for audit and compliance purposes.
Ensure steptypes.json Files Are Valid for Custom Job Steps: With the 25.4 B2C Commerce release, only valid steptypes.json files are supported. This change enhances the reliability of your custom job steps and reduces runtime errors, ensuring smoother job processes.
Discontinued Cloudflare Auto-Minification: The auto-minification feature offered through Cloudflare CDN is no longer available. With the discontinuation of auto-minification, removing empty lines from HTML documents is now automated. This update, released with 24.8, offers a refined approach to page optimization for performance and search visibility. Investigate performing minification at build time.
Replace eCDN Firewall Rules with new eCDN Custom Rules: Commerce Cloud B2C Commerce has migrated all existing firewall rules to a new custom rules CDN-API endpoint. All customers are directed to transition to using custom rules in place of firewall rules.
SCAPI Taxation APIs: The following ScriptAPI methods are available to support SCAPI external Taxation APIs with hooks. Previously, SCAPI hooks and external taxation excluded each other, and SCAPI hooks could only be used if external taxation wasn’t in use. They can now be used together.
Enhance Storefront Search Scale and Performance: Enhance the scale and performance of storefront search for keyword search and product browsing with the new B2C Commerce search settings option. Improve page load times for large product catalogs when processing search results that exceed a configurable threshold. Shoppers get quicker results when performing a keyword search, refinement calculation, product grouping, sorting, and category browsing. For example, if your storefront doesn’t use search refinement counts in the refinement bar, a setting is available to improve refinement calculation and search and category page load times.
Sign Up for the Shop the Store Pilot: Improve your B2C Commerce site’s functionality by letting shoppers refine product searches according to store-level inventory. The Shop the Store pilot feature integrates store inventory data directly into your storefront search and browsing capabilities, providing customers more-tailored shopping options. Additionally, there’s no need for custom platform modifications or workarounds, such as high-scale price books.
Experience Improved Rule-Based Categorization: Rule-based categorization import and export is more efficient and accurate. It handles special characters better and export processes now automatically default to x-default when encountering an undefined locale.
Specify a Date Format for Locales: You can now modify the date settings format in Business Manager so that the script API method dw.util.Calendar.getFirstDayOfWeek() returns the first day of the week in the date format used by your site locale. Previously, you couldn’t modify the date format to match the local or regional context.
Stream Logs From Log Center: Log Center now supports Log Streaming into third-party log aggregation tools such as Splunk, Datadog, New Relic, Grafana Loki, or through a generic HTTP connection. This enhancement enables enterprise-scale monitoring and automation capabilities for Log Center users.
Streamline Bonus Product Management: Merge bonus products from the same promotion into a single basket. Missing fields under bonusDiscountLineItems > bonusProducts are now included in merged baskets. To align with OCAPI and SCAPI standards, empty merged baskets are now stored.
Get Enhanced Security with TLS v1.3: The B2C Commerce service framework now supports TLS v1.3 for outgoing HTTP calls made from the platform. TLS v1.3 provides enhanced security features that don’t require complex configuration. It offers modern encryption standards that protect against known vulnerabilities and supports secure integration with third-party partners. If you encounter connectivity issues while using TLS v1.3, contact Support for assistance.
Track Your On-Demand Sandbox Account Credit Balance in Real Time: Monitor your organization’s on-demand sandbox (ODS) Account Credit Balance effectively with the new monthly credit consumption reports in the Control Center. Accessible to users with OpcRealmAccess privileges, this feature allows viewing of real-time credit balances at both the organizational and realm levels, facilitating better budget and resource decisions.
Update On-Demand Sandbox Email with Ease: Simplify your on-demand sandbox (ODS) configuration with enhanced email management capabilities. Users with instance or realm-level access can now easily add or modify email addresses during sandbox creation or within the email settings, ensuring smoother setup and management of communication channels.
Update Social Selling Cartridges: Extend your social selling business functionality with the following updates. The updates cover common updates across all channels as well as channel-specific functionality.
Updated Cipher Suite: To increase security Account Manager now supports the following cipher suites:
Use OCAPI Hook to Get Payment Methods: The OCAPI hook dw.ocapi.shop.basket.payment_methods.afterGET is fully supported. The hook is Called before returning the list of available payment methods to the customer. Allowing modifications of the result. Previously, the hook was not called.
Use SCAPI, the New Standard for API Integration: Salesforce suggests using the B2C Commerce API (SCAPI) instead of the Open Commerce API (OCAPI) for all new projects or any major refactoring work. For details, refer to Why Use SCAPI Instead of OCAPI.
View Security Logs in Log Center: Security Logs are now available in Log Center. You can view all your security logs in one place, along with your other logs. Previously, you had to use Business Manager or WebDAV to see your security logs.
View SLAS Logs in Log Center: You can now access the Shopper Login and API Access Service (SLAS) 4xx error logs in Log Center. Previously, you only error messages from SLAS API responses were available.
New Account Manager Warning Message: During Account Manager log in, administrators now receive a warning message when their organization has users who have been in a deleted state for 90 days or more. The message includes a reminded to purge those users. To maintain security and compliance, Account Manager users that are in a deleted state are automatically removed after 180 days.
Write Custom Script Code with SCAPI Custom APIs: SCAPI Custom APIs are now generally available. SCAPI Custom APIs provide a framework enabling developers to write custom script code and expose this functionality as a custom REST API under the SCAPI framework.
Support for DNS CNAMEs Now Available: You can use a Domain Name Server (DNS) Canonical Name (CNAME) to map an alias to an on-demand sandbox URL. The DNS CNAME allows you to do SEO, site path, and locale setting testing.
Increased Storage Available for On-Demand Sandboxes: On-demand sandboxes now have access to 10 GB of shared realm data. All on-demand sandboxes in a realm can access data uploaded to the shared volume. You can use the shared space for import and export processes initiated through Business Manager or WebDAV uploads. In addition, storage space for each individual on-demand sandbox has increased from 5 GB to 10 GB.
New Customer Metrics in the Traffic Dashboard: We added new customer metrics to the Commerce Cloud Reports and Dashboards Traffic dashboard Number of New Customers (Registration) and Total Number of Customers. The new metrics provide details about initiatives to drive storefront customer registration and the total number of customer registrations by site or across all sites. You can filter both metrics by site and date.
Localize Product Tax Classes with the Localized Tax Class ID Attribute: If you operate one site across multiple regions, you can use the localizedTaxClassId to define different tax class Ids for the same product in different locales. The new attribute eliminates the need to map a different tax rate for each product that requires a specific tax handling.
UX Studio 20.10 Release: UX Studio release 20.10.0 is now available for download. This version of UX Studio contains a fix to allows UX Studio to work with OpendJDK8 and a Security enhancement to guard against Man in the Middle exploits.
Case Sensitivity in Coupon Data API for OCAPI 21.9: The Coupon Data API allows the case_insensitive property to be set during coupon creation, and the multiple_codes_per_basket property to be set during coupon creation and update.
Access to a B2B Store: Specify which profiles and permission sets can access a store. Create buyer accounts and assign them to buyer groups, or set up self-registration so that customers can create an account and log in on their own. You can also enable guest browsing to allow unauthenticated users to browse the store.
Activate Your Store: Activating your B2B store makes it available to customers and accessible to external services and online search engines. Activating the store also publishes it.
Add Recommended Products to B2B Store Pages: Increase engagement by showing personalized product recommendations on your store pages. Use a Carousel component with the Product Recommendations data source to show dynamic suggestions based on shopper activity.
Add Cart Import and Export Components to Your B2B Store: Cart import and export use the Cart Details component. If you created your B2B store before Summer ‘26, and aren’t using advanced cart management, then add the Cart Details component to the Cart page in your B2B store.
Considerations for Address Autocomplete for B2B Stores: Customers checking out or entering contact information on the My Account page in a B2B store, a D2C store, or a Pay Now site can enter text in address fields and select possible matches from a picklist. When a customer selects a match from the picklist, their address fields are populated automatically. Get familiar with these considerations for using address autocomplete.
Agentforce for B2B Commerce: Use the power of generative AI to drive a better shopping experience and a more personalized communication with customers and to help merchants achieve greater shopper conversion in your B2B stores. Agentforce for Guided Shopping - B2B helps your customers discover new products, view past orders, reorder, and check on order status in your B2B stores. Agentforce Merchandising for B2B Stores streamlines merchandising tasks and improves business outcomes through insights.
Agentforce for Guided Shopping for B2B Commerce: Guided Shopping Agent blends the best of in-store and online shopping in your B2B stores. Powered by generative AI and advanced language models, the agent helps customers discover new products, view past orders, reorder, and check on order status.
Create a Guided Shopping Agent for a B2B Store: Create a Guided Shopping Agent to unlock agent capabilities in your store. Guided Shopping Agent includes standard subagents, which are preconfigured categories of actions that help the agent recognize how to behave and respond for different jobs.
Implement a B2B Guided Shopping Agent: A guided shopping agent can recommend products, reorder a previous order, and look up existing orders in your B2B stores. To improve the customer experience, implement your agent with standard and custom topics.
Localize a B2B Guided Shopping Agent: Reach more customers with a multilanguage Guided Shopping Agent for a B2B store. Configure the agent to interact with customers in their preferred language.
Create an Omni-Channel Routing Flow for the B2B Guided Shopping Agent: An Omni-Channel routing flow routes messages from the messaging service to your guided shopping agent for your B2B store. Create a flow to automate routine tasks, and to make agent communication more efficient.
Test and Activate Your B2B Guided Shopping Agent: Before launching an agent in your store, test the agent to confirm that the agent understands a user’s request or instruction and provides the correct actions. Review whether the agent's responses are helpful and accurate and then activate the store.
Agentforce Merchandising for B2B Stores: Use the merchant agent to reduce store creation time and grow revenue through data-driven shopper insights. Communicate with Einstein using natural language with fewer clicks and more precision.
Add Agentforce Merchandising for B2B Stores Topics: Add topics to define what you want Merchandising Agent to do. The promotions topic helps you craft promotions that meet your business needs. The business insights topic retrieves helpful insights into your store.
Enable Agentforce Merchandising for B2B Stores: Use the power of a Merchandising Agent to help you be more productive, eliminate the need to navigate to screens, fill in values, and take action. Activate Einstein generative AI features and other required features and tasks to power up your productivity.
Launch Agentforce Merchandising for B2B Stores: Before launching an agent, test it to ensure good performance. After Merchandising Agent is live, depending on the topics you selected, the agent can help you create promotions or get insights about how to improve KPIs.
AI-Powered Search for Commerce: Improve store search experiences with Einstein semantic search in D2C store. Einstein semantic search reduces the occurrence of “no results found” pages, lowers bounce rates by providing a smoother shopping experience, and improves conversion rates. Einstein semantic search uses natural language processing to interpret queries and matches the information in the Product Name, Product Description, and Category Name fields with the terms entered in the query.
Commerce Analytics Dashboards and Reports: Take action on insights about revenue, product performance, and customer behavior from Commerce Analytics dashboards and reports.
Subscription Management in B2B Stores: Buyers can amend, renew, or cancel their subscriptions from the subscriptions page in the store, and view subscription history. The history for each subscription shows a detailed timeline of all modifications made to the subscription, including amendments, renewals, and cancelations. Republish your store after enabling the feature. Merchants can amend, renew, and cancel a buyer's subscription by using the B2B Commerce APIs.
Assign a CMS Public Channel to a Commerce Store: When you create a store, a CMS workspace and a public channel to the workspace are added. If you have an LWR store built on an enhanced LWR site, you can change the public channel. A store can access content from all CMS workspaces that include the store’s public channel.
Add Profiles and Permissions for B2B Store Community Members: Specify which profiles and permission sets are members of the store community. Only users with profiles or permission sets that are part of a store’s community can access the store.
Create a Buyer Group or Store Price Book for B2B Commerce Stores: To display prices to your customers, create a buyer group or store price book. You can assign a price book to buyer groups, stores, or both, but you must have at least one. When you assign a price book to a store, any customer who can access the store is eligible for prices within that price book. When you assign a price book to a buyer group, the accounts associated with that buyer group are eligible for prices within that price book.
Resolve Asynchronous Order Failures for a B2B Store: When an asynchronous order fails with a PlaceOrderFailed exception, the exception is converted into a process exception record. You can then view the record and investigate the cause of the error. After you fix the problem and change the record’s status to Resolved, the Retrigger Place Order flow resubmits the order.
Retrigger Failed Orders in a B2B Store with an Automatic Flow: When an order fails (PlaceOrderFailed), a process exception record is created. As a Commerce admin, you can view the record to investigate the cause and fix it. After the record’s status is changed to Resolved, you can use the Retrigger Place Order flow to place the order gain.
Resolving Asynchronous Order Failures in B2B Stores: B2B stores created with the LWR template in Spring ’23 or later process orders asynchronously. Asynchronous order processing improves store performance and responsiveness. However, when an order is processed asynchronously, the store can sometimes generate failed orders (PlaceOrderFailed exceptions). To handle these exceptions, you give the Commerce admin access to the Process Exception object and activate the Retrigger Place Order flow.
Add an Attribute Set to a Product: You can add an attribute set to one or more products, but you can associate a product with only one attribute set.
B2B Licenses and Allocations: A B2B license is based on your anticipated gross merchandise volume (GMV) or the number of orders placed to your store (PPO). You can purchase as many licenses as you need, but you can’t mix and match licenses, for example, a standalone and standalone plus license or a PPO and GMV license.
Commerce Basics: Learn about B2B terms and concepts, personas, and licenses.
Bulk Translation for a B2B Store: To accomplish bulk translations of B2B store metadata and Product, Category, and Promotion fields, use the Translation Workbench source export option. The Translation Workbench supports the XML Localization Interchange File Format (XLIFF) and the Salesforce Translation File (STF) file formats. Salesforce recommends that you use the XLIFF format.
Grant Buyers Access to External Accounts for a B2B Store: An external account is an account for which the buyer isn’t a contact. You can grant a B2B buyer access to an external account by assigning them the Buyer Manager role. When shopping in a B2B store, the designated buyer can switch to an external account that they have access to. The buyer can purchase on behalf of that account or add and activate users, reset passwords, and view their shopping carts, depending on how you configure their privileges.
Manage Access to a B2B Store: Create buyer accounts directly from the Customer Workspace or use a business account or a person account to create buyers. Add the buyer account to a buyer group. Associate the buyer group with a store. The products and prices buyers can access in the store are determined by the entitlement policies assigned to the buyer group.
Buyer Group Extension: Dynamically assign buyers to buyer groups for a B2B store by using a custom Apex logics. Review the considerations to understand the factors that influence how these assignments take place in your store.
Associate a Buyer Group with a B2B Store: Product prices and the products that buyers can access depend on the price books and the entitlement policies assigned to the buyer group. When you create a store, a default buyer group is assigned to the store.
View Your Store’s Buyer Groups and Entitlement Policies: Make sure that your customers have access to the correct products in your store by checking your buyer groups and associated entitlement policies. A B2B store can have multiple buyer groups and markets. You can also assign products to multiple entitlement policies and associate the policies to different buyer groups to determine which customers can access the products in the store.
Dynamically Assign Buyer Groups by Using Apex Logics: Dynamically assign guest and authenticated buyers to buyer groups for a B2B store by using custom Apex logics. When buyers visit the store pages, the Apex logic adds them to a buyer group based on the defined criteria. Assigning buyers dynamically when they visit a storefront ensures timely, personalized shopping experiences including targeted product visibility, pricing, and promotions, without manual intervention.
Create a Buyer Manager Profile Menu for B2B Stores: You might not want buyers to have access to the same user profile menu items as your buyer managers. In Experience Builder, you can create a separate user profile menu for buyer managers and edit the default profile to apply just to buyers.
Buyer Groups, Entitlements, and Pricing Strategies for B2B Stores: Set up buyer groups, entitlements, and price books to customize product visibility and pricing for each buyer in your store. Here are three examples of strategies you can consider for your store.
Set Up the Buyer Group Page to Support Markets in B2B Stores: Add the Locales related list to your Buyer Group object page. The Locales related list appears on all Buyer Group pages, even Buyer Groups that aren’t of type Market, where locales aren’t applicable. Configuring locales for non-Market Buyer Groups can cause errors.
Create Localized Email Templates in Your Store: You can send custom Welcome, Order Confirmation, and Abandoned Cart emails to your customers in any language supported by your B2B store. Create email templates in each language, and then customize the email flows to trigger sending localized emails based on the language the customer selects in the store.
Enable Cart Preview and Checkout from the Cart Icon in a Commerce Store: Let customers go to the Cart page, preview their cart, or complete their purchase on any page in your B2B store by including a mini cart display. In Experience Builder, customize the Cart Badge component to add these features.
Design the Cart Page in a B2B Commerce Store: The Cart page is where customers can review their order before checking out in a B2B store. In Experience Builder, you can customize the page to show line item details, total costs, and savings. You can also style the checkout button and add a field for customers to enter coupon codes.
Improve Cart Processing for B2B Stores: Increase cart size limits to process larger orders. Speed up shopping with faster add-to-cart. Let customers add duplicate items to their cart.
Cart Import and Export: Allow buyers to import products into a cart or export cart contents in B2B Commerce by uploading or downloading a CSV file. Buyers can use a CSV file to quickly add multiple line items to a cart without manual entry, or export a cart’s contents to a CSV file for offline review, editing, or record-keeping. Import and export uses the Cart Details component. Cart exports are subject to a daily limit of 1,000 data exports per account.
Create a Catalog and Assign It to a Store: Before you can make products available to buyers and shoppers, your B2B Commerce store must have a catalog. A catalog is the entire collection of products that you offer through your store. When you create a store, a default catalog is assigned to the store. You can use the default catalog or assign a different catalog to the store. You can assign a catalog to more than one store, but a store can have only one catalog at a time.
Catalogs for a Store: A B2B Commerce store must have only one catalog that represents the entire collection of products offered through your store. To make it easier for shoppers and buyers to find products, you can group them into categories.
Add Products to Categories in a B2B Store: To make a product available in a B2B Commerce store, add it to a category. The maximum number of products in a category is 1.8 million. You can add products from either the Category workspace or the Product workspace.
Choose Product Categories to Use in Breadcrumbs: The order of breadcrumbs is determined by a combination of a category and product and the date and time that their association was established. The first category that a product is associated with is the product’s primary category and becomes the basis of the breadcrumb order. You can customize the default order of breadcrumbs by explicitly identifying categories as primary. When you identify a category as primary, your store uses it to construct the category path that populates the breadcrumbs on the Product Detail page. You can associate a product with multiple categories, but it can have only one primary category.
Create Product Categories and Subcategories in a B2B Commerce Store: Organize products into categories and subcategories to enhance product discoverability. Providing a structure improves search and navigation, making it easier for customers to find what they’re looking for.
Categorize Products for Discoverability in Your B2B Stores: Categories make products easier to discover in searches and through navigation. Build a category structure that shows product relationships and makes products easier to find. When you create a store, a default catalog with one Products category is assigned to the store.
Checkout Solutions for a B2B Commerce Store: Add checkout functionality, including payment, tax, and shipping services, to your B2B store. If you have a B2B store, you can only use custom checkout. Managed checkout integrates Salesforce merchant services and automatic updates for your store’s checkout UI. With customized checkout, you use third-party providers and can customize your store’s checkout UI.
Website Design for the Checkout Page in a B2B Commerce Store: The Checkout page is where customers enter their shipping and payment information to complete their order. Customize the Checkout page in Experience Builder to work with the shipping and payment services that are selected in your store settings.
Customize the Payment Section of Checkout in a Commerce Store: After you set up your payment service provider, use Experience Builder to customize how you collect payment and billing details from your customers during checkout in a B2B store. You can customize checkout only if your store uses custom checkout. If your store uses managed checkout, you can’t customize the Checkout page.
Customize the Shipping Section of Checkout in a Commerce Store: After you set up your shipping calculation service, use Experience Builder to customize how you collect shipping details from your customers during checkout in a B2B store. You can customize checkout only if your store uses custom checkout. If your store uses managed checkout, you can’t customize the Checkout page.
Using Salesforce CMS for Product Media: A Content Management System (CMS) workspace offers a secure environment to create, edit, organize, and manage digital content for your B2B Commerce stores. When you create a store, a CMS workspace for the store and a public channel from the store to that workspace are added. You can upload or import product media from a CMS workspace into your store.
Get Help with Product Visibility Issues with the Troubleshooting Assistant: To troubleshoot issues with product visibility, ask the Troubleshooting Assistant for help. The Troubleshooting Assistant can help you determine whether a buyer or guest customer can see a product in the B2B store. The Troubleshooting Assistant displays the tasks required to configure a store and its products and which of those tasks have been completed.
Commerce Einstein: Commerce Einstein uses AI to automate tasks and personalize customer shopping experiences.
Commerce Knowledge Articles: Create knowledge articles with answers to common questions and concerns that shoppers or buyers tend to ask. Your customer service representatives can share these knowledge articles directly with customers. You can also work with your developer to embed the knowledge articles in your store.
Commerce Pricing: Set up pricing for your B2B store by configuring a standard and custom price book for your store and buyer groups. Highlight reduced pricing for customers by configuring a strikethrough price book. When you create a store, it's automatically assigned a default price book and a default strikethrough price book. Before you can add products to other price books, they must have an entry in the standard price book.
LWR Store Components: B2B stores created with the unified Commerce Store template share the same Commerce components in Experience Builder.
Expressions in Commerce Components: Expression Language is a specialized syntax that pulls data into an LWR component in Experience Builder. You can use expressions instead of static text to make your B2B store more customized and dynamic.
Adding an Expression to a Commerce Component: Enter expressions into any LWR component on a page with data providers. In some components, you can select an expression from a provided list. You can also combine expressions or add values.
Create Attributes for Product Variations in B2B Stores: An attribute identifies a specific product feature, such as size or color. A product can have multiple attributes, so you can group attributes into an attribute set. Then, apply the set to one or more products and then assign individual attributes. By using attribute sets, it provides consistency across products.
Manage Guest Access to a B2B Store: A guest is someone who isn’t logged in to your store as an authenticated customer. Depending on the level of access that you provide, guests can browse your store, add products to their cart, and place orders.
Configure Tax Rates: When you configure the manual Salesforce tax solution for B2B Commerce, you configure tax rates and tax treatments. A tax rate specifies the percentage at which a product is taxed and the country, state, or province where that rate applies. A tax treatment maps the tax rate to products. A tax policy includes all the tax treatments for your store’s products.
Configure a Custom Domain and CDN: For B2B stores created with the LWR template, if you prefer a branded URL or a URL without my.site.com, connect your store to a domain. Connecting the store to a domain automatically enables the Salesforce content delivery network (CDN) partner. You can use a single custom domain for multiple Commerce stores. A Salesforce admin typically configures the custom domain.
Configure Displayable Fields in Commerce (Beta): Before you enable displayable fields for your B2B Commerce org, you must set up displayable fields in the Commerce App and configure product fields in Experience Builder for all of your stores. You can complete steps 1 and 2 in either order, but the product fields that you configure in Experience Builder must be set up as displayable before you enable displayable fields to see improvements on your search, product, cart and checkout pages.
Set Up Gifting for a B2B Store: Enable gifting options for your store. Add gift messaging and gift wrapping features to offer personalized services to your customers.
Format the Display of Product Cards on Search Pages in a B2B Commerce Store: In Experience Builder, you can change the number of product card columns and the spacing between cards on the product list page. You can also configure your search results or product listing page to show products spanning multiple pages by either page numbers or the Load More button.
Configure Markets for Your Commerce Store: Use one B2B store to segment customers into markets based on their locale. When you create a market, assign a price book, an entitlement policy, a currency, ship-to countries, and the locales that it supports. After you create a market, you can also assign a promotion.
Configure Your B2B Commerce Org to Support Digital Products: Add digital products to your store, such as downloadable cookbooks, e-books, music files, or software. To do this, you must configure the page layout for the Product object to include the Shipping Charge Not Applicable field.
Configure Pricing Procedure Plans for B2B Stores: Configure pricing procedure plans to customize how pricing is calculated in your B2B stores. Create a procedure plan from the default Commerce procedure plan template and then customize it with your own context definitions, pricing procedures, and Apex hooks.
Enable Product Cards on Search and Category Pages in a B2B Commerce Store: The Results Grid component and the Product Card component enable product cards to display on the product list page. If you’re creating a store after the Summer ‘24 release, the Results Grid component is configured by default. For stores created before Summer ‘24, you must use Experience Builder to add the component and configure it.
Configure Volume-Based Adjustments for Contract Pricing: Offer more savings by applying volume-based discounts on top of contract prices when B2B buyers purchase in larger quantities. Volume-based adjustments apply to both subscription and non-subscription products.
Contract-Based Pricing for B2B Stores: Create custom pricing contracts to offer negotiated prices to buyers. Override standard prices with contract pricing for selected products, so buyers automatically see their agreed rates across the store pages. Use this feature to manage complex pricing scenarios where different customers receive different prices.
B2B Commerce Cookies: B2B Commerce stores use cookies to improve functionality and accelerate processing times. By saving a user’s settings, cookies can enhance the user’s experience and the performance of the store. In addition to these Commerce-specific cookies, stores can use cookies that apply to all Experience Cloud sites.
Create a Product Bundle for a Commerce Store: A product bundle is a collection of complementary products purchased under one SKU. The bundle’s parent product and child products are shown together on the product page under one price. The bundled products become one product. For example, you create the “Work From Home Desktop Bundle” with a desktop monitor, keyboard, mouse, and monitor stand as the child products. The “Work From Home Desktop Bundle” is the bundle’s parent product. You set the price for the bundle at the parent level and price the “Work From Home Desktop Bundle” at $199.99 even though the individual child products are sold separately: desktop monitor priced at $129.99; keyboard priced at $39.99; mouse priced at $15.99; and monitor stand priced at $29.99. The “Work From Home Desktop Bundle” displays all of the individual child products to shoppers under the price of the bundle’s parent product.
Create a Product Set for a Commerce Store: A product set is a collection of related products displayed together on the product page. Each child product is priced separately. A product set doesn’t have its own price. A shopper can add all the products to the cart in a single operation or selectively add individual products. For example, you create the “Work From Home” product set that includes a desktop monitor, laptop stand, wireless mouse, keyboard, standing desk, and office chair. The product set displays all of these products together on your store, but each product is priced separately. Customers can select which products they want to add to the cart or add the whole set, but purchasing all of the products in the set doesn’t afford your customers any savings.
Add a Buyer for a B2B Store: You can add buyers in different ways. You can add a buyer from your Customer workspace or enable a business or person account.
Create a CMS Workspace to Import Images to a Commerce Store: When you use a CSV file to import images, you must specify a CMS workspace where the imported images are linked. If you don’t have a CMS workspace, create one before you begin the import process.
Create Configurable Bundles in a B2B Store: Create configurable bundles that buyers can customize. Define required and optional items, define rules, and enable real-time pricing updates.
Create Configurable Products with Dynamic Attributes in a B2B Store: Create products that buyers can customize based on specific attributes, such as size, color, material, or technical specifications. Unlike product variations, dynamic attributes update pricing dynamically as buyers make their selections without requiring separate SKUs for every combination.
Create a Buyer Group Based on a Data Segment: Personalize your customers’ shopping experience by combining the power of Data 360 segments and Commerce buyer groups. Build a targeted customer group using Data 360 segments and associate it with a Commerce buyer group. You can then deliver personalized promotions and content that directly caters to customer needs and interests.
Manually Localize Product, Category, and Promotion Data: You can manually enter translated text for your B2B product and category names and descriptions. To translate promotion names and descriptions, you must use Translation Workbench. To perform bulk translations for product, category, or promotion data, use Translation Workbench.
Create Geo Countries for the Manual Salesforce Tax Solution: When you configure the manual Salesforce tax solution for a B2B store, you assign a geo country to a tax rate to specify which country the tax rate applies to. Create a geo country for every country where you want to specify a tax rate. The geo country is the country to which a product is shipped, not from where the order was placed.
Create Geo States for the Manual Salesforce Tax Solution: When you configure the manual Salesforce tax solution for a B2B store, you assign a geo state to a tax rate to specify which state or province the tax rate applies to. Create a geo state for each state and province that you want to specify a tax rate for. The geo state is the state or province to which a product is shipped, not from where the order was placed.
Create Boost and Bury Rules: A strategic management of product listings in B2B makes sure that shoppers see the most relevant products first. Use boost and bury rules to align your search results and category pages with your business goals, like stock management, new product promotions, or selling high-value products. Select specific products manually or define attribute-based conditions to apply rules to matching products dynamically.
Create Multiple Shipping Profiles for a B2B Store: Create multiple shipping profiles to categorize products. After you set up the shipping profiles, you can define shipping rules based on different zones for each profile. Assign rates based on order value or delivery group weight to meet your store's specific needs. For example, Emma owns a home decor store with a wide range of products. She creates different shipping profiles based on shipping zones and rates. One profile is for light items like wall art and candles, with affordable rates. Another profile is for heavy items like sofas and dining tables, with higher rates to cover professional delivery. By doing this, Emma can manage shipping costs more efficiently.
Add a B2B Store to an Existing Experience Cloud Site: Reuse your Exprerience Cloud site’s domain, settings, branding, and styling to maintain a consistent look and feel. The site template, pages, components, and navigation stay the same. After you add the store, you can design your commerce experience using your commerce pages and components.
Start Selling Online: The store is where shoppers and buyers go to view, select, and purchase your products. We provide the Commerce Store template to get you started creating B2B stores.
Create a Tax Engine: A tax engine calculates tax rates for cart items based on specified geographic and regulatory rules. Set up a tax engine if you're using simple gross tax. When you configure the manual Salesforce tax solution in B2B Commerce, set up a tax engine record using your tax provider's name, mailing address, seller code, Apex adapter name, and credentials.
Create a Tax Policy: A tax policy determines how taxes are calculated and applied to products during checkout. When you configure the manual Salesforce tax solution in your B2B store, create a tax policy for each product type, so that the correct taxes can be applied when buyers check out their cart. A tax policy must be associated with a tax treatment.
Create a Tax Treatment: A tax treatment defines how taxes are calculated for a specific item through the product's tax code. When you configure the manual Salesforce tax solution in B2B Commerce, create a tax treatment.
Default Object CRUD Permissions for B2B Commerce: You can perform Create, Read, Update, and Delete (CRUD) operations on objects in your org depending on your permissions. Users assigned to preconfigured permission sets receive CRUD permissions according to their persona’s required functionality.
Set Up Commerce Manually: If you choose not to use the Commerce Setup Assisant, you can manually set up your Commerce org and store.
Support Multiple Currencies in a Commerce Store: To support international customers, provide multiple currencies in your B2B store. By default, a store supports only the currency listed as the currency locale on your Company Information page, unless you turn on multiple currencies. The currency settings apply to all stores in your org.
Configure Custom Checkout for a B2B Store: Custom checkout gives you more control over your store’s checkout configuration. You can use third-party apps instead of Salesforce’s native merchant services for payments, tax, and shipping. Or, you can extend native merchant services using custom checkout. You can design your own checkout page in Experience Builder with preset layouts, custom sections, and components. For B2B stores, custom checkout is the only option for configuring checkout.
Use a Custom URL for Your Store: The default URL for a Commerce store includes a temporary path you specified when creating the store. The default URL is suitable for testing pre-production stores during development. However, before you launch a B2B store created with an LWR template into live production, we recommend that you configure a custom URL for the store. Associate the custom URL with a custom domain served by the Salesforce CDN, with Cloudflare as the CDN partner. For B2B stores created with an Aura template, a custom URL is optional. However, we recommend using a custom domain and corresponding CDN if broad access and high security are required.
Assign a Page Layout for a Custom Store Header or Footer: B2B stores created with the LWR template include responsive header and footer components. Alternatively, a developer can build a custom header or footer. For each page where you want to use a custom header or footer, assign the commerce custom layout using Experience Builder.
Enable Advanced Carts for B2B Buyers: Configure your store to allow buyers to organize their purchases into independent project-based carts. After the advanced cart feature is enabled in your store, use Experience Builder to add advanced cart management components to your store.
Advanced Cart Management: With advanced cart management, B2B buyers create and manage multiple independent shopping carts simultaneously, keeping complex project requirements organized without mixing data. Buyers can specify any saved cart as the default and change the default later. From any saved cart, buyers can request quotes or check out directly without switching to the default cart. Buyers can also apply and remove coupons, configure multi-address shipping, add gift wrapping and messages, and sort and paginate their cart list. Any cart is shareable with other buyers in the same account, with View, Edit, or Checkout access assigned to each collaborator.
Customize B2B Store Pricing with Apex Hooks: To support unique pricing scenarios, add custom Apex logic to your pricing procedure plans. You can use Apex hooks to apply custom business logic that modifies the pricing context before or after your pricing procedure runs. Apex hooks are custom code that run at specific points in the pricing procedure plan.
Website Design for B2B Stores: Use the Website Design workspace to add basic design elements to your store without leaving the Commerce app. For example, add your logo and set fonts, colors, and button styles. For more advanced design changes, such as configuring store components, pages, or navigation, you can move out of the Commerce app to Experience Builder.
Import and Export Commerce Data: Import data, including products, product variations, and images, by uploading a CSV file. Perform other tasks while the import runs asynchronously. You can import up to 10,000 products with nine images each per session, though import times may increase with more images. We recommend using the CSV file import process, but for large imports, use Data Loader. You can also export data for up to 300,000 products to a CSV file.
Set Up Data 360 for B2B Commerce: Integrate B2B Commerce with Data 360 to gain key business insights and unlock valuable analytics, personalization and automation capabilities for your store.
Data 360 Connectors for B2B Commerce: When you provision Data 360, it's connected to your Salesforce org and has access to data from B2B, D2C Commerce, and Salesforce Order Management. You can use connectors to bring data into Data 360 from other sources, such as Omichannel Inventory or store customer engagement data.
Deactivate Your B2B Commerce Store: Deactivating your store makes it inaccessible to customers. Deactivate only when you want to temporarily or permanently bring down the store.
Disable the Welcome Email for Your B2B Commerce Store: When you activate your store, all members of the site receive a welcome email. You can turn off this feature before you activate so that the email isn’t sent.
Displayable Fields for B2B Stores: Displayable fields help to decrease page load times and retrieve product data faster on search, product, cart, and checkout pages.
Design the Checkout Page in a Commerce Store: Use a preset layout and customize its components, or design a layout using sections and components to guide customers through the checkout process in a B2B store. You can customize checkout only if your store uses custom checkout. If your store uses managed checkout, you can’t customize the Checkout page.
Enable Storefront Activity Tracking: Storefront activity tracking captures browser-based, real-time buyer or shopper activities in your store, unless settings are explicitly changed by the buyer or shopper. Storefront activity tracking requires a Content Security Policy (CSP) trusted site for the Commerce Einstein domain.
Storefront Activity Tracking: Storefront activity tracking captures browser-based, real-time customer activities on your storefront, unless settings are explicitly changed by the customer.
Tracked Data: Commerce Einstein uses cookies and session storage objects to store and track browser activities. It uses this information to tailor customer experiences. Some cookies are essential, and some are functional. Essential cookies are necessary for a site to work correctly and can’t be disabled. Commerce Einstein uses functional cookies and tracked API activities to personalize shopper data.
Enable Commerce Einstein: Commerce Einstein features personalize shopper experiences, increase merchandiser productivity, and improve conversion. Enable Commerce Einstein so that merchandisers can turn on storefront activity tracking, turn on semantic search, and configure Einstein recommendations. Commerce Einstein deployment can take up to 24 hours to complete.
Enable Semantic Search for Commerce: Semantic search improves your search results by matching and returning items that are semantically related to a query. Semantic search requires a Content Security Policy (CSP) trusted site for the Commerce Einstein domain.
Reindex Commerce Einstein: Changes to your store’s product catalog are automatically sent to Commerce Einstein every 7 days, but you can manually reindex after making changes. Reindexing can take up to 24 hours to complete.
Semantic Search: Semantic search improves search results by matching and returning items that are semantically related to a query.
What Is Commerce Einstein?: Commerce Einstein provides AI-powered merchandising tools to enhance the shopper experience.
Enable Data Translation: When you enable data translation, you can translate the data stored in your B2B store product, category, and promotion fields. You can also enable data translation for custom text and URL fields on the product and category objects.
Enable Displayable Fields in Commerce (Beta): Enable displayable fields to decrease page load times and retrieve product data faster on search, product, cart, and checkout pages for B2B Commerce stores.
Manage Product Readiness for B2B Stores: Product Readiness is available in the Product Workspace. Anytime a custom rule set is enabled or disabled, build an initial score for your catalogs.
Enable Shipping to Multiple Addresses for Custom Checkout: Let customers ship items in one order to multiple addresses in a B2B store or a Pay Now site. At checkout, customers can split a single cart into multiple shipments. You can’t use split shipping with managed checkout or with digital or subscription products.
Enable Cart Sharing: Enable buyers to share carts in your B2B Commerce store from the store settings. Turn on this setting to ensure that buyers can share carts with other collaborators. You can also view shared cart history and track collaborator actions using the Shared Cart Activity component.
Enable Qualification Rules in Your B2B Commerce Store: Enable qualification rules from the Store settings in your B2B Commerce store. When you enable qualification rules, your store no longer uses entitlement policies to determine which product and product categories are visible to buyer groups.
Entitlement Policies for B2B Stores: Entitlement policies make it easy to manage buyer groups and products. You can use entitlement policies to decide which products a buyer group can see, and whether the buyers can see the product prices. When you create a store, the system automatically creates a default buyer group and a default entitlement policy. You can create additional buyer groups and entitlement policies as needed.
Example: Customize a Store Based on a Shopper's Locale: Acme Retail is a global fashion retailer that sells to customers in the United States and Europe. Acme can manage an online store in three languages (English, French, and German) by using markets and assigning locales to them. It can also offer different products, prices, promotions, entitlements, and ship-to countries for each market.
Example Promotions: When you configure a promotion, you customize it based on what you would like customers to receive and how they qualify. The examples show you how to combine basic discount and qualifier options to create different outcomes. Use them as a starting point, try your own unique combinations, and incorporate more advanced settings to create the promotions that you need.
Example: Limit Product Visibility in a B2B Store Based on Qualification Rules: Alpine Coffee sells to retailers across the United States. Two of the distributors for Alpine Coffee are Alpine Distributor and Go Coffee Distributor. This example uses disqualification rules to specify that buyers for Alpine Coffee see products and product categories that are specific to Alpine Coffee, and buyers for Go Coffee see products and product categories that are specific to Go Coffee.
Use Experience Builder to Design a Commerce Store: Use Experience Builder for advanced design tasks, such as configuring store components, pages, or navigation. With Experience Builder, you can make the Commerce Store template yours by dragging components onto your page and customizing properties. Use the Commerce Store template to create B2B stores. You can add images and styles to your stores to create a unique experience for your customers. You can also add markup to the head of every page.
Connecting a B2B Store to a Third-Party Domain: If you’re using a third-party provider to manage your domain, you can connect your Salesforce store to the domain. When shoppers enter the domain URL, they are redirected to your store. By connecting your store, you can still use the third-party provider to manage and renew your domain. When you connect your store and domain, Salesforce sets up a content delivery network with Cloudflare.
Export Commerce Data for B2B Stores: Export up to 300,000 products to a CSV file. Only product columns, including product variations, are included in the export. Large exports can result in more than one CSV file. Filters and sorting applied to the product workspace are reflected in the export file. All product fields, both standard and custom, that appear in the workspace are included in the export file.
Create Multiple Versions of a Commerce Component: Create multiple versions of a component, and assign visibility rules to target specific customer groups with each variation. Use Component Variations to tailor the shopping experience for different customers.
Control When a Commerce Component Is Visible: Create dynamic visibility rules to control when a component is visible on the storefront. Use Expression-Based Visibility (EBV) to show and hide storefront components based on ecommerce data-driven conditional expressions.
Replace a Default Commerce Process with an Apex Class: Use extension points to enhance or replace default Salesforce Commerce processing with Apex classes. For example, by default Salesforce Commerce uses standard Salesforce price books to determine how products are priced. If you want to use a different pricing method, you can use an Apex class for pricing instead.
Improve Product Page Performance in a B2B Store: To speed up the shopping experience in your LWR store, turn on the Faster Add-to-Cart feature. By splitting processing time across Product and Cart pages, Faster Add-to-Cart improves the response time on a Product page when a customer adds an item to their cart. This setting is enabled by default for B2B stores created in Winter ’24 or later and D2C stores created between Winter ’24 and Spring ’25.
Show Product Collection from Any Category on the Home Page: Show products from any category in a collection on your D2C store's the home page. For example, show all the new arrival products from a category by adding them to a Carousel component on the home page.
Create Featured Product Collections for Your B2B Store: Upsell or cross-sell your products by associating a product with up to 10 featured products. Create multiple user-defined collections, such as Complementary Products, Best Sellers, New Arrivals, and more. Showcase these static product recommendations on your B2B store's home page, product listing pages, or product detail pages.
Get Started with Salesforce Commerce: Prepare your Salesforce org for Commerce and create a draft store. Explore resources and learn more about Commerce features and functionality.
Set a Target to Track Goal Progress: Track the progress of your goal over time, and see how completing recommended actions impacts your progress. The target remains set until you reach the target value or its end date.
Goals & Actions: Get specific actions that you can take to achieve performance goals for your B2B Commerce store. Goals can include improving site conversion and increasing site traffic and average order value.
Get Recommended Actions to Improve Store Performance: Use the available goals and their corresponding recommended actions to achieve specific targets for your B2B Commerce store. You can choose which recommended actions to take. Some are based on insights into your store and unique to your store’s data, and others are general recommended actions. Monitor goal progress over time with data-driven insights into conversion rate, average order value, site traffic and more.
Account Creation for Guest Checkout in B2B Stores: If your B2B store allows guests to purchase products, you can configure whether to create a person or business account for the guest upon checkout. As of Winter ’25, person accounts don’t need to be enabled for B2B store guest checkout.
Prevent Duplicate Person Accounts for High Scale Orders in a B2B Store: Starting in Summer ’24, the High Scale Orders feature requires a Person Account duplicate rule for guest users. This duplicate rule is required for B2B stores created with the LWR template. When a guest user places an order, the rule determines whether a Person Account record exists for the guest user. If a matching record exists, the system uses the record. Otherwise, the system creates a record for the guest user. If you don’t create a Person Account duplicate rule, the system creates a Person Account record for every order by every guest user, potentially resulting in a large number of duplicate records.
Ensure Apex Code Works with High Scale Orders for a B2B Store: If you extended the Commerce_Domain_Checkout_CreateOrder extension point before Summer ’24, it’s possible that your Apex code doesn’t work correctly with the High Scale Orders feature enabled. You must test your existing code to make sure that it works as expected, modifying it as needed. Also, consider how the High Scale Orders feature in general can affect your Apex code.
Enable High Scale Orders for B2B Stores: Starting in Summer ’24, if you use the Commerce Setup Assistant to set up a new B2B or D2C store created with the LWR template, high-scale order ingestion (HSOI) is enabled by default. For existing stores, you can manually enable HSOI by enabling Enhanced Commerce Orders.
Image Import for B2B Stores: Product images and attachments that customers see when visiting your store are typically linked to a Salesforce CMS workspace. Usually the images are stored on a host external to Salesforce. You can configure the external host as a trusted site for your org. If you don’t have a CMS workspace, create one before beginning the import.
Import Using Data Loader: We recommend that you use the CSV data import file to import data into the Commerce app. The commerce import file maintains the correct relationships between commerce objects and supports importing up to 10,000 products with nine images each, along with the required updates to records in related objects. Typically, more than 50,000 updates are required to related objects for 10,000 imported commerce products. However, if you want to bulk import more than 10,000 products with nine images each, you can use the Salesforce Data Loader tool.
B2B Integrator Permissions: Salesforce provides several system permissions that enable users to integrate their B2B and D2C stores with third-party applications.
Data 360 for B2B Commerce Assets: When you install the Commerce data kit in Data 360, all Data 360 assets and data mappings are created. When you install Intelligence Analytics, the data transforms run, ingesting Data 360 data and creating the CRM Analytics dashboards and components.
Intelligence Analytics Dashboards Powered by Data 360: Intelligence Analytics dashboards display key store performance metrics to help you make data-driven decisions for business agility. Get a comprehensive view of the best performing categories and products within a store, and keep on top of inventory health across your locations and location groups. Explore the Shopper Intelligence dashboard to learn about customer first-time and repeat purchase behavior to drive and retain loyalty.
Inventory Intelligence Analytics Dashboard: If you’re using Salesforce Omnichannel Inventory, use this dashboard to get insight into inventory performance. View data about inventory levels and orders across locations and units sold.
Advanced Insights Overview Dashboard: In the advanced Insights Overview dashboard, you can view trends and calculated insights tied to specific goals and recommended actions. The dashboard also provides real-time visualizations of key performance indicators by store. Use these insights and actions to make informed decisions about how to improve your B2B Commerce store performance.
Product Intelligence Analytics Dashboard: Get insight into product performance and top-selling categories across regions. View data about low-selling products, product searches, and see which products are frequently bought together.
Search Intelligence Analytics Dashboard for B2B Stores: Monitor and analyze your storefront's search performance with the Search Intelligence dashboard to understand shopper search behavior and optimize search results. The Search Intelligence dashboard provides comprehensive analytics about how shoppers search. Use these insights to identify search terms that return no results, track click-through rates, and understand search trends over time. This data helps you improve product findability and optimize the search experience.
Refresh Intelligence Analytics Dashboard Data: The Intelligence Analytics dashboards rely on up-to-date data by regularly refreshing the data. The refresh includes running the data transforms and updating the datasets.
Data 360 for B2B Commerce: By combining the power of Data 360 with B2B Commerce, you can gain key business insights and unlock valuable analytics, personalization, and automation capabilities to provide connected, personalized experiences to your customers.
Interpret Commerce Analytics Dashboards and Reports: Commerce Analytics provides preconfigured dashboards composed of Lightning reports. To monitor key metrics for your B2B Commerce stores, use the Business Overview Dashboard. For details about your store’s payment processing, promotional effectiveness, and overall financial well-being, use the Commerce Payments, Promotions, and Finance dashboards. To get insights into order volume, fulfillment efficiency, returns, and refunds, use the Commerce Orders Dashboard.
Salesforce B2B Commerce: Salesforce B2B Commerce is a unified platform that helps businesses connect with their customers. Quickly create a customer-friendly B2B store. Take advantage of the store templates to create and customize your store with Experience Builder. Use standard Lightning functionality to set up checkout and payment and configure store settings. Define customer experiences, including search, carts, and checkouts. Import commerce data for accounts, products, price books, and entitlements using a CSV file.
Configure Language, Ship-To Countries, and Currencies for a B2B Store: Configure your B2B store for international customers by specifying the languages, shipping countries, and currencies that you support. Buyers can then see the pricing and shipping options based on their location and account.
Sell Globally: Enable languages, translations, and currencies to expand the reach of your B2B Commerce store to countries around the world.
Increase Cart Size Limits for a B2B Store: Most stores limit cart size to 500 line items per order. However, if your B2B store requires a higher limit, you can enable support to process up to 2,000 line items per order. To increase your line item limit, contact Customer Support.
Learn More About B2B Commerce: Learn about the possibilities with Salesforce B2B Commerce. Design a store website that showcases your brand and offers engaging customer experiences. Add products to the store, and configure the tax, shipping, and payment services. Optimize store performance using SEO, insights, and recommended actions.
License Requirements for Custom Checkout Order Tracking: To comply with B2B Commerce licensing requirements, make sure that your custom checkout implementation is tracking orders for Gross Merchandise Value (GMV) and Price Per Order (PPO). If your cart-to-order process invokes the Cart to Order flow core action or the Commerce Webstore Checkout Orders Connect REST API, no additional steps are required.
LWR and Aura Store Templates: Starting with Summer ’23, all new B2B stores are built on the Lightning Web Runtime (LWR) platform. Some B2B stores still use the Aura platform and, in some places, the Commerce App UI and documentation still refer to Aura features and components. If you’re using a new LWR store, you can ignore the Aura information.
Manage Shipping Zones and Rates for a B2B Store: Whether you’re using managed or custom checkout, you can organize countries with similar shipping costs into shipping zones. A zone can include countries with different currencies. For each zone, you can set shipping rates based on the monetary value of the order or by weight.
Store Management: Manage stores more efficiently using workspaces. Expand the reach of your store by enhancing language and currency support. Create and manage promotions to increase buyer incentive. Migrate store configurations, create custom reports, and manage existing integrations. Set up the emails that shoppers and buyers receive when they place an order, and what they see when your site isn’t available. Review the steps required to use Omnichannel Inventory with B2B stores.
Manage Pending and Failed Orders in B2B Commerce: Provide transparency to buyers and automate post-order cleanup when orders encounter issues after checkout. Display pending and failed states in buyer account pages, release reserved resources, reverse payments, and notify buyers automatically over email for failed orders.
Marketing Consent Store Components: Use Experience Builder to place consent components on your B2B storefront to show consents to customers. These components give customers the option to enter an email address and then consent to receiving marketing campaigns or promotional messages.
Enable Marketing Consents: You can easily enable marketing consents for your B2B store from within the Messaging workspace. A default consent is created for you. You can edit this consent to fit your needs. After consents are enabled, the consents appear on your store in the consent components that you have configured in Experience Builder.
Manage Marketing Consents for B2B Stores: Use the Commerce Messaging workspace to create customer consent messages to capture emails and grow your marketing campaigns. Marketing consents for B2B requires the CommerceMessagingAddOn license, which is packaged with Commerce Growth or Advanced editions. You'll need an enhanced CMS workspace and the refreshed Commerce app. It also requires Marketing Cloud and Data 360 and it uses Data 360 credits. Reach out to your account executive to learn more about credit usage. Marketing consents aren’t available for Reorder or Pay Now stores.
Create and Manage Marketing Consents: It’s important to build direct connections with B2B customers so you can build brand loyalty. With proper consent management, you can get customers’ email addresses and permission to send them marketing messages.
Marketing Cloud for B2B Commerce: Use Marketing Cloud and Data 360 with B2B Commerce to manage customer messaging and marketing consents in the Commerce app. Customize automated notifications, such as order confirmations and abandoned cart emails, from the Messaging workspace. You can also create customer consent messages to capture emails and grow your marketing campaigns.
Segment a Store into Markets Based on Locale: Instead of standing up multiple stores for different regions, use one store and segment your customers into markets based on locale. When customers visit the store, they can choose their locale. Based on their selection, the store displays prices, promotions, and entitlements specific to their market. You can have a total of up to 25 active locales for a store across all markets. For example, your store could have one market with 25 locales or 25 markets with one locale each. A locale can be used only one time across all markets assigned to a store.
Enable Markets for B2B Authenticated Buyers: With markets enabled, buyers can enjoy a more localized shopping experience. This personalization enhances the buyer experience and facilitates smoother transactions for international B2B buyers. Markets for B2B authenticated buyers is disabled by default. Enable this feature from B2B authenticated user access under store settings.
Mass Enable Accounts as Buyer Accounts for a B2B Store: Use any tool or mechanism that can create data inside of Salesforce—for example, Data Loader, Flow Builder, or the sObject API—to enable accounts as buyer accounts.
Create a Footer Link List Menu in a B2B Commerce Store: By default, the Link List component is located in the footer of each page in your store. In Experience Builder, you can edit this component to link to pages that describe your company, your privacy policy, your return procedure, or other important information.
Influence Product Positioning with Commerce Merchandising Rules: The ability to get the right products in front of your customers can reduce store abandonment and increase site conversion rates. Use merchandising rules to gain more control over the positioning of products in search results and category pages on your B2B Commerce store. Pin specific products to fixed positions on the category pages to ensure that high-priority products always appear where you want them, regardless of other ranking factors.
Considerations for B2B Commerce Product Bundles and Sets: A Commerce product bundle or set is a simple product that can contain simple products and variation products as child products. When you have bundles or sets and run Product Readiness for your catalog, Commerce checks for different product scenarios related to the parent and child products. Certain scenarios limit readiness. Before you create and configure a product bundle or product set for your store, keep these considerations in mind to increase readiness and support for other features, like search.
Manage Customer Messages for B2B Stores: Use the Commerce Messaging workspace to manage and tailor customer messages, such as order confirmations and welcome emails.
Set Up an Email Domain for Commerce Messaging: To use Commerce Messaging for your B2B Commerce stores, you must have a valid email address to indicate who the message is from. You can use the default address provided by Salesforce or create a from address using an authenticated store domain to provide a branded experience.
Enable a Message in Commerce Messaging: After you’ve customized your message template, enable the message to begin sending messages. When a message is enabled, a flow is created for that message and store. The flow waits for specific events, like the placement of an order, and triggers message sending using Marketing Cloud services.
Troubleshoot Commerce Messaging: If you don’t see a message or can’t enable it in the Messaging workspace, try these troubleshooting steps.
Customize Messages in Commerce Messaging: Use the provided message templates to customize your messages. You can also update the message templates with your store logo and colors.
Migrate a B2B Store Configuration: After you configure your store, you can migrate its configuration to a new environment, for example, from sandbox to production, by creating a change set. The change set includes the store’s metadata, such as descriptions, localization, pricing, and search settings.
Publish Your B2B Store as a Mobile App: Transform your LWR-based B2B store into a branded, native mobile app for Apple and Google Play. Using Mobile Publisher for Experience Cloud, you can offer buyers a secure mobile experience featuring push notifications, biometric login, and streamlined purchasing.
Considerations for Working with Multiple Pricing Recipes: If your org uses both Revenue Cloud and B2B Commerce, you likely have a Revenue Cloud default pricing recipe and a B2B Commerce default recipe. Note these considerations when managing multiple pricing recipes:
Update the My Account Theme Layout for a Commerce Store: The My Account theme layout provides persistent navigation on the left side of the page with page content appearing on the right. You can link to existing pages or create custom pages and add links to the layout’s navigation menu. When you add navigation links to the menu, they appear on all pages that use the My Account layout.
Offer Contract-Based Pricing to a B2B Buyer: Create a contract to define negotiated prices for a specific buyer account. Contracts override standard price book prices, ensuring buyers see their negotiated prices across store pages.
Order Management and Omnichannel Inventory: You can use Salesforce Order Management and Salesforce Omnichannel Inventory with B2B Commerce. Order Management helps you manage your orders throughout the order lifecycle, from creation to fulfillment to servicing. Omnichannel Inventory delivers real-time inventory availability data, helping you avoid costly undersells and oversells. If your B2B store integrates Omnichannel Inventory and you offer express payment options at checkout, then orders placed using those methods fail. Express checkout payment options don’t support inventory checks.
Open Source Components for B2B Stores: Open source components offer editable source code for standard B2B store components. Use an open source component to enhance the component or customize it to meet your requirements without having to rebuild the entire component.
Set Up a Strikethrough Price Book to Highlight Discounts: To highlight a discount that you granted to a buyer, you can show a strikethrough price next to the negotiated price. It’s called a strikethrough price because the value is shown with a line through it. The strikethrough price is the product’s original price or manufacturer’s suggested retail price (MSRP). The strikethrough price book is automatically created with your B2B Commerce store.
Orphaned Payments in Your B2B Commerce Store: Orphan Payments Sweeper automatically reverses or refunds payments that were authorized or captured at checkout but never tied to a completed order. The sweeper prevents funds from remaining stranded when a checkout is interrupted or abandoned. For abandoned authorized payments, the sweeper reverses the authorization or refunds the captured amount. The number of days required for the reversal or refund depends on the payment method.
Add a Third-Party Payments Service for Custom Checkout: For a B2B store using custom checkout, instead of using Salesforce’s native payment service, you can use a third-party gateway adapter to integrate with your store's checkout process.
Guidelines for Assigning Permission Sets: We recommend that you assign permission sets to users that grant them only the required permissions to carry out their jobs.
View Permission Set Overviews: The permission set overview page gives detailed information about permission set functionality. From there, view settings such as Object Settings, Flow Access, and System Permissions.
B2B Commerce Permission Sets: Permissions determine the information users can access and the actions they can take when configuring or shopping at a store. Salesforce provides preconfigured permission sets, which define multiple permissions for internal and external users.
Create a Buyer for a B2B Store from a Person Account: One way to add a buyer is to enable a person account as a buyer account and a customer user. The individual identified in the person account has access to stores related to the account’s buyer group. When you enable a person account as a buyer, you can't convert the person account to a business account. You also can't merge the account with other accounts. To merge or convert the account, you must disable it as a buyer, merge or convert the account, and then reenable it as a buyer.
Commerce Personas and Permissions: A typical B2B implementation involves several task-based personas, such as commerce administrator, merchandiser, developer, and shopper.
Pin Products to Category Pages: Pin up to 10 products to fixed positions on B2B category pages to ensure that high-priority products appear first. Pinned products override the sorting order and always appear first in the order you define. By pinning products to category pages, you can prioritize high-margin items, contract SKUs, safety-critical products, or seasonal promotions without developer support. Pinning rules apply per category and can vary by store and locale.
Release Resources and Reverse Payments for Failed B2B Commerce Orders: You can specify that when an order fails in your B2B store, reserved resources, including inventory reservations and coupon redemptions, are automatically released. You can also configure your store to automatically reverse payments associated with the failed order.
Preconfigured Permission Sets for B2B Commerce: Preconfigured permission sets provide B2B users, from customers to admins, with access to required features and functionality. An admin can customize a preconfigured permission set by cloning it and then modifying the individual permissions in the permission set.
Prepare Your B2B Store Catalog with Product Readiness: Before activating your catalog, run Product Readiness. After checking all products in the catalog against the default rule set, Product Readiness displays which products still need some attention.
High Order Volume for B2B Stores: Starting in Summer ’24, the High Scale Orders feature is enabled by default during checkout for new B2B and B2C stores created with the LWR template. However, some initial setup is needed to ensure that the High Scale Orders feature is fully enabled. In addition, developers must understand how this feature can affect their Apex code. The High Scale Orders feature isn’t supported for B2B Commerce Aura stores.
Prepare Your Commerce Store to Sell Product Bundles and Sets: To sell product bundles and sets, you add the Child Components related list to the Product object’s page layout. If you’ve set up your store using the Commerce Setup Assistant or created product sets before, the related list is already added. You then create a product relationship type for both bundles and sets. Most stores already have the product relationship types created. For out-of-the box product bundle support, your store must have the Cart Calculate API enabled.
Preview Merchandising Rules: After you create merchandising rules for your B2B Commerce store, such as boost or bury rules, you can preview how the rules affect product positioning. Access the Preview screen from the Rules workspace.
Pricing for B2B Stores: You can set up pricing for your B2B store by configuring a standard strategy and pricing procedure, or enable advanced pricing for more complex pricing use cases.
Use Custom Fields in B2B Pricing Procedure: Customize pricing rules by integrating custom fields into your pricing procedure. Extend the standard Commerce context definition to add your custom Account and Product attributes, such as Loyalty Status or Product Capacity. Map these attributes to the pricing context so they're available for use in your pricing procedure.
Pricing Procedure Plans for B2B Stores: Use procedure plans to customize how prices are calculated in your B2B store. A procedure plan is a framework that combines your pricing procedure with optional custom code (Apex hooks). The procedure plan defines the sequence that your custom logic and pricing procedure follow to calculate the final price.
Set Up a Pricing Strategy in a B2B Store: In a B2B store, a buyer can be a member of multiple buyer groups, or multiple price books can be associated with a buyer group or store. So it’s possible that an individual buyer can have multiple price books assigned to them. When multiple prices are available to a buyer, you can set a pricing strategy to determine which price is shown.
Guidelines for Adding Product Images to a B2B Commerce Store: Enhance the visual appeal and user experience in your store with product images. Showcase alternate views, list images, banners, and tiles to help customers better understand and engage with your products.
Add Media to Products and Categories: To provide more information about your products and categories, add images, videos, and attachments. You can associate media to parent and variation products. You can also associate a banner image to your B2B store’s product category pages.
CSV File Format for Importing Product Data to B2B Stores: You can import product data into B2B Commerce by creating a CSV file. Specify column headings for Product, Category, and Price Book information. Each row in the file represents a unique product and its variations.
Product Classes, Variations, and Attributes: A product class determines whether a product is sold individually or has variations. You can assign a product variation up to five attributes. Each variation has its own SKU so that you can track it.
Configurable Products and Bundles for B2B Stores: Offer configurable products and bundles so that buyers can customize their purchase to their exact specifications. The total price of the product or bundle updates dynamically based on the buyer’s selections.
Set Up Product Configurator for B2B Stores: Use the product configurator to offer configurable products and bundles to your buyers. To set up the product configurator, configure Revenue Cloud features, permissions, sharing settings, and advanced pricing. Then, create a configurator flow, assign it to your store, and republish your store.
Enhance Product Descriptions with Einstein: Generate product descriptions using Einstein Generative AI. Einstein uses your instructions to generate revised product descriptions for the selected product in your B2B or D2C store. Product descriptions support instructions in English only. You can generate descriptions in all languages in your B2B store. Then review the generated description and accept or reject the changes. You need the Einstein Generative AI license to use Einstein Generative AI. Any user can generate product descriptions with Einstein, but only the Salesforce admin can accept or reject recommendations. Contact your account executive for more information.
Product Image Optimization: B2B Commerce store components that include product images automatically scale the images for optimal performance and remain sharp across different devices.
Import Product Data for a B2B Store: Upload and import the CSV file that contains the products that you want to add or update for use by all stores.
Product Readiness: Improve your customers’ shopping experience with a comprehensive, consistent level of detail for all products on your B2B storefront. Use Product Readiness to find any products that are missing important elements that can make the product difficult for a customer to understand and purchase. Ensure that all the products in a catalog are storefront ready before you set the catalog to live.
Product Recommendation Sources in B2B Stores: Learn about the available recommendation sources and types for product recommendations in B2B stores. The Source setting defines the context used to generate recommendations, and the available Recommender options vary based on that selection. Select the right source for each page to deliver more relevant recommendations and improve the shopper experience.
Product Bundles and Sets for B2B Stores: Group products together in bundles or sets to increase sales, manage your inventory, and offer customers convenient buying options and savings. A product bundle is a collection of complementary products purchased under one SKU. The bundle’s parent product and child products are shown together on the product page under one price. A product set is a collection of related products displayed to shoppers. Each child product is priced separately. A shopper can add all the products to the cart in a single operation or selectively add individual products. Bundles and sets work for most B2B stores without any administrative setup.
Use External Product Media URLs in B2B Commerce: Add external URLs for product media instead of uploading them to Salesforce CMS. This feature is useful for large catalogs, where adding media for every product to Salesforce CMS individually can take days. This setting applies to all stores in your org, affects only product media (not category media, which continues to use Salesforce CMS), and takes effect immediately. After you enable the feature, add media URLs directly on the product.
Add a Product to a B2B Commerce Store from the Workspace: Add a product to up to five categories. The product can include variations such as color and size. You can also add digital products, which can be excluded from shipping calculations.
Enhance Product Fields with Einstein: Generate product text fields for multiple products in one process using Einstein Generative AI. Einstein uses your instructions and any linked reference fields to generate revised product text for the selected products. Product fields support instructions in English only. You can generate product text fields in languages in your B2B store. Then review the generated text and accept or reject the changes. You need the Einstein Generative AI license to use Einstein Generative AI. Contact your account executive for more information.
Manage Products for B2B Stores: Make products easy to find in your B2B store with informative product fields and descriptions. Enrich product pages with high-quality images and attachments to enhance the visual appeal and user experience.
Add a Product to a Custom Price Book: You can add products that are in your standard price book to a price book tailored for a specific store or buyer group. You can then manage the products in the custom price book for the audience.
Create a Purchase Quantity Rule for a B2B Store: You can define the minimum and maximum amounts of a product that a customer can buy and the number of products to add with each increase. You can assign a quantity rule to simple products and product variations. Because parent products aren’t sold, they don’t need quantity rules.
Purchase Quantity Rules for a B2B Store: A purchase quantity rule defines the minimum and maximum amounts of a product that a customer can buy and the number of products that are added with each increase. You can assign one purchase quantity rule to each simple product and product variation. In the rule, the minimum and maximum quantities must be multiples of the increment. For example, minimum 3, maximum 300, increment 3. You can define quantity amounts as whole numbers or as fractions up to four decimal places.
Enable Purchase Quantity Rules for a B2B Store: To make purchase quantity rules available for your store’s products, add the Quantity Rule related list to the Product object’s page layout.
Add a Promotion Tier for a B2B Store: Use tiers to create progressive discounts for a promotion. You can add tiers only to a promotion that was created as a tiered promotion. All discounts within a tier must be of the same type. You can create up to 10 tiers per promotion.
Target Customers with a Promotion Segment: Use segments to associate your promotion with specific stores or buyer groups. Then only customers who are a member of the store or buyer group can see the promotion. You can apply one promotion segment at a time to a store. A promotion segment can have up to 50 automatic and 50 manual active promotions.
Promotion Combinations: There are hundreds of ways to combine promotion levels, types, and qualifiers to craft the perfect promotion for your store’s needs.
Configure a Promotion: Create a promotion for your B2B store by adding segments, discounts, qualifiers, and coupons. Customize each element to target specific customer groups, maximize engagement, and boost sales.
Edit a Coupon for a B2B Store: Create a coupon code that customers can manually enter to redeem a promotion. Control the coupon usage by setting redemption limits and specifying the start and end dates.
Commerce Promotions: Enhance your B2B store by adding customized promotions. Create segments, discounts, qualifiers, and coupons for the right customers to receive the right deals. Highlight promotions for eligible customers on store pages and during checkout to boost engagement and sales.
Edit a Promotion Discount for a B2B Store: Modify a promotion discount to better meet your business goals and customer needs by adjusting the target audience, discount type, and amount.
Advanced Promotion Examples: When you’ve familiarized yourself with the basics of creating a promotion, here are a few ways to customize them.
Order-Level Promotion Examples: To create different types of promotions for a customer’s total order, use these discount and qualifier settings. You don’t need to specify a discount target for an order-level promotion.
Product Promotion Examples: To create different types of promotions for specific products, use these discount and qualifier settings.
Product Category Promotion Examples: To create different types of promotions for products in a product category, use these discount and qualifier settings.
Considerations for Commerce Promotions in B2B Stores: Optimize your B2B store promotions by considering key factors such as discount configuration, application timing, eligible recipients, and coupon requirements. Effective promotions can drive purchases and enhance customer loyalty.
Configure a Promotion for a B2B Store: Use the guided workflow to walk you through creating a promotion, including setting up discounts, qualifiers, and coupons. Choose from prebuilt templates to get started, or use Einstein to generate a promotion.
Localize Promotion Data: You can manually enter translated text for promotion names, display names, and terms and conditions if you have Data Translation enabled.
Prioritizing Promotions: When a cart is eligible for multiple promotions, your exclusivity and priority rules determine which promotions apply. Priority is first determined by exclusivity, which specifies whether a promotion can be combined with other promotions. Next, the promotion’s priority is based on its priority number, discount type, discount amount, and promotion ID.
Product Promotion Combinations: Product-level promotions provide discounts based on the type, number, and amount of products in an order.
Edit a Promotion for a B2B Store: Manage promotions by configuring a promotion record. You can edit a promotion’s details, such as the discount type, qualifying conditions, and duration, in the promotion record.
Edit What Qualifies for a Promotion for a B2B Store: Use a qualifier to set specific requirements for a discount to be added to a promotion. For example, you can require customers to spend a minimum amount to qualify for a percentage discount on a particular product.
Remove a Promotion: You can remove a promotion from your store temporarily or permanently.
Create a Promotion Using the Guided Workflow with Einstein: Draft a promotion for your B2B store with just a few clicks by using Einstein and Commerce data. Quickly create basic and advanced promotions using natural language instructions and generative AI.
Considerations for Einstein Promotions: To create Einstein Promotions with Einstein Generative AI, consider supported functionality, usage, limitations and allowances, limits, and other issues.
Publication and Activation: When you’ve previewed your pages and are ready to start selling, it’s time to make your B2B Commerce store available to your customers. First, configure a custom domain and CDN. Assign the store a custom URL. Then publish the store and activate it.
Publish Your Store: As you work on your B2B store, you can preview what it looks like to customers. When you’re ready to make it public, you publish the store and then activate it. You also republish your store whenever you make changes.
Qualification Rules in Your B2B Commerce Store: Using qualification rules in your B2B Commerce store simplifies the process of defining which products are available to which buyer groups, reducing implementation costs and significantly simplifying product configuration.
Set Up Commerce with the Automated Assistant: Use the automated and guided assistant to configure your Salesforce org for Commerce and create an online store. Preview and polish the store before going live.
Refresh B2B Store Pricing Decision Tables: To ensure accurate price calculations, map your price records to the correct pricing logic. Use the table to identify which Decision Table handles each pricing component type.
Customize the Refreshed Commerce App: In Summer ’24, Salesforce introduced a refreshed Commerce app with enhanced navigation and features designed to simplify online store management. If you've been using the Commerce Storefront Console app and have customized pages, you can add those custom pages to the refreshed app. You can also modify the navigation for the refreshed app.
Sharing Settings for a Commerce Reorder Portal: When a rep invites a contact to a reorder portal, the action creates order summary records for the context order and the past year of order records associated with the contact. Make sure that both the sales rep and reorder portal buyer have read access to these order summary records.
Request for Quote: With Request for Quote, buyers in B2B stores can request quotes for complex or high-value purchases directly from their cart. You can review and manage the quotes in Sales Cloud or Agentforce Revenue Management. This streamlined negotiation process provides insights into buyer intent to help you close deals faster.
Customize Contract Resolution with Apex Hooks: When multiple contracts apply to the same product and account, Salesforce selects a contract by matching the account, product, and product selling model, along with the contract currency and effective date. To resolve contracts using your own logic, add custom Apex logic to override the default resolution and select the contract for each product.
Commerce Resources: In addition to Salesforce Help, Commerce has documentation resources to help you successfully learn about, set up, administer, and extend the B2B apps.
Agentforce Revenue Management for B2B Commerce: Create products with personalized offerings that cater to your B2B customers. Present complex product offerings, and validate product selections instantly. Handle complex pricing strategies, and provide advanced configuration, pricing, quoting, and subscription management tools.
Manual Salesforce Tax Solution: You can set up taxes for your B2B store by using the manual Salesforce tax solution. The manual tax solution is available only with a custom checkout configuration. Configure tax rates and tax treatments and assign them to the store’s tax policy.
Manage Product Search Filters for a B2B Store: Help customers narrow their search results by managing product search filters in B2B Commerce. Configure filters for standard product fields, such as price and product family, or variation attribute fields, such as size and color. Control how filter values appear to buyers by setting the sort order for each filter.
Automatically Select the Most Relevant Facets: Automatically select, order, and display the most relevant facets based on search results of your B2B store. For example, a customer searching for "Shoes" sees categories like "Boots," "High Heels," and "Sandals" based on the number of results of each category.
Product Custom Fields in a B2B Commerce Store: Custom fields have characteristics that affect whether you can control the field’s searchable, facetable, displayable, and sortable behavior.
How Behaviors Are Controlled: Each product in your B2B Commerce store is a record of the Product2 object. Use the Product2 object fields to control the behavior of sort, search, facet, and display. All Product2 standard fields are available to all products in your store. If you add custom fields to the Product2 object, those fields are also available to all store products.
Controlling Standard Product Fields for Search in a B2B Commerce Store: Product and product category standard fields have characteristics that affect whether you can control a field’s searchable, facetable, displayable, and sortable behavior. You can use these characteristics to make it easier for customers to discover products when they search your store.
Create a Synonym Rule for B2B Store: Define one-way or two-way relationships to map buyer search words to your catalog data. Connect alternate phrasing, informal words, or regional terms to your exact product names to make sure that buyers find relevant products even when they use search terms that don’t exactly match your catalog.
Modify or Remove Searchable Custom Fields: Before renaming or deleting a custom field that is configured as searchable in your B2B store, mark it as not searchable, and remove it from Results Filters, Sort Rules, and Displayable Fields.
Configure How to Display Search Results: Define how many values appear for each search filter and how many search results to show on a page. You can choose to skip additional entitlement checks, automatically select and display relevant facets, and group search results under parent products.
Enable Partial SKU Search in Your B2B Store: Reduce "no results found" errors by enabling buyers to locate products using incomplete or unformatted SKUs. For example, buyers can search for a product with SKU "SKU:123-57-ABC" by entering "ABC", "57-AB", "1235", or "123-5". The search query matches the terms buyers enter to parts of the SKU, ignoring hyphens, underscores, spaces, periods, or slashes.
Commerce Search Index: The search index makes products in your B2B Commerce store searchable. Rebuild the search index after making updates to your store so that the changes are reflected for your customers.
Update the Commerce Search Index: Update your search index so that changes to your products appear on your search and category pages. You can manually update the index or turn on automatic system updates.
Commerce Search Index Considerations: Before activating your B2B Commerce store, update your search index to enable shoppers to see products on your search and category pages. Also update the search index after you make changes to your store configuration or product catalog. If you only modify price books or price book entries, you don’t need to update the index unless you have a sort rule based on price. You can manually update your index or turn on automatic updates.
Commerce Search Index Error Mapping: Updating the search index can result in product errors and index failures. If all products have errors, the index fails. Review index failures in the red banner on the Search Index page, and review product errors in the orange banner. You can also download a CSV file to resolve product errors. Product errors and index failures are refreshed with each partial index update.
Commerce Search Index Troubleshooting: Updating the search index can result in product errors and index failures. When some products have errors, you can download a CSV file on the Search Index page to review and resolve the errors. If all products have errors, the index fails. A common reason for product errors and index failures includes exceeding limits.
Commerce Search Index Update Methods: You can run a partial or full search index update depending on the type of information that has changed in your B2B Commerce store configuration or product catalog.
Languages Supported for Search Results: Search for B2B stores supports all languages provided by Salesforce. For D2C stores, search results are returned in the language of the store. For B2B stores, search results are returned in the language assigned to the buyer’s user account. If a buyer is configured to use a language that isn’t enabled for the store, search results, including facet and filter values, are returned in the store's default language.
Sort Options: Add and modify sort rules to let customers arrange results in search and category pages of B2B Commerce stores. You can create rules from available products and product attributes and define how these rules appear to customers.
Mark Product Fields as Searchable or Not Searchable for a B2B Commerce Store: Marking fields as searchable helps the search engine index more content, improving search accuracy and relevance in you B2B Commerce store. Avoid marking fields as searchable if the fields contain sensitive information or provide generic data.
Mark Products as Searchable or Not Searchable: After you create your initial search index, all products in the catalog are searchable by default. If you want to make a product not searchable, you can exclude it from search. You can change whether a product is searchable at any time.
Set the Maximum Number of Values per Facet: On Category Detail and Search Results pages of B2B Commerce stores, facets can have values that buyers use to further narrow the products that are returned. For example, a facet like “shoes” can have values like “women,” “men,” and “children.” You can specify the number of values that a facet can have.
Create a No Search Results Message: If you have a B2B store built using an LWR template, you can display a message on the search results page when there are no results. Use the No Results Layout component in Experience Builder to display and modify the message.
Before You Begin: Other features in your B2B Commerce store and in your Salesforce org can affect whether a product is discoverable.
Set the Maximum Number of Results per Page: You can limit the number of products that appear per page on Search Results and Category Detail pages of B2B Commerce stores.
Search Suggestions for B2B Stores: Search suggestions offer term and product suggestions, making it easier and faster for buyers to find relevant items.
Search Suggestions for B2B Commerce Stores: Boost user experience by showing relevant terms as customers type and highlighting bestselling products under the search bar even before they start typing. Additionally, offer specific product suggestions with images.
Search and Merchandising: Get the most out of your B2B Commerce store by helping shoppers find what they’re looking for.
Set Up Search Suggestions: To enhance the search experience in your B2B store, configure the Search Suggestions section in the Search Box component. You can use the Search Box component to provide search term and product suggestions to your buyers, including recent suggestions and bestselling products.
Reduce Entitlement Checks for Faster Search Results in B2B Commerce Stores: User entitlement checks are run as part of a search index update and also when retrieving search results. Though applying both entitlement checks ensures the most accurate information is provided in Search query results, you can get faster search performance by skipping the second entitlement check.
SKU Search: SKU search helps customers quickly find products by searching for SKUs. In B2B stores, you can enable partial SKU search, which allows buyers to find products even when they enter incomplete or unformatted SKUs in a search query. Partial SKU search isn’t available in D2C stores.
Select a Price Book for Sorting: To arrange search results in your B2B store by price, select a price book for sorting. The price book you select is always used for sorting, regardless of whether a customer is assigned to a different price book based on buyer group or entitlement policy. Deleted, archived, or inactive products are excluded from search results, which are sorted based on the store’s default currency. If the store's default currency is set to one type, such as EUR, and you sort the products by another currency, such as USD, products without prices in the sorting currency but with prices in the default currency are still considered to have prices and are displayed in the middle of the sorted list, while products without prices in the default appear at the end of the sorted list.
Enable or Disable Sort for Search Results: Sorting is enabled for search and category pages in B2B Commerce stores by default. However, you can control whether customers can see the sorting menu that appears on these pages with the Results Layout component. You can change the sorting properties on any page that uses the Results Layout component.
Add a Sort Rule: Create a sort rule based on available products and product attributes to let customers arrange results in search and category pages for B2B Commerce stores.
Edit or Delete a Sort Rule: You can edit a sort rule and change where it appears in the sorting menu of your B2B Commerce store. To remove a sort rule from the sorting menu, delete the rule.
Synonym Rules for B2B Stores: Synonym rules define relationships between different search terms that buyers use to describe the same product. Buyers often search using everyday language rather than your exact catalog terms. By mapping alternate words to your catalog terminology, synonym rules ensure searches return relevant results and make products easier to discover. Configure one-way rules for targeted mappings or two-way rules for fully interchangeable terms. For example, a one-way rule allows a search for “sofa” to return products named “couch”, while a two-way rule ensures searches for either term return results for both.
B2B Commerce Search and Auto-Correction Management: Auto-correction, or typo tolerance, helps customers find the products that they’re looking for when they inadvertently enter incorrect search terms. Typo tolerance corrects suggestions by matching and returning terms similar to the terms entered in a query. For example, if a customer mistypes shert in the search bar of a site that sells apparel, typo tolerance can suggest terms like shirt.
Assign Weights to Searchable Product Fields: Assign weights to searchable product fields such as Name, SKU, and Brand to prioritize high-value matches in search results. By assigning weights on a scale of 1 to 10, where 1 is the lowest and 10 is the highest, to searchable fields, you can control which fields carry the most influence in search rankings. By assigning weights to standard and custom searchable fields, product attributes, and category fields, you can influence ranking behavior without requiring backend engineering or AI intervention.
Configure Self-Registration for a B2B Store: When you enable self-registration, customers can create their own account and then log in to your store using that account instead of browsing as a guest.
Search Engine Optimization (SEO) for B2B Commerce: Search engine optimization (SEO) helps customers discover and explore your store through search engines. Use a combination of creative and technical SEO strategies to enhance your store's search engine rankings and visibility.
Add URL Slugs to B2B Commerce Store Pages: You can add a URL slug directly on a Product or Category record, or bulk update Products and Categories with a CSV file import. To use URL slugs, first configure languages and localizations for your store. You can only add one URL slug for each language. When you enable URL slugs, default URLs for product and category pages are updated. For example, product pages use the base URL /product/:urlName.
CSV File Format for Importing Category Data for a B2B Commerce Store: When you construct a category import file, specify column headings that correspond to category path, URL slug, and category description information. Each row in the file represents a category and its structure. The column headings are case-insensitive, and the columns can be in any order.
SEO-Friendly URLs for Store Categories: Set up SEO-friendly URLs for a B2B Commerce store’s categories in bulk using a category import. When you perform a category import, you can also add or update category paths and descriptions.
SEO-Friendly URLs for B2B Commerce: Use canonical URLs and configure URL slugs to ensure your store’s URLs optimally serve users and search engines.
Import Category Data for a B2B Commerce Store: Use a category import to add or update category paths, descriptions, and their corresponding SEO-friendly URL slugs. Product import files can also include columns for categories, but a product import can’t include URL slugs or descriptions for categories.
Configure Meta Tags to Commerce Store Pages for SEO: To improve your products’ search engine visibility, add meta tags that describe the product. You can add product titles and descriptions individually or generate meta tags for multiple products at once using Einstein generative AI.
Page Meta Tags for B2B Commerce: Meta tags in HTML documents provide structured data used by search engines for ranking and to show content in search results. You can configure page meta tags, such as titles, descriptions, and headings, in your store. For product and category pages, the Title Tag and Meta Description product and category fields determine the title and description meta tags.
Manage the Store Sitemap: Sitemaps for B2B stores improve SEO by giving search engines structured information for more efficient indexing. Like other Experience Builder sites, B2B stores automatically refresh their sitemaps weekly. You can also generate a manual sitemap refresh every 24 hours.
Store Snapshots for SEO: To improve SEO performance, B2B stores provide web crawlers with SEO optimized HTML using the Content Snapshot service.
Structured Data for Commerce Product Meta Tags: Create rich and engaging search results by using structured data from your store to dynamically update a page’s meta tags. For example, you can map product attributes like color or size to meta tags using expressions.
Set Up Displayable Fields in Commerce (Beta): Set up the category, custom, and standard product fields that you want to enable as displayable on your search, product, cart, and checkout pages for B2B Commerce stores.
Set Up Inventory for B2B Stores: To integrate inventory with your store, use Omnichannel Inventory or a custom provider. Use the Commerce Setup Assistant to quickly configure default settings in Omnichannel Inventory. You can also manually configure your store to add custom integrations.
Manually Set Up Inventory for a Commerce Store: You can manually configure Salesforce Omnichannel Inventory or a third-party inventory service if you don’t want to use the Commerce Setup Assistant.
Set Up Salesforce Native Shipping for Custom Checkout: Provide customers accurate shipping methods, including default free shipping, flat rates, and custom rates with the Salesforce native shipping service for your B2B store.. You can use the shipping service with custom checkout or managed checkout, but if you configure your store using custom checkout, you must add the shipping service manually. You can create custom shipping zones and turn off shipping if you don’t sell physical goods.
Set Up Pricing for B2B Stores: Select a price book, pricing strategy, and a custom pricing service provider. Physical products require a price book entry, without Product Selling Model (PSM) to show pricing on category and search pages. If a product only has a PSM with no base price, the price doesn’t show on the search or category pages.
Add a Third-Party Shipping Service for Custom Checkout: A shipping calculation service determines how much customers pay for shipping in your B2B store. Instead of using Salesforce’s native shipping service, you can add a third-party shipping application to your store or set up your own shipping service.
Products and Pricing: After you create your B2B store, you can set up your products and pricing.
Add a Tax Calculation Service for Custom Checkout: A tax calculation service determines how much your customers pay in taxes based on their location. You can set up the Salesforce Tax Solution or use a third-party tax calculation service for your B2B store.
Set Up Lowest List Price Compliance: When you announce a promotion or price reduction, a European Union (EU) mandate requires that stores must show the lowest price for a product over the past 30 days. If the original price is displayed and is greater than the list price, the lowest list price also displays. B2B stores must show the lowest price and any price adjustments for guest users but don’t need to show it for logged-in users. For new stores, the Lowest List Price component is included on the Product Details page. For existing stores, you must add the component to the page. After this feature is enabled, you can’t disable it.
Set Up Quotes in B2B Stores: Configure your store so that buyers can request quotes from the cart and track quote statuses.
Set Up Taxes in B2B Commerce: Setting up tax calculations for your B2B store ensures compliance with regional tax requirements, exempt certificates, VAT, and real-time rate changes during checkout. Salesforce B2B Commerce provides flexible options to calculate taxes based on your business model and operational needs.
Create a Shareable URL for Your Store: Customers can use a shareable URL to access your B2B store. The shareable URL contains a special URL parameter that's associated with a buyer group that has its own price book and discounts. Customers who get to the store using the shareable URL are automatically assigned to the associated buyer group, either in addition to the buyer group the customer is already part of or instead of that buyer group, depending on how your developer set up buyer group extensions.
Cart Sharing in B2B Commerce: With the advanced cart management feature, B2B Commerce buyers can share a cart with other people on their account and control what each person can do with the cart. Cart sharing helps teams collaborate on an order and route it for internal approval before anyone buys.
Add Shipping Weight Options to a B2B Store: If you set up shipping rates based on weight, you can add fields to the product page to enter weight for individual products.
Configure What Shoppers or Buyers See When a Store Isn’t Available: When a CDN is enabled for your B2B Commerce store, the Service Not Available page is available in Experience Builder for you to customize with your own brand and message. Shoppers and buyers see the Service Not Available page when your store is unavailable.
Enable Order Fulfillment from Multiple Addresses for Custom Checkout: When a customer chooses to send products in one order to different addresses, you can fulfill the order from multiple locations. The Split Order Fulfillment flows create a fulfillment order for each address. You can also manually split fulfillment for an order.
Set Up a Standard Price Book: All products in your B2B store must be included in the standard price book before you can add them to custom price books for specific stores or buyer groups. You can have only one standard price book.
Commerce Store Components: Components are the building blocks of B2B stores. You can make a B2B template yours by dragging components onto store pages and customizing component properties.
Default Import Records for a B2B Store: When you create a store, several required records are created by default. The only default record that you can delete is the category.
Configure Default Store Navigation: Use Experience Builder to set up the default navigation of your B2B store to use product categories. Customers use the categories to navigate the store.
B2B Store Setup Considerations: The Commerce Setup Assistant and the Store Setup Assistant work together to create a guided path for store creation. This path is simplified to get you up and selling as fast as possible. However, you can customize a store for your specific needs by configuring locales, languages, and currencies. If you haven’t configured these before creating your store, only the default options configured for your Salesforce org show. You can update these values after creating your store.
Commerce Store Setup Tasks: To get your store running, complete the guided tasks on the store home page. You can complete the recommended tasks after you activate your store.
Connect a B2B Store to Your Domain: Redirect shoppers to your Commerce store when they enter your domain URL. When you connect your store to a domain, your store has access to the Salesforce content delivery network (CDN), with Cloudflare as the CDN partner. If you don’t yet have a domain, you can choose one from the sample registrars or any other trusted registrar.
Structure of the Store Data Translation Source File: The XLIFF source files for products, categories, and promotions include each object’s translatable fields. Each data source file’s element structure is specific to your store’s products, categories, or promotions. To avoid missed translations, download the XLIFF source files after your products, categories, and promotions are set for your store launch.
Create Subscription Product Bundles in Your B2B Commerce Store: Bundle related digital subscription products together as a single SKU. Specify a parent product for the bundle, and add child products to the bundle. Also specify the price of the bundle. At present, you can bundle only digital subscription products.
Configure Checkout to Support Subscriptions for B2B Stores: To support subscriptions, your B2B store must use Custom Checkout with Salesforce Payments as your payment provider. You can customize the Salesforce native shipping service with an Apex extension to support subscriptions. Or, you can use a third-party shipping provider. After you configure checkout, you can sell subscription products in your store.
Configure Commerce Pages to Support Subscriptions: To create subscription products in a B2B store, modify the Price Book Entry and Product page layouts to show the product selling model option. After you modify these page layouts, you can create subscription product selling models and subscription products.
Configure Subscription Shopping in a Commerce Store: In Experience Builder, customize your B2B store pages so that shoppers can purchase subscription products and manage their active subscriptions from their profile.
Considerations for Using Commerce Subscriptions: In B2B stores, you can sell digital subscription products. Commerce Subscriptions is supported by Revenue Cloud, but it’s a separate product from Revenue Cloud’s Subscription Management. Before you create and configure subscription products for your B2B store, or before you switch from Subscription Management to Commerce Subscriptions, keep these considerations in mind.
Create a Digital Subscription Product in a Commerce Store: You can create a one-time, evergreen (non-expiring) subscription, or a term-defined (expiring) subscription for digital products. To create a subscriptions product for a B2B store, you first must create a proration policy and a subscription Product Selling Model (PSM). Then you can add the policy and PSM to an existing or a new product that you want to sell as a subscription.
Enable Advanced Pricing and Subscriptions in Your B2B Store: Use Advanced Pricing for Commerce Powered by Revenue Cloud to define subscription pricing and bundle pricing. When Commerce Subscriptions and Advanced Pricing are enabled, all products (both subscription and non-subscription) are priced using Advanced Pricing for Commerce Powered by Revenue Cloud.
Subscription Products and Pricing for B2B Stores: Create, manage, and sell digital products in your B2B store through an integration with Revenue Cloud. Bill and collect payment from customers on a defined schedule, and manage subscription pricing policies. Only authenticated users can check out a cart with subscription items.
Assign a Tax Policy to a Product: After you select the default tax policy for your B2B store, the tax policy and tax treatment for your products are updated. To override the default tax policy for individual products, assign a new tax policy to each of the products. You can manually assign tax policies to products only if your store is using Stripe or an extension provider.
Show Tabs for Manual Salesforce Tax Solution: If you’re using a Salesforce org provisioned with B2B Commerce before the Winter ’23 release, make the tax-related entities visible for your B2B store.
Taxing and Promotion Adjustments with the Manual Salesforce Tax Solution: Items that are part of a promotion or tier adjustment in a B2B store configured with the manual Salesforce tax solution are taxed after the promotion amount is subtracted from the product price. The tax is calculated on the adjusted amount.
Tax Service Extensions and Calculator Services: Taxes in a B2B store often consider exempt certificates, VAT, regional jurisdictions, and real time rate changes. To handle this complex tax calculation and ensure compliance and accuracy, you can use a provider-extension model.
Manually Localize Store Labels: Some B2B component labels are translated for you into the store's selected language, but you need to manually translate some labels. To translate your store’s text elements in bulk, use the translation tool.
Localize Store Labels in Bulk: When you add languages to Experience Builder, some component labels are translated for you into the selected language. If you add more languages, you can translate your B2B store’s text elements in bulk by using the translation tool. You can also translate configurable labels manually in the component properties.
Enable Translation Workbench: To assist with localizing B2B store information, enable the Translation Workbench and add the languages that you want to use in your stores.
Manage Translations for B2B Commerce Stores: You can translate the product, category, and promotion text. If you’re using product variations, you can also translate the variation attribute names. In Experience Builder, you can localize the store component labels.
Disable Shipping for a B2B Store: If you’re using managed checkout or native Salesforce shipping for custom checkout, you can turn off shipping for stores that don’t ship physical products. Turn off shipping for stores offering digital goods, service subscriptions, or in-store pickups.
Secure Buyer Contact Updates with Two-Step Verification: Secure buyer contact updates for a B2B Store with one-time passcodes (OTP). If a shopper changes their email address or phone number, an OTP is first sent to their current email address to confirm their identity. A second OTP is then sent to the new email address or phone number to verify the change. This process ensures that only authorized shoppers can update their contact details.
Use Case: Set Up and Capture Shopper Consent for a Marketing Campaign: Promotional emails are a great way to increase sales and improve engagement with your Commerce store. Before you can start sending discounts to a customer, you need their explicit permission. In this use case, we show you how to configure consent across B2B and Marketing Cloud. Then, we walk you through how to create a promotional discount and add it to an email campaign.
Use Case: Create Promotions for Buyers Who Make Large Purchases: Use Data 360 to create customer segments based on buying frequency or spending amounts. Offer these customer segments personalized promotions that target their buying behaviors. For example, a B2B store offers a bulk discount to customers who consistently purchase large quantities of a particular product. You can use these personalized promotions in B2B stores.
Use Case: Drive Customer Engagement with Emails Triggered by Shopper Actions: Increase shopper engagement by targeting your B2B customers with timely, personalized emails. Personalized emails with relevant content are more likely to get a customer’s attention and have higher open rates. Use the provided templates to send welcome emails, order confirmations, and abandoned cart reminders with content tailored to your customers. Personalized messaging can increase your marketing return on investment.
Use Case: Use Analytics, Insights, Goals, and Actions to Improve Site Conversion Rate: Intelligence analytics dashboards and calculated insights help you study how products, categories, search, and promotions affect your B2B or D2C Commerce site's conversion rate. Based on your review, you can complete recommended actions to help improve the site's conversion rate. You can also set goals to measure the performance of your completed actions and their impact on the site's conversion rate over time.
Use Case: Showcase Product Variations: In B2B stores, products often come in various colors, sizes, or styles. With variation products, shoppers can easily explore options without having to go to multiple pages. Show swatches on the Product Listing page for quick previews, and use dropdowns or pills on the Product Detail page for easy selection.
Use Case: Promote Product Discovery with Predictive Search: Keep customers in your B2B store by improving product search accuracy. Boost conversion rates and decrease bounce rates by helping customers find relevant products quickly and easily.
Use Case: Offer Tiered Discounts to Boost Sales and Clear Inventory: Encourage customers to increase their average order value in your D2C store by offering tiered discounts.Use this strategy to help improve overall sales and clear out excess inventory, especially for seasonal products.
Product Variations and Attributes: Use variations to extend the range of products that you offer in your B2B store. For example, add size and color options to a tee shirt. Configure variations to be searchable in your stores and available in multiple languages.
Localize Product Variation Data: If you’re using product variations in your B2B store, you can translate the variation attribute names into languages that your org supports to offer product variations in multiple locales.
Options for Displaying Product Variation Search Results: Configure how to display product search results on your B2B store’s Product List page. You can show all the variations of the parent product, show only the parent product, or show only the best match.
Product Variation Search Results: Choose how you want to display product search results on your B2B store’s Product List page. Options include showing all the variations of the parent product separately, showing only the parent product, or showing only the best match.
Configure How to Display Product Variation Search Results: Tailor how search results appear on your B2B store Product List page. You can opt to show only the parent product, only the best matching product, or all the variations of the parent product.
Design a Store in the Commerce Website Design Workspace: Use the Website Design workspace to add basic design elements to your store without leaving the Commerce app. Add your logo and set fonts, colors, and button styles. You can also modify the text, images, and header layout.
About the Manual Salesforce Tax Solution: The manual Salesforce tax solution is a built-in service that calculates taxes for B2B stores that use gross taxation—taxes are included in the product price. The manual Salesforce tax solution supports tax percentage calculations at the country, state, and province level. The manual solution is appropriate if you have a simple gross tax situation. In any case, consult with a tax expert when setting up taxes for your store.
Which Salesforce Commerce Product Do I Have?: Salesforce Commerce includes the B2B Commerce products and the B2C Commerce product. It’s important to know which product you’re using so that you can access the correct documentation and resources.
Commerce Workspace Considerations: Commerce workspaces are dedicated to specific merchandising jobs to help with the setup and ongoing management of your B2B store. The Commerce workspace list view functions a little differently from the standard Salesforce list view. Each workspace functions specifically for the type of data it’s meant to manage, but you can accomplish some common tasks across workspaces.
Commerce Workspaces: In the Commerce app, you can use multiple workspaces to make your work easier, find and update information, and organize shared content. You can access each workspace without having to leave the Commerce app. Understand the landscape of each workspace and the difference between the Commerce workspace list view and the standard Salesforce list view. Customize list views, apply bulk actions, and edit entries in the workspaces to manage your B2B store’s needs. Manage your store’s registered buyers and shoppers in the Customer workspaces.
Manage Commerce Store Data with Workspaces: With workspace lists, you can personalize your list view to work with just the records you’re interested in for your B2B store. Customize information to show and create filtered lists. Apply bulk actions and edit entries directly in the workspace.
Configure Internal Users for Commerce: Several internal users are involved in creating stores. System administrators perform Salesforce configuration tasks. Commerce admins perform commerce administration tasks, and merchandisers design and manage the storefront, import products, and configure search. Create a profile for these internal users, and then use the profile to create the users, assigning the appropriate permission set for each type of user.
Enable Person Accounts for Commerce: Person accounts are required for D2C stores, which use them to represent shoppers who visit the store and purchase products. Person accounts are optional for B2B stores, which typically use business accounts that include multiple buyers. You can either set up person accounts through the automated process from the Commerce Setup Assistant setup page or manually. This topic describes the steps to use to enable person accounts manually, without using Commerce Setup Assistant.
Enable State and Country Picklists for B2B Commerce Stores: Stores based on the LWR (Lighting Web Runtime) template accept only ISO codes for country and state or province. To minimize user entry errors, we recommend enabling state and country picklists, so that users select values from a list instead of typing them in. The picklists ensure that ISO codes are used consistently throughout the entire organization.
Composable Storefront Release Notes Archive: The Progressive Web App Kit (PWA Kit), Managed Runtime, and the B2C Commerce API make up the composable Storefront. Review and features and updates from releases published before October 2023.
Composable Storefront Features Released by Month in 2025: Composable Storefront features are released as often as monthly, so check back again soon for the latest changes. Composable Storefront for B2C Commerce is based on two key technologies: the Progressive Web App Kit (PWA Kit) for creating your storefront and Managed Runtime for hosting it.
Customize the Split Shipping Page in a B2B Commerce Store: After you enable shipping to multiple addresses, use Experience Builder to customize how you collect split shipment details from your customers on the Split Shipment page of a B2B store. You can customize split shipping only if your store uses custom checkout. You can’t use split shipping with managed checkout or with digital or subscription products.
Ayden Framework Upgrade: The Adyen framework library has been upgraded to version 1.25.9. This upgrade resolves an issue related to boarding a device with iOS 13.
Final Version of Endless Aisle and Module Code: Endless Aisle 2.5.4 is the final version of the reference app. No maintenance or support will be available for any version of the reference app after September 30, 2021.
Image Tests: A set of test images at commonly used sizes, including both 2x and 1x versions.
Get More Storefront Calls: The api.dw.net.HTTPClient.send quota has doubled. You can now make up to 16 storefront calls. The warning threshold has also been increased from 5 to 10.
Add a Location: Add a distribution center, warehouse, or retail store to use as a fulfillment location.
Add a Location Group: Add a location group to aggregate inventory availability across multiple locations.
Add Locations and Location Groups: Use the Omnichannel Inventory app to add locations, location groups, and location group assignments in this order.
Assign a Location to a Location Group: Use the Omnichannel Inventory Console to assign a location to a location group to aggregate inventory availability across multiple fulfillment locations.
Introduction to Omnichannel Inventory: Omnichannel Inventory is a scalable inventory solution that shows you near real-time inventory availability at the location level across all your fulfillment channels. Omnichannel Inventory combines the power of headless APIs and the flexibility of the Salesforce Platform to provide merchants and shoppers with a single source of truth for inventory availability. It integrates seamlessly with Salesforce B2C Commerce, B2B Commerce, D2C Commerce, and Salesforce Order Management, so you can deliver a true end-to-end shopping experience on your ecommerce storefront.
Customize the Omnichannel Inventory Console: While the standard Omnichannel Inventory console is fully functional right away, you can customize it for your team. Add custom tabs and fields, modify page layouts and components, and assign the app to particular user profiles.
Delete a Location: Use the Omnichannel Inventory Console to delete a fulfillment location when you no longer use it to fulfill orders. When you delete a location or location group, its inventory reservations are also deleted.
Delete a Location Group: Use the Omnichannel Inventory Console to delete a location group if you no longer use the location group to aggregate inventory availability. When you delete a location or location group, its inventory reservations are also deleted.
Edit a Location: Use the Omnichannel Inventory Console to change existing fulfillment location details.
Edit a Location Group: Use the Omnichannel Inventory Console to change existing fulfillment location group details.
Get Started with the Omnichannel Inventory Console: The Omnichannel Inventory console is the first thing you see when you open the Omnichannel Inventory app. Use to look up inventory availability, add and edit SKU counts, and manage locations, location groups, and location group assignments.
Import or Delete Inventory with a CSV or JSON File: Use the Omnichannel Inventory app to add, update, or delete inventory in bulk. You can use either a CSV or JSON file that contains the inventory SKUs.
File Format Guidelines for Modifying SKUs with Omnichannel Inventory: Use a CSV or JSON file to import, update, or delete SKUs. When you construct the inventory file, specify column headings that correspond to location, SKU, quantity, and availability information. If other fields are included, they’re ignored. We recommend that you use the provided sample CSV filei.
Manage Location Groups: Location groups represent sets of related locations. Assign locations to a location group. A location group provides an aggregate view of inventory availability across the locations in the group. Manage them using the Omnichannel Inventory Console.
Manage Locations: Locations represent physical locations—distribution centers, warehouses, or retail stores—where you have inventory available for fulfilling orders. Manage them using the Omnichannel Inventory Console.
Locations and Location Groups: Omnichannel Inventory aggregates inventory availability information across locations and location groups. Use the Omnichannel Inventory Console to add, edit, and delete locations, location groups, and location group assignments. Search, sort, and filter data in the list views, or customize the list views to show only the records or data that you want.
Omnichannel Inventory: Omnichannel Inventory is a scalable inventory solution that delivers near real-time inventory availability at the location level across all your fulfillment channels.
Omnichannel Inventory APIs for B2B and D2C Commerce: Get near real-time inventory availability, streamlined reservation processing, and location-based order fulfillment with Salesforce APIs and Omnichannel Inventory. Provide customers with accurate inventory information and efficient order management.
Omnichannel Inventory App: Use the Omnichannel Inventory app to view, add, and edit inventory SKU counts and manage locations, location groups, and location group assignments.
Omnichannel Inventory Connect REST APIs: Connect your inventory management process by connecting your Omnichannel Inventory service to Salesforce Platform apps. Use the Connect REST APIs to import and upload inventory files, access real-time inventory availability, and manage reservations.
Omnichannel Inventory Headless API Endpoints: Connect your Omnichannel Inventory service to your storefront and order management systems using Salesforce Commerce API endpoints. Import and upload inventory files, retrieve inventory updates from your back-office system, provide real-time availability data, and manage reservations. Maintain accurate inventory levels and ensure product availability across multiple channels.
Omnichannel Inventory Implementation Guides: These guides outline the necessary steps for Salesforce Administrators to understand, set up, and use Salesforce Omnichannel Inventory.
Omnichannel Inventory Integrations: Connect Omnichannel Inventory with B2C Commerce, B2B Commerce, Salesforce Order Management, and your back-office systems to optimize fulfillment across your network of stores and distribution centers.
Omnichannel Inventory Resources: In addition to Salesforce Help, Omnichannel Inventory has documentation resources to help you learn about, set up, administer, and extend Omnichannel Inventory.
Omnichannel Inventory Service: The Omnichannel Inventory service is a collection of APIs that you can use to get inventory availability data and manage reservations across all your fulfillment channels. Retrieve inventory updates from your back-office systems, such as WMS, ERP, and POS. Provide near real-time inventory availability to shoppers, and reserve inventory when shoppers submit orders. You can also share inventory availability by location and location group for order fulfillment.
Remove a Location from a Location Group: Use the Omnichannel Inventory Console to remove a location from a group when you no longer want to include it in the group’s aggregate inventory availability counts.
Omnichannel Inventory Reservation Lifecycle: When an item is added to a cart, an inventory reservation is created and assigned an ID. All subsequent actions for the reservation, such as cancel, unreserve, transfer, and fulfill, generate events that are grouped under the reservation ID. You can review which reservations have completed their lifecycle and which haven’t.
Modify Order Management Flows to Include Reservation Tracking: The Salesforce Omnichannel Inventory flows perform routing, cancellation, and fulfillment, which are all transactions available in the reservation lifecycle after a reservation has been created. Add the reservation ID to each flow as needed.
Reservation Tracking with B2C Commerce and Salesforce Order Management: To provide an end-to-end ecommerce experience for shoppers and use reservation tracking, integrate Omnichannel Inventory with both B2C Commerce and Salesforce Order Management. You can also integrate with B2C Commerce and other third-party management applications.
Cap Safety Stock: Safety stock acts as a buffer to control a location’s inventory and reduce the risk of running out of stock. Although safety stock works on a location level, it aggregates up to the group level and can impact other locations in the group. A safety stock quantity that exceeds a location’s on-hand stock can limit the available stock across the network when it aggregates to the group. Prevent underselling by capping your safety stock to prevent it from exceeding on-hand counts.
Shipping Eligibility for a Product: You can make an item ineligible to ship from a specific location but make it available for in-store pickup. This feature provides merchants more flexibility with how and from where an order is fulfilled.
Share Data Using Omnichannel Inventory File-Based Data Kits: File-based data kits simplify and streamline the deployment and management of data streams between Omnichannel Inventory (OCI) and Data 360. Using data kits makes integrating data efficient and automatic.
Shared Group Reservations: When an order is placed, Omnichannel Inventory reserves inventory to fill that order. Because a reservation can be held at a location group, the system considers that one or more of the group’s member locations can also be a member of another location group. Before the reservation is routed to an individual location, the system first attempts to allocate a location group reservation to individual locations that aren’t shared.
Reservation Tracking in Omnichannel Inventory: Reservation tracking simplifies the process of monitoring all reservation-related activities, from the moment that inventory is placed in a cart through fulfillment or cancellation. Each reservation has a unique ID that’s used to track actions associated with the reservation as it progresses through the fulfillment process.
View Commit Status: Async Operation logs store information about each batch of changes that you commit to the Omnichannel Inventory service. Use the logs in the Omnichannel Inventory Console to view details about committed changes and to troubleshoot issues with failed commits.
Deploy PWA Kit Storefronts with the Managed Runtime: The Managed Runtime deploys and operates PWA Kit storefronts so that front-end teams don’t have to worry about the operational cost and complexity of running mission-critical, highly scalable infrastructure. Set up single sign-on for authentication and authorization. Manage project users and permissions, auto-scale environments to handle traffic spikes, and protect against denial-of-service attacks.
Deploy PWA Kit Storefronts with the Managed Runtime (Generally Available): The Managed Runtime deploys and operates PWA Kit storefronts so that front-end teams don’t have to worry about the operational cost and complexity of running mission-critical, highly scalable infrastructure. Set up single sign-on for authentication and authorization. Manage project users and permissions, auto-scale environments to handle traffic spikes, and protect against denial-of-service attacks.
Deploy PWA Kit Storefronts with the Managed Runtime: The Managed Runtime deploys and operates PWA Kit storefronts so that front-end teams don't have to worry about the operational cost and complexity of running mission-critical, highly scalable infrastructure. Set up single sign-on for authentication and authorization. Manage project users and permissions, auto-scale environments to handle traffic spikes, and protect against denial-of-service attacks.
Deploy PWA Kit Storefronts with the Managed Runtime: The Managed Runtime deploys and operates PWA Kit storefronts so that front-end teams don’t have to worry about the operational cost and complexity of running mission-critical, highly scalable infrastructure. Set up single sign-on for authentication and authorization. Manage project users and permissions, auto-scale environments to handle traffic spikes, and protect against denial-of-service attacks.
Deploy PWA Kit Storefronts with the Managed Runtime: The Managed Runtime deploys and operates PWA Kit storefronts so that front-end teams don't have to worry about the operational cost and complexity of running mission-critical, highly scalable infrastructure. Set up single sign-on for authentication and authorization. Manage project users and permissions, auto-scale environments to handle traffic spikes, and protect against denial-of-service attacks.
Get More Functionality with OCAPI 22.4: With the release of OCAPI 22.4, new functionality has been added to some Data and Shop APIs. You can now search and sort creation_date and lastmodified_date in more Data API searches. In Shop API, use the new guest flag for the Order response document to determine whether the order was created by a guest or a registered customer.
OCAPI 22.6 - Manage Access Keys with Data API: With the release of OCAPI 22.6, Business Manager users with the Manage_Users_Access_Key permission can generate, delete, and rotate access keys for other users via a Data API call. The API automates access key generation and rotation for users who primarily use in-store apps to log in to the B2C platform. By using this API, these Business Manager users are no longer required to log in to Business Manager to generate or rotate access keys manually.
OCAPI Caching on eCDN: OCAPI caching is now supported on eCDN for the GET products API. OCAPI caching decreases the load of API requests to the origin, and improves the API response time by 50% or more - improving performance and load times.
Activate Omnichannel Inventory: Inventory availability in your store is only considered when the inventory integration is configured and turned on.
Step 5: Activate the B2C Commerce Integration: If you’re integrating Omnichannel Inventory with a Salesforce B2C Commerce storefront, follow these steps to activate the integration.
Activate the Integration: Activate the integration and start using Omnichannel Inventory with your B2C Commerce storefront.
Add Locations and Location Groups: Omnichannel Inventory is an external system that must know what location and location groups exist so it can track inventory properly. Set up your location graph by creating locations and location groups in your Salesforce org and committing them.
Add the Inventory Reservation Component to the Checkout Page (Deprecated): The Checkout Inventory Reservation component was deprecated in Summer ‘25. This component is no longer available in Experience Builder for new implementations. If you have an existing inventory reservation flow that uses this component before Summer ‘25, the component functions as designed. If you remove the component from the Checkout page, you won’t be able to re-add it.
API Access: The headless Commerce API is the main programmatic interface with Omnichannel Inventory. To use it, configure authentication via Account Manager or set it up as an external client app.
Step 3: Configure Omnichannel APIs: You can implement Omnichannel Inventory functionality via the headless Commerce API, Connect API, and invocable actions.
Assign Permission Sets in Omnichannel Inventory: There are three permission sets in Omnichannel Inventory, the inventory manager, the retail manager, and the merchandiser. The inventory manager has the widest range of access, including read and write permisssion to both inventory and location management. The retail manager has read and write permission to inventory data. The merchandiser only has read permission to inventory data.
Assign Permission Sets in Omnichannel Inventory: There are three permission sets in Omnichannel Inventory, the inventory manager, the retail manager, and the merchandiser. The inventory manager has the widest range of access, including read and write permisssion to both inventory and location management. The retail manager has read and write permission to inventory data. The merchandiser only has read permission to inventory data.
Salesforce B2C Commerce Considerations: If you use a Salesforce B2C Commerce storefront, be sure to consider these things as you plan your implementation.
Step 2: Integrate B2C Commerce: If you’re integrating Omnichannel Inventory with a Salesforce B2C Commerce storefront, configure the integration. Otherwise, skip to the next step.
B2C Commerce Inventory Modes: B2C Commerce can be in one of three inventory modes: Commerce Platform Inventory, OCI Cache Enabled, Omnichannel Inventory.
Connecting Omnichannel Inventory to Multiple B2C Commerce Instances: You can connect storefronts from multiple B2C Commerce instances or realms to a single Omnichannel Inventory instance so that all inventory is powered from a single source. All orders from the various instances are sent to a single order management for processing.
Omnichannel Inventory Basics: Familiarize yourself with basic Omnichannel Inventory concepts to help you plan your implementation.
Create a Location Graph for Omnichannel Inventory: A location graph consists of locations and location groups. You can create the graph using the Omnichannel Inventory console app, Connect in Apex, or Connect REST API.
Deactivate Omnichannel Inventory: This process includes steps to deactivate the connection between B2C Commerce and Omnichannel Inventory.
How Omnichannel Inventory Works: Review the typical flow when using Omnichannel Inventory with Salesforce Order Management and B2B Commerce and D2C Commerce.
Salesforce Omnichannel Inventory Implementation for B2B and D2C Commerce: Omnichannel Inventory is a scalable inventory solution that delivers near real-time inventory availability at the location level across all your fulfillment channels. It integrates with Salesforce B2B and D2C Commerce and Salesforce Order Management, so you can deliver a true end-to-end shopping experience on your ecommerce storefront.
Inventory Fulfillment Locations: Omnichannel Inventory uses three objects to represent the facilities that fulfill orders: Location, Location Group, and Location Group Assignment.
Fulfillment Locations in Omnichannel Inventory: Omnichannel Inventory uses three objects to represent the facilities that fulfill orders: Location, Location Group, and Location Group Assignment. The complete set of locations, groups, and assignments is called a location graph. When using D2C Commerce, your location graph is limited to one location and one location group.
The Inventory Lifecycle: This example illustrates the process of setting up and maintaining a system using Omnichannel Inventory with Salesforce Order Management and B2C Commerce.
Inventory Reservations: When an order is placed, the system reserves inventory to fulfill that order. A reserved quantity of a specific product at a location or location group is called a reservation. When a reservation is assigned to a location group, you can implement business rules to transfer it to a specific location for fulfillment.
Omnichannel Inventory Reservations: When a customer places an order, the system reserves inventory to fulfill the order and a reservation is created. When a reservation is assigned to a location group, you can implement business rules to transfer it to a specific location for fulfillment.
Location Graph: Set up your Location Graph by creating locations and location groups in your Salesforce org and committing them.
Omnichannel Inventory Basics: To help you plan your implementation, familiarize yourself with Omnichannel Inventory concepts.
Run the Commerce Setup Assistant: Use the Commerce Setup Assistant to configure Omnichannel Inventory. If you’ve already set up Commerce, run the setup assistant to update settings with optimized values. Other manual steps are required to complete the implementation.
Users and Permissions: To access Omnichannel Inventory features, users require either the System Administrator profile or the Omnichannel Inventory Manager permission set. You can assign the permission set to users with the Identity user license.
Account Fields: The Account object represents an individual shopper. When using person accounts, an account of the Person Account record type represents an individual shopper. When not using person accounts, a standard account and contact together represent an individual shopper. A business account buyer or shopper always has a standard account and a contact.
Account Objects: Learn about the Account objects and fields available for reporting in Order Management.
Activate the Exchanges with RMA Flow Template: The Exchanges RMA flow lets a customer service representative create even, uneven, and post-fulfillment exchanges. To use the flow, copy and activate the flow template, and then clone or customize the flow as needed.
Activate the Order on Behalf Of Flow Template: The Order on Behalf Of flow lets a customer service representative use OOBO or Order Entry to create an order on behalf of a customer. To use the flow, copy and activate the flow template, and then customize the flow as needed.
Add Classifiers to Flow: The final step in configuring Return Insights is to add classifiers to flow.
Add Country and State Picklists: To let customer service representatives (CSR) select state and country codes for an address from a dropdown menu, enable state and country picklists. If you don’t enable picklists, the CSR must enter the state and country code into the address, which can introduce errors.
Add the Exchanges with RMA Flow to an Object Page: Give customer service representatives easy access to the Exchanges RMA flow by adding it to the Actions & Recommendations component on a Lightning page for an object. Because all orders are associated with an order summary, add the flow to the Actions and Recommendations component on the order summary page.
Add the Order on Behalf Of Flow to an Object Page: Give users easy access to the Order on Behalf Of flow by adding it to the Actions & Recommendations component on a Lightning page for an object. Because all orders are associated with an account, add the flow to the Actions and Recommendations component on the account page.
Add a Service Flow to an Object Record Page: You can give users easy access to a flow by adding it to the Actions & Recommendations component on an object’s Lightning record page. Most Order Management flows service existing order summaries, so they’re usually added to the Order Summary record page. The Order on Behalf Of flow creates an order for a customer, so we recommend adding it to the Account page. That allows a customer service agent to create an order for a customer while viewing the customer’s account.
Address Fields: The Address object represents a mailing, billing, or home address.
Adjustment Objects: An adjustment object represents discounts applied to an order or order product. Adjustment summary objects provide a dynamic view of adjustments.
Alternative Payment Method Fields: The Alternative Payment Method object represents a payment method that doesn’t have a defined Commerce Orders object, such as Card Payment Method or Digital Wallet.
Enable Order Management Analytics: Connect your org’s Data 360 license to Order Management to access the Analytics dashboard and create and view calculated insights.
Order Management Analytics: The Order Management Analytics dashboard provides key metrics across the order fulfillment lifecycle. Use AI-generated insights to enhance decision making for your order management operations with real-time, unified data. Create data streams to bring Order Management data into Data 360. Then connect your Data 360 license to Order Management to create calculated insights for order fulfillment performance.
Automated Order Routing: You can use autolaunched flows to route orders to fulfillment locations. Order Management includes some flow core actions that you can use to implement configurable routing rules. These actions work together by first identifying locations that can fulfill an order and then determining which locations are closest to the recipient. You can also access this functionality using the Connect API.
B2C Commerce Connections: When you use a Salesforce B2C Commerce storefront, you can provision or deactivate integrated features, such as Omnichannel Inventory, Order Self-Service, Order Integration, and Cart and Checkout Data.
Billing Objects: Learn about the Billing objects and fields available for reporting in Order Management.
Charge Return and Cancel Fees: You can charge fees for an order item being returned or canceled. Create one or more products to represent the fees, then implement a return or cancel process that handles them.
Check for Active Process Exceptions: When a process exception occurs, Order Management creates a process exception record and generates a notification that appears at the top of the associated Order Summary page. The process exception typically states the problem that requires user review or intervention. Your business logic and workflows determine whether to continue processing an order summary when an exception occurs. When necessary, you can suspend order processing until the issue is reviewed and resolved.
Close a Managed RMA Return Order: When you receive returned order items, you can close the return order and process a refund to the shopper or buyer.
Close a Return Order for Exchange with RMA: After you've received the returned order items from your exchange, you can close the return order. Closing the return order completes the return portion of the exchange. The funds necessary to fund the new products only become available after the return order is closed.
Configure Commerce Delivery Service for B2C Commerce: Configure the Commerce Delivery Service (CDS) Commerce App to forecast delivery dates using your fulfillment locations, real-time inventory, processing and cutoff times, and carrier transit times. The estimated delivery dates appear on the Checkout and Product Detail pages on your Storefront Next site.
Configure Dynamic Revenue Orchestrator to Pause Status Changes: Coordinate fulfillment between Dynamic Revenue Orchestrator (DRO) and Order Management by configuring pause steps that wait for specific Order Management milestones. For example, pause fulfillment until all ordered items are delivered.
Order Management and Salesforce Flow: Order Management works with Salesforce Flow to help you to create manual and automated functions. We provide out-of-the-box flow templates for processes such as order summary creation, placing orders on behalf of shoppers, order fulfillment, and order servicing.
Configure Rejection Reasons: If a store associate can’t pick an item, they can select a reason for rejection. The options are Damaged, Just Sold, Out of Packing Supplies, Out of Stock, and Other. You can also create your own reasons.
Configure Store Associate Users: Set up your store associates and assign them the necessary permission set to access the store fulfillment app.
Connect B2C Commerce and Salesforce: To get product and pricing data from B2C Commerce, set up a connection between B2C Commerce and your Salesforce org.
Considerations for Deleting Order Management Records: Data protection and privacy policies can require deletion of records used in Order Management. Because many records share complex relationships, the order in which you delete them is important. If you delete a record before deleting another record that references it, the reference can cause errors.
Contact Fields: The Contact object is used with the Account object to represent an individual shopper. When not using person accounts, a contact and standard account together represent an individual shopper. When using person accounts, contacts aren’t used for individual shoppers. A business account buyer or shopper always has a contact and a standard account.
Create a Managed RMA Return Order: Use the return management authorization (RMA) workflow to create a managed return for one or more order items that have been fulfilled and are associated with a managed order summary.
Create a Process Exception: Create a process exception to manage a processing issue that isn’t automatically identified by your order management processing business logic.
Create an Unmanaged RMA Return Order: You can create an unmanaged RMA return order to manually track a return for one or more order items directly from the Order Summary page. You can create an unmanaged RMA return order only for items that are fulfilled and associated with a managed order summary.
Create Calculated Insights: To create your return insights, go to the Calculated Insights tab in Data 360.
Add Credit Types for Refunds: Add credit types to control and expand how refunds are returned when a customer returns an item. A customer service representative can divide the refund amount across multiple credit types.
Create a Markdown Avoidance Rule: A markdown avoidance reduces the risk of products selling at a discounted price by shipping products from locations at risk of future discounts. To implement a markdown avoidance, create a markdown avoidance rule in the Markdown Avoidance tab, sync it, and then add it to a rule group.
Create Return and Cancel Fee Products: For each type of fee that you want to charge, create a product record and one price book entry for each supported currency. The actual price doesn’t matter, because you specify the fee amount when you create a return order or process a simple return or cancel.
Set Up a Store Fulfillment Site: The Store Fulfillment template guides you through creating a fulfillment site. After you set up your site, make it accessible to anyone with the Identity User license.
Create Streams for Return Insights: You can complete most of the Return Insights configuration by using the Data 360 Setup guide. After you finish setting up Data 360, create data streams. Data streams are the connections and associated data ingested into Data 360.
Credit Memo Fields: The Credit Memo object represents an amount to be refunded after an invoice has been generated. This object can be associated with one or more change orders.
Credit Memo Line Fields: The Credit Memo Line object represents a portion of the amount of a credit memo. One credit memo line can represent the full amount of a credit memo.
Custom Weighted Routing Rules: A custom weighted routing rule provides a greatly expanded level of freedom when it comes to creating a rule. You can create a rule based on any standard or custom attribute available on Order Management objects. An attribute’s value or existance creates the condition for your rule, and the score and weight of each attribute and rule determine which locations get selected.
Customize the Order Management Console: Modify settings in the Order Management Console to make it your own. Configure custom tabs and fields, and modify page layouts and components to make it easier for users to find the information that they want.
Preview a Delivery Estimation: After you configure your delivery estimations, use the preview function to see how long it could take to ship and fulfill various items across your org. You can also preview when an order will arrive when a shopper creates an Buy Online Pickup in Store (BOPIS) order.
Deactivate a B2C Commerce Connection: Deactivate the B2C Commerce storefront integration or a related feature. Before refreshing or running DBInit on a B2C Commerce instance, deactivate all of its connections.
Configure Delivery Estimation for a B2C Store: Connect the Commerce Delivery Service to your B2C store and implement the delivery estimation service for checkout. Use this section as a guideline only. Your configuration may differ.
Set Up a Delivery Estimation: A delivery estimation contains information about a store and sales channel, including hours, processing times, and whether the store or sales channel support Buy Online Pickup In Store (BOPIS). The delivery estimation sets processing and store hour information for an entire location group. You can change this information for individual locations on the Location Assignment tab.
Delivery Estimation Prerequisites: After you install, configure, and turn on both Order Management and Omnichannel Inventory, there are a few prerequisites for Delivery Estimations.
Configure Processing Times for Order Management Delivery Estimations: Fulfillment times can vary depending on the product and the location fulfilling the order. Define processing times at the location level, category level, item level, or a combination. This granular level of processing data provides more accurate delivery estimates.
Set Up Shipping for Order Management: Order Management supports both managed and static shipping carriers. The managed shipping carriers are Canadian Post, FedEx, Royal Mail, UPS, and USPS. A shipping carrier method is a specific method that transports a product or order to its destination. For example, an org that uses the shipping carrier FedEx has the shipping carrier methods FedEx Overnight, FedEx Priority, and FedEx Ground.
Enable and Sync a Delivery Estimation: After you’ve configured estimations and shipping, and you’ve connected Commerce Delivery Services to B2C Commerce as necessary, enable your delivery estimation.
Deleting Information from Restricted Data Fields: Because some restricted fields can contain customer personal information, they’re subject to data privacy and protection policies. Compliance can require a user with appropriate permissions to mask or delete their values. Only a Salesforce admin or a user with the Edit Activated Orders permission can modify the restricted fields.
Configure a Delivery Method for Order on Behalf Of: To ensure that orders are consistently mapped from B2C Commerce, configure the delivery methods in your org that correspond to the shipping methods in your storefront.
Digital Wallet Fields: The Digital Wallet object represents a digital payment method.
Discount an Order Item: You can process a discount or price adjustment for one or more order items either before they’re allocated or after they’re fulfilled.
Distributed Order Management: Order Management includes tools for distributing orders across your fulfillment network based on custom business logic. If you use Salesforce Omnichannel Inventory, you can also incorporate its availability features into your order routing process.
Dynamic Revenue Orchestration with Order Management: Use the Dynamic Revenue Orchestrator (DRO) with Order Management to manage orders containing both physical products and digital services. With DRO and Order Management, customer service reps (CSRs) can see physical logistics and digital orchestration in one order summary, without switching between systems.
DRO for Order Management Prerequisites: Before you can use DRO with Order Management, enable the feature, clone the necessary flows, and set up Revenue Cloud DRO.
Deleting Order Management Records: Certain situations require that you delete Order Management records. For example, some records can contain customer personal information and are subject to data protection and privacy regulations. To maintain data integrity, before you delete records consider their dependencies and access restrictions on some of their data.
Order Management Editions: Learn about the editions and user interfaces that support Order Management.
Process an Exchange (Simple): Run an even exchange whenever a customer needs to exchange their product for a variant of the same product. For example, if a shopper orders a size large blue sweater and then decides that they prefer the same sweater in red, size medium, you can process an exchange.
Configure Flow for Exchanges with RMA: Exchanges with RMA support both EnsureFunds and EnsureRefunds. These variables must be configured properly in your org.
Exchanges with RMA Returns Overview: An exchange with an RMA return provides a more robust exchange experience for customers. Unlike a simple exchange, which only allows for same-cost variant exchanges, an exchange with RMA processes the return of the previous product before letting a customer service representative (CSR) order a new item, enter a new delivery address, and select a shipping method, all on behalf of the user. Finally, the CSR can process any refund or additional funds needed from the customer.
Exchanges with RMA Setup: After you have installed and configured either an Order Management, B2B Commerce, or D2C Commerce org, configure Exchanges with RMA Returns.
Enable Cancellation of All Eligible Items from an Order: You can use all Order Management service flows out of the box, and you can also customize a flow and expand its functionality. This customization lets a Customer Service Representative (CSR) cancel all eligible items from an order in a single process. You can enable Cancel All in the Cancel Item flow. If you’ve created your Cancel Item flow after the Winter ‘26 release, Cancel All is already enabled on your org.
Set Up a Default Fee for a Service Flow: You can use all Order Management service flows out of the box, and you can also customize a flow and expand its functionality. This customization ensures consistency across service fees and saves time while processing an order by setting a default fee.
Clone an Order Management Flow Template: Before you can activate or customize a flow, you need to clone the flow. Cloning creates an editable version that you can modify or activate out-of-the-box on your store. If you set up your store using the Commerce Setup Assistant, your flows are already cloned.
Customizing Order Management Service Flows: The Order Management service flows let customer service representatives (CSRs) help customers with their orders. You can use the provided flows as is, and you can also expand and customize them. Here are some common customizations that you can implement.
Choose Which Product Selector Fields to Show: You can use all Order Management service flows out of the box, and you can also customize a flow and expand its functionality. This customization tailors which fields a customer service representative sees when selecting products.
Set the Discount Tax Type: You can use all Order Management service flows out of the box, and you can also customize a flow and expand its functionality. This customization sets the discount tax type based on your store’s locale. Depending on the discount tax type, when a customer service representative discounts an amount off an order, the amount either does or doesn’t include the tax amount. You can set a discount tax type in the discount flow.
Enable Multiple Currencies for Even Exchanges: All Order Management service flows work out of the box, but there are some easy ways to customize service flows and expand their functionality. Orgs that support multiple currencies require customization to support the even exchanges flow. Only the even exchange flow requires customization to support multiple currencies.
Process a Product Bundle in an Order Management Flow: You can use all Order Management service flows out of the box, and you can also customize a flow and expand its functionality. This customization lets customer service representatives process product bundles.
Add a Reason Text Option to a Service Flow: You can use all Order Management service flows out of the box, and you can also customize a flow and expand its functionality. This customization gives customer service representatives more flexibility when tracking a return or discount by providing an empty field to add a reason.
Allow Multiple Credit Types for Refunds: You can use all Order Management service flows out of the box, and you can also customize a flow and expand its functionality. This customization lets you process returns as unreferenced refunds. Unreferenced refunds are disconnected from the original payment method, so the funds can be returned to any credit type. You can enable unreferenced refunds in the return and RMA flows.
Choose Whether to Allow Discounts for Allocated Items: You can use all Order Management service flows out of the box, and you can also customize a flow and expand its functionality. This customization defines whether a customer service representative can apply a discount to items that are already in the fulfillment process.
Customize a Flow for Omnichannel Inventory: You can use all Order Management service flows out of the box, and you can also customize a flow and expand its functionality. However, some service flows require customization to work with Omnichannel Inventory. This customization requires an Order Management Growth license.
Enable Inventory Checks on the Product Detail Page: You can use all Order Management service flows out of the box, and you can also customize a flow and expand its functionality. This customization lets customer service representatives (CSR) see whether a product is in stock from the product detail page. The inventory check helps reduce out-of-stock errors by giving the CSR up-to-date stock information before they add an item to a cart.
Set Up Bulk Actions in a Service Flow: You can use all Order Management service flows out of the box, and you can also customize a flow and expand its functionality. Bulk actions let your customer service representatives perform the same action on multiple selected products, up to 100.
Salesforce Order Management Flows: Order Management includes flow templates for creating, fulfilling, and servicing orders. The flows automate your business processes by collecting and using data to accomplish order-related tasks, such as returning or canceling an order. Some templates are available only with certain licenses, and some have special implementation considerations. You can customize the flows or run them as is.
Configure Fulfillment Locations: Configure the location object to represent your locations and, optionally, location priorities. Then create a location record for each fulfillment location.
Fulfillment Objects: Learn about the Fulfillment Order objects and fields available for reporting in Order Management.
Fulfillment Order Fields: The Fulfillment Order object represents a group of products and delivery charges on a single order that have the same fulfillment location, delivery method, and recipient. The products can be included in one shipment or split into multiple shipments. A fulfillment order is associated with one order summary.
Fulfillment Order Product Adjustment Fields: The Fulfillment Order Product Adjustment object represents a price adjustment on a fulfillment order product, usually a discount. It’s associated with an order product adjustment summary.
Fulfillment Order Product Fields: The Fulfillment Order Product object represents a product or delivery charge associated with a fulfillment order. It’s associated with one order product summary.
Fulfillment Order Product Tax Fields: The Fulfillment Order Product Tax object represents the tax on a fulfillment order product or fulfillment order product adjustment. It’s associated with an order product tax summary.
Fulfillment Processes and Flows: Order Management includes an unmanaged package containing sample flows and processes. The samples demonstrate how you can create a fulfillment process to allocate order items to a fulfillment location and generate a fulfillment order.
Fulfillment Types: Order Management provides three fulfillment categories and six fulfillment types. Each category is associated with one or more types. You can’t change the categories, but you can customize the list of types as long as you associate each category with at least one type.
Get to Know the Order Management Console: The Order Management Console is the first thing you see when you log in to Order Management. The Order Summary page is the primary workspace in the console.
Enable High-Scale Integration for Order Management: Salesforce orgs use high-scale order ingestion (HSOI) to create order summaries. HSOI can handle 5,000 orders placed per minute and 2,500 orders processed per minute for approximately 50 locations. Each order can have up to 2,000 lines.
High-Scale Orders and Deduplication: High-Scale Orders uses the Pending Order Summaries REST API to create summaries from order summary graphs. Entities included in the request parameter aren't subject to deduplication rules.
High-Scale Orders: High-scale orders, supported on Hyperforce, can ingest orders from B2C Commerce and other order channels. High-scale orders use an internal data service called Zero Object Service (ZOS), which acts as a buffer for storefront order data and prevents Order Management processing from being overwhelmed. ZOS then sends the buffered data asynchronously to Order Management, which creates order summaries and processes the orders.
Identify the Cause of a Process Exception: Process exceptions can occur at any stage in the order lifecycle. Identifying the cause of a process exception is the first step toward resolving the issue.
Create an API Client for Order Management (Optional): To help troubleshoot and gather metrics, create a dedicated API client ID for your Order Management integration with B2C Commerce. The API client helps you identify actions associated with the client ID. You can also use an existing API client and share it with other functions.
Prerequisites for Order Management: There are a few mandatory steps to take before setting up Order Management. Some of these steps depend on which Commerce product you’re running. Additionally, there are a few optional steps you can take before proceeding with the setup.
Configure Service Flow Reasons: When a customer service representative (CSR) services an order, they often have to select from a list of reasons, such as Wrong Item or Customer Changed Mind. Order Management provides some default reason values, but you can add more. Up to 2000 reasons can show on each flow’s return picklist.
Use Matching Rules for Shopper Account Identification: Order Management identifies an existing shopper by matching the shopper’s name or email address to an existing Account, Contact, or Person Account record. However, you can configure Order Management to use your org’s duplicate and matching rules instead when looking for existing shoppers.
Configure Custom Field Permissions: When you add a custom field to an object for use in Order Management, Order Management users need access to that custom field. Update each permission set that includes the custom field.
Enable Order Management for B2C Commerce: When you’re ready to send order data from B2C Commerce to Order Management, use Business Manager to enable the integration.
Configure Field-Level Security: Give the System Administrator profile permissions to access specific fields on order-related objects. These permissions allow users to access Order Management functionality.
Install Growth Order Routing: Because the Growth license can be purchased along with B2B, D2C, and B2C Commerce, all three products can use Growth Order Routing.
Import Historical Order Data: After you start using Order Management in production, you can import historical order data from a legacy system for reference purposes.
Custom B2C Commerce Storefront Data Integration: You can pass custom data on certain B2C Commerce objects to Order Management by adding custom attributes to objects in B2C Commerce and matching custom fields to the corresponding objects in Order Management. When an attribute ID and field name match, and the data types also match, the values are included in the created Order Management records. If you also create a matching field on the corresponding summary object, Order Management includes the custom data when it creates a summary record.
Implement Order Management: Order Management can run with all Commerce products. After configuration, there are some additional steps B2C Commerce orgs must take to link their stores with Order Management.
Manually Configure a Payment Gateway for Order Management: If you don’t use Salesforce Payments or you’re using B2C Commerce, you can manually configure a payment gateway to view and manage payments in Order Management. Configure a gateway for each payment provider, for example, Stripe, PayPal, Adyen, or Cybersource. Payment packages are available on AppExchange for some vendors.
Commerce Order Routing: Use the Commerce Order Routing flow to manage routing and fulfillment. Order Routing is optional unless your org uses Salesforce Payments. There are two versions of the order routing flow: Connected Commerce Order Routing and Growth Order Routing. Connect Commerce Order Routing can only be used with B2B and D2C Commerce.
Install Connected Commerce Order Routing: If you’re using Connected Commerce Order Routing, you can install the flow through the Commerce Setup Assistant. Because Connected Commerce only includes B2B and D2C Commerce, B2C Commerce can’t install this version of the app.
Payment Methods for Order Management with B2C Commerce: For B2C Commerce, the Order Management integration with Salesforce Payments supports credit cards, digital wallets, and non-card options, such as SEPA and iDEAL.
Payment Processing for Order Management: To let Order Management execute payment authorizations, captures and issue refunds, integrate a payments component. You can view payment activity in the order payment summary for each order.
Payment Sequencing: You can control the sequence in which to apply original funds or refund amounts to payment methods. For example, if an order is partially paid with a gift card, you can refund the gift card first, regardless of how the payment amounts were originally distributed. Or, if the order is modified between when different fulfillment groups are fulfilled, you can capture the partial payment amount from the gift card first in the case that a future order fulfillment is canceled, and preserve the full gift card amount.
Product Bundle Associations: Order Management doesn’t support custom attributes on B2C product options. To use product bundles, you can pass the information as custom data.
Connect B2C Commerce and Order Management: Set up a connection between B2C Commerce and the Salesforce org where Order Management is configured. This connection enables Order Management to receive orders from B2C Commerce and get product and pricing data for creating and updating orders.
Set Up Payment Gateways with StoreIntegratedService: Order on Behalf Of can take payment for the order and use the Commerce Webstore Payment Token and Commerce Webstore Checkout Payments APIs. To let your store access these APIs, use the StoreIntegratedService entity to associate your WebStore with the Payment Gateway.
State and Country Codes: The values that you use in your store order data must match in Order Management. The values that you can use depend on whether you enable state and country/territory picklists in Salesforce.
Integrate Order Management with B2C Commerce: Set up a connection between B2C Commerce and the Salesforce org where Order Management is configured. This connection lets Order Management receive orders from B2C Commerce.
Configure Gross Tax Display: If you only do business in a locale that uses net taxation, such as sales tax, no extra configuration is needed. If you do business in a locale that uses gross taxation, such as value-added tax (VAT), you need to configure your page layouts to display amounts that combine prices and taxes. If you’re using multiple currencies, add a user profile for service agents and create page layouts that use gross tax fields.
Update a B2C Permission Set After Adding a Custom Field: The Order Management B2C Service permission set provides access to Salesforce records. When you add a custom field to a Salesforce object, update the permission set by adding read and edit access to the new field. You also must add edit access to the permission set that provides access for your Order Management users.
Order Management Users and Permissions: To access Order Management features, users need the System Administrator profile or either the Standard Platform User profile or the Identity User profile along with the Salesforce Order Management feature permission set license. Users also require access to the Order Management console app and to any customizations that you implement. Order Management includes some persona-based permission sets that you can use as is or clone and customize.
Give Access to Person Accounts: If you’re using Person Accounts to represent shoppers, give access to the appropriate permission sets to access Person Accounts.
Order Management Web Store Records for B2C Commerce: Both the Even Exchange and the Order on Behalf Of flows require users to select a web store record that represents their B2C Commerce storefront. Order Management creates the required web store records for you. These system-generated web store records set the LocationType to Virtual. If you want to control the location or change other fields, you can create your own web store records.
Install Return Insights Package: After Data 360 and Einstein are configured on your site, install the Return Insights package.
Omnichannel Inventory: Omnichannel Inventory delivers real-time inventory availability at the location level across all your fulfillment channels. If you’re using Omnichannel Inventory with Order Management, you can get inventory availability data from the Omnichannel Inventory service and use APIs to transfer, fulfill, and release reservations. You can also manage fulfillment locations and location groups using the Omnichannel Inventory app.
Inventory Objects: Learn about the Inventory objects and fields available for reporting in Order Management.
Invoice Fields: The Invoice object represents an amount to be paid. This object is associated with one fulfillment order.
Invoice Line Fields: The Invoice Line object represents a portion of the amount of an invoice. One invoice line can represent the full amount of an invoice.
Salesforce Order Management Licenses and Allocations: Salesforce Order Management (SOM) license allocations are based on either the anticipated gross merchandise volume (GMV) of the order summary record or the number of order summary records created. Order summary records can be either managed or unmanaged.
Order Management Lifecycle Statuses: Each object type has status categories with default statuses that reflect the order lifecycle. Find these statuses in Object Manger, in the Statuses section of an object type. You can’t change the status categories, but you can customize and add statuses as long as you associate each status with a status category. Having status categories that never change is helpful if you have custom processes that depend on a record’s status category.
Location Fields: The Location object represents a location that fulfills orders, such as a warehouse or retail store.
Location Group Assignment Fields: The Location Group Assignment object represents the relationship between a location and a location group that includes it. You can assign a location to multiple location groups. If a location is assigned to more than one location group, each group has a location group assignment object.
Location Group Fields: The Location Group object represents a group of inventory locations. You can define location groups according to the logic of your business needs. For example, a location group can represent the warehouses in a geographic region, or it can include the fulfillment centers associated with a particular online storefront.
Managed and Unmanaged RMA Return Orders: Return merchandise authorization (RMA) return orders support both managed and unmanaged orders, so whatever degree of service you provide for orders, you can still keep a tight level of control over returns and refunds.
Map Reasons to Service Flows: Reduce the time and effort it takes to service orders by only showing reasons relevant to the current service flow. For example, when a Customer Service Representative (CSR) processes a return, they only see the return-related reasons in the reason picklist. Up to 2000 reasons can show on each flow’s reason picklist.
Monitor Order Management Integration Rejections: Detect and troubleshoot your Order Management integration failures by setting up a Log Center alert. When Order Management rejects an order after accepting it for asynchronous processing, B2C Commerce writes a warning entry to Log Center. Use these logs to monitor and troubleshoot order-integration failures.
Create a Custom Routing Rule: Custom rules modify routing by selecting locations based on any standard or custom attribute available on Order Management objects. Custom rules can filter out locations or select an ideal location by calculating condition-based scores.
Objects Used by Order Management: Order Management objects, together with existing objects, represent the elements of an order as it progresses through its lifecycle.
Order Adjustment Group Fields: The Order Adjustment Group object defines a related set of price adjustments to order products on one order. In Order Management, you usually interact with order adjustment group summaries instead of order adjustment groups.
Order Adjustment Group Summary Fields: The Order Adjustment Group Summary object defines a related set of price adjustments on order product summaries belonging to one order summary.
Order Analytics: The Order Analytics dashboard gives you real-time visibility into active order workflows, delays, and financial risk across your fulfillment network. It brings together summary metrics, status breakdowns by fulfillment location, and root-cause analysis for cancellations and returns, so your team can act on order delays and reduce lost revenue.
Order Delivery Group Fields: The Order Delivery Group object defines a group of order products belonging to one order to be fulfilled using the same delivery method and delivered to the same recipient. In Order Management, you usually interact with order delivery group summaries instead of order delivery groups.
Order Delivery Group Summary Fields: The Order Delivery Group Summary object defines a group of order product summaries belonging to one order summary to be fulfilled using the same delivery method and delivered to the same recipient. An order delivery group summary is used to create one or more fulfillment orders.
Order Delivery Method Fields: The Order Delivery Method object is used together with the Product object to represent a delivery method. The product record is added to an order to represent a charge for that delivery method.
Order Fields: The Order object represents the original order or a change to an order, such as a return or cancellation. It’s associated with one order summary, which represents the current state of an order. The order record values don’t usually change. In Order Management, you usually interact with order summaries instead of orders.
Order Fulfillment: The order fulfillment process streamlines the allocation, assignment, picking, packing, and shipment of order items.
Order Management Lifecycle: As an order moves through the order lifecycle, it progresses through four stages: capture, fulfillment, delivery, and post fulfillment. These stages determine which services you can perform on an order. Managed and unmanaged orders are processed differently during the order lifecycle.
Order Management Lifecycle Stages: Each order in Order Management moves through a series of stages that collectively make up the order lifecycle.
Order Management Lifecycle Types: An order summary’s lifecycle type specifies whether you manage it with Order Management features.
Salesforce Order Management: Order Management is your central hub for handling all aspects of the order lifecycle, including order capture, fulfillment, shipping, payment processing, and service.
Order Management and Service Cloud: Use Order Management with Service Cloud to give service agents a single view of order and service history to ensure timely processing of requests.
Order Management Console: The Order Management Console shows all your order information at a glance. It includes tools that help you track, manage, and service orders throughout the order lifecycle.
Order Management Report Types: Your Salesforce admin defines report types that determine the reports that you can create.
View the Order Management Reports Dashboard: The Order Management Reports package includes a prebuilt reports dashboard. The dashboard is built from components of the available reports and shows key metrics at a glance. You can edit the components on the dashboard to meet your business needs. Use report filters to define the date ranges to display for each component.
Order Management Resources: In addition to Salesforce Help, Order Management has documentation resources to help you learn about, set up, administer, and extend the Order Management app.
Order Management Objects: Order Management objects, together with existing objects, represent the elements of an order as the order progresses through the order lifecycle. The process for creating records in Order Management depends on your storefront. For example, if you use Salesforce B2C Commerce, the B2C Commerce Integration imports order data into Order Management. The terms “item” and “product” are used interchangeably throughout Order Management. Usually, technical areas like APIs and flow actions use “item,” while the user interface uses “product.”
Order Objects: Learn about the Order objects and fields available for reporting in Order Management.
Order on Behalf Of Overview: Use Order on Behalf Of (OOBO) or Order Entry to let customer service representatives (CSRs) place orders directly on behalf of a customer. This feature works with Order Management, B2B Commerce, D2C Commerce, and B2C Commerce.
Order on Behalf Of Setup: After you’ve installed and configured either an Order Management or B2B Commerce org or B2C Commerce instance, there are some Order on Behalf Of (OOBO) specific steps to take. Many of these tasks are the same whether you’re using Order Entry or OOBO. However, there are a few steps that are specific to the individual products. Complete the steps for your product and organization.
Order Payment Summary Fields: The Order Payment Summary object represents one or more payments that use the same payment method and are associated with the same order summary. The order payment summary’s values are the sums of the values of the included payments. Unlike most summary objects, there’s no corresponding Order Payment object.
Order Product Adjustment Line Item Fields: The Order Product Adjustment Line Item object represents an adjustment to the price of an order product, usually a discount. In Order Management, you usually interact with order product adjustment summaries instead of order product adjustments.
Order Product Adjustment Line Summary Fields: The Order Product Adjustment Line Item Summary object represents an adjustment to the price of an order product summary, usually a discount.
Order Product Fields: The Order Product object represents an original product on an order. It can also represent a charge, such as a delivery charge. With an order product summary change, it can represent a change to a product on an order, such as a return or cancellation. In Order Management, you usually interact with order product summaries instead of order products.
Order Product Summary Change Fields: The Order Product Summary Change object represents a change to an order product summary, such as a return or cancellation. It’s associated with an order product summary and an order product.
Order Product Summary Fields: The Order Product Summary object represents the current state of a product in an order summary. It tracks status by quantity. For example, it could show an ordered quantity of 3, a canceled quantity of 1, and a fulfilled quantity of 2. This object is associated with an original order product and the order product summary changes that apply to it, such as returns or cancellations.
Order Product Summary Status: The order product summary status shows where an order product is in the order lifecycle. This status is determined by the order product summary’s quantity fields.
Order Product Tax Line Item Fields: The Order Product Tax Line Item object represents the tax on an order product. In Order Management, you usually interact with order product tax summaries instead of order product taxes.
Order Product Tax Line Item Summary Fields: The Order Product Tax Line Item Summary object represents the current state of tax on an order product summary or an order product adjustment line item summary. Multiple order product tax summaries can apply to one order product summary or order product adjustment summary.
Order Self-Service: Create a customer portal using the SFRA Order Management Self-Service plug-in to let customers manage their orders. Customers can track orders, view order history, and manage cancellations and returns. Order Self-Service supports the RMA return flow, which lets customers return products on their own, but requires that the store validates the return before issuing the refund.
Order Summary: An order summary pulls together all order details into a single, consolidated view. It can help you manage and service orders before, during, and after fulfillment.
Order Summary Fields: The Order Summary object represents the current properties and state of an order, including fulfillment information. It’s associated with one order that represents the original order. The order summary’s values are the sums of the values in the original order and subsequent orders representing changes, such as returns or cancellations.
Manually Import a Pending Order Summary: When the high-scale system is enabled, orders usually flow quickly from the Zero Object Service (ZOS) into Order Management. But when order volume is high, such as during a flash sale, orders can spend time waiting in ZOS. While an order is in ZOS, it’s visible in Order Management as a pending order summary. If you want to service an order that’s still in ZOS, you can manually import the pending order summary.
Order Summary and the Order Lifecycle: The order summary consolidates all order information—from order capture through fulfillment, payment collection, shipping, delivery, and service—and displays it in a single view. Use the order summary to manage the entire order lifecycle.
Order Summary Routing Schedule Fields: The Order Summary Routing Schedule object represents an attempt to route an order summary to one or more inventory locations for fulfillment. You can use it to schedule future attempts and to record completed attempts.
Order Transaction Objects: Learn about the Order Transaction objects and fields available for reporting in Order Management.
Pack a Fulfillment Order: After an order is picked, it shows in the Ready to Pack tab. From there, you can pack the item quantities, reject any that couldn’t be fulfilled, print your shipping label, and ship the order.
Order Management Package Links: Some Order Management features require you to download a package link before you can configure and use them. Before downloading a package for the first time, ensure your org meets the requirements. Some package links have multiple requirements.
Payment Authorization Adjustment Fields: The Payment Authorization Adjustment object shows information about an adjustment made to an authorized transaction.
Payment Fields: The Payment object represents a single payment capture or sale.
Payment Gateway Fields: The Payment Gateway object represents a connection to an external payment gateway.
Payment Gateway Log Fields: The Payment Gateway Log object stores information exchanged between the Salesforce payment platform and external payment gateways.
Payment Group Fields: The Payment Group object represents a group of payment transactions that have been processed for an order.
Payment Line Invoice Fields: The Payment Line Invoice represents a payment allocated to or unallocated from an invoice.
Payment Objects: Learn about the Payment objects and fields available for reporting in Order Management.
Payment Records and Processes: Order Management creates an order payment summary for each order. The order payment summary represents a set of payment records that use the same payment method and are associated with the same order summary. The payment details from the included payments dynamically update the order payment summary, so you can see an order’s balances across multiple payments, including authorization, capture, and refund amounts.
Payments and Invoices: The authorization, capture, and reconciliation of payments occurs as orders move through stages in the fulfillment workflow. Your Salesforce admin can automate payment capture, invoice generation, and refund processing to help manage your payment transaction needs.
Payments for Exchanges with RMA: Because an exchange can result in a partial refund for the customer, you must configure payments to process this refund. You can find payment activity in the order payment summary for each order.
Payments for Order on Behalf Of: Processing payments is an integral part of the Order on Behalf Of process. Whether you’re using Order Entry or OOBO with Order Management, you need a payment service. You can find payment activity in the order payment summary for each order.
Complete a Pick Ticket: Fulfill orders by selecting a pick ticket and picking the items on the list. As you fulfill the order, track which items have been picked, select rejection reasons for unpicked items, and print item fulfillment specifics.
Create a Pick Ticket for a Fulfillment Order: Create a pick ticket to find and pick items for new fulfillment orders. Select one or more orders to pick items for and create your pick ticket.
Place an Order on Behalf of a Customer: Place orders directly for customers from your own device. You can search for products, set variables and quantities, add the products to a cart, and process customer payments.
Preconfigured Permission Sets for Salesforce Order Management: Users assigned to a preconfigured permission set receive permissions according to their persona’s required functionality. You can customize a permission set by cloning it and modifying the individual permissions.
Price Book Entry Fields: The Price Book Entry object represents the price of a product in a price book. Although Salesforce Order Management doesn’t directly use this object, it creates stand-in price book entry records because order products require them. As you create products to represent delivery methods, add stand-in price book entry records to them.
Agentforce Proactive Fulfillment Alerts: Stay ahead of supply chain volatility by transforming insights from the Analytics Dashboard into actionable recommendations. Agentforce continuously monitors fulfillment orders and triggers proactive alerts when it detects fulfillment risks by evaluating real-time disruptions like weather alerts and operational inefficiencies, such as processing delays, workflow or lay out issues. Use these recommendations to trigger autolaunched flows so that Agentforce can temporarily exclude specific locations and reroute existing allocated orders or update the processing time of slower locations to mitigate delays before they affect the customer experience.
Process Exception Fields: The Process Exception object represents an unexpected problem with a business process, such as payment capture.
Process Exceptions: You can automate order processing across every stage in the order lifecycle. When your automated business logic encounters an issue that interrupts normal processing, a process exception occurs. Various issues can cause a process exception, such as a failed fraud check, a payment capture error, a lack of available inventory, or a problem with a shipping carrier.
Process Exception Objects: Learn about the Processing Exception objects and fields available for reporting in Order Management.
Using Return Merchandise Authorization: Sometimes, it’s useful to track the return process before issuing a refund. A return merchandise authorization (RMA) gives you closer oversight on the return process, to make sure that the product is returned in the appropriate condition and quantity. RMAs can be especially user for larger, more expensive items, or for smaller businesses that have limited stock. For example, if the wrong product was shipped, the RMA ensures the product is returned before you refund the cost.
Product Fields: The Product object represents a product that a merchant sells or has sold. A product is also used to represent delivery charges for one or more order delivery methods.
Provide Access to Store Fulfillment Apex Classes: The Store Fulfillment app uses an Apex class and Visualforce page for the pick ticket generation and picking process. Configure your user profiles to access these items.
Refund Fields: The Refund object represents a single refund transaction.
Refund Line Payment Fields: The Refund Line Payment object represents a portion of a refund that has been applied to or unapplied from a payment. One refund line can represent the full amount of a refund.
Remove an Item from a Fulfillment Order: Removing an item from a fulfillment order cancels the fulfillment process for the item. You can remove an order item only if it hasn’t been fulfilled. For example, you can reallocate an item to a new fulfillment order if the item is no longer available at the specified location.
Reports for Order Management: Use reports to retrieve and analyze order, fulfillment, and payment information to help you optimize service delivery and keep your order workflow running smoothly.
Reship an Order Item: Reship missing or lost order items by creating a reship fulfillment order.
Resolve a Process Exception: After you identify the cause of a process exception, you can resolve the issue and continue normal processing on the order summary.
Return and Cancel Fee Processes: To charge a fee on a return order line item during an RMA return, include the fee when creating the return order and process it when returning the return order line item. To charge a fee on a simple return or cancel, include it when submitting the return or cancel.
Return Insights Overview: Use Einstein to identify products with high return rates and analyze the reasons that customers are retuning them.
Considerations for Return Insights: To create Return Insights with Einstein Generative AI, consider supported functionality, usage, limitations and allowances, limits, and other issues.
Return Order Item Tax Fields: The Return Order Item Tax object represents the tax on a return order line item or a return order item adjustment.
Create a Simple Return with a Refund: Use the simple return workflow to process a return for one or more items and issue a refund. For example, a customer can use a return slip included with the order invoice to return items directly to you without contacting a service rep or creating a return request online. If you don’t track returns that are initiated online or through a service rep, you can also use this workflow. You can process a simple return with a refund only for items that are fulfilled and associated with an order summary.
Return an Order Item: Digital selling channels give customers many ways to initiate and complete returns for items that they purchased online. Order Management tools help you manage the various return scenarios.
Return Order Line Item Fields: The Return Order Line Item object represents a specific order product that is associated with a return order.
Choose a Return Type: When processing a return, you can process a simple return and issue a refund or create a return order and return merchandise authorization.
Routing via Flows: A series of automated routing flows picks up order summaries, determines which fulfillment locations can most efficiently handle the order's items, and routes its inventory reservations to those locations. When the automated process has trouble with an order, it creates a process exception to notify users of the issue. An included screen flow allows a user to manually create fulfillment orders for that order. Then, a special automated flow picks up those fulfillment orders and inserts them back into the main process.
Routing Objects: Learn about the Routing objects and fields available for reporting in Order Management.
Routing via Rules: Use rule groups to modify routing logic directly in the Order Management UI instead of using code or Salesforce Flow.
Routing with Omnichannel Inventory: If you’re using Omnichannel Inventory, you can combine its flow core actions with your routing logic to create and manage reservations as part of your fulfillment process.
Sales Channel Fields: The Sales Channel object represents an order source, such as a web storefront, physical store, marketplace, or mobile app. If you use Salesforce B2C Commerce, we recommend creating a sales channel record for each site in your B2C Commerce implementation.
Order Servicing: Order servicing lets your customer service representatives (CSR) provide shoppers with order-related services, such as returns, exchanges, and cancellations. Order Management uses flow templates to help automate the these tasks. A Salesforce Admin can copy and customize these templates and then make the process flows available in the Actions & Recommendations section on the Order Summary page. Service agents can then quickly respond to requests for cancellations, reshipments, discounts, exchanges, and returns.
Salesforce Payments and Order Management: Facilitate secure and convenient order processing with payment collection and refunds by integrating Salesforce Payments and Order Management. If your Payments merchant accounts are linked to a Stripe account, Order Management can capture payments and issue refunds. If your merchant accounts are linked to a PayPal account, Order Management can only issue refunds.
Share Data Using Order Management File-Based Data Kits: File-based data kits simplify and streamline the deployment and management of data streams between Order Management (OM) and Data 360. Using data kits makes integrating data efficient and automatic.
Shipment Fields: The Shipment object represents a shipment of order items. It’s associated with one fulfillment order.
Shipment Item Fields: The Shipment Item object represents a product included in a shipment. It’s associated with one fulfillment order product.
Shipment Objects: Learn about the Shipment objects and fields available for reporting in Order Management.
Configuring Shipping Labels for the Store Fulfillment App: To let store associates view and print shipping labels for a packed order, configure the logic for the app. If the logic isn’t configured, the labels don’t show, and store associates see an empty page. The Store Fulfillment app contains placeholder logic to facilitate creating shipping labels.
Shopper Data with the B2C Commerce Integration: The B2C Commerce integration creates standard accounts and contacts to represent business shoppers or buyers. It identifies a business buyer by the presence of a company name in an order’s billing address. By default, it also creates standard accounts and contacts to represent individual shoppers.
Order Management Shopper and Buyer Records: Order Management uses the Account and Contact objects to represent business and individual shoppers. It can also use Person Accounts to represent individual shoppers. When it receives an order, it searches for the shopper. If it finds the shopper, it associates the order with the existing records. If it doesn’t find the shopper, it creates records for that shopper. B2B Commerce uses the term “buyer” instead of “shopper.” In Order Management, references to shoppers also apply to buyers.
Shopper Representation: In Salesforce, accounts represent business entities, and contacts represent individuals associated with accounts. To represent a shopper in commerce transactions, you need elements of both objects.
Find and Cancel Order Items with AI Tools: Look up an order by order number and cancel every eligible item in a single conversation. A service agent describes the goal in natural language. The AI client checks eligibility, submits the cancellation, and confirms the result without opening the Order Management console.
Estimate Delivery Dates with AI Tools: Prepare your delivery estimation configuration and quote delivery promises to customers in one conversation. With headless Order Management, the AI client reads and updates your estimation setup and returns a delivery date.
Set Up Order Management with AI Tools: Streamline Order Management setup through a guided conversation with an AI client. The agent turns on Order Management, configures sharing and the Order Summary page, and can connect a B2C Commerce storefront.
Look Up and Adjust Inventory with AI Tools: Check real-time Omnichannel Inventory availability for a stock keeping unit (SKU) and correct quantities in one conversation. With headless Order Management, the AI client reads the group rollup and per-location breakdown, applies your change, and rereads availability to confirm the result.
AI Agent Use Cases for Order Management: Use an AI agent to set up Order Management and complete common Order Management tasks conversationally, such as finding and canceling order items.
Explain Order Routing Decisions with AI Tools: Ask why an order was routed to a specific location, and why it split, without reading logs or filing a ticket. With headless Order Management, the AI client reads the recorded routing explanation and returns the winning rule, the competing scores, and a per-shipment reason.
Store Fulfillment Application Overview: The Store Fulfillment app gives you quick and easy access to each step of the fulfillment process: selecting a store, finding new orders for the store, creating a ticket for one or more orders, picking or rejecting items, and packing them up or shipping them out.
Store Fulfillment App Setup: The Store Fulfillment app provides guided workflows that walk store associates through the process of picking and packing each order. Store associates can indicate how much of each item they can fulfill and how much they can pack. They can also track the items that they can’t fulfill and the reasons for rejection. Access to the site is controlled using the Identity User license. After the Identity User license is configured, create accounts for your store associates and assign the license to them.
Submit an Unmanaged RMA Return Order: When you receive returned order items, you can submit the unmanaged RMA return order and process a payment refund to the shopper or buyer.
Tracking Routing Attempts: When implementing logic for rerouting orders that weren’t fully routed or that had a reservation canceled, information about previous routing attempts is useful. To manage this information, use the Order Summary Routing Schedule object and the Routing Attempts field on the Order Summary object.
Place an Exchange with an RMA Return: Place a post-fulfillment exchange when a shopper or buyer needs to substitute a product after it has already been fulfilled. These exchanges can be uneven, so the new product doesn’t always have the same value as the original product. In this case, the exchange results in a refund or additional funds owed.
Unmanaged Orders (Order Entry Only): Order Entry doesn’t include any of the order management functions available through Salesforce Order Management.
Unreferenced Refunds: By default, when a product is returned, the refund is credited to the original payment source. To credit the refund to a different source, process the return as an unreferenced refund. You can credit an unreferenced refund amount to any credit type configured in your org.
Change the Status of a Fulfillment Order: Typically, the status of a fulfillment order updates automatically as the order moves through the fulfillment workflow. If needed, you can also update the status manually if the order hasn’t yet been fulfilled. However, you can’t go back to a status that’s already been passed in the workflow.
Verify Setup: After you’ve set up Return Insights, ensure that it’s been configured correctly.
View a Credit Memo: A credit memo is generated automatically when you process a return for one or more items in an order.
View an Invoice: Your Salesforce admin determines the timing for invoice generation, for example when the order status changes to fulfilled. Your admin can also integrate invoice generation with third-party ERP systems to automate financial reconciliation.
View Fulfillment Locations: Fulfillment locations identify the physical locations from which order product items are fulfilled, such as warehouses and retail stores.
View Records in the Order Management Console: Your order records display in a list view in the Order Management Console. List views are a great way to sort, prioritize, and analyze the records that are most important to you.
View Return Orders: A return order record contains details about the returned items and related records, including the associated order summary.
View the Payment Gateway Log: Your customers can use various electronic payment methods when they submit orders from your ecommerce storefront. The Payment Gateway Log stores all the information exchanged between your payment platform and your external payment gateways. When a payment transaction doesn’t complete as expected, you can view the Payment Gateway Log for help with resolving the issue.
Add a Web Store Inventory Source for Exchanges with RMA (B2C Only): To use reservations when adding a new item to an exchange order, add a web store inventory source. Reservations help reduce out-of-stock errors by holding a product as soon as it’s placed in a cart.
Add a Web Store Inventory Source for Order on Behalf Of: To use reservations when placing an order on behalf of a shopper, add a web store inventory source. Reservations help reduce out-of-stock errors by holding a product as soon as it’s placed in a cart.
Webstores for Order on Behalf Of (Optional, B2C OOBO Only): To create orders that aren’t already being pulled in from a storefront through integration, create a webstore. If you’re using B2B Commerce or D2C Commerce, your webstores are already configured.
Add a Payment Link to a Salesforce Record: To create a Pay Now payment link, use the Generate Payment Link flow. This flow guides you through the link creation process. How you incorporate a link into your business application and share it with your customer is specific to your work flow.
Pay Now Payment Pages: When customers click a payment link, they are sent to a Pay Now payment page. This branded and customized page is where enter they enter payment information to complete a transaction. It's like an invoice or a statement of what's owed. The payment link type determines which page the customer sees. You can add the text on the page during payment link creation. You can also access these pages from the Pay Now store's Experience Builder Pages menu.
Set Up Pay Now as a Standalone Feature: Use the Commerce Setup Assistant to set up Pay Now. This assistant is available with Salesforce Payments, regardless of whether you have B2B and D2C Commerce. The assistant enables Salesforce Payments, which is a prerequisite to use Pay Now, and helps you create a Pay Now store.
Set Up Pay Now for Orgs with Payments and Commerce: For orgs with B2B and D2C Commerce plus Payments, use the Commerce Setup Assistant to set up Pay Now. The assistant automates Commerce setup, enables Salesforce Payments, which is a prerequisite to use Pay Now, and creates a Pay Now store.
Check the Pay Now URL in the Payment Settings: The Pay Now store's URL is one of the Payments settings. After you set up Pay Now, this URL is linked to the active store. If you have trouble generating payment links, verify that the correct URL is specified in the settings.
Generate a Pay Now Payment Link: To create payment links, use the Generate Payment Link flow in Flow Builder. This flow automates payment link generation. You can also customize the flow to pass custom metadata with a payment link. The third-party payment gateway uses this custom data to reconcile transactions and track invoices.
Salesforce Pay Now: Pay Now, powered by Salesforce Payments, is a payment solution that facilitates quick and convenient payments for customers. With Pay Now, you create and share a secure payment link with your customer. Your customer clicks a payment link, is directed to a branded, mobile-responsive web page, and enters their payment information to complete the transaction. You can associate a payment link with any Salesforce object, so you can add a payment service to any business workflow for a revenue opportunity. You can use Pay Now with or without Salesforce Commerce.
Payment Link Types: Use the Generate Payment Link flow in Flow Builder to create links for products with predefined amounts or with preselected products. If your org has Salesforce Payments only, then the Predefined Amount Link is the only link type available. If your org has Salesforce Payments and Commerce, then the Predefined Amount Link and With Products Link types are both available. You can also create a custom flow.
Troubleshoot Your Pay Now Setup: The Commerce Setup Assistant automates the setup of a Pay Now store. If you have any issues with Pay Now, you can verify the setup configuration.
Enable Self-Registration and OTP Authentication for Pay Now Stores: Enable your buyers to self-register and securely authenticate one-time payments at checkout directly through the Pay Now store. This setup enables buyers to securely save their shipping addresses and payment methods directly to their profiles for future use. During subsequent visits, buyers can opt to log in via a unique one-time password (OTP) sent to their registered contact number rather than remembering a password. After authenticating, the system automatically retrieves their saved contact information and payment details to populate the checkout fields.
Pay Now Payment Links: With Pay Now, you can create unique or reusable payment links that you share with your customers to accept payment. The link takes the customer to a branded, mobile-responsive web page where they can enter their payment details. Add a payment link to any Salesforce record for integration into existing workflows.
Pay Now Setup: Use the Commerce Setup Assistant to set up Pay Now as a standalone feature or for orgs with Payments and B2B and D2C Commerce. The Commerce Setup Assistant is available for either configuration. The assistant enables Salesforce Payments, a prerequisite for Pay Now, and it automates the creation of a Pay Now store.
Generate a Payment Link for a Single-Currency Org: The default Generate Payment Link flow for Pay Now is set up for multi-currency orgs. To generate payment links for a single-currency org, you have to edit the flow and remove all references to the Get Default Currency from Store flow element.
Check Your Pay Now Store: The Commerce Setup Assistant creates a Pay Now store for you. Confirm that your Pay Now store is available and active.
Verify One-Click Checkout Settings for the Pay Now Store: The Commerce Setup Assistant automatically enables self-registration so customers can sign up for an account at your store, and use one-click checkout. If you are having any issues with one-click checkout, verify the passwordless login setting for the store.
Upgrade Pay Now Stores Created Before Winter '24: If you have a Pay Now store created before Winter ’24, upgrade the payment page components to improve the layouts, ensure express checkout options, and to enable one-click checkout.
Set Up Salesforce Payments for Custom Checkout: If you created a B2B store with an LWR template, we recommend using Salesforce Payments, our native payment service. Salesforce Payments includes safeguards for transactions, express payment options, and a saved payment option. It provides two components—Salesforce Payments and Express Checkout, which you can add to your checkout page to collect payment information. These components automatically pull in the accepted payment methods that you configured for your store, and they provide fraud protection by using 3D Secure authentication.
Add Payment Source Information to the Payment Details Page: As of Spring ’25, you can view the origin of a payment on the payment intent record. If you’ve been using Payments before the Spring ’25 release, you can add the Source section to the record page to capture the information.
Payments Processing for Commerce and Order Management: Salesforce Payments provides payment processing for Salesforce B2B and D2C Commerce and Salesforce Order Management. When Payments is installed on the same Salesforce org as Commerce, Payments is responsible for tokenization and authorizations for payment methods, such as credit cards, digital wallets, and alternative payment methods for purchases. It also offers fraud protection with 3D Secure authentication. When installed on the same org as Salesforce Order Management, Order Management enables payment management of post-order tasks, such as returns and refunds. The integration also aids fulfillment work flows, where Order Management is responsible for capturing funds authorized at checkout.
View Payment Charts from the Payments Home Page: You can customize the Home landing page to display charts that show a snapshot of your payments activity. You can access the entire report directly from the chart.
Switch to Managed Checkout to Simplify One-Click Checkout: Easily set up one-click checkout by switching your D2C store from custom checkout to managed checkout. If you have no custom checkout integrations, switching to managed checkout gives you access to one-click checkout without complex setup. However, if your store has a custom integration, you lose it if you switch to managed checkout.
Set Up a Channel Manually for Payment Data: Set up an Experience Cloud site as a channel for payment data to flow from the payment gateway to Salesforce Payments. This site is required to enable Salesforce Payments and it’s used only as a data pipeline. Your customers don’t access this site.
Domain Registration for Apple Pay, Google Pay, and Link: To accept Apple Pay, Google Pay, or Link (Stripe only) as payment methods, register your store’s domain name with Stripe or Adyen. Register your domain for each Salesforce Payments merchant account that accepts one of these payment methods. For example, to support Apple Pay on 25 merchant accounts, register 25 times.
Generate B2C Payment Records in the Payments Workspace: Centralize all payment activity, including payments from B2C storefronts, in the Payments Workspace. To make B2C payments accessible, create a merchant account in the Payments app that is linked to an existing B2C merchant account associated with Stripe. This account consumes payment data from Stripe and generates payment intents listed in the Payments Workspace. You can distinguish B2C, B2B, or D2C payment intents based on the associated merchant account.
Automate Actions Initiated by Payment Events: Tailor the customer experience by building customized automations that are triggered by payment events. For example, automatically send an email receipt to a customer after a payment is made.
Enable Salesforce Payments for Commerce and Pay Now: Instead of using a third-party provider, use Salesforce Payments, the native service you can use to accept payments during checkout. With Salesforce Payments, you can offer customers a variety of payment options. Payments is available for B2B, D2C, and Pay Now stores. After you enable Payments, you can't disable it.
Enable Manual Capture for Payments: Use manual capture for payment processing for greater control, flexibility, and security in managing their payment transactions. Manual capture is available for Commerce and Pay Now stores.
Payments Event Notifications: To ensure smooth operation, get notified of Payments platform events as a transaction goes through its lifecycle. Events can include payment authorizations, captures, and refunds.
Salesforce Payments Licenses for Commerce and Pay Now: You can use Salesforce Payments and Pay Now independently or in conjunction with Salesforce Commerce. Choose a license based on the features you need, and whether you want only payment processing or a comprehensive checkout experience.
Manual Capture for Payment Processing: Manual capture lets you authorize a payment, and then capture that payment at a later time. Capturing payments manually gives you more control and flexibility over the payment process.
Enable Salesforce Payments Manually: To use Salesforce Payments in B2B and D2C Commerce stores for financial transactions, first set up an Experience Cloud site as a data channel between the payment provider and Payments. Then, enable Payments for your org and assign permissions to users. Finally, follow a guided setup to create a merchant account and payment method set, which is a group of payment methods that you accept from customers.
Salesforce Payments Merchant Accounts and Payment Methods: To use Salesforce Payments as your payment service, configure a merchant account and add payment methods to that account. If you are using Payments with a B2B, D2C, or Pay Now store, complete these tasks when you configure store checkout. If you are using Payments independent of any store configuration, complete these tasks from the Payments app.
Merchant Account Considerations for Adyen and Stripe: Before you configure merchant accounts in a B2B Commerce or Pay Now store, understand how your Salesforce org type determines whether you use live or test accounts for Adyen and Stripe.
Set Up Merchant-Initiated ACH and Credit Card Transactions: Configure the Merchant-Submitted Payment component in native payments to securely process ACH and credit card transactions in B2B and D2C Commerce stores on behalf of your customer. Collect and save the payment details from your customer over the phone, via email, or in writing for future transactions.
One-Click Checkout for Faster Transactions: Simplify the checkout process at your D2C and Pay Now stores using one-click checkout with passwordless login. Customers save their contact and payment information for future transactions, eliminating the need for passwords. If your store uses managed checkout, one-click checkout is enabled by default. If your store uses custom checkout, you can add a component to enable this feature. Customers can always check out as a guest.
Send a One-Time Password to Any Store on the Same Org: For a registered customer to use one-click checkout, they must receive a one-time password. A customer can register only one time with an org, regardless of whether the org is hosting more than one store. To send a one-time password for any store on the same org, share the shopper profile with each store.
Payment Page Tamper Detection: To make sure customer payment data is secure, Salesforce Payments complies with the latest PCI standard for detecting changes to Content Security Policy (CSP) headers and scripts. The PCI standard applies to any payment form where customers enter their information, including the checkout page, Pay Now payment pages, and mini carts that include express checkout.
Payments Personas and Permissions: A typical Salesforce Payments implementation involves several task-based personas that require certain permissions to do their jobs.
Salesforce Payments: Salesforce Payments, our native payment service, streamlines your checkout process and provides secure transactions for your customers. Bring new sites to market across geographies using a variety of payment methods, such as credit and debit cards, direct debit, digital wallets, and non-credit card alternatives like SEPA Debit and Bancontact. Salesforce Payments also powers Pay Now for quick creation of unique or reusable payment links that you can embed with any record in Salesforce. Salesforce Payments is offered as a standalone license or with Salesforce Commerce and Order Management for a complete commerce solution
Merchant Account Record Access and Sharing: Maintain strong data access controls by allowing merchant account access to only relevant users. Different merchant accounts can help organize your business by different regions and currencies. Dividing merchant account ownership limits access, which improves security. Ensuring the right people in each geography have necessary account access helps with issues such as regulatory compliance. To distribute responsibilities, merchant account owners can configure sharing on a per-record basis so payment processing runs smoothly.
Customize a Payment Report: You can customize a payment report type or create your own. A report type specifies the records and fields that the report uses. The report displays only the records that meet the criteria defined in the report type.
Salesforce Payments Monitoring: You can view payment activity using the Payments Workspace, reports, and event notifications. From the Payments Workspace, view each payment record, and see details such as the payment intent ID, the status, and payment method. To analyze the financial health of your business, use Payments reports. The variety of reports lets people in your company view payment data in the way that's most useful to them. You can customize the reports provided or create your own. Stay informed of Payments operations by subscribing to Payments event notifications.
Let Customers Save and Manage Their Payment Methods: Give registered customers the option to save their payment information for future transactions. Saving payment methods reduces a customer's checkout time because previously entered information is filled in. For B2B and D2C stores that use custom checkout, you must enable this feature manually. For D2C stores that use managed checkout and Pay Now stores, this feature is enabled by default. The option to save payment methods isnʼt supported for guest customers.
Salesforce Payments Setup: Use Salesforce Payments for easy-to-integrate payment processing for B2B and D2C Commerce and Pay Now stores.
Enable Payment Methods Sharing in B2B Stores: Give B2B buyers more control and flexibility with their payment methods by enabling payment methods sharing in B2B stores. By default, payment methods are linked to individual contacts and remain private. However, when you enable shared payments, buyers can share saved payment methods with other contacts within the same account.
Stripe Payment Fee Data: To view transaction costs and allow for better payment reporting, access payment fee data from Stripe and bring it into Salesforce or other enterprise systems, such as an ERP or accounting system. You can retrieve fee information for either of the two Salesforce Payments pricing models, blended rate and interchange plus (IC+). Fees are charged differently for each. If you don’t know what pricing model you're on, contact your Salesforce account executive or review your Salesforce contract.
Payments Timeline to Track Processing: The payment timeline provides a view of key events that occur during a transaction’s lifecycle. Use it to evaluate your business operations. You can access the timeline from each payment intent record in the Salesforce Payments Workspace.
Payment Methods for B2B Commerce: Salesforce Payments for B2B Commerce supports credit cards, digital wallets, bank debits, bank redirects, and Buy Now, Pay Later (BNPL) options. Available payment methods, countries, and currencies vary by Stripe, Adyen, or PayPal gateways. Supported countries and currencies also vary by payment method within each gateway. Before adding a payment method to your store, confirm that both the gateway and the customers' location support the payment method.
View Financial Activities from Payments Reports: To view payment activity related to your merchant account, Salesforce Payments provides reports. You can examine payment data in various combinations and share financial insights with others. You can choose which reports to display on the Payments app Home page. All reports are localized so that labels show in your org’s language. To automate payment operations, configure notifications for specific payments events.
Capture and Refund Payments from the Payments Workspace: Capture and refund credit card purchases from the Payments workspace, instead of going to the payment gateway's dashboard. For example, you can manually capture payments, or process courtesy refunds outside of the return time frame. The available action is determined by the payment status. You can only take actions on payments processed by Stripe or Adyen.
Do More with Components in Page Designer: You can now copy up to 10 components to a clipboard from the component’s action dropdown menu. You can paste the components in the same or other page or across browser tabs from a region’s Add action in the Page Structure panel. You can now also target components to specific locales, in addition to customer groups and campaigns. Additionally, pages loaded in Page Designer are responsive before all referenced images, external resources, or client-side scripts have completed loading, cutting down on wait time.
PWA Kit 1.0.0: The B2C Commerce PWA Kit 1.0.0 release.
PWA Kit 1.1.0: The B2C Commerce PWA Kit 1.1.0 release.
PWA Kit 1.2.0: The B2C Commerce PWA Kit 1.2.0 release.
PWA Kit 1.3.0: The B2C Commerce PWA Kit 1.3.0 release.
PWA Kit 1.4.0: The B2C Commerce PWA Kit 1.4.0 release.
PWA Kit 2.0.0: The B2C Commerce PWA Kit 2.0.0 release.
PWA Kit 2.1.0: The B2C Commerce PWA Kit 2.1.0 release.
PWA Kit 2.2.0: The B2C Commerce PWA Kit 2.2.0 release.
PWA Kit 2.3.0: The B2C Commerce PWA Kit 2.3.0 release.
PWA Kit 2.4.0: The B2C Commerce PWA Kit 2.4.0 release.
PWA Kit 2.5.0: The B2C Commerce PWA Kit 2.5.0 release.
PWA Kit 2.6.0: The B2C Commerce PWA Kit 2.6.0 release.
PWA Kit 2.7.0: The B2C Commerce PWA Kit 2.7.0 release.
PWA Kit 3.0.0: The B2C Commerce PWA Kit 3.0.0 release.
Build Modern Shopping Experiences with PWA Kit (Generally Available): The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on minor fixes and enhancements around quantity picker components, developer experience, and localization.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on localization updates and improvements related to SEO, performance, and shopper experience.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on localization updates and improvements related to SEO, performance, and shopper experience.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on localization updates and improvements related to SEO, performance, and shopper experience.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on localization updates and improvements related to SEO, performance, and shopper experience.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on localization updates and improvements related to SEO, performance, and shopper experience.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on localization updates and improvements related to SEO, performance, and shopper experience.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on localization updates and improvements related to SEO, performance, and shopper experience.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on localization updates and improvements related to SEO, performance, and shopper experience.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on localization updates and improvements related to SEO, performance, and shopper experience.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on localization updates and improvements related to SEO, performance, and shopper experience.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on localization updates and improvements related to SEO, performance, and shopper experience.
Build Modern Shopping Experiences with PWA Kit: The Progressive Web App (PWA) Kit is a new storefront technology for headless commerce using Salesforce Commerce APIs and React. It provides front-end developers with a more flexible and agile approach to build and maintain modern shopping experiences. This release focuses on localization updates and improvements related to SEO, performance, and shopper experience.
Get More Commerce Partner Apps on AppExchange: By March 2023, more than 250 Commerce Partner apps are migrated from the Commerce Cloud LINK Marketplace and made available on AppExchange - reducing costs, increasing efficiency, and driving Commerce Cloud customer success. Use Commerce Partner apps to deliver digital and composable experiences faster, easier, and with less cost. Streamline operations while increasing revenue, and create personalized customer moments with dynamic shopping experiences.
Auto Renew CDN Certificates: Starting May 19, 2023, if you can self-manage your custom SSL certificates, you have the option to configure eCDN managed provisioned SSL certificates for automatic renewal. Auto renewing a certificate saves time and keeps you from missing deadlines. It also improves managing eCDN on staging instances. You can configure auto renewing certificates for development, staging, and production instances. Auto renewal is available only for eCDN managed certificates and only with the CDN-API. You can renew up to 5 auto-renewing certificates per realm at no additional cost.
ISV Partners Can Get a Trial Sandbox Automatically When Registering: B2C Commerce independent software vendor (ISV) partners can now get a trial sandbox environment within minutes of joining the AppExchange Partner program. ISV partner prospects can opt in for a 90-day trial sandbox when they register on the Partner Recruitment page. After their information is submitted, a trial sandbox is automatically provisioned, and the ISV partner receives an email with their sandbox credentials.
JobExecution Updates for OCAPI 21.10: The JobExecution document has a new property log_file_path, that specifies the full WebDAV path of the log file. The property log_file_name has been removed.
New Location for Job Files: Starting with 21.10 log files of custom and system jobs are created in WebDAV path /Sites/LOGS/jobs/<job name>/<log file name>.log.
Use Commerce Data in Tableau: Use the Tableau for Commerce Web Data Connector to import your commerce data into Tableau.
Assign Promotions and Pricing to Specific Stores: Merchants can now assign price books and promotions to stores. This feature lets shoppers view pricing and promotions targeted to their selected store in session.
Text in Content Slot Fields Validate Properly: Free-form text in the content asset, product, and category Content Slot fields now validate properly. If an entry exceeds 3,500 bytes, an error is returned. To remedy the error, consider using Add to select IDs or limit entries to just the ID, instead of the entire content.
WebDAV Upload Limit Is Increased: The upload limit for a WebDAV push into a Salesforce B2C Commerce instance has been increased from 100 MB to 500 MB.
Manual Refresh Data Maps as Needed: Sync new custom attributes in Salesforce Order Management with your B2C Commerce org with the click of a button. Manually trigger a data map refresh to get instant access to new schema changes instead of waiting for the next scheduled sync.
Monitor Suspicious Access to Sensitive Shopper Data: Security logs now capture the source IP address that accesses sensitive shopper data in Business Manager. Use these enhanced logs to investigate suspicious activity and validate authorized access to sensitive customer and order details.
Five Minute Minimum Period Enforced for WAF Log Retrieval: A minimum period of five minutes is now enforced for retrieving WAF logs. This enhancement prevents setting the end time for log requests within five minutes of the current time.
Access On-Demand Sandbox Logs in Log Center: Salesforce B2C Commerce On-Demand Sandbox (ODS) logs are now available in Log Center. This enhancement eliminates the need to use a separate URL to access ODS logs for the first-party instance of Log Center.
Add EPS as a Payment Option: EPS is an Austria-based payment method supported by all Austrian banks. You can add the EPS option to your storefront in Business Manager Payment Settings.
Add Klarna as a Payment Option: Commerce Payments now supports Klarna as a Multi-step payment option. You can offer shoppers the option to buy now and pay later. The Klarna payment option makes it convenient for shoppers to purchase items in all price ranges.
Use Keyboard Shortcuts to Switch Between B2C Commerce Tools: You no longer need to use the mouse to switch between tools. Instead, press Command+k (macOS) or Ctrl+k (Windows) to open the App Launcher and move between B2C Commerce tools.
Enjoy the Lightning Design User Experience in Business Manager: We added Lightning Design System to the most commonly used Business Manager features and app navigation. This update gives Business Manager the same user experience that you’ve come to expect from other Salesforce products.
Get More JavaScript Features and Functionality with Compatibility Mode 22.7: With compatibility mode 22.7, the B2C Commerce server-side JavaScript engine supports more elements from ECMAScript 6 (ES6) and later. You can access new and expanded features, including top-level built-in types and methods for existing classes.
Get Complete the Set Recommender Types for Products Without Shopper Interactions: Einstein Product Recommendation now generates Complete the Set recommender types for products that have no or minimal shopper interactions. Einstein Complete the Set finds the closest matching product with an assigned set and assigns the set to the product. After the product has sufficient product-to-product interactions, it’s assigned to its own natural set. Previously, new products and products with minimal shopper interactions were excluded from Complete the Set recommendations.
Use More Product Verticals in Einstein Complete the Set: Einstein Complete the Set now includes the health, party supplies, and office supplies product verticals. The expanded list also includes beauty, cosmetics, home furnishing, sporting goods, and gym equipment.
Configure Up to 10 Categorization Conditions: When configuring a categorization rule in Business Manager, you can now set up to ten categorization conditions per categorization rule set. Previously, Business Manager supported five conditions per rule set while the API supported ten conditions per rule set.
Configure eCDN Zones for Staging Instances: You can now configure eCDN zones for staging instances using the new CDN API. Create an eCDN zone and certificate or implement an existing custom certificate. You can upload customer certificates to test Salesforce Commerce APIs. You can also configure vanity host names for staging instances on eCDN.
Configure Promotion Search Refinement with OCAPI and SCAPI: You can now refine promotion searches in B2C Commerce OCAPI and SCAPI. Use the promotion search refinement APIs to generate and display results that help shoppers discover products that are on sale or part of a promotion.
Use Custom Caches to Return Immutable Objects: Custom caches are designed to return immutable copies of the original objects stored in the cache. Previously, edge cases existed where objects and arrays in custom caches could be modified. This issue has been fixed.
Use Custom Caches to Return Immutable Objects on Production Instances: Custom caches are designed to return immutable copies of the original objects stored in the cache. Previously, edge cases existed where objects and arrays in custom caches could be modified. This issue has been fixed.
Merge Variation Group Results: Use the new merge global display setting in Business Manager to group the results of product variations and search hits as a single product hit. The setting applies to the site search and category level, including category fallback.
Enhance Order Access Security with the Allow List: Enable the Allowlist feature on the Limit Storefront Order Access setting if you aren’t yet limiting Storefront Order Access at all. This feature enhances security, ensuring that the customer ID of the current session is identical with the customer ID used for the creation of the order being accessed.
Export Controls Notice: In compliance with export control and economic sanctions laws and regulations where Salesforce operates, service to and from Cuba, Iran, North Korea, Syria, the regions of Crimea, Luhansk, or Donetsk is restricted without prior government authorization. As a result, customers, merchants, and shoppers from restricted locations are unable to access Salesforce-supported sites.
Enjoy Faster eCDN Zone Load Times: The Business Manager Embedded CDN (eCDN) page is now more efficient with faster zone load times. For B2C Commerce Instances with large numbers of zones, the eCDN page now loads up to ten times faster.
Fine-Tune Your Site’s Regional Settings: You now have full control in Business Manager over all parameters used for converting numbers and dates into strings. Use the new Format Symbols tab and regional parameters to add Locale details.
Get Accurate Allocation Amounts with a Null Allocation Payload: PATCH and PUT /product_inventory_records/{product_id} now supports a null allocation payload while keeping accurate account of product allocation amounts and allocation reset date. Previously, sending a Patch or Put call to set a custom inventory record attribute using a null allocation payload resulted in an invalid reset date.
Get Coupon-Based Promotions with New Script API: The PromotionMgr.getActiveCustomerPromotions(boolean ignoreCouponCondition) script API returns all active promotions including coupon-based promotions when ignoreCouponCondition set to true. You can use the returned promotions to expose promotions on your storefront. For example, display a callout message for coupon-based promotions on product detail or product list pages.
Holiday Preparation Database Optimization: As part of the 2022 Holiday preparation, the 22.8 release includes some database optimizations. The optimizations have the potential to cause a one-time increase in migration time during the 22.8 Preview and GA deployments. Some instances see a slightly longer impact during the maintenance window as part of the release deployment.
Use Customer Import and Export for Salesforce Payments: The Customer object (customer.xsd) now supports import and export of site-specific data about payment customers. The customer data tells the system where to find the payment data. It doesn’t include actual customer payment data.
Improve Product Discoverability with the Google Inventory Listings Cartridge: The Google Inventory cartridge is a B2C Commerce direct integration cartridge. You can use the cartridge to list your local store products on Google’s free product listings. Shoppers can discover products in stores near them. This increases local store foot traffic.
Improve Readability for Exported Custom Attributes of Type Number: Custom attributes of type number are exported to a xsd:double compatible format for XML exports. To better support use cases where xsd:decimal is assumed, B2C Commerce now exports values that are also compatible to xsd:decimal. This change supports a well-defined range of numbers that don’t need scientific notation. In terms of persistency/database the supported values are zero, as well as positive and negative fixed numbers with absolute values from 1.0E-130 to but don’t include 1.0E126. NaN, Infinity, and -Infinity aren’t supported.
Inclusive Language Updates in Business Manager: As we refine language in our products to more accurately reflect inclusivity, we replaced the word “master” with “main” or “base” in the Business Manager user interface and our documentation. To avoid any effect on customer implementations, we didn’t make any API changes.
Historical Business Manager Reports: The Business Manager Analytics Reports are now the Historical Business Manager Reports. The reports are only available for viewing historical data. For your current business insights use the B2C Commerce Reports and Dashboards.
Archive Long File Names During System Import Jobs: The system import job steps can create long file names that exceed some file system length limits, which caused problems when archiving files. You can now use Archive in Subfolders mode or Archive Overwrite Existing mode during system import jobs.
Get Ready for Multi-Factor Authentication Enforcement in May: The requirement to use multi-factor authentication (MFA) when accessing Salesforce products went into effect on February 1, 2022. To help customers satisfy this requirement, MFA is soon to be a permanent part of the B2C Commerce login experience. Starting May 1, 2022 and continuing on a rolling basis through the end of May, Salesforce is enabling and enforcing MFA for all users who log in directly to B2C Commerce applications.
Migrate Deprecated Custom Jobs to Step-Based Jobs: Use the new migration tool to convert your deprecated custom jobs to step-based jobs. Previously, migrating deprecated custom jobs required long development times. The migration tool is available on the Jobs Details page for jobs running on the deprecated framework.
Data Retention Has New Limits: To comply with Salesforce Commerce Cloud data management and regulation standards, B2C Commerce is implementing a strict 180 days data retention for code and data replications. Replications after 180 days aren’t visible in the Business Manager replications module.
Use a Unified URL for Your On-Demand Sandboxes: You can now access your on-demand sandboxes with a unified cluster-agnostic host name, so you no longer have to remember the cluster that your sandbox belongs to. The hostname matches the pattern <realm>-<instanceId>.dx.commercecloud.salesforce.com, for example, zzzz-001.dx.commercecloud.salesforce.com. It also matches the domain name of the B2C centralized admin API server, admin.dx.commercecloud.salesforce.com.
Configure a Max-Age for HSTS: Add additional security to your B2C Commerce instance with the max-age for HSTS setting. Setting a max-age determines how long the HSTS settings stay enabled.
OCAPI 23.1 - Basket Flash Validation Update: With the release of OCAPI 23.1, The property selection mechanism now works with all Shop API resources that return a basket or create an order. Previously, validation returned an error in most instances.
API Encryption Parameter Has Been Changed: The encryption parameter that handles encrypted and masked payment instrument data, including credit card, bank account, and driver license numbers, in the dw.order.Order.getOrderExportXML API has been completely revised.
OCAPI 23.1 - Use Selectors with Expressions: Selectors with expressions now work correctly when objects contain a property with markup text. Previously, when an object contained a property with markup text, selectors with expressions didn't work correctly.
OCAPI 23.1 - Property Selector Key Error Identifier: Beginning with OCAPI Version 23.1 a MalformedSelectorException is thrown if the selector key is incorrect. Previously, the property selection didn't work when the "select= key was incorrectly defined. For example, select%20=(price), resulted in the selector being skipped without any error message, and the normal response was returned.
Enforce Login_On_Behalf Permission: The Login_On_Behalf permission is now required for agents to access a storefront on behalf of another user. Previously, agents had access without that permission.
Create and Delete On-Demand Sandboxes: Manage on-demand sandboxes (ODS) and B2C Commerce instances in a central location with clicks not code. Use B2C Commerce Control Center to create and set the ODS TTL value and resource profile settings, monitor ODS status, and delete your ODS instances.
Manage On-Demand Sandboxes with the Operations Scheduler: Use the Control Center Operations Scheduler to start and stop on-demand sandbox (ODS) instances within a realm. By scheduling ODS starts and stops, you can control the usage of ODS credits. The Operations Scheduler is a convenient UI-based tool. Developers can still use the swagger UI or the Sandbox API to schedule operations.
Commerce Cloud Order Management Retirement: Salesforce B2C Commerce retired the Commerce Cloud Order Management product on July 31, 2022. There are no further updates or access to the Commerce Cloud Order Management documentation including the Infocenter and Release Notes.
Protect Against Bots and Malicious Attacks: To help you protect your B2C Commerce environments from bots and malicious attacks, Commerce Cloud is restricting external sources from directly accessing the demandware.net hostname.
Origin Shielding Phase 3: To protect from bots and other malicious attacks on your environment, demandware.net lockdown (Origin Shielding Phase 3) blocks all traffic that doesn’t originate from the Commerce Cloud eCDN from accessing Commerce Cloud. All calls accessing PROD and DEV instances that aren’t internal to the Commerce Cloud ecosystem are rejected.
Move Components in Page Designer More Easily: Dragging components in Page Designer is now more intuitive. Know exactly where you can place a component. And after you drop a component and refresh the page, the component remains in focus and highlighted until another selection is made in the canvas.
Improved Page Designer Structure and Usability: The Page Designer page structure in the canvas editor has been redesigned. The asset hierarchy outlines all the assets on your page. The visual connection between what is selected in the canvas and its location in the page structure is also improved.
Set Commerce Payment Credential Storage: Commerce Payments now supports payment card credential storage. The Payment card credential storage. There are two settings.
Set Up Payments for Immediate or Future Payment Capture: You can use the SalesforcePaymentRequest script API to set immediate or future payment captures. Use this method to override the site-level payment settings and gain greater flexibility over how payments are captured.
Get PayPal Integration in Salesforce Payments: When you offer PayPal as a payment method, your shoppers get expanded payment options and you see fewer abandoned carts. You can now add the PayPal payment option to your B2C Commerce storefront. The PayPal integration eliminates customizing PayPal implementations.
Limit Allowed Component Types: Developers can now limit which components are added to a region by defining an allowlist in component_type_inclusions in addition to the existing blocklisting via component_type_exclusions.
Assign SKUs to Page Templates: In Page Designer, you can now assign products SKUs to a PDP template, making it easier to create PDPs for one or many handpicked products. You can assign multiple product SKUs across categories to the template. For added efficiency, enter multiple SKUs (comma delimited) into the search field to return multiple results, and then complete a multi-selection in one step.
Promotion Bonus Product Limits: Promotion bonus products are limited to a total of 50 product SKUs. Previously, you could set promotion bonus products to more than 50 SKUs.
Receive Rejected Order Alerts in Business Manager: B2C Commerce Business Manager now displays an alert notification when orders are rejected by Salesforce Order Management. Users with access to the Business Manager orders module receive the alert and can review and act on rejected orders. The alert is also available in Slack when you connect your Business Manager instance to Slack.
Get eCDN Zones Ready for Hyperforce and Improve Site Efficiency: Now you can migrate legacy zones to proxy zones using B2C Commerce Business Manager and the CDN-API. This migration is a prerequisite for customers moving to Hyperforce. Proxy zones standardize your eCDN configuration, include the latest security and auto-renewing certificate features, and prevent legacy zone hierarchy issues.
Enable the New Business Manager UI (Generally Available): The UI has a fresh design and is easier to use. The GA release includes improved tooltips, spacing, text box padding, and banner and home page alerts. It also adds favorites, store IDs, and catalog insights to the home page. You can switch back to the classic UI if something isn’t working as expected.
25.1 Release: The B2C Commerce 25.1 release occurs December 05, 2024 through January 28, 2025.
Ingest Registered Shopper Profiles into Data Cloud: You can now export registered shopper profiles for specific sites as well as profiles modified after a certain date. The exported shopper profiles are then ingested into Data Cloud using the B2C Commerce Connector.
Verify Host Name Ownership with a TXT Record: When you create a zone and after you upload a custom host name certificate, you’re now required to verify ownership using a TXT record. The verification record is displayed in Business Manager after uploading the certificate. You create a TXT record in your DNS portal.
Brotli Compression Enabled: Brotli compression is now enabled for all environments. Browsers that support Brotli experience smaller download sizes for pages and static assets, resulting in improved performance.
Business Manager UI in Dutch: The Business Manager user interface is now available Dutch. To choose this new language, select the respective value in the dropdown in your user profile settings.
Check for Customization with SCAPI: Two new SCAPI response headers are available to check for custom requests and resulting hook execution errors.
Configure eCDN for Staging in Business Manager: Starting with the 24.4 release, Business Manager will support configuring eCDN for staging environments. eCDN settings are specific to each instance (development, staging, and production), and you manage them individually. When you create a proxy zone in production, the zone doesn’t replicate a corresponding proxy zone in your development or staging instance. The new eCDN configuration feature simplifies onboarding new sites for staging instances, making it easier to mimic your production instance. Because the configuration uses the existing CDN-API, you can use either Business Manager or the API to manage your eCDN configurations.
Prioritize Resource Bundle Lookup: You can now change the order of the resource bundle lookup and give priority to the WebDAV resource bundle. The default lookup first checks the resource bundle IDs of the code cartridges assigned to your site and then checks WebDAV. If you have resource bundles with the same ID in the cartridge and WebDAV, the cartridge resource bundle is always selected over the resource bundle in the WebDAV location (/webdav/Sites/Dynamic/[SiteID]/resources/) . You can now use a toggle to switch the order to check WebDAV first.
Display Alert Messages in Business Manager: Display alerts as a persistent banner on the top of every Business Manager page. Alerts can relate to Business Manager modules and are only visible to users with permissions to access the module. Salesforce might also use the enhanced alerting framework to display critical system messages to Business Manager users.
Upgrade Your Security Posture with eCDN WAFv2: B2C Commerce announces the upgraded version of our eCDN, now featuring WAFv2, bringing a host of advanced security features to safeguard your online presence.
Insulate B2C Commerce Against Rogue Queries: Elastic search queries configured in Business Manager or using the customer_search and order_search APIs are now limited to 200 thousand results. Queries for results greater than 200 thousand time out. Limiting the elastic search results helps insulate your B2C Commerce Instance from rogue queries. If you use the APIs, run queries with a smaller offset to avoid a timeout.
Update Main Product Variants for a Bundled Line Item: You can now update a main product variant in a bundled line item. This change allows shoppers to select a main product variant when adding a bundled line item to a cart. For example, a product bundle contains a belt and a T-shirt. The T-shirt is a main product with red, blue, and green variations. When the shopper adds the product bundle to a basket, the belt and T-shirt are added as bundled items, and the shopper can select a T-shirt color, one of the T-shirt variants. Previously, the API didn’t support selecting a main product variant when a main product was included in a line item bundle.
Enable Temporary Baskets for Immediate Order Requests: You can now create temporary baskets for immediate order requests in B2C Commerce. For example, a shopper uses a Buy Now option to purchase an item. The temporary basket, which has a limited lifetime of 15 minutes, is populated with all the data required to ready the basket for checkout without affecting the regular shopper basket.
Enable Temporary Baskets for Immediate Order Requests in OCAPI: OCAPI 23.4 includes support for temporary baskets. Temporary baskets allow for immediate order requests in B2C Commerce. For example, a shopper uses a Buy Now option to purchase an item. The temporary basket, which has a limited lifetime of 15 minutes, is populated with all the data required to ready the basket for checkout without affecting the regular shopper basket.
Add More Product Line Items per Basket: If your site was limited to 50 line items per basket, the maximum number is increased to 200. This new limit doesn’t affect users who have been granted a lower or higher limit.
Add Environment Variables to Your Application: You can now manage environment variables with the Managed Runtime API. Without making code changes, you can use environment variables to add variables into an application process running in an environment. Environment variables are stored securely, and are ideal for the following use cases:
Support for Correct Ad Attribution: B2C Commerce now sends FPC and FBP cookie Ids in the server-side purchase event to Facebook. This enhancement supports deduplication of purchase events and enables correct Facebook ad attribution. Facebook ad attribution enables you to measure and understand the impact of your ads across multiple publishers, channels, and devices.
Improve Code Profiler Tracking: The Code Profiler Script API calls (shown as SCRIPT_API) are no longer measured when using Production Mode. This change improves code profiler tracking without causing performance issues.
Improve Product Search Result in Japanese: You can now enable a new language analyzer for Japanese locales in B2C Commerce. The new analyzer supports advanced methods for search query tokenization. This enhancement provides more relevant search results for product searches in the Japanese language. It also reduces the merchandising effort to optimize storefront search for Japanese locales. For example, setting up additional synonyms and search dictionary entries.
Auto-Correction is Disabled by Default: The default setting for auto-correction for searchable attributes added after the B2C Commerce 24.4 release is now set to No. This change affects searchable attributes added through the Business Manager UI or via import. Existing configurations aren’t affected. Previously, when you added a searchable attribute, the default setting was Yes, which could cause issues in instances when search functions shouldn’t correct values, such as the product SKU, ID, or ISBN. Additionally, the auto-correction dictionary’s size can incrementally increase over time, leading to search noise.
Manage More Images in Page Designer: The Page Designer image and media picker now supports up to 1,000 images per folder. Previously, only 200 images within a folder were accessible in the image picker, even if more existed. The increased image limit improves the user experience for merchandisers and content creators and avoids workarounds, such as creating subfolders for extra images.
Use Node 18 for Projects: Node 18 is now available for projects. You can upgrade projects to PWA Kit 2.7.3 or 3.0. Both versions support Node 18. Node 14 and Node 16 are now deprecated. The End-of-life for Nodes 14 and 16 is September 13, 2023. To avoid any disruptions to deployments, upgrade to Node 18.
OCAPI JWT Response to Updated Passwords Is Changed: To enhance security and align with the SLAS JWT session handling, we updated how the OCAPI JWT handles password changes. Now, if your customer changes their password, all previously issued active OCAPI JWTs are invalidated. The OCAPI client receives an HTTP 401 response, accompanied by a body message that indicates an invalid access token. Previously, the JWT remained valid until its normal timeout.
Offer AfterPay as a BuyNow, Pay Later Payment Service: Let your shoppers pay in interest-free installments with AfterPay. Salesforce Payments offers AfterPay through your Stripe Merchant account. When AfterPay is active on your storefront, the product details page and checkout cart list it as a payment option.
Offer Venmo as a Payment Service: Salesforce Payments supports Venmo as an express and multi-step payment service for U.S.-based merchants and shoppers using U.S. currency. Shoppers can use Venmo from your mobile or desktop Storefront Reference Architecture (SFRA) sites. Using Venmo on your SFRA storefront requires a PayPal integration with Salesforce Payments and a payment zone configured for the Venmo U.S.-based criteria.
Partitioned Cookie Explicit Expiry Mode: Admins can now use the new Partitioned Cookie Explicit Expiry Mode to control if an expired partitioned cookie is sent for an existing partitioned cookie.
Prepare for Changes to Sever-Side Web-Tier Caching: If you provision your SCAPI zone with short code, SCAPI caching is enabled by default after March 12, 2024, and the feature switch SCAPI Server-Side Web-Tier Caching is has no effect. If you enroll in SCAPI before March 12, 2024, you can continue to enable SCAPI caching in Business Manager. To enable caching, in Business Manager, select Administration > Feature Switches, and turn on SCAPI Server-Side Web-Tier Caching.
Protect Against Brute Force Attacks: Starting September 12, 2023, B2C Commerce will introduce custom rate limits rules for the eCDN CDN-API. Rate limiting rules allow you to specify rate limits for requests that match a particular expression and then perform an action when those rate limits are reached.
Refine and Customize Promotions: The Business Manager Promotion Refinements feature now offers expanded support for custom product attributes. With this update, users can now create refinable promotions that utilize custom localizable product attributes, as well as custom product attributes of type enum-of-string and enum-of-int. This enhancement addresses the previous limitation where Business Manager users could not set up refinable promotions with these specific custom attribute data types or localizable attributes.
Renew eCDN Certificates in Business Manager: You can now use Business Manager to auto-renew up to five proxy zone eCDN certificates per realm. The new feature simplifies the annual renewal for eCDN certificates. If you use custom certificates, you can easily switch to auto-renewing certificates in the Business Manager UI. When you create a CDN zone, you can select to use eCDN Managed certificates.
Rogue Query Timeouts in B2C Commerce: To protect customer instances and associated services from outages, B2C Commerce restricts rogue queries that produce 200 thousand results or more. To better protect Salesforce B2C Commerce, Salesforce plans to limit the allowed offset value from 200 thousand to 10 thousand..
Set Up CDN Logpush: You can use the CDN-API to store firewall events and CDN logpush for HTTP requests in your S3 bucket for immediate log visibility. The API supports visibility of HTTP requests and firewall events in the CDN logs. The logs are also available for eCDN implementations.
Set Up Custom Firewall Rules with the CDN-API: To enable better rule enforcement, the B2C Commerce CDN-API now supports custom firewall rules. The API also provides custom firewall controls to target traffic from a specific path or user agent. Custom firewall rules are a superset of existing firewall rules, it will replace the existing firewall rules for IP, ASN, Geo, the existing firewall rules will be deprecated by February 1, 2024. All firewall rules will be deprecated by February 1, 2024.
Get Einstein Recommendations for Large Product Catalogs: Commerce Cloud Einstein now generates recommendations for product catalogs that exceed 3 million product SKUs. Einstein Product Recommendations enable you to create and manage recommenders and assign strategies that predict the most relevant products to promote to individual shoppers.
Validate Hostnames for Certificates: B2C Commerce now validates the hostname in the HTTPS certificate for outgoing connections. Validating the hostname eliminates the chance that a connection is made to the wrong host. To identify failed verifications, search the logs with the keyword phrase: Host name verification failed. This validation can be disabled on specific requests using the new setHostNameVerification method on the HTTPClient script API.
Rogue Query Limits in B2C Commerce: To maintain the highest level of system performance and reliability, Salesforce B2C Commerce now restricts rogue queries that produce 10 thousand results or more. This restriction applies to queries configured in Business Manager or using the the customer_search, and order_search APIs (OCAPI Shop API) and get orders (SCAPI). To mitigate the risk of running a query with too many results, use targeted filters and offset values that limit results when querying data.
Create a Unique Host Name Alias for On-Demand Sandbox SEO Testing: You can now use the On-Demand Sandbox aliases API to create a unique, global host name alias. Previously, to access a sandbox globally, you had to use an already existing DNS CNAME record that points to the sandbox origin. To access a sandbox locally, you can still create a reusable host name using a non-unique alias and generate a registration link to access the sandbox.
Create an Operation Scheduler for On-Demand Sandboxes: Administrators can now use the Operation Scheduler to start and stop sandboxes in realms that have their autoScheduled parameter set to true. Previously, they stopped each sandbox manually. Sandboxes that are running consume more uptime credits than when they’re stopped.
Assign Resource Profiles to On-Demand Sandboxes: When your create a new On-Demand Sandboxes, you can assign one of three discrete resource profiles to define sandbox disk, CPU, and memory allocation. Sandbox resources are expensive, so it's important to use them wisely. Resources profiles enable customers to create the right size sandbox for their specific needs. In addition, resource profiles enable developers to more easily maintain sandbox content, ensuring configuration is aligned with the production environment.
Access Page Designer with SCAPI: You can now use the Shopper Experience SCAPI API to add content created in Page Designer to your B2C Commerce headless implementation. Use the SCAPI Shopper Experience API to look up page information for pages created in Page Designer. The Shopper Experience API responses include:
Script API Sort Methods Are Stable: As required by ECMAScript 2019, the B2C Commerce Script API methods Array.sort() and Array.sort(function) are now documented as stable, so equal elements aren’t reordered as a result of the sort.
Selective Origin Shielding: To restrict access to PODs not originating from the Commerce Cloud content delivery network (eCDN) and increase site security and availability, we’re implementing selective origin shielding (SOS). SOS prevents bots from accessing the origin outside the eCDN.
Selective Origin Shielding: To restrict access to PODs not originating from the Commerce Cloud content delivery network (eCDN) and increase site security and availability, we’re implementing selective origin shielding (SOS). SOS prevents bots from accessing the origin outside the eCDN.
See Your Most Recent B2C Commerce Site at Login: When you log in to Business Manager, Merchant Tools shows the last storefront that you viewed. Previously, you had to select a site at each login. Merchant Tools now also shows the full site name, making it easier to identify a site.
Limit Source Code Group ID Characters: Source code group IDs are now limited to 28 ASCII characters. The limit applies to source codes defined using the Business Manager Source Code Creation page and through import. If a source code exceeds 28 ASCII characters, an error message states the character limit. Previously, source code IDs that exceeded 28 ASCII characters were truncated.
Avoid Chargebacks with a Site-Specific Statement Descriptor: Use a site-specific descriptor to help shoppers identify the source of an account charge on their credit card statements to reduce payment disputes and chargeback requests. You set the customer statement descriptor in Business Manager Payment Settings. The setting overrides the value set in your Stripe merchant account.
Secondary Instance Group Sandbox Stop Function is Deprecated: The ability to STOP sandboxes in a Secondary Instance Group (SIG) environment is now deprecated in Control Center. Stopping a SIG sandbox has no benefit. This deprecation doesn't apply to On-Demand Sandboxes (ODS).
Product Search Is Improved: The new unified data structure improves how the storefront sorts and displays products in a store. Search results are displayed faster, require less memory, and enhance the browsing experience.
DKIM Support for Google and Yahoo Email Spam Reduction: To ensure Google and Yahoo's announcements regarding reducing spam mails don’t disrupt your business operations, Salesforce B2C Commerce is making the following changes to our Commerce Cloud mail service:
Update Social Selling Cartridges: Extend your social selling business functionality with the following updates. The updates cover common updates across all channels as well as channel specific functionality.
Use Primitive Data Types Only with Job Context: Jobs that store non-primitive data types of values, for example, arrays and objects, in dw.job.JobExecution.getContext() now fail. Previously, the job logged a warning, ignored the invalid value, and continued.
Recursive Infinite Copies No Longer Supported: You can no longer use the WevDAV copy command to generate a recursive infinite copy in a B2C Commerce instance. When you use the command to copy a file’s content into itself, the destination is excluded because it exists. Excluding the copy prevents a recursive infinite copy that fills the file system.
Buy Now Items Get Their Own Cart: Shoppers can now use Buy Now express checkout without losing the contents of an existing shopping cart. Buy Now express checkout puts items for purchase in a separate cart. To use this feature, upgrade the Payments plug-in (plugin_commercepayments) to the latest version.
Change Customer Passwords with the Headless Commerce API: To provide this functionality, we updated the OCAPI Shop API PUT customers/{customer_id}/password endpoint to change the password in the PUT call instead of in the afterPUT hook. The Headless Commerce API doesn’t allow hooks. Also, the dw.ocapi.shop.customer.password.afterPUT_v2 extension point replaces the dw.ocapi.shop.customer.password.afterPUT extension point. If you have customizations for this resource, update your code accordingly.
Business Manager UI in Traditional Chinese for Taiwan: The Business Manager user interface is now available in Traditional Chinese for Taiwan. To choose this new language, select the respective value in the dropdown in your user profile settings.
Access Stripe with Commerce Cloud Payments (Generally Available): Commerce Cloud Payments, also referred to as Commerce Payments, lets brands launch commerce sites with an out-of-the-box payments solution powered by Stripe, a preferred provider. With Commerce Payments, brands can get to market faster and boost conversion rates with checkout experiences that support credit cards, express checkout options such as Apple Pay and Google Pay, and noncard payment methods such as SEPA, iDEAL, and Bancontact, all with integrated fraud protection. You can integrate Commerce Payments, now generally available, with B2C Commerce to begin processing payments quickly through Stripe.
Use Commerce Payments for Express Checkout Payment Methods: You can now offer customers the option to use Commerce Payments only for Express Checkout payment methods, alongside their existing payments processors and integrations. This new functionality provides an easy way to use payment methods such as Apple Pay and Google Pay with minimal or no implementation effort.
Access New JavaScript Features and Functionality with the Latest Compatibility Mode: When you select compatibility mode 21.2, the B2C Commerce Server-Side JavaScript engine supports elements from ECMAScript 6 (ES6) and later. With compatibility mode 21.2, you can access numerous fixes and new and expanded features, including new top-level built-in types and methods for existing classes.
Configure B2C Commerce Alerts for Slack: Send Business Manager alerts and notifications directly to Slack. Connect your Slack workspaces to Business Manager and configure notifications such as security vulnerabilities, campaign and promotion updates, or site alerts.
Configure Origin Rules with CDN Zone APIs: Configure Phased headless rollouts of SFRA to PWA implementations with the new CDN Zone APIs. You can now migrate specific pages to a PWA origin without completely switching from SFRA to PWA. You can also create and update origin rules to direct traffic to a PWA origin.
Avoid Invalid Characters in Cookie Names: Starting with compatibility mode 21.7, using invalid characters in a cookie name causes dw.web.Cookie to throw an exception.
Cookie Names with Invalid Characters in Custom Code Cause Errors: Our servlet container is now upgraded to implement Java Servlet specification 4.0, which has stricter rules for cookie names. Any use of invalid characters in a cookie name, as described in RFC6265, which references RFC2068, now causes an exception.
Configure How Long Einstein Waits Before Recommending Already Purchased Products: Einstein Configurator now lets you define how many days a recommender waits before recommending previously purchased products. You can choose from 7, 30, 60, or 90 days. The default setting is 30 days. Previously, Einstein Configurator provided a static 30-day wait time before recommending previously purchased products. For some customers, this setting was either too short or too long.
Use the Einstein B2C Experiences Learning Map: Want to learn more about how to create compelling customer experiences? Chart a course for success using the Einstein B2C Experiences learning map.
Assign Promotions to Campaigns with Enhanced OCAPI Data API Endpoint: `/sites/{site_id}/campaigns/{campaign_id}/promotions/{promotion_id}` now allows the `PATCH` method and accepts a body for the `PUT` and `PATCH` methods. This body is identical to the response of the `/sites/{site_id}/promotion_campaign_assignment_search` API, but it now supports a new `required_qualifier` property. With this body, you can set qualifiers and other properties, such as rank, on a promotion assignment when you create it. You can also update these values.
Assign Promotions to Campaigns with Enhanced Data OCAPI Endpoints: `/sites/{site_id}/campaigns/{campaign_id}/promotions/{promotion_id}` now accepts a body for the `PUT` and `PATCH` methods. This body is identical to the response of the `/sites/{site_id}/promotion_campaign_assignment_search` API, but it now supports a new `required_qualifier` property. With this body, you can set qualifiers and other properties, such as rank, on a promotion assignment when you create it. You can also update these values.
Extend Payment Processing with Salesforce Payment APIs: Use the new Salesforce Payment APIs to connect with third-party order management systems or platform-specific custom features. The APIs support capture, cancel, refund, and updates. For example, you can directly cancel or refund a payment in an order failure event by cleaning up payment authorizations. The APIs are available as Script APIs.
Use Server-Side Activity Tracking for Facebook: Commerce Cloud customers using the Facebook Dynamic Ads feature can now configure their Commerce Cloud instance to track shopper activity and send data server side to Facebook.
Determine Whether a Customer Has an External Profile: If your client application authenticates customers through an external Identification Provider (IDP) such as Google or Facebook, each customer needs an external profile. You can now make a GET call to the Shop API customers/ext_profile endpoint to determine whether customer has an external profile.
Get the Active Inventory Integration Mode: When code depends on whether B2C Commerce is integrated with Omnichannel Inventory, use the new dw.catalog.ProductInventoryMgr.getInventoryIntegrationMode() Script API method to get the active inventory integration mode. It returns a constant defined in the ProductInventoryMgr class.
Grouped Taxation Applied to Import and Export Orders: B2C Commerce now recognizes imported and exported orders created with group taxation and uses the group taxation method to calculate tax for those orders.
Guest Basket Lifetime Limit Is Increased: The lifetime limit for a guest customer basket is now the lesser of 30 days and the registered customer basket lifetime. Previously, it was the lesser of 7 days and the registered customer basket lifetime. This limit applies to input validation in the BM Basket Preferences UI and Basket Preferences Import. It also affects resolving the guest basket lifetime if it isn’t set, for example, for the basket cleanup job.
Embedded Objects Not Allowed in HTML Attributes: For security reasons, only Business Manager users with strong authentication, such as through multi-factor authentication with Account Manager, can include objects embedded with iframe, object, applet, or embed tags in the HTML attributes of a database object. A Business Manager user with strong authentication can temporarily allow users without strong authentication to embed objects in HTML attributes.
Improved Order History Retrieval: Use the new dw.customer.OrderHistory#getOrders() methods in your storefront to retrieve the order history for the shopper currently in session. If existing code uses dw.order.OrderMgr methods to retrieve a shopper’s order history, refactor it to use the new methods. For usage details, see the Script API documentation in the Infocenter.
B2C Commerce Infocenter Retirement: The Salesforce B2C Commerce Infocenter is being retired on July 15, 2023. Between June 15 and July 15, B2C Commerce documentation will be available in both the Infocenter and its new locations to help ensure a smooth transition for users. This change applies to all versions of Salesforce B2C Commerce.
Manage Inventory with Salesforce Omnichannel Inventory: You can support real-time availability for your storefront experiences by integrating with the new Salesforce Omnichannel Inventory product. B2C Commerce provides a seamless native integration that you can configure using clicks, not code.
Get Runtime Insights for OCAPI 21.8 Requests: The new OCAPI Data API /metrics/{apitype}?offset={Integer}&limit={Integer} provides insight into runtimes of individual OCAPI requests against the Shop or the Data API. The metrics resource responses are JSON-wrapped metrics in Prometheus Exposition format.
Use Strong Authentication as Required for Some Business Manager Modules: For security reasons, starting with Release 21.3, you must use strong authentication, such as through Multi-factor Authentication (MFA) with Account Manager, to access certain Business Manager modules. In Release 21.2, a warning message appears if you try to access these modules without using strong authentication.
New Page Designer Default Page: The Default-Start and Home-Show endpoints now utilize Page Designer if the page is available.
A New Quota and Logging for Objects Embedded in HTML Attributes Were Added: Starting with Release 21.3, only users with strong authentication, such as through MFA with Account Manager, can include objects embedded with iframe, object, applet, or embed tags into HTML attributes. A new quota implemented in Release 21.2, api.object.EmbeddedObjectInHTMLAttributeUserWithoutStrongAuth, helps you to prepare for the upcoming 21.3 restriction. Use the new quota to see if you have objects embedded in HTML attributes and if so, make sure that users who embed such objects use strong authentication.
Deleted Impex and Temp Files No Longer Being Retained in Trash Folders for 30 Days: As previously announced, updated file retention rules are applied to files in the /Logs, /Securitylogs, /Impex, and /Temp folders. During the transition period to these new rules, some instances used /Impex/_trash and /Temp/_trash folders to retain deleted files for 30 days. The transition period ends with the 21.2 release for POD sandbox and primary instances. /Impex and /Temp files are now deleted without first being moved to the _trash folders.
Organize Page Designer Pages in Folders: You can assign Page Designer pages to Business Manager content library folders. Folders keep pages organized and easy to find. Developers can write custom code that implements page navigation based on folders. For example, custom code can add breadcrumbs to the tops of pages or accordian-style page navigation based on folders. Developers can also write custom code that specifies that when a shopper performs a search, the shopper sees results organized by folder.
Render a JSON View of a Page Designer Page: You can expose the data assembled by a Page Designer page and its components in JSON format. A JSON version of a page is easier to expose to external services for native mobile apps or custom heads.
No Restrictions for CONTENT_SECURITY_POLICY: Set the CONTENT_SECURITY_POLICY in B2C Script class dw.system.Response to any string value. Previously, the only directive allowed was frame-ancestors.
Automate Pricing and Promotion Assignments with Jobs: Admins can now automate price book and promotion store assignments using job steps during the import and export process. All assignments in the system are exported when using the jobs framework.
Add Product Sets as Qualifying or Discounting Conditions for Promotions: You can add product sets as qualifying or discounting conditions to all promotion rules, except for the Choice of Bonus Product rule. When you add Product Set ID as a qualifying or discounting condition, any product belonging to that set can trigger the promotion and receive a discount from the promotion, or both. The only exception is that a Choice of Bonus Product rule promotion can’t use a product set to define the bonus products.
New Promotion Limits: To ensure that promotions are evaluated efficiently, limits for the number of promotion tiers, product options, categories, and other attributes are now enforced.
New File Retention Rules Enabled for POD Sandbox and Primary Instances: As previously announced, updated file retention rules are applied to files in the /Logs, /Securitylogs, /Impex, and /Temp folders. Previously, different folders, instances, and environments used different file retention periods or no retention period at all. With the 21.1 release, the new retention logic is enabled for POD Sandbox and primary instances. Download and save files you want to retain for longer than the new retention period.
Inclusive Language Updates: As part of our efforts to refine language in our products to more accurately reflect inclusivity, Salesforce is replacing terms deemed noninclusive.
Shipping Method Restrictions Validated by Shipment: When an order includes multiple shipments, a non-default shipment can now use a shipping method that isn't allowed for a product in the default shipment. The reason is that the basket process now validates a shipment’s shipping method only against the products in that shipment. Previously, it validated each shipping method against the products in the default shipment. If a product in the default shipment was excluded from a shipping method, then attempting to use that method in any shipment caused an Invalid Shipping Method error.
SOAP Web Services List Types: If you use the Web references package to call SOAP-based web services, we recommend that you migrate to the Webreferences2 package. To help make this migration easier, a new property enables the Web references2 package to generate list types as arrays instead of as lists. Arrays are the default list type for the Web references package. Lists are the default list type for the Webreferences2 package.
Check the Syntax of Your Steptypes JSON File: The steptypes.json file describes custom job steps. You can now access a steptypes.schema file to make sure that your steptypes.json file is using correct syntax.
Track Page Designer Rendering Performance: When editing in Page Designer, the page, region, and component rendering performance is now logged in your browser’s developer console. You can use the log to identify bottlenecks and optimize the rendering speed.
Update to Checkout Flow: We removed the Checkout-Login endpoint, and the email field from the billing section. In addition, we added the customer login to the checkout page.
Do More with VAT Calculation Method for Taxation: B2C Commerce now supports tax calculation and rounding based on tax groups. You can now calculate tax and use rounding based on tax groups. The calculation method uses a new Tax Rounding Level site preference called Group. The tax groups are exposed via OCAPI and Script API to support customization.
Access Point of Sale on Android and Windows: Point of Sale for Android and Windows is available by invitation. Request access for testing or for distributing the app to your stores.
Advanced Configurations for Point of Sale: Take your setup further by configuring payment gateways, Salesforce and third-party integrations, and tax providers. You can also manage Point of Sale data feeds, map fields, and export order files for review or reconciliation.
Set Up Third-Party Integrations: Point of Sale supports integrations with third-party systems. Connect to external systems, such as gift cards, tax, finance, OMS, and ERP, to create a unified retail experience. Integrating third-party systems streamlines retail operations and ensures data consistency across platforms. This allows retailers to use specialized services and technologies while maintaining a cohesive technology ecosystem.
Set Up Your System for Email Communications: To send emails using Point of Sale, you must verify that you’re authorized to use an email address, domain, or both for each region where your stores operate. Point of Sale uses Amazon Simple Email Service (SES) to verify your email address and domain identities. You can manage identities in the CMS, view verification statuses, and take action as needed. Verify a domain if you send email from multiple email addresses or verify just one email address to send communications.
Verify Domain or Email Identities: Verify your domain or email address in Point of Sale CMS to begin the verification process. Verifying domains and email addresses confirms that you own them for secure, reliable communication.
Check Identity Verification Status: Quickly view your identity verification status within Point of Sale CMS. Find domain verification details, including TXT and CNAME records, directly in the Email Integration settings. Copy these values and publish them to your domain's DNS provider within 72 hours to verify your domain and ensure seamless email integration. Email verifications do not require further action.
Integrate with ERP Systems: Integrate Point of Sale with various ERP systems to streamline operations and enhance data flow. Connecting Point of Sale with ERP systems such as NetSuite and SAP ensures seamless data exchange between your retail operations and back-end systems. This integration simplifies address verification and order management, and improves overall efficiency. With complete integration, you can automate processes, reduce errors, and gain a unified view of your business.
Address Verification and Complete Integrations: Point of Sale supports address verification and address completion through integrations with technology partners. Use partner integrations to ensure accurate address information.
Afterpay Salesforce Commerce Integration: Integrate Afterpay with Salesforce Commerce to offer customers a flexible payment option. By integrating Afterpay, retailers can provide a buy now, pay later option. This payment flexibility can lead to increased sales and customer satisfaction. Review the architecture and integration steps to enable Afterpay within Point of Sale.
Integrate NetSuite ERP in CMS: Enable order management by integrating your NetSuite ERP with Point of Sale CMS. Begin with an initial configuration on your NetSuite account. Then, complete the setup in the CMS.
NetSuite Integration Guide: Integrate your Point of Sale brand with NetSuite, streamlining data and workflows across platforms. Configuring both NetSuite and your content management system (CMS) ensures a seamless connection. This integration helps to maintain consistent branding and product information, and enables efficient order and inventory management. With connected systems, you reduce manual data entry and improve overall operational efficiency.
POS Access List–URLs and IP Address: To enable POS and cloud services to interact with external, third-party services, allowlist specific URLs and IP addresses within the merchant's firewall. Ensure necessary communication for Adyen Payments, Elavon Payments, and other connectors by allowlisting URLs configured on CMS and product or order systems. The in-store IT team handles store firewall and POS app URLs, while the corporate IT team manages backend outbound NAT gateway IPs for connectors.
Recommendations Integrations: Point of Sale supports product recommendations from technology partners to help you provide shoppers with the most relevant products. Point of Sale also supports size and fit recommendations from TrueFit, ensuring customers find the right fit every time.
SAP Integration Guidelines: Integrate your POS with SAP ERP to manage products, inventory, and orders. SAP Financials data can be reconciled with POS. Link your SAP data to Point of Sale to align with your business requirements. Ensure that your customized SAP configuration works seamlessly with your POS system.
Configure SCAPI ERP Integration in Point of Sale: Integrate B2C Commerce with Point of Sale using SCAPI to enable customer data synchronization and unified commerce capabilities. Configure the ERP connection in the Point of Sale CMS with your B2C Commerce SCAPI credentials.
Integrate WineDirect: Point of Sale supports WineDirect's clienteling service. Get details of the configuration set up required in the CMS and the WineDirect services supported by Point of Sale.
Connect to Finance Systems: Integrate Point of Sale with finance systems to streamline financial operations and gain a unified view of your business. Connecting Point of Sale with your finance systems helps you manage payments from various sources, such as HiPay, Adyen, PayPal, and Square. By configuring your finance system for integration, you ensure accurate financial reporting and reconciliation.
Configure Your Finance System: Integrate Point of Sale CMS with your finance systems using the new payment gateway integration. You can now configure systems such as Synchrony and Nebraska Furniture Mart. Streamline your financial processes and gain better control over payment transactions. Accept payments seamlessly through your Point of Sale CMS.
Set Up HiPay Hosted Page Payments: HiPay allows Point of Sale to generate a hosted page or payment link where customers can pay securely. Learn how to implement this in CMS implementation and get details of the user flow in the POS app. By enabling HiPay, you provide a secure and trusted payment experience for your customers.
Set Up OAuth Payment Token for PayPal Here Devices and Square: Discover the process of setting up an OAuth token for a Paypal Here device and Square for use in Point of Sale. For these card readers to work, after merchants have provided initial keys, the user needs to login to CMS and invoke the Paypal and Square buttons to generate a secure token that will be used for checkout.
Set Up Processing of Synchrony Credit Card Purchases using Adyen: The POS app, in combination with an Adyen terminal, supports the recognition of Synchrony cards and enables financing transactions. During checkout, when a customer chooses to pay with their Synchrony PLCC and the card is presented, the store associate can process the payment. If the order total meets a set threshold, the store associate can offer financing, which requires the customer to sign an electronic disclosure and financing contract. The threshold, electronic disclosure, and financing contract terms are customizable in the CMS.
Maintain PCI Compliance with Synchrony: Add a form to your Point of Sale app for customers that opt to use Synchrony as a payment method. After a store associate submits the form, the app retrieves a secure, PCI-compliant token that substitutes for a credit card number. The token enables the checkout to remain compliant without collecting the customer's full card information.
Configure Gift Card Integrations in Point of Sale: Integrate with Clutch and Givex to provide customers with enhanced gift card options. Using these integrations allows businesses to create customized gift card programs and track gift card use. Seamlessly incorporate gift cards into your sales and marketing efforts to increase customer engagement.
Integrate Clutch Gift Cards: The Point of Sale (POS) app supports gift card integration with Clutch. Learn how to configure a Clutch account with the supported functionality.
Integrate Givex Gift Cards: Point of Sale's POS supports gift card integration with Givex. Learn how to configure a Givex account with the supported functionality.
Integrate with OMS Systems: Integrate Point of Sale with Order Management Systems (OMS) to streamline retail operations. Enable Buy Online Return In Store (BORIS) for SFOMS integration. Configure NetSuite OMS CMS to optimize inventory and order fulfillment.
Enable BORIS for SFOMS Integration: Buy Online Return In-Store (BORIS) allows customers to purchase products online and have them shipped. Customers can return the product to a physical store or alternative location if they are unsatisfied with their purchase. Enable Point of Sale's BORIS feature so customers have options for how they receive and return their products. Review the sections and corresponding components in the CMS to get started.
Configure NetSuite OMS CMS: Integrate NetSuite Order Management System (OMS) with Point of Sale to centralize and streamline order fulfillment processes. Connecting these systems improves inventory visibility and enables efficient order routing. With this integration, retailers gain a unified view of orders, inventory, and customer data. This single view helps create seamless customer experiences.
Configure Tax Integrations: Integrate Point of Sale with third-party tax solutions such as Vertex, OneSource (Sabrix), Native Tax Engine, and Avalara. Tax integrations help ensure accurate tax calculations and compliance within your retail operations. By connecting Point of Sale with a tax service, you can automate tax determination, calculation, and reporting. This automation reduces errors, saves time, and helps businesses stay compliant with changing tax regulations.
Integrate the Native Tax Engine: Onboard a merchant for integrating with Point of Sale's inbuilt tax engine - the native tax engine. By default, POS supports the native tax engine.
Integrate OneSource (Sabrix): Facilitate tax calculations during sale transactions with OneSource (Sabrox) tax engine. Ensure that the OneSource engine handles all necessary tax computations. The process operates as follows: a real-time request is sent to OneSource with the cart details, and the corresponding VAT information is retrieved. For transactions occurring in offline mode, the necessary data is stored to enable offline processing.
Integrate Tax Engines: To calculate taxes, apply exemptions, and support tax overrides during checkout, configure a tax engine in the Point of Sale CMS.
Integrate Vertex: Integrate Point of Sale with the Vertex tax engine to facilitate tax calculations during sale transactions. Confirm that the Vertex engine handles all necessary tax computations.
Point of Sale Vertex Common Questions: Find answers to common questions about tax rates, offline fees, tiered taxes, promotions, and token refresh behavior for the Vertex integration.
Set Up Vertex for Point of Sale: Configure your taxpayer entity, product classes, and category mappings in the Vertex portal before connecting Vertex to Point of Sale.
Set Up Vertex Tax Exemption for Point of Sale: Configure tax exemption for Point of Sale, including partial tax exemption and fees, both supported in online mode. Offline mode uses previously downloaded tax rates.
Configure Point of Sale Data Feeds: Point of Sale data feeds streamline data integration, ensuring your retail operations run on accurate and up-to-date information. Configuring data feeds involves managing feeds and setting field mappings, so you can customize the flow of information. Refer to the feed file specifications to ensure data integrity and compatibility with the Point of Sale platform. By configuring data feeds properly, you gain better visibility into your retail business and optimize decision-making.
Manage Feeds: Configure Point of Sale data feeds to manage and schedule the transfer of product, pricing, and inventory data. Managing feeds ensures accurate data synchronization between systems, such as exporting documents in CMS. You can manually run feeds, schedule them for automated updates, and implement multi-region feeds for global operations. You can also monitor feed pipelines and logs to identify and address any issues, and configure and manage export jobs for efficient data delivery.
Feeds Deployment Best Practices & Strategy: Use Point of Sale to ingest data onto the POS Cloud platform with multiple options. Optimize data setup based on different customer scenarios. This ensures a smooth data flow, enabling retailers to gain valuable insights and make informed decisions. With efficient data ingestion, retailers can enhance their operations and improve the customer experience.
Export Documents in CMS: The Document Export feature lets merchants export documents, such as finance contracts, as PDF files to their SFTP or FTP servers. By configuring an export job in CMS, you specify key details such as the destination and file naming. Contract files convert to PDF, transfer to Retail Cloud's backend, and forward to your specified server. You can also update or delete export jobs as needed.
Configure and Manage Export Jobs: Use export jobs to extract data from Point of Sale by using Secure File Transfer Protocol (SFTP). Configure and schedule these jobs in CMS to automate data extraction, and monitor their progress in the Export Logs for timely, efficient data retrieval.
Import a Data Feed on Demand: Import a scheduled Point of Sale data feed immediately with the Import Now feature. The Import Now functionality allows you to force a scheduled feed to run when you need the most up-to-date information. Ensure that your data is current and drive timely decision-making.
View Feed Logs in Point of Sale CMS: Quickly identify the success of Point of Sale data feeds by using feed logs. When you review feed logs, you can begin troubleshooting issues. The feed logs page shows the runs for each feed and their status.
Run Feeds Manually: Sometimes you need to run a data feed right away. You can manually run data feeds in Point of Sale to update your data immediately, rather than waiting for the next scheduled run. Implement these steps when you need the most current data.
Multi-Region Feeds: Point of Sale multi-region feeds let merchants with operations in multiple regions run feeds in the master region. Merchants can also configure other regions to perform product searches against the master catalog. By using multi-region feeds, merchants can streamline their operations and ensure that product searches are accurate across all regions. This feature saves time and improves efficiency by centralizing feed management.
Feeds Overview: Use feeds to efficiently import bulk data, such as products, categories, and stores, into Point of Sale. Feeds streamline the process of updating your Point of Sale platform with the latest information. You can schedule and manually upload feeds, then review logs to ensure data accuracy. Point of Sale supports various feed types and configurations to meet your data import needs.
Create a Feed Pipeline: Create feed pipelines in Point of Sale to schedule feed types to run in a specified order. Running feed pipelines on a set schedule keeps your data current and accurate. Configure the pipeline, add the feed types, and set the schedule. You can also edit a pipeline as business needs change.
Required Data Feeds: Point of Sale includes a mobile search engine that is built for speed. To optimize the mobile experience for customers, Point of Sale uses data feeds. Customers benefit from a faster mobile search experience.
Schedule Feed Runs in Point of Sale CMS: Schedule your data feeds in Point of Sale so that you have the most up-to-date data. Select a runtime that meets your business needs. Get advice on creating the schedule. When no longer needed, delete a schedule.
Display the Site Merch Order: Point of Sale support two options for adding merchandising sort order to the product feed.
Set Field Mappings: Set Field Mappings in Point of Sale CMS to transform data from external sources into the format that Point of Sale uses. Field mappings use transformations and regular expressions. When you import data feeds, the field mappings ensure that your data is accurate and consistent. This consistency helps to streamline your retail operations.
Define Export Orders Field Mappings: Review the available field names and descriptions for Point of Sale export order field mappings. Use this information to understand the purpose of each field and how it relates to your exported order data. Knowing the available fields allows you to create effective and accurate export mappings for your retail operations. No fields are required.
Map Data Feed Fields: Set Field Mappings in Point of Sale to transform data from external sources into the format that Point of Sale uses. Field mappings use transformations and regular expressions. When you import data feeds, the field mappings ensure that your data is accurate and consistent. This consistency helps to streamline your retail operations.
Transformations & Regular Expressions: Point of Sale data mapping uses transformations and regular expressions so you can get values in the correct formats. Use transformations such as applying arithmetic operations, formatting text, and converting date and time values. Regular expressions use patterns to find and replace strings to refine your data mapping.
Review Feed File Specifications: Use data feeds to import and update critical product, inventory, pricing, and store data in Point of Sale. Data feeds include detailed specifications and examples, such as ASN, category, notification, and POS register feeds. Note that the POS register feed only updates existing registers and does not create new ones. You can also manage product bundles, inventory, promotions, store associates, and tax rates using data feeds. With data feeds, you can ensure your Point of Sale data is accurate and up-to-date, which leads to improved sales and customer satisfaction.
ASN (Advanced Shipping Notice) Feed: The Advanced Shipping Notice (ASN) feed provides specifications for inbound shipping notices in Point of Sale. Warehouse shipping information is sent to receiving clerks before merchandise arrives at the store. Receiving clerks use ASN to verify delivered merchandise by scanning barcodes, labels, pallets, cartons, or UPC tags. Once received, the merchandise is added to the on-hand item list.
Troubleshooting Product Feeds: Understand and solve issues that can occur when working with Product Feeds in Retail Cloud.
Product Feed: Create a robust user experience in the POS app by viewing product details such as search results and filters.
Product Bundles Feed: Product bundles in Point of Sale consist of Shop-the-Look and selling multiple items as a set.
Use Product Delta Feed: The POS delta feed lets you update product information, such as price and inventory, and add new products. This incremental product feed minimizes bandwidth use and lets you provide frequent updates to the POS app offline product feed. Now you can keep your product information current without importing a full product feed each time. Improve efficiency with faster, targeted updates.
Promotions Feed: The Point of Sale product promotion details can be derived from the product feed itself. Providing a separate promotion feed allows you to send multiple promotion call outs for a product.
POS Register Feed: Update multiple existing POS registers using a feed file through CMS. The register feed updates existing registers only and does not create new registers.
Store Feed: The Point of Sale store feed drives the functionality to find a nearby store for a user based either on the user’s location or a manually entered location by the user.
Store Associate Feed: The store associate feed drives the functionality that creates store associates for all stores. If an associate exists in Point of Sale, all of the data is updated with content from the file.
Store Device Feed: The Point of Sale store device feed is used to load all printer MAC addresses and device names that are used in a store.
Store Hierarchy & Store Area Goals Feed: The Dashboard Report, which is shown in the Point of Sale (POS) app, requires data setup pertaining to revenue targets assigned to areas, stores, or associates. These targets can be uploaded into the system using a file upload in CMS. It requires the below two files to be uploaded in the same order.
Store Inventory & Pricing Feed: The Point of Sale store inventory feed is used for the Find-In-Store feature. On the PDP, a user can opt to see if a product is available in a nearby store.
Tax Rates Feed & Setup: Point of Sale has the capability of calculating taxes via its tax engine. This tax engine relies on a tax feed that provides information about various taxes and rates that are applicable to products in different locations. If required, the tax engine can also compute the value-added tax (VAT) components out of a product price that already has VAT built into it for print and reporting purposes.
Export and Review Order Data: Point of Sale offers data export options, such as Transaction Log (TLog) Export, Store Inventory Delta Export, and Electronic Journal Data Export. Data exports help retailers analyze transaction data, track inventory changes, and manage electronic journal information. By leveraging these exports, retailers gain valuable insights into their operations, optimize processes, and make data-driven decisions. Use TLog to review and analyze order data.
Schedule an Export Job for Electronic Journal Data: Schedule export jobs for Point of Sale Electronic Journal data to extract and analyze transaction records. Exporting data regularly helps you gain insights into sales trends, customer behavior, and operational performance. You can then use these insights to optimize your retail strategies and improve decision-making. Schedule these jobs to automate the process and ensure that you always have access to the latest data.
Export Quiz Data: Schedule an export job in Point of Sale to extract quiz data that provides customer-relevant information. You can export data, such as customer IDs, question IDs, and updated quiz answer times. Use the exported data to analyze customer responses and improve engagement.
Export Store Inventory Delta: Export only the changes to your Point of Sale store inventory to improve efficiency and save time. The Store Inventory Delta Export runs daily and exports inventory data from the previous day. With a focus on efficiency, you can maintain data continuity.
Benchmarks and Best Practices for Orders and Transaction Export: Exporting orders and transactions from POS to an external system can be done in multiple ways. Learn about the various export options available, and understand the specific artifacts that can be exported. You can integrate POS data with other systems. Having the flexibility to export orders and transactions ensures comprehensive data management.
TLog Export FAQs: Find answers to frequently-asked questions about the Point of Sale TLog export.
TLog FAQ: Find answers to frequently-asked questions about the Point of Sale TLog.
Manage Global Blue Tax-Free Forms in the POS app: Create tax-free forms for eligible customers during checkout by using Global Blue in the POS app. When a customer qualifies for tax-free shopping, complete the Global Blue form in the POS app and print the form on an A4 or thermal printer.
Configure Payment Gateways: Integrate payment gateways into Point of Sale to securely process customer transactions. Payment gateways authorize and settle payments, ensuring smooth and reliable financial operations. You can configure callback URLs for seamless payment gateway integrations. Compare payment providers and terminal payment gateway processors to find the best solution for your retail business.t
Configure a Payment Gateway: Configure payment gateways in Point of Sale CMS to securely process customer payments. By connecting preferred payment providers, you streamline transactions and enhance the customer checkout experience. Accept a variety of payment methods, reduce friction, and improve overall sales efficiency.
Payment Error Handling: An order failure with unknown payment statuses is critical. Point of Sale made enhancements addressing this issue by adding additional parameters and descriptive order statuses in the CMS reporting. Additionally, there is the abort option in the app's user interface to mark the payment status as unknown in case of communication failures between the app and the terminal. This enables you to verify and reconcile the transaction later depending on the order status in the CMS failed order report.
Payment Providers: Feature Comparison Matrix: Learn which payment providers, such as Adyen, Elavon, and Verifone, are supported in Point of Sale. Each payment processor provides unique support for omni-channel and POS implementations. Knowing which provider best suits your business needs helps you deliver exceptional customer experiences.
Point of Sale eComm Integration Guide: Point of Sale offers native integration with leading e-commerce platforms, such as Demandware and Magento, to unify data and streamline operations.
Merchant Configuration and API Integration Fields: Merchants in the CMS have key properties such as their name, locale, region, and currency support. Using Cloud configuration details, Point of Sale connects to the merchant's e-commerce platform. View the merchant's developer credentials, API keys, and related API usage details for efficient API management. You can also determine if the environment is active and if it's a store merchant.
Terminal Payment Gateway Processor Matrix: Discover which processors are supported by each payment gateway in Point of Sale. Payment gateways, like Verifone Point, support specific processors, such as Fiserv. Knowing the supported processors for each gateway helps you to plan your payment processing strategy. You can optimize your retail operations by choosing the right combination.
Set Up Salesforce Integrations: Integrate Salesforce products and services with Point of Sale so that you can connect your data and workflows. With Omnichannel Inventory (OCI) integration, you can enable buy online, pick up in store (BOPIS) functionality. Also, use the Point of Sale Connector to integrate Salesforce Commerce and Salesforce Service with Order Management System (OMS) and Content Management System (CMS) configurations.
Configure BOPIS for SFOMS Integration: Buy Online Pick-up In-Store (BOPIS) is an omnichannel fulfillment method where customers can shop online and go to the store or pickup location once the order is ready. This allows businesses to drive in-store traffic by connecting their offline and online experiences. This is a guide to enable and use Point of Sale's BOPIS feature.
Migrate Point of Sale Connected Apps to the Client Credentials Flow: Migrate your existing Point of Sale connected app from the OAuth username-password flow, which Salesforce is deprecating, to the client credentials flow. You need admin access to each Salesforce org where Point of Sale uses the flow.
Set Up Point of Sale External Client App for Service: Create an External Client App (ECA) to provide Point of Sale access to Salesforce APIs for clienteling purposes. As of Spring '26, new merchants must use External Client Apps instead of Connected Apps.
Set Up Salesforce Omnichannel Inventory (OCI) Integration: Point of Sale has native integration with Salesforce Omnichannel Inventory (OCI) to do live inventory checks for online orders. Learn how to configure POS and SFOMS to take advantage of this omnichannel capability.
Point of Sale - SFCC (Salesforce Commerce) Integration: Use the cartridge integration and OCAPI’s to expose Salesforce Commerce's endless aisle functionality. POS integrates with Salesforce Commerce (SFCC) via OCAPI’s interfaces. This approach lets SFCC build and manage the cart (tax, promos). Point of Sale is a Salesforce-certified commerce integrator and is certified for OCAPI 21 integration. There is also a cartridge with default hooks for customization for client needs.
Configure the Salesforce (SF) Order Management System (OMS) in CMS: Discover the steps to configure the Salesforce Order Management System (OMS) in CMS. Point of Sale platform has an inbuilt Salesforce OMS connector. The connector is built on the best practices and collaboration with the Salesforce team.
Set Up Point of Sale Connector for Salesforce Core CRM Connector: Use REST APIs to integrate POS with the Salesforce Core CRM Connector for clienteling purposes. Create a Salesforce Connected App in Salesforce for Point of Sale to access the requisite APIs. The primary objects of interaction are Accounts and Notes. POS provides capabilities like search, create, and update for customer accounts that are maintained in Salesforce Core CRM.
CMS Configuration and Setup - Italy: Configure fiscalization requirements for Italy in Point of Sale (POS) CMS and change the logo, department number, and X and Z report settings.
How to Access Point of Sale CMS: Access the Point of Sale CMS to control the behavior of the POS app through customization. Access the CMS through a corporate gmail account, or link a non-Gmail corporate account to gmail. Use the latest version of Google Chrome to access the CMS.
Accessing Point of Sale CMS: Access the Point of Sale Content Management System (CMS) using a custom URL after configuring Azure AD. Merchants use their designated URL slug and environment to reach the CMS.
Alternate Store IDs: Use the Alternate Stores ID field in Point of Sale to assign multiple stores to an associate that works at multiple stores.
Policy Features: Configure approval policies for returns, exchanges, ASN receiving discrepancies, and other point-of-sale transactions in Point of Sale CMS.
Assign Roles and Permissions to Store Associates: Configure in Point of Sale CMS what actions managers or associates can perform, which helps streamline store operations and maintain security and compliance.
Assign Stores to Franchise Groups: After creating franchise groups, associate stores with the appropriate franchise in Point of Sale CMS.
Configure App Roles in Your Identity Provider: Create app roles in Microsoft Entra ID and map them to Point of Sale CMS user roles. App roles grant employees access to the CMS based on their assigned role.
Restricting Single Sign-On (SSO) to Microsoft Entra ID in Point of Sale CMS: Restricting Single Sign-On (SSO) to Microsoft Entra ID streamlines Point of Sale CMS authentication. When enabled, employees access the CMS only through their Microsoft Entra ID login, enhancing security and simplifying user management.
Configure Single Sign-On (SSO) Tenant ID: The SSO Tenant ID is a unique identifier for your Microsoft Entra ID account. Retail Cloud CMS uses the ID to restrict authentication to Microsoft Entra ID.
CMS - Configuration and Setup: Create store associates manually or through a feed in Point of Sale CMS. Add associates so they can view store analytics in the CMS.
Configuring Azure AD: Set up Azure Active Directory (AD) to work with Point of Sale CMS.
Point of Sale CMS Roles: Control user access in Point of Sale CMS with roles and permissions. Each CMS user has a role that determines their permissions.
Configure Returns and Exchanges: Manage refund and exchange processes in Point of Sale CMS. Provide a seamless post-purchase expereince for customers.
Configure Store Settings in Point of Sale CMS: Support store operations by managing store associates, setting up offline mode and fiscalization, configuring returns and exchanges, and managing franchises. Define store-level policies and permissions to align with your daily workflows.
Delete Point of Sale CMS Users: Delete users directly within Point of Sale CMS. Non-CMS Admin roles can be deleted directly within the CMS. For CMS Admin roles, you can either contact Customer Support or change the user's role to another role to proceed with deletion.
Enable Azure AD with Point of Sale CMS: Enable single sign-on to Point of Sale CMS using Azure Active Directory (AD) and simplify user access management. Configure Azure AD, add users to Point of Sale CMS, and resolve common issues. Users can access the CMS through a custom URL.
Enable OneLogin with Point of Sale CMS: Integrate OneLogin with Point of Sale CMS to validate user credentials during login. After the login information is validated, establish communication with Point of Sale.
Filter POS Reports by Franchise ID: Corporate admins can use the franchise ID filter to narrow report data to a specific franchise or compare performance across franchises.
Access to Reporting - Austria: Point of Sale reporting data is available at both the company and register levels. This means auditors can easily request and get the required DEP files.
Access to Reporting - France: Retrieve required fiscal reports, like FR Journal Archive and FR Fiscal, from the EFSTA portal in Point of Sale CMS for audits in France.
Access to Reporting - Germany: Download the Point of Sale merchant’s store register data from the EFSTA portal to share with auditors.
Access to Reporting - Portugal: Access SAFT-PT files to send them to Portuguese tax authorities monthly. You can download fiscalization reports for each register in a store via Point of Sale CMS.
Accessing EFSTA Fiscal Reports: Generate fiscal reports using Point of Sale and EFSTA to sign every transaction with TSE.
EFSTA Cloud EFR for Point of Sale: EFSTA (Electronic Fiscal Standards Association) Cloud EFR (Electronic Fiscal Register) is a cloud-hosted fiscal register that records, signs, and reports every Point of Sale transaction. A Cloud EFR ensures that each transaction meets local tax authority requirements in France, Germany, and Austria.
EFSTA Cloud EFR Resources for Point of Sale: This table provides links to the EFSTA (Electronic Fiscal Standards Association) portal, country-specific documentation, downloads, and support contacts for setting up and maintaining EFSTA Cloud EFR (Electronic Fiscal Register).
Set Up EFSTA Cloud EFR in Point of Sale CMS: Configure Point of Sale CMS to connect to EFSTA (Electronic Fiscal Standards Association) Cloud EFR (Electronic Fiscal Register) with the credentials EFSTA provides. Then verify the connection with a test transaction.
ELSTER Reporting Requirements: Merchants in Germany who use Point of Sale CMS must electronically report their systems to their relevant tax office by uploading an XML file to MyElster.
Fiscal Checklist: Use the fiscal checklist to track action items for fiscalization in supported regions before going live with Point of Sale.
Hardware Configuration and Setup - Italy: Set up your Epson fiscal printer to connect to your POS. Then, obtain the IP address so you can manually add the printer to the POS app and begin fiscalization.
High-Level Requirements - France: To comply with French fiscal regulations, Point of Sale (POS) software must be certified by French Audit Authorities and record all transactions.
Known Issues & Restrictions - Italy: Understand the limitations in Point of Sale for printing receipts in offline mode, including different order scenarios and restrictions.
Offline Behavior - Portugal: Due to Portuguese regulations, printing receipts in offline mode is unavailable. Transactions are fiscalized when the system is online. Store associates enter the paper receipt number from the preprinted receipt given to the customer into the Point of Sale (POS) app.
Fiscalization Online and Offline Capabilities: Quickly learn which fiscalization methods countries support in online and offline mode. Use this when configuring fiscalization in Point of Sale.
Other Country-Specific Information - Portugal: To comply with Portugal's VAT requirements, merchants accepting gift cards must include a line item with 0% VAT in their VAT file in Point of Sale.
POS App Flow: The POS app lets store workers do important sales tasks, like printing tax-adjusted receipts after a sale and storing data in the cloud for tax reporting.
Providing EFSTA Merchant Access: Give merchants access to the EFSTA portal so they can download reports. You can manage Point of Sale user access to the EFSTA portal and confirm each user’s appropriate level of permissions.
Fiscalization Requirements for Austria: Austrian merchants must register with tax authorities via Finanz Online and digitally sign all Point of Sale (POS) transactions.
Fiscalization Requirements for France: Confirm that your Point of Sale (POS) or cash register system in CMS meets criteria like inalterability, security, data retention, and archival.
Fiscalization Requirements for Germany: Point of Sale integrates with EFSTA to adhere to German fiscal regulations, providing a digital interface for financial administration.
Fiscalization Requirements for Italy: Set up Epson FP90III RT model printer and configure Point of Sale CMS to gain fiscalization compliance in Italy.
Fiscalization Requirements for Mexico: Mexican tax rules require sellers to provide buyers with an electronic proof of payment. Point of Sale integrates with FiscalPop to ensure compliance with Mexico's fiscal requirements.
Setup and Configure Merchants - Mexico: Merchants who want to use Point of Sale's services in Mexico must set up a FiscalPop account. During setup, give Point of Sale key merchant details such as the Stamping URL, Auth Token, and Invoice URL.
Setup and Configure Merchants - Portugal: Set up the ATCUD for each register and document type by sharing the required information with your Point of Sale Customer Success Manager
Troubleshooting - Italy: Troubleshoot issues when printing fiscal receipts in Italy with error messages in the POS app, which helps store associates identify and resolve problems.
Data Exports with Franchise Attribution: All data exports from Point of Sale include franchise attribution. Corporate admins can export reports for all stores and franchise groups. Franchise admins can export reports only for their franchise stores, and exports automatically include their franchise ID.
Franchise Management Overview: Franchise management in Point of Sale enables centralized oversight of corporate-owned and franchise stores while granting franchise operators controlled access to their specific locations.
Franchise Reporting in Point of Sale: Franchise Reporting in Point of Sale gives corporate and franchise admins access to report data based on their role. Corporate admins have full visibility across all franchise groups. Franchise admins can access data only for stores in their assigned franchise group. This role-based access keeps franchise data fully separate while giving each user type the visibility they need.
POS Reports Available to Franchise Admins: Franchise admins have access to reports that automatically show data only from stores within the franchise admin's assigned franchise group. Store dropdowns don't include stores from other franchises or corporate-owned locations.
Franchise User Roles and Permissions in Point of Sale: Point of Sale grants corporate admins broader access than franchise admins across franchise setup, stores, users, reports, and promotions. Corporate admins manage all franchises and can edit any promotion, while franchise admins are limited to their assigned franchise and can edit only the promotions they create.
Activate and Register Point of Sale App: Activate your iOS device and install it as in-store register. First, download the TestFlight and Point of Sale (POS) apps on your iOS device.
Activating the Point of Sale App: Scan a QR code to turn on the POS app on your device for the first time. Make sure you have CMS environment access and a POS device with the TestFlight app installed.
Adyen - Buy Now Pay Later: Use Point of Sale (POS) app and Adyen terminals to accept Affirm payments, offering customers a Buy Now, Pay Later option.
Turn on Card BIN Capture for Adyen Payment Terminals: Capture richer payment data with extended Bank Identification Numbers (BIN) in reporting. Retain the first 6–8 (depending on the institution) digits of the card BIN in TLogs and transaction JSONs for payments done on Adyen portals. Turn on card BIN capture in your Adyen Customer Area.
Adyen - Line Item Display: Display purchase details on the Adyen terminal before payment. Showing the cart summary on the payment terminal gives shoppers an overview of their purchase, including quantity, discounts, and taxes.
Processing Installment Payments for Mexico Retail Stores with Adyen Terminals: If you have Point of Sale stores in Mexico, you can process installment payments through Adyen integrated terminals. Work with Adyen to install the necessary configurations and update your terminal to receive installment prompts during payment processing. Add a tag to your receipt layout to print installment details for shoppers. Review the limitations if your terminal uses the card acquisition flow and the necessary workarounds for debit card payments.
Adyen Payment Methods: Integrate supported Adyen payment methods integrate with Point of Sale (POS), allowing your customers to use a variety of payment options.
APG 320 Cash Register Setup Guide: Integrate your APG 320 cash register with your receipt printer for operations within the Point of Sale (POS) app.
Access API Keys for POS App: Increase security by using Point of Sale CMS to generate brand and environment-specific Activation QR Codes. Simplify the process of managing API keys for different Point of Sale (POS) app brands and environments.
Adyen - Enabling Beacons: Beacon functionality in Adyen Terminal allows it to broadcast its presence to nearby Bluetooth devices. We use beacons in the Adyen terminals to locate them from the Point of Sale Point of Sale (POS) app and connect them to the one to carry out the particular transaction.
Adyen Payment Gateway Information: You can configure different payment gateways at the store level, such as store-level settlements, reporting, and currency requirements and integrate Adyen into Point of Sale.
Ayden Payment Resources: Integrate Adyen payment resources with Point of Sale CMS to process point-of-sale transactions. Use either Adyen SDK or Terminal API configurations for terminals.
Ayden QR Code Payments: Enable your customers to complete in-store payments quickly and securely with their preferred QR code wallet apps via Adyen. The Point of Sale (POS) app supports payments through AliPay and WeChat Pay.
Donations with Adyen Giving: Configure the Point of Sale (POS) app to capture information about donations made with Adyen terminals. Customize donation options, secure payment processing, fee coverage, comprehensive reporting, and integrate into existing systems.
Best Practices for Wi-Fi and 3G/LTE Setup on the POS App: Confirm compatibility with Store LAN peripherals so your Cellular iPad connects, regardless of the network. Select LTE as the backup network mode to provide a failover mechanism for continuous connectivity if Wi-Fi fails.
Epson Bluetooth Printer Setup: Configure the printer settings in Point of Sale CMS and connect to the printer in the Point Of Sale (POS) app. You can then print receipts and manage cash drawers efficiently.
Capture Customer Information From Payment Terminal: Allow customers to directly enter information, such as email addresses, on Adyen and Verifone terminals, streamlining data collection. Reduce the need for store associates to verbally collect information. Configure custom layouts in Point of Sale CMS and designate text input or checkbox fields for terminal input to tailor the data collection process.
Configure Ayden Terminal for Point of Sale: Connect an Adyen terminal to a network so you can board it and complete the pairing process with the Point of Sale (POS) app.
Configure and Manage Barcode Scanners: Setup barcode scanners to capture and enter data into the Point of Sale (POS) app. Improve data accuracy, save time, and increase productivity.
Set up Payment Gateway Settings in Point of Sale CMS: Configure gift card settings for Adyen and Verifone payment gateways so customers can use gift cards at your store. Enable gift cards, select a provider and SKU, and enter a cash-out configuration within Point of Sale CMS.
Configure and Manage Elavon Payment Terminals: Process customer payments securely and efficiently with Elavon Payments in the Retail Cloud Point of Sale (POS) app. Streamline transactions, automate billing processes, and enhance customer experiences through secure and seamless payment processing.
Configure Elavon Terminal for Payments: Set up Elavon Terminals to use with the Point of Sale (POS) app. The Elavon card reader terminals can process payments using Ingenico Move 5000, Lane 7000, and Link 2500 Elavon card reader terminals.
Configure Gift Card Payments in Payment Terminal: Configure Point of Sale's Point of Sale (POS) to accept gift card payments, add value, cash out, and check balances, using a payment terminal. Merchants can select the integration approach that suits their needs, verifying all transactions are available through gateway reporting.
Configure and Manage Other Payment Terminal Settings: Accept diverse payment methods using the Point of Sale (POS) app, including gift cards, manual credit card entry, and external credit card readers, to provide customers with flexible options.
Configure Hardware for Point of Sale: Connect the physical components of your store. Set up printers, barcode scanners, cash drawers, and payment terminals from providers such as Adyen, Verifone, and Elavon to power your POS experience.
Configure POS App: Set up your Point of Sale (POS) application and register to start processong transations efficiently. Check the app permissions, configure the hardware, and set up the netwrok topology for the app and the hardware.
Configure Current Register Hardware: Check the current register hardware configuration in the Point of Sale (POS) app. View the current configuration for each device connected to the register, device details, and the configuration source.
Configure and Manage Verifone Payment Terminals: Integrate Verifone payment devices with the Point of Sale (POS) app,to securely process transactions. Streamline payment operations and improve accuracy.
Configure and Manage Adyen Payment Terminals: Integrate the Ayden payment platform into the Point of Sale (POS) app. Acceppt payments globally, reuce fraud, and streamline reconciliation while providing a seamless checkout experience.
Configure and Manage Cash Drawers: Connect a supported cash drawer to the Point of Sale (POS) app to manage transactions and track cash flow. Streamline the checkout process and reuce errors.
Configure and Manage Printers: Configure printers to produce customer documents from the Point of Sale (POS) app. Show the printer name instead of the MAC address.
Configure Standalone Mode: Configure Adyen terminals to accept payments via Point of Sale without a store associate Point of Sale (POS) app connection during an outage.
Configuring Notifications for Verifone: Use Verifone Central Notifications in Point of Sale to receive transaction status updates and automate business processes, such as order management and report downloads.
Adyen Payment Terminal Onboarding and Pairing to POS: Set up Adyen terminals to connect to the Modern POS and process payments. Connect your Adyen terminal to Wi-Fi, board the device, and then pair it with the POS app.
Datalogic Scanner Support in Point of Sale: The Datalogic Magellan 1500i is a corded barcode scanner that connects to a supported Epson printer's USB port. The USB port passes the scanned data to Point of Sale (POS).
Dynamic Currency Conversion: Select the currency to use for completing credit card transactions, either the local currency or the card’s billing currency. Configure Dynamic Currency Conversion (DCC) keys in Point of Sale CMS to print on physical receipts.
View Virtual Receipts for Elavon Terminal Purchases: Show Point of Sale customers their cart summary on the Elavon payment terminal during checkout. By configuring an Elavon Payment Gateway, the terminal displays line item details, discounts, and taxes.
Epson IP Printer Setup: Configure your Epson IP printer in Point of Sale CMS, connect it to the Point of Sale (POS) app, and switch to DHCP to connect to the network and print receipts.
Network Tethering Using Epson Printers: Use network tethering to connect your register to a network via an Epson printer if Wi-Fi is unstable or there are limited ethernet ports. Connect the register to the printer using a USB cable for a stable and reliable Point of Sale (POS) system, while also charging the iOS device.
Epson Printer Troubleshooting: Solve common issues with Epson printers in Point of Sale to quickly restore printer functionality and minimize disruptions.
View Features Supported by Elavon: Stay informed about transaction payment capture, offline support, and other key functionalities of Elavon features and how they interact with Point of Sale.
View Gift Card Payments in the POS App: Accept gift cards as payment by swiping at the terminal, manual entry, or scanning. Manage insufficient balances by applying partial payments, and use gift cards in multitender payment flows.
Understand Gift Card Error Handling: The Point of Sale (POS) app provides error handling for failed gift card transactions, so store associates know what actions to take.
Credit Card with Manual Key Entry: Enter credit card information manually via Adyen, Elavon and Verifone payment terminals using the Point of Sale (POS) app.
Migrating to Point of Sale Release App: Migrate from the UAT app to the Point of Sale (POS) Release app. Confirm that you have received a TestFlight invite to access the new app.
Star mPop Hardware Troubleshooting: Resolve iPad and printer connectivity issues by ensuring proper power, Bluetooth connections, and Device Manager settings in Point of Sale.
Network Topology for POS and Hardware: Integrate Point of Sale with supported peripherals by understanding the necessary network calls and communication protocols. Ensures communication among your iPad, iPhone, and devices like card readers, printers, scanners, and cash drawers.
Allow Payment Gateway and Gift Card Providers: Integrate gift card providers with your payment gateways to turn on gift card functionality. The gift card provider supplies credentials that your gateway provider configures as a payment method.
Check Point of Sale App Permissions: Check the status of the Point of Sale (POS) app permissions. Review a list of all the permissions required by the app to fully function and are prompted to approve any permission that is not authorized.
Start the POS App: Configure your system to get the Point of Sale (POS) app to work. Grant permissions to make certain the app functions completely, turn on features like scanning QR codes and connecting to devices via Device Manager.
Using Production TestFlight IPAs: Sign IPAs with your own credentials in Point of Sale before distributing them to stores. Use an MDM provider to share the application or use TestFlight to test with both internal and external users.
Program the Datalogic Scanner for Point of Sale: Scan configuration barcodes from the Datalogic Product Reference Guide to change how the Magellan 1500i formats scans in Point of Sale (POS), or to reset the scanner.
Setting up TestFlight on Your Device: Test Point of Sale (POS) on Apple devices using TestFlight so merchants can effectively test the app. Register new accounts and provide corporate email addresses to your Salesforce contact to receive the TestFlight app.
Star Micronics Printer Setup Guide: Connect Star Micronics mC-Print3 printers to your POS app to print receipts. Make sure your Point of Sale (POS) app meets the minimum build requirement before you configure app settings in the CMS.
Star mPop Setup Guide: Connect the Star mPOP receipt printer to your iPad via Bluetooth to print receipts. In Point of Sale CMS, configure the register by selecting Star mPop as the model and Bluetooth as the connection type.
SteadyLAN using Star Printers: Make sure of reliable Point of Sale (POS) system operation, even if stores have unstable Wi-Fi or a shortage of ethernet ports.
Configure Tap to Pay: Turn on Tap to Pay in Point of Sale for a register in Store Management and configure the Adyen URL in Payment Gateways.
Tap to Pay—Test Setup: Test tap to pay in a Point of Sale production environment or sandbox environment by using Adyen Test Cards.
Tap to Pay - User Experience: Quickly process customer payments on a Point of Sale register configured to use Tap to Pay.
Request Tap To Pay Entitlement: Configure Tap to Pay on iPhone for your custom apps. Request an entitlement from Apple to use iPhones as payment terminals with the Point of Sale Platform.
Tap to Pay Overview: Accept contactless payments directly on an iPhone using the Point of Sale (POS) app.
Support Tipping on Adyen Terminals: Allow customers to provide tips during checkout using Adyen terminals in the Retail Cloud Point of Sale (POS) app, which enhances the payment experience.
Hardware Topology Setup: Point of Sale's Printer and Payment Terminal Topology allows you to determine whether the application is paired with a printer or payment terminal one-to-one (1:1) for an extended period of functionality or whether it's one-to-many (1:N) where it is prompted each time to select the device to use.
Troubleshooting POS App Connection with Ayden Terminal: Resolve POS connectivity issues with Adyen terminals by using these troubleshooting steps. Make sure smooth transactions occur by addressing error messages, connection problems, and configuration issues.
Troubleshoot Payment Terminal Issues: Troubleshoot common misconfiguration errors to verify smooth gift card functionality. Correctly configure settings on Point of Sale CMS, Adyen terminal settings/payment methods, and gift card provider settings.
Tap to Pay—Troubleshooting: Resolve Tap to Pay errors and connection problems by verifying your Adyen configuration in the Point of Sale (POS) app and internet connection.
Verifone Payments: Feature Support: View a comprehensive list of supported features for Verifone Payments integration with Point of Sale, so you can decide if it fits your business needs. See which POS versions support transaction payment capture, terminal payment cancellation, refunds, and other functions.
Verifone - Line Item Display: Show your Point of Sale customers an overview of their purchase on Verifone payment terminals before they pay. The cart summary displays the number of items, taxes, and the order total on the terminal.
Verifone Payment Onboarding: This article goes over the onboarding steps for using the Verifone Payments terminals with Point of Sale.
Verifone Payments: Perform a sale using a Verifone Payments terminal integrated with Point of Sale.
Set Up Verifone Store and Forward (SAF): Configure Verifone Store and Forward (SAF) so the Point of Sale (POS) app keeps processing credit card transactions if the network isn't working.
Zebra Scanner Support: Configure your wired or wireless Zebra scanners in the Point of Sale (POS) to make sure of accurate and efficient barcode scanning.
Language Selection and Usage: The POS app lets users change the language at any time or select a language for a specific operation, such as searching for products or printing receipts.
Design Layouts in Point of Sale CMS: Customize the POS experience by creating app configs, managing layouts, and applying layout templates. You can also configure receipts by using metadata, create deep links to key actions, and personalize the in-store experience with quizzes and UX rules.
Create App Configs: Tailor POS appearance and behavior for diverse retail scenarios. App Configs enable custom configurations for different use cases or segments. Retailers gain flexibility and control to optimize user experience and operational efficiency across devices, roles, and locations.
App Configs in Point of Sale CMS: Customize and manage multiple app configs to tailor the appearance and behavior of POS for different use cases or segments, ensuring each register uses the most appropriate settings for its specific scenario. This flexibility enhances user experience and operational efficiency.
Configure CMS to use App Config Segmentation: Customize Point of Sale app configurations for different user groups to enhance personalization and control. Toggling settings in CMS allows you to disable defaults and enable layout groups, ensuring a tailored experience. iOS users can select from a variety of native, license-free fonts by typing the name directly. Set and edit segmentation preferences to refine the user experience at associate and manager levels.
POS App Flow: After a reset, users can retrieve a specific Point of Sale App Config using a token or opt for the default configuration. Token retrieval takes precedence only if the register and associate are not targeted by any app config segmentation rules, ensuring a tailored user experience. Once logged in, the app config name is visible on the cart screen, providing transparency and control.
Known Issues & Restrictions: Get details of known issues and restrictions with Point of Sale App Config Segmentation.
Rules of Precedence: When defining segmentation rules for app configs in Point of Sale, prioritize specificity and granularity to resolve conflicts. Clear precedence ensures that registers or associates are targeted accurately, enhancing app functionality and user experience.
Copy App Configs: Copy and compare Point of Sale artifacts and app configurations.
Copy Point of Sale Artifacts: Efficiently copy Point of Sale artifacts between environments using the CMS Copy Tools. Export and import artifacts with ease, ensuring seamless content management and deployment.
Compare Point of Sale Artifacts: Diff Tools help you quickly identify configuration discrepancies between environments, ensuring accurate artifact imports and streamlined debugging processes. By pinpointing differences, you can verify the integrity of your deployments and resolve issues more efficiently.
Copy an App Config: Copy a Point of Sale app config to create a new version while maintaining the same layout references, ensuring that any layout changes affect both configs. This method streamlines app configuration management and reduces redundancy.
Copy Tool Features: The Point of Sale Copy Tools offer robust import and export capabilities, enabling users to efficiently manage and duplicate a wide range of artifacts. Users can easily create accurate copies, streamlining their workflow and ensuring consistency across projects.
Copy Tools Known Issues & Restrictions: Point of Sale Copy Tools operate on a user-specific basis, e.g., any Product Bundles you create are only visible to you. Other users are unable to view or access these Product Bundles generated when using Copy Tools.
Copy Multilanguage artifacts: Multilanguage support allows users to import app configs, email templates, layouts, and reason codes in different languages, enhancing global brand consistency. Other artifacts default to the primary language, ensuring seamless integration.
Copy Tools: Migrate App Configs, Layouts, and Field Mappings across environments and locales with the Point of Sale Copy Tools. Export from your current merchant/locale and import seamlessly to any other, but avoid using between single-language and multilanguage accounts to prevent bugs and unintended side effects.
Copy Tools Use Case Scenarios: Use the Point of Sale Copy Tools to reset app configurations and restore settings in your test environment. Import bundles with multi-language support to update app configs and layouts, while field mappings are imported in the default language.
Segment App Configs: POS offers deep customization through App Config Segmentation. This feature lets retailers tailor the POS experience based on device, personnel roles or associates, and store locations. This enhanced method simplifies configuration and provides granular control over the POS interface for different users and contexts.
Enhanced Method for App Config Segmentation: This approach is recommended, especially for new and onboarding merchants. It allows you to segment app configs for Point of Sale based on three criteria: Device Type (iPad vs. iPhone), Personnel (based on role or individual associate), and Location (based on store group or store).
Create an App Config for the Enhanced Method for App Config Segmentation: Create a Point of Sale app configuration in CMS to customize your app's look and feel with logos, fonts, and other settings. iOS users can leverage a variety of native, license-free fonts by typing the name directly.
Enable the Enhanced Method for App Config Segmentation: Enable Point of Sale App Config Segmentation to customize app configurations for different user groups, enhancing personalization and control. By toggling specific settings in the CMS, you can disable role-level or associate-level defaults and enable layout groups, ensuring a more tailored user experience.
POS App Flow for the Enhanced Method for App Config Segmentation: After a reset, users can retrieve a specific Point of Sale App Config using a token or opt for the default configuration. Token retrieval takes precedence only if the register and associate are not targeted by any app config segmentation rules, ensuring a tailored user experience. Once logged in, the app config name is visible on the cart screen, providing transparency and control.
Rules of Precedence for the Enhanced Method for App Config Segmentation: When defining segmentation rules for app configs in Point of Sale, prioritize specificity and granularity to resolve conflicts. Clear precedence ensures that registers or associates are targeted accurately, enhancing app functionality and user experience.
App Config Segmentation in the POS app: One fundamental capability of POS is how easily and deeply it can be customized. A core component of that configurability, is the App Configuration or, App Config, for short.
Traditional Method for App Config Segmentation: This approach involves directly linking roles and associates to a designated Retail Cloud app config. This method will be deprecated in the future.
Create an App Config using the Traditional Method for App Config Segment: Set up your app's visual identity in Point of Sale by configuring the logo, fonts, and other settings in the CMS. iOS supports a wide range of license-free fonts, allowing you to customize the app's appearance to match your brand.
POS App Flow for the Traditional Method for App Config Segmentation: When launching the POS app, the merchant-level default app config is initially loaded. Users can override this with tokens before login, but associate or role-level configs in CMS take precedence post-login, ensuring personalized settings. This allows for flexible and tailored app configurations, enhancing user experience and operational efficiency.
Rules of Precedence for the Traditional Method for App Config Segmentation: When loading app configs on the POS app, the system prioritizes configurations assigned directly to associates, followed by role-specific configurations, and finally the app's default settings. This ensures that associates always use the most appropriate configuration, enhancing efficiency and accuracy in store operations.
Create Deep Links: Quickly navigate Point of Sale with a detailed list of deep links and their supported uses, empowering users to access specific features and streamline retail tasks. By using these direct links, retailers can enhance efficiency and provide customers with faster access to key functionalities within their accounts. Explore how each link simplifies navigation and improves the overall user experience.
Account Deep Links: Explore a detailed list of Point of Sale account deep links, each with a clear description and supported context. Links include features for account management, orders and deliveries, payment details, and personalization. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
BOPIS/Store Fulfillment Deep Links: Explore a detailed list of Point of Sale BOPIS/store fulfillment deep links, each with a clear description and supported context. Links include features for order status, fulfillment, history, packing, and pickup. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Create Branch Deep Links: Generate deep links for Point of Sale using the Branch.io dashboard to enhance user navigation and improve customer engagement. Active link creation streamlines the user experience, driving higher conversion rates and better tracking of marketing campaigns.
Cart Options Deep Links: Explore a detailed list of Point of Sale cart options deep links, each with a clear description and supported context. These links include cart, order, payment methods, transaction, product, and tender management along with discounts and rewards, loyalty programs, and payment flows. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Cash Register Deep Links: Explore a detailed list of Point of Sale cash register deep links, each with a clear description and supported context. Links include features for cash management, reporting, transactions, and cash register operations. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Create a Category Browse Deep Link: Automate your category navigation with Point of Sale's category browse feature. Set your preferred UI in the CMS, and let the system dynamically generate and update category pages based on your feed structure, saving you time and effort.
Chat Deep Links: Explore a detailed list of Point of Sale chat deep links, each with a clear description and supported context. Links include bold and live chat. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Clienteling Deep Links: Explore a detailed list of Point of Sale clienteling deep links, each with a clear description and supported context. Links include features for customer management, client profiles, and CRM activities. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Configure Deep Link Dependencies: Deep links in the POS app can launch specific views, but some require additional configurations. Learn which deep links need dependencies and how to set them up to avoid errors and ensure smooth functionality.
Engagement Deep Links: Explore a detailed list of Point of Sale engagement deep links, each with a clear description and supported context. Links include features for media, social interaction, and content management. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Add Inline Deep Links: Use inline deep links in Point of Sale to render content inside the current screen. This capability keeps users engaged by providing relevant information without navigating away from their current task. Enhance user experience and streamline workflows by embedding content directly within the interface. Boost productivity and provide seamless access to essential resources.
Layout Deep Links: Explore a detailed list of Point of Sale layout deep links, each with a clear description and supported context. Links include features for customer information and general layouts. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Comprehensive List of Deep Links: Explore a detailed list of Point of Sale account deep links, each with a clear description and supported context. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Loyalty Deep Links: Explore a detailed list of Point of Sale loyalty deep links, each with a clear description and supported context. Links include features for displaying the ADS and general loyalty screens as well as unlinking loyalty details. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Media Deep Links: Explore a detailed list of Point of Sale media deep links, each with a clear description and supported context. Links include features for Vimeo, YouTube, and other video links. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Other Deep Links: Explore a detailed list of Point of Sale other deep links, each with a clear description and supported context. Links include features for advanced carts, application management, configuration options, and user interface elements. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Peripherals Deep Links: Explore a detailed list of Point of Sale peripherals deep links, each with a clear description and supported context. Links include features for switching barcode scanner, card reader, and printer, and resetting the Zebra scanner. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Personalization Deep Links: Explore a detailed list of Point of Sale personalization deep links, each with a clear description and supported context. Links include features for language and region pickers, notification details, and quizzes. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Print Receipt Deep Link: Discover the Point of Sale print receipt deep link. Use this link to help users quickly navigate to receipt printing and emailing for standard receipts, gifts, and invoices, enhancing their experience and streamlining retail operations.
Configure Product Bundle Deep Links: Point of Sale product bundles are packages of related products or services offered together at a discounted price. This can encourage customers to buy more, providing convenience and value. Product bundles can be ingested as a feed or authored in the CMS.
Product Search Deep Link: The Point of Sale product search deep link lets users initiate a product search from multiple access points. Users can launch product searches from a layout, a tab, the hamburger menu, a notification, or even an Instagram post. With a configurable search, users can quickly find the products they need, enhancing their shopping experience.
Add a Product Search Deep Link: Add a Point of Sale product search deep link to let users initiate a product search from multiple access points.
Product Search Deep Link Search Control: Use the search controls in the Point of Sale product search deep link to determine various default settings for a search, such as search order, filters, and style of results shown.
Product Search Deep Link Master Product: Use the master product deep link to show available products for a given variant group ID in a Point of Sale product search deep link. This is used, for example, to show other available sizes when the linked size is out of stock.
Product Search Deep Link Search Parameters: Use the search and category parameters in the Point of Sale product search deep link to initiate a search for specific content.
Products Deep Links: Explore a detailed list of Point of Sale products deep links, each with a clear description and supported context. Links include features for search, browse, purchase, and scan barcodes. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Purchase Order Deep Links: Explore a detailed list of Point of Sale purchase order deep links each with a clear description and supported context. Use these links to help users quickly navigate to purchase order creation and history, enhancing their experience and streamlining retail operations.
QR Code Linking to App: Use a QR code in Point of Sale to enable a user to click or scan a web link and be directed to the POS app or a web page.
Reporting Deep Links: Explore a detailed list of Point of Sale reporting deep links, each with a clear description and supported context. Links include reports for associates, sales, reconciliation, and more.. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
Store Associate Deep Links: Explore a detailed list of Point of Sale store associate deep links, each with a clear description and supported context. Links include features for checkout, shipping, inventory, adjustments, orders, quotes, transactions and more. Use these links to help users quickly navigate to specific features and functionality, enhancing their experience and streamlining retail operations.
URL Deep Link: Discover the Point of Sale URL deep link. Use this link to help users open a URL, enhancing their experience and streamlining retail operations.
Deep Link Values: Get details of the deep link values for various destinations in the Point of Sale app. Each URI ensures users can navigate directly to key destinations, streamlining their workflow and enhancing productivity. In each, you need the URI provided by Salesforce.
Manage Layouts in Point of Sale CMS: Layouts offer flexible and modular design options, allowing customers to seamlessly customize their digital experiences for various needs. Easily manage and customize your layout with powerful editing tools to add, insert, resize, and delete rows and cells. Enhance user experience with features like pagination, app config overrides, and snap-to-grid alignment for tailored and efficient solutions.
Create a Category Layout: Learn how to design a visually engaging category page in Point of Sale that contains six images and product search deep links.
Cell Configuration in Layouts: Learn about the different ways that cells can be configured in Point of Sale layouts with content and interactive behavior.
Layout Editor: Easily manage and customize your layout in Point of Sale with powerful editing tools. Add, insert, resize, and delete rows and cells, and adjust cell padding for precise control. Enhance user experience with features like Paginate for full-screen views, override app config settings for tailored UI options, and Snap to Grid for accurate overlay alignment.
Edit Rows and Cells in the Layout Editor: Easily manage your Point of Sale layout by adding, inserting, resizing, and deleting rows and cells. Customize cell padding and split cells horizontally or vertically for precise control, enhancing your design flexibility and efficiency.
Edit Layout Settings in the Layout Editor: Customize layout settings in the Point of Sale Layout Editor to enhance user experience and control. Enable features such as Paginate for full-screen cell views, override app config settings for tailored UI options, and use Snap to Grid for precise overlay alignment.
Create a Home Layout: Learn how to design a visually engaging Point of Sale app home page with a GIF, text overlay, padded image, and carousel. Enhance user experience by integrating dynamic elements and clean layout techniques.
Introduction to Layouts: Layouts in Point of Sale offer flexible and modular design options, enabling seamless customization for a variety of user needs. By leveraging Layouts, customers can easily adapt and enhance their digital experiences, ensuring a tailored and efficient solution.
Create and Publish Layouts: Learn how to create and publish layouts using the Point of Sale Layout Editor, including starting from a blank layout or a template, and managing live versions, drafts, and scheduling. Discover how to edit, save, publish, and restore layouts, ensuring your content is always up-to-date and tailored to your needs.
Personalize User Experience (UX): Personalize the POS app using CMS to configure custom fonts and launch images. Extend your brand to the POS app by uploading fonts that match your company's brand guidelines. Launch images configured in the CMS provide a fresh look without requiring a new build, so you can quickly update the application's appearance and keep it current. Using appropriately sized and formatted digital assets also helps you maintain the visual appeal and functionality of your POS interface.
Point of Sale Digital Asset Specs: Use digital assets in layouts with the correct specifications for the POS app. Customize the app's flow by adding images, ensuring they meet the recommended specifications for optimal display. By adhering to these guidelines, you maintain the visual appeal and functionality of your POS app. Optimize your layouts with appropriately sized and formatted digital assets.
Set Up Custom Fonts: Custom fonts help you extend your brand to the POS app. Upload your fonts to match your company's brand guidelines, and use CMS to select them. You can then customize your app with your specific fonts.
Configure a Launch Image: Launch images appear on the screen immediately after the POS app loads. Configuring these images in the CMS provides a fresh look and feel without requiring a new build. Using CMS to configure the launch images lets you quickly update the look and feel of the application. You can keep the application current without the overhead of managing application updates.
Quizzes: Use Point of Sale quizzes to gather customer preferences and valuable data. Create engaging quizzes, forms, or polls to capture user feedback and information. Add surveys after successful checkouts and include mandatory questions to ensure you get the data you need. You can also create quizzes where users see real-time poll results after submitting their answer.
Use Quiz Analytics and Insights: Quiz analytics and insights provide performance data in Point of Sale CMS. Access responses to quiz questions and text responses to gain valuable insights. Analyze results to understand user engagement and improve content.
Quiz Best Practices and Recommendations: Create effective quizzes in the POS app that engage users and gather valuable insights. Follow these best practices for designing multipage workflows, providing clear answer summaries, and optimizing answer layouts. These guidelines help you build quizzes that are user-friendly and provide actionable data.
Create a Checkout Quiz: To collect additional information related to an order in the POS app during checkout, create quizzes that appear either just before tendering payment or just after an order is placed.
Create a Quiz: Use quizzes in Point of Sale to understand your customers' preferences and gather valuable data. Create engaging quizzes, forms, or polls to capture user feedback and information. Add surveys after successful checkouts and include mandatory questions to ensure you get the data you need. You can create quizzes that will allow users to answer a question and see the results of the poll in real-time after submitting their answer.
Edit Quizzes: Point of Sale quizzes consist of layouts, questions, and customer attributes. Understanding these components helps you to effectively create quizzes. Knowing these components also enables you to avoid errors while editing quizzes. Leverage this knowledge to build effective quizzes in Point of Sale.
Set Up Product Feedback Quizzes: Capture customer feedback about a product using the POS app. By configuring CMS, you can gather valuable insights on products from customers within the app. This feedback loop empowers businesses to promptly address concerns, refine offerings, and improve customer satisfaction. Use the customer's voice to optimize product experiences and drive business growth.
Use Polls: The quiz feature in Point of Sale can be used to administer a poll where users submit an answer and instantly see the poll results.
Use Quiz Styles: Customize the look and feel of inline Point of Sale quiz deep links.
Configure Receipts: Customize your customer's checkout experience by setting up various receipt layouts, including alterations and SKU-level gift receipts in Point of Sale. Efficiently manage invoice documents and meet specific Mexico requirements for order receipts. This flexible configuration process allows you to present essential transaction details clearly and even brand your receipts with a logo image, enhancing customer satisfaction and streamlining record-keeping.
Set a Logo Image on a Receipt: Set a logo image in your Point of Sale receipt configuration so that you can customize your receipts to reflect your brand. Upload your logo within the receipt configuration settings, ensuring it meets the recommended size and format for optimal display. A branded receipt enhances the customer experience and reinforces brand recognition with every purchase.
Alterations Receipt: The POS app lets you print store-copy order receipts with product alterations info on top. These receipts are intended for use and record keeping in the store. Printing a store copy helps users keep track of product changes. This ensures accurate record-keeping and facilitates easy reference for store personnel.
Configure Receipts: Customize Point of Sale receipt appearance to match your branding and create a consistent customer experience. Control email receipt-sharing options so that you can ensure secure and efficient delivery. Format receipt content to highlight important information and improve readability.
Set Up Gift Receipt at SKU-level: POS users can print gift receipts at the individual SKU level. The app prints a gift receipt for each unique SKU in the transaction. Print these receipts after a sale or when you reprint a confirmed order.
Use Invoice Document Receipts: POS lets you print invoices for your customers, either immediately after a transaction or later. Easily provide customers with detailed records of their purchases by printing invoice documents. These invoices offer a comprehensive alternative to standard receipts.
Use Metadata for Receipts: Point of Sale print and email tags are placeholders that display dynamic data in layouts, print templates, and email templates. They pull specific information from data, which is shown instead of the placeholder, so you can customize your output. Configure print tags in layouts with native or HTML text overlays, and use email tags for email and print templates. Grouped lists print a series of data points for each given tag.
Receipt Associate Profile Component Tags: Understand the print and email tags for the associate profile component of Point of Sale receipts and see the templates they are included in.
Receipt Barcode Component Tags: Understand the print and email tags for the barcode component of Point of Sale receipts and see the templates they are included in.
Receipt Billing/Shipping Component Tags: Understand the print and email tags for the billing/shipping component of Point of Sale receipts and see the templates they are included in.
Configure Email Tags: Email tags in Point of Sale are placeholders for email and print templates that pull specific information from data that are then shown instead of the actual placeholder.
Configure Print Tags: Print tags are placeholder strings that dynamically display data in Point of Sale layouts. Add print tags to native or HTML text overlays to display information such as order totals, customer names, or store details. You can also use print tags in certain app-level settings.
Receipt Customer Component Tags: Understand the print and email tags for the customer component of Point of Sale receipts and see the templates they are included in.
Receipt Fiscal Data Component Tags: Understand the print and email tags for the fiscal component of Point of Sale receipts and see the templates they are included in.
General Receipt Component Tags: Understand the print and email tags for use in any of Point of Sale receipt components and see the templates they are included in.
Receipt Inventory Component Tags: Understand the print and email tags for the inventory component of Point of Sale receipts and see the templates they are included in.
Comprehensive Print Tags List: Show dynamic data in your layouts by using Point of Sale print tags as placeholders. Each tag includes its description, location, receipt components, group list, and data mapping. Grouped lists output multiple data points for each tag.
Receipt Order Component Tags: Understand the print and email tags for the order component of Point of Sale receipts and see the templates they are included in.
Receipt Products Component Tags: Understand the print and email tags for the products component of Point of Sale receipts and see the templates they are included in.
Receipt Products Tags: Understand the print and email tags for the products component of Point of Sale receipts and see the templates they are included in.
Receipt Refund Summary Component Tags: Understand the print and email tags for the refund summary component of Point of Sale receipts and see the templates they are included in.
Receipt Store Component Tags: Understand the print and email tags for the store component of Point of Sale receipts and see the templates they are included in.
Receipt Tax Component Tags: Understand the print and email tags for the tax component of Point of Sale receipts and see the templates they are included in.
Receipt Transaction Component Tags: Understand the print and email tags for the transaction component of Point of Sale receipts and see the templates they are included in.
Customize Layout Settings: Explore settings to tailor your Point of Sale experience. Discover how to adjust accessibility, configure apps and layouts for different segments, and efficiently manage communication templates. Learn to streamline POS operations by copying special forms and setting up barcode scanning. Enhance the customer experience through countdown timers, customized receipts, engaging media, and optimized product and list page layouts.
Accessibility Settings: Point of Sale's Layout Editor helps ensure your app meets ADA compliance, enhancing accessibility with alternative text and a 75px by 75px touch target. This feature helps businesses serve all customers, including those with disabilities, by adhering to federal standards.
Set Up Scanning and Parsing Barcodes on POS App: Point of Sale's barcode scanning feature on the POS app lets you quickly input customer data, such as customer IDs, using the iPad camera or an external scanner. By creating a parsing rule in CMS, you can extract and display only the necessary information, streamlining the checkout process and enhancing customer service.
Set Up an App Configuration: Segmenting Point of Sale app configurations by app version ensures that newer versions can use advanced features unsupported by older versions. This approach allows for seamless updates and enhanced functionality, improving user experience and operational efficiency.
App Configuration and Layout Segmentation: Personalize Point of Sale apps with app configs and layout segmentations for a tailored user experience. App configuration segmentation runs at startup based on app version, while layout segmentation adjusts post-login according to user demographics, ensuring a more relevant and engaging interface.
Copy Special Forms on POS App: Add a copy button to your custom order layout in the POS app to quickly duplicate forms. Tapping the button creates a new form with all original input values, which can be edited and is automatically added to the cart. This feature streamlines order management for store associates, especially for similar items.
Layout Image Best Practices: Learn about the recommended specifications for images for use in Point of Sale layouts.
Product Image Specifications: Optimize image specifications for Point of Sale product search and display pages to enhance user experience and ensure visual consistency. Clear guidelines for image size, format, and resolution improve product visibility and customer engagement.
Insert a Video Using a URL: The Point of Sale Media Library lets you seamlessly integrate externally hosted videos into your POS app layout, enhancing the user experience and providing dynamic content. This feature allows for easy updates and consistent branding across all retail touchpoints.
Set Up Layout Groups: Layout groups (aka Personalized Layouts) in Point of Sale enable you to tailor app experiences for different user segments, such as gender and loyalty tier, ensuring a more relevant and engaging experience for each customer. By customizing layouts, you can enhance user satisfaction and drive higher engagement and loyalty.
Media Library: The Media Library allows you to upload images and videos or reference them using a URL, enabling seamless integration into the Modern POS UI for a visually engaging user experience. This feature enhances the layout editor, making it easy to create dynamic and appealing interfaces.
Set Up Product Display Page Mappings: The Point of Sale Product Display Page (PDP) mappings allow retailers to customize product display pages for specific contexts, such as off-brands, enhancing user experience by showing relevant layouts. Retailers can tailor the PDP to meet their specific needs, improving engagement and conversion rates.
Set Up a Product List Page Search Layout: The look and feel of the Point of Sale search results screen (aka PLP) is controlled by app config settings and the Search Layout associated with the app config.
Customize Receipts Using Functions: Functions in Point of Sale receipt layouts dynamically display relevant information, improving clarity and reducing clutter. For instance, cash details are hidden for credit card payments, and employee discount info is omitted for non-employee sales, ensuring a cleaner, more user-friendly receipt.
Set Up Layout Segmentation: Personalize layouts within your Point of Sale app by setting up segments through CMS. Customize user experiences by creating and assigning layout groups to app configurations, enhancing usability and engagement.
Set Up a Countdown Timer: Add a Countdown Timer to any cell in the Point of Sale Layout Editor to visually track time until a future date. Customize the appearance and format to fit your design needs, ensuring users stay informed and engaged.
Tips for Using the CMS Email and Print Template Editor: Discover essential tips and tricks for using TinyMCE in Point of Sale CMS to create efficient and visually appealing print and email templates. Learn how to optimize your content creation process and enhance user experience with practical techniques.
Implement Layout Templates: Tailor Point of Sale chat, clienteling, and review layouts to enhance user interaction and gather valuable feedback. Retail professionals can also personalize email templates, login screens, order confirmations, and product display pages to create a seamless and branded customer journey. Streamline processes like password recovery and new customer sign-ups, ultimately boosting customer satisfaction and loyalty.
Set Up a Chat Layout: Create and assign Point of Sale custom chat layouts to enhance user interaction with brand specialists to find the right products. Easily edit and test layouts to ensure a seamless and engaging chat experience for users.
Set Up a Clienteling Layout: Create a Point of Sale clienteling layout by selecting a template for iPad, iPhone, or iPod. Customize the font to enhance the user experience and ensure seamless interaction on your chosen device.
Email & Print Templates: Explore the diverse range of Point of Sale email templates designed to enhance communication efficiency. Retail professionals can quickly generate consistent and effective messages, improving customer engagement and satisfaction.
Set Up Email Templates: Set up Point of Sale email templates using pre-configured options or custom HTML. Learn to convert tags and test your templates for a seamless, personalized customer experience.
Types of Email & Print Templates: Discover the various types of Point of Sale email templates and learn how to generate each one efficiently. Tailored for retail professionals, these templates streamline communication, ensuring messages are consistent and effective.
Set Up a Forgot Password Layout: Implement a Point of Sale forgot password layout or use a mobile site to streamline the password recovery process. Users can easily reset their passwords, enhancing security and improving user experience.
Set Up a Hamburger Menu: Configure a hamburger menu in the POS app to access a wide range of features without cluttering the screen. This setup streamlines navigation, making it easier for users to find and use essential functions quickly.
Set Up a Login Layout: Learn how to create a Point of Sale login layout with input fields and link it to an app config, ensuring seamless user authentication and a smooth login experience. Set up the login deep link to direct users to the correct page, enhancing user convenience and security.
Set Up an Order Confirmation Layout: Customize order confirmations in Point of Sale to meet your specific merchant needs, ensuring customers receive clear and detailed purchase information. Use the Layout Editor to tailor the content, enhancing customer satisfaction and clarity.
Set Up a Pickup Information Layout: Configure the Pickup Information layout in the CMS to collect essential details from customers picking up orders, ensuring a smooth and secure in-store experience. Customizable fields enhance data accuracy and streamline the pickup process.
Set Up Product Forms: The Point of Sale product forms are designed to link forms with specific products in the POS app, allowing merchants to obtain product-specific details before a sale. Additionally, these forms can be applied to add-on products like insurance and protection plans.
Receipt Layouts: Customize Point of Sale receipts to enhance customer experiences. Configure store-level print receipts and use templates for order returns. The Receipt Layout editor allows you to tailor headers, footers, and item details. Understand common challenges and best practices for clear and readable receipts, including managing returns and exchanges.
Set Up a Receipt Layout: Set up custom Point of Sale receipt layouts by configuring store-level print receipts and using templates for order returns. Learn to disable receipts and revert to layouts from Modern POS 7.16.5 and earlier, ensuring consistent and tailored customer experiences.
Receipt Layout Editor in Point of Sale CMS: Customize receipt elements like headers, footers, and item details to match your brand and improve the customer experience. Create custom rules to print sections only under certain conditions.
Known Issues & Restrictions in Receipt Layouts: Explore common challenges in Point of Sale receipt layouts, such as text wrapping and spacing issues, which can affect the clarity and readability of receipts. Understand how to handle return and exchange transactions, customize receipt headers and footers, and navigate the hamburger menu for deep linking, ensuring a seamless customer experience.
Set Up a Dynamic Review Layout: Customize review forms for different products using Point of Sale dynamic review layouts. Map specific layouts to product classes to ensure a tailored review experience, improving user engagement and feedback quality.
Set Up a New Customer Sign Up Layout: Point of Sale enables businesses to boost customer engagement and loyalty by setting up a new customer sign-up layout. Customers can easily create accounts, subscribe to newsletters, and join rewards programs, enhancing their overall experience and driving long-term retention.
Locate and Manage Store Associates: Edit an associate's information, locate profiles, or reset passwords, all from one place in Point of Sale CMS.
Manage Franchises in Point of Sale: Franchise management in Point of Sale enables centralized oversight of corporate-owned and franchise stores while granting franchise operators controlled access to their specific locations.
Manage Operational Settings: Configure and manage Point of Sale (POS) stores by using CMS. Configure Omnichannel settings, manage store associates, track inventory, and generate reports. You can also configure returns and exchanges, manage stores, and access support resources.
Manage Store Associates: Control who can access sensitive customer and sales data in Point of Sale CMS, and ensure smooth store operations.
Accessing Reports: View inventory counts in Point of Sale CMS by specific store, product search, or inventory bucket. Also, group the report by product ID or variant ID.
Completing Cycle Count: Finalize cycle counts after verifying all batches are complete and items are scanned. Configure settings to automatically update inventory counts or send files for corporate review.
Configure Cycle Count Options: Improve cycle counts using serialized inventory and bulk entry to identify and track individual items uniquely in Point of Sale CMS.
Configure Modules in Point of Sale CMS: Expand functionality by enabling modules for inventory, order management, products, and promotions. Point of Sale supports omnichannel capabilities so you can manage fulfillment, product visibility, and operational logging from one place.
Configure Omnichannel Capabilities: Efficiently manage orders with multiple fulfillment types per cart or a single fulfillment type with OmniChannel in Point of Sale CMS. Customize the product display page and configure shipping methods on the Point of Sale (POS) app.
Create Cycle Count in CMS: Create cycle counts in CMS to make sure of accurate inventory management.
Create or Start Cycle Count in CMS: Create or start cycle counts in the Point of Sale (POS) app to make sure of accurate inventory management.
Create a Size Passport: View and add to your list of Custom-Made sizes in the Point of Sale (POS) app.
Creating or Starting Cycle Counts: Create cycle counts to accurately manage inventory records. You can create them in the Point of Sale (POS) CMS, the POS app, or with an API.
Download Inventory Reports: Retrieve reports in Point of Sale CMS about how many of a specific product you have in stock.
Enabling Omni Settings in Point of Sale CMS: Set up Omnichannel fulfillment options in CMS so that your store associates can fulfill orders from the Point of Sale (POS) app.
Exporting Inventory Events in Point of Sale CMS: Create an inventory export event in the CMS to export inventory data from the Retail Cloud Backend via Secure File Transfer Protocol (SFTP).
Finding Items to Be Adjusted: Scan and locate serialized items to more easily track inventory adjustments in Point of Sale CMS's Point of Sale (POS) app.
Inventory Configuration: Manage inventory settings in Point of Sale to use PredictSpring (Point of Sale), SPI, or Salesforce Omnichannel Inventory (SFOCI) as your inventory provider.
Inventory Ledger in Point of Sale: Use an inventory ledger to track item details, quantities, costs, dates, and balances in Point of Sale CMS.
Inventory Overview Configuration and Setup: Inventory tracking is required to make sure accurate results in the Point of Sale Inventory Overview and Bucket Adjustment report.
Manage Inventory: Manage store inventory in the Point of Sale CMS.
Managing Cycle Count as a Store Manager: If you are a store manager, you can use manager-specific views in Point of Sale CMS to oversee store associate counts, manage and edit batches, and view product statuses to efficiently monitor and maintain accurate inventory.
Use Multiple GTINs for Products: Scan items that have the same product ID but different GTINs or UPC codes in the Retail Cloud Point of Sale (POS) app.
No-Cost Shipping Promotion: Create promotions in Point of Sale CMS that automatically apply no-cost shipping to eligible orders at checkout on the Point of Sale (POS) app.
Offline Promotion Logs: Set up promotions in Point of Sale CMS so that your point of sale (POS) app can download the latest promotions in offline mode.
Omnichannel: POS App Flow: Create customized shopping experiences for your customers using the Point of Sale (POS) app.
Omnichannel: Serialized Products: Configure store associates to record serial numbers for serialized products within the Point of Sale (POS) app.
Omnichannel: Single Fulfillment Type per Cart: Set the default fulfillment type in Point of Sale CMS to make sure orders work if a merchant can't support different fulfillment types in one cart.
Omnichannel (v2) Overview: Integrate shopping experiences across channels with Point of Sale's Omnichannel.
View External Order Logs with Outbound Logger: View all logs in Point of Sale CMS related to an order's correlation ID to debug errors when posting an order to an external platform.
Pause Batch: Temporarily stop the scanning process in the Point of Sale (POS) app.
Perform Cycle Count as an Associate: As an associate, you can create and use batches to perform cycle counts for store inventory in Point of Sale CMS.
Policy Management & User Subscription Setting: Create monitoring policies in Point of Sale CMS to designate email addresses for receiving alerts about subscription or application-based events.
Product Search Configuration in Point of Sale: Configure the product search function in the Point of Sale CMS to define the data fields used to match query text in search requests.
Product Search Synonyms: Configure synonyms in Point of Sale CMS to optimize the search algorithm.
Product Variant Configuration: Create variants in Point of Sale CMS based on any product attribute and sort variant options, such as Material—Leather, Cloth, Satin.
Promotions Upload Overview: Import promotions manually from the CMS, schedule automatic uploads, or use Retail Cloud’s API.
Serialized Products CMS Configuration and Setup: Configure serialized products through the Point of Sale Product Feed by creating a dedicated boolean column, which indicates whether serialization is required.
Set Up Products: Use products to track inventory, manage pricing, and generate reports in Point of Sale CMS.
Set Up Promotions: Create a variety of promotion types, such as discounts, free shipping, or private sales in Point of Sale CMS. You can offer incentives to customers, encouraging purchases and boosting sales.
Multi-Language Support: POS supports multiple languages in the same country, which benefits merchants in different locales across the globe.
Troubleshooting: Make sure that your device's region and language settings are correctly configured to avoid errors while loading a specific app configuration in the Point of Sale (POS) App.
View Top Styles Sold Report: Identify popular products and optimize inventory. Use the report in Point of Sale CMS to view product title, style, units sold, and gross sales data. In the point of sale (POS) app, filter the report by SKU or style and display results for the current store or all stores.
Password Management: Password management in Point of Sale CMS controls store associates' login authentication using Point of Sale Identity Management.
Permission and Roles Examples: Control store associate actions with manager overrides in the Point of Sale (POS) app.
Point of Sale App Flow: Point of Sale app flow ensures secure transactions requiring manager approval.
Remove Customer Data From Point of Sale: To comply with privacy regulations, you can mask a customer's Personally Identifiable Informaton (PII) in order history, cart quotes, and all PII associated with collecting interactions. In order history, PII is deleted from orders and returns and pay information. In cart quotes, PII is deleted from sales, returns, and suspended carts.
Access Associate 360 Report on the POS App: Track assocate's individual productivity. Use snapshots of key metrics to better benchmark and course-corret relative to targets that determine performance and compensation.
Associate and Register Reports: Track metrics about associate productivity and register software versions in Retail Cloud CMS.
Detailed Sales Report: Use the Detailed Sales report to see details related to sales, refunds, registers, and safes on the POS app.
View Electronic Journal Report Builder: Generate order reports and analyze sales data by time. Generate reports such as store, store associates, and products sold to gain insights into your business performance.
View Payment Reconciliation Report: Confirm the accuracy of financial data and identify inconsistencies among the Retail Cloud order amount, the amount requested to the payment gateway, and the amount collected by a processor.
Performance and Sales Reports: View insights in Point of Sale CMS about sales performance, trends, and key metrics. Use the information to make informaed business decisions.
Price Lookup Report: View a consolidated list of products in Point of Sale to determine prices at store and product levels.
Product Not on File Report: Generate reports for products that didn't originate from a product feed import in Point of Sale and were manually added by a store associate.
Reconciliation and Financial Reports: View information in Point of Sale CMS about financial data to confirm accuracy and integrity. Highlight discrepancies in the data
Reconciliation Report in Point of Sale CMS: Summarize sales, refunds, and discounts to accurately reconcile financial data. Adjust the time frame and time zone, sort columns, and view country or store details to gain insights.
View Register Version Report: Review what versions your registers are on by country, store, and register in Retail Cloud CMS. See how a new version works, or find out if you're on an unsupported version.
Access Sales Attribution Reports in Point of Sale: Measure sales associate performance, predict commissions, and get a summary of sales and returns attributed to each associate in Point of Sale CMS.
Point of Sale Sales Audit Position: Maintain accurate transaction records with the sales audit tools that Point of Sale's Point of Sale (POS) system provides. You can also detect errors with order balance, promotions, taxes, and inventory.
Saving and Sharing Electronic Journal Reports: Track and document sales transactions in Point of Sale CMS. Include details such as the date, customer information, item description, quantity sold, and the corresponding financial amounts.
Successful Orders in Point of Sale CMS: View key sales transaction data such as order date, store ID, gross sales, and external order references in Point of Sale CMS. Monitor and analyze your sales operations.
Single-Use Promotion Code (SUPC) Report: Troubleshoot issues and view information on promotion codes, such as status, ID, and redemption status in Point of Sale.
Tender Reconciliation Report in Point of Sale: Identify and investigate these mismatches by accessing detailed information, including transaction details, payment information, and authorization amounts related to each order.
Utilities and Logs: View and generate electronic reports and log files for products and sales in Retail Cloud CMS.
Viewing & Generating Electronic Journal (EJ) Reports: Provide digital records of Point of Sale sales transactions and order details to help merchants track sales and manage inventory. Generate reports by configuring stores, date, time, and time zone to view the data.
View and Manage Reports in Point of Sale CMS: Track store performance with reports on sales, inventory, associates, and financial reconciliation. Use built-in tools to access logs and export data for audits or downstream processing.
Reset Store Associate Password: Quickly reset a store associate's password in Point of Sale CMS so they can access the tools and information they need.
Point of Sale User Roles and Authentication FAQs: Understand the types of users and roles supported by Platform Services (PS) for both Content Management Solution (CMS) and POS solutions. CMS users, with Google account authentication, access configuration, and management tools, and admins can create additional roles and link users.
Security and Encryption Overview: Point of Sale employs security measures, including TLS 1.2 encryption, to protect your data in transit and at rest. Point of Sale encrypts sensitive data, uses encrypted hard drives, and refrains from storing credit card data and standalone PII.
Set Up Store Management: Manage stores in Point of Sale CMS to gain a centralized view of your retail network. Manage inventory, track sales, and reconcile transactions.
Aborted Order Alerting: Set up email alerts for aborted orders on the Point of Sale (POS) app, so you can take corrective measures.
Fiscalization Requirements for Spain: Set up Point of Sale CMS to follow Spain's tax rules, including Verifactu and TicketBAI. These tools check how much VAT is being reported and if it's being paid.
Hierarchy of Store Pricing: Determine how prices are calculated based on store, store group, sales price, and list price in Point of Sale CMS.
Known Issues and Troubleshooting: Address Point of Sale (POS) issues such as a product not found when scanning a UPC-A barcode offline.
Manage Registers: Add, monitor, and maintain POS registers in Point of Sale CMS.
Offline Checklist Playbook: The Offline Checklist Playbook ensures the Point of Sale (POS) app continues to function smoothly during network outages.
Offline Data Security: Understand how Point of Sale (POS) secures your data when processing orders offline.
Point Of Sale Offline Feature Support: Understand which Point of Sale (POS) features are supported while offline to help your associates continue to assist customers.
Offline Feed Files Configuration and Setup: Enable store pricing and schedule jobs and logs to your offline product feeds so that you can access them later in Point of Sale CMS.
Offline Feed File Extracts: Offline feed files help the Point of Sale (POS) app function properly, where at least one online session is needed to download the required files.
Sending Information Back to Platform: The Point Of Sale (POS) app syncs offline orders to the platform after a network connection is established, allowing you to maintain accurate order records.
Setting Up Offline Testing: Simulate offline scenarios in your Point of Sale (POS) app through various testing methods to validate products, tax rates, and store logins.
Order Reconciliation: Order Reconciliation in Point of Sale provides real time key sales audit metrics within the Sales Audit Dashboard, acting as a central hub for delving into specific reports.
Order Reexport: Point of Sale's order reexport feature allows merchants to resend failed order exports to their ERP systems via webhook integration.
Point of Sale App Flow: The Point of Sale app requires data to operate offline, including product feeds, store logins, and tax rates. After the app is back online, it syncs offline tills and orders placed offline.
Point of Sale Permission Levels: The default permission levels in Point of Sale CMS dictate which Point of Sale (POS) features are available to different roles.
Point of Sale Registers: Configuring Point of Sale (POS) registers lets you track devices that run the Retail Cloud store app.
POS Deep Link Support: Quickly access specific functionalities on the Point of Sale (POS) app in both offline and online modes.
POS Offline Detection: Point of Sale monitors the device network connection to determine connectivity status.
Offline Payment Configurations: Configure your POS to support offline transactions with Adyen terminals by specifying the types of offline transactions, card types, and transaction limits.
Refund System Options: With Point of Sale, process credit card refunds using default, unreferenced, or external systems.
Reopening a Store: If a store is closed prematurely in Point of Sale CMS, reopen it so associates can create a till.
Retail Reconciliation - Suggested Practices: By performing daily reconciliations with the Point of Sale (POS) app, you avoid financial loss due to mistakes or fraud and gain insight into your business's cash flow.
POS App Flow: See how to configure returns in the Point of Sale (POS) app and be aware of limitations with certain receipt printers.
Returns Policy Configuration: The Point of Sale (POS) app lets store associates perform returns on purchased items based on configured policies.
Scheduled Feed File Imports: Scheduled feed file imports automatically generate offline extracts on a set schedule in Point of Sale CMS after product pricing changes.
Set Up and Configure Returns Policy: Configure store return policies for online and offline support in the Point of Sale app. You can create a policy for outlet stores and regular stores.
Socket Mobile Scanner Setup Guide: Integrate your Socket scanner with the Point of Sale (POS) app to streamline barcode scanning. Supported models connect via Bluetooth, enhancing the checkout process.
Store Creation: Create stores and edit store details in Point of Sale CMS
Store Price Support Offline Feed POS App Flow: Test your configuration and setup changes by relaunching your Point of Sale (POS) app, then refresh the app's product feed by manually downloading it.
Sync Device Time Zone and Store Time Zone: Prevent store closure failures due to time zone mismatches between POS devices and store locations. For merchants on Salesforce POS build 11.8.1 and later, time zone checks are automatic when associates log in to POS devices. For merchants on builds before 11.8.1, you can manually enforce this time zone check with a CMS setting.
Enable Franchise Management: Enable Franchise Management in Point of Sale CMS for the Merchant Location Region (MLR).
Point of Sale Single Sign-On: Point of Sale Single Sign-On (SSO) lets users sign in with a single set of credentials and access components such as the Content Management System (CMS) and the POS app. Point of Sale supports common identity providers (IdPs), including OneLogin and Azure Active Directory (Azure AD).
Store Associates: Store associate users can be fed into the Point of Sale platform through a feed file or they can be created and managed manually in the CMS.
POS Offline Support: Continue operating the POS app if the device isn't connected to WiFi or Ethernet, or your internet service is down. Sync the POS app data after you're back online.
Support Offline Mode: Continue working with Point of Sale CMS data even without an internet connection. Stay productive in areas with little-to-no internet access.
Support Fiscalization: Ensure sales transactions meet goernment-specific requirements and provide EFSTA access in Point of Sale CMS.
Time Zone Preferences: Select your time zone in your Point of Sale CMS user profile to view reports with dates and times in your local time.
Troubleshooting: Use the Azure AD sign-in logs to debug Point of Sale CMS user issues.
Testing Tap to Pay in Non-production Environments with the POS Beta App: Starting with POS version 11.6.1, tap to pay testing requires a separate app in Adyen terminals. Previously, you could test tap to pay transactions in both production and non-production environments using a single app. Adyen’s SDK changes in POS v3.11.0 split environments into AdyenPOSLive for live environments and Adyen POSTEST for test environments. Install the POS app beta app to test Adyen’s tap to pay functionality in a non-production environment.
CMS User Management: Customize users in CMS to control access to reports, configurations, and other features within a company.
Create Franchise Administrator Users: To grant specific access to franchise staff, define permissions and link their account to a specific franchise group in Point of Sale CMS.
Configure Point of Sale CMS: Begin by setting up Point of Sale CMS, the central tool for managing your retail environment. Customize user settings, assign roles, and configure multilanguage and time zone preferences to match your store operations.
Customize User Settings: Control user access and permissions within the system. Add, modify, and remove user accounts, as well as assign roles and permissions to control access to specific features and data. Configure security settings, such as password policies and multi-factor authentication, to protect user accounts and data.
Go-Live Checklist Tool: The Go-Live Checklist in the Point of Sale CMS provides a clear overview of a merchant's readiness for launch, ensuring a smooth transition to live operations. Users can quickly access and complete specific checklist items, with easy links to help articles for guidance. This tool streamlines the go-live process, helping users efficiently manage
Get Started with Point of Sale: Learn about supported hardware, onboarding steps, and store-readiness requirements. Refer to a go-live checklist and general Frequently Asked Questions (FAQs) to guide your deployment process.
Onboarding Overview: Get started with Point of Sale's by understanding the deployment lifecycle and key integration points. Quickly configure feeds, ERP, and payment gateways, and manage your store operations and analytics through the content management system.
Supported Devices and Platforms: Point of Sale runs on iOS, Android, and Windows devices. Point of Sale supports certified terminals, stands, barcode scanners, printers, and cash drawers. Self-certify legacy hardware from supported manufacturers to use that hardware with the POS app.
Certify Legacy Hardware for POS App: To use legacy hardware from one of the supported manufacturers with the Point of Sale POS app, self-certify printers, scanners, cash drawers, and card reader terminals.
Certify Legacy Card Reader: Conduct validation tests to certify a legacy card reader for a supported vendor for the POS app.
Certify Legacy Cash Drawers: Conduct validation tests to certify a legacy cash drawers for a supported vendor for the POS app.
Certify Legacy Printers: Conduct validation tests across all supported interfaces (IP, Bluetooth, and USB) to certify a supported vendor's legacy printer for the POS app.
Certify Legacy Scanners: Conduct validation tests to certify a supported vendor's legacy scanner for the POS app.
Point of Sale: Point of Sale is a mobile-first POS and omnichannel platform for managing in-store operations and connecting with online commerce systems. Point of Sale supports point-of-sale transactions, clienteling, endless aisle, and store-based fulfillment. Configure layouts, receipts, and store settings with a built-in, no-code CMS. Point of Sale integrates with payment providers, business planning and order management systems, and tax platforms. The platform is designed to scale with evolving business needs and store formats.
Point of Sale on Android and Windows: Point of Sale is available on Android and Windows, in addition to iOS. Use Android or Windows devices for in-store checkout and other retail operations.
Apply Customer Groups to Promotions: Merchants can create targeted promotions tailored for specific customer groups, for example veterans, teachers, which are defined in their customer records. By using the customerGroup attribute, shared across the SPI and Salesforce fields, merchants can efficiently apply these targeted promotions to groups of customers. This functionality is supported via Point of Sale's SPIs and Salesforce Sales Cloud (SFSC). For NetSuite customers, contact a Retail Cloud representative for custom mapping instructions.
Processing BORIS (Buy Online Return In-Store) Returns in Point of Sale: Point of Sale offers flexible methods for processing BORIS returns, including referenced and unreferenced refunds, and tender remapping. These options are tailored to merchants using SPIs, Salesforce Order Management, or NetSuite connectors, ensuring alignment with specific business needs.
Adyen 2024 Pay by Link (PBL) Updates in Point of Sale for EU Merchants: For EU merchants using Pay By Link (PBL), Adyen has added three fields: Browser IP Address, Cardholder Name, and Cardholder Email Address or Cardholder Phone Number. Adyen automatically handles the Browser IP Address, but the other two require configuration in both the CMS and your Adyen account portal.
Currency Rounding in the POS app: Currency rounding is the practice of rounding order totals to some monetary increment. Currency rounding is common in countries where rounding is legally required (like Canada, Australia, South Korea), and in other countries where smaller coins are phased out. Salesforce POS supports multiple rounding scenarios, including calculation-driven, cash, currency specific, and currency conversions. This support ensures smoother cash handling and accurate change, enhancing customer shopping experiences and precise transactions for accurate sales reporting. Configure cash rounding in CMS and review rounding behavior for sales, returns, and exchanges.
Set Up Card on File (CoF) in Point of Sale: Configure Card on File to process transactions by using a customer’s saved card. This feature supports Adyen payment terminals.
Configure Discounts and Price Corrections for POS: Configure the Point of Sale settings and manager approval policies for discounts and price corrections before applying them in the POS app. You can also limit the changes that associates can make.
Configure Deposits at Item Level for POS: Customize deposit percentages within the POS app to meet specific business needs. Configure rules in CMS for different store types and define requirements based on product attributes or specify that fulfillment and shipping methods require full payment. Deposit details are clearly displayed in the POS app, including during returns and order edits, ensuring transparency and control over payment options.
POS Deposit Behavior: Sales associates can view deposit details, initiate multitender flows, and adjust orders with deposits. Deposits are automatically calculated based on product and tax rules. The deposit details can be found in the TLogs, so merchants can locate tokenized information and shopper references.
Applying Manual Discounts & Price Corrections in POS App: Efficiently manage pricing adjustments and errors at checkout using manual discounts and price corrections in the POS app. Discounts can be applied, for instance, to damaged items. You can also set checks and manager approval rules to limit the changes that associates can make. Configure these settings in CMS before using them in the POS app.
Configure Employee Discounts in Point of Sale: POS lets employees enter their information to receive purchase discounts. To apply discounts, create a Customer rule that checks for an employee when you create a promotion. You can also configure employee validation using an SPI to validate employee information before applying promotions.
Enable Express Checkout in POS: Speed up customer checkouts with Express Checkout in the POS app. Configure express checkout with a deep link, by manually adding items, or a quantity picker. Associates can scan items directly into the cart, handle errors, and complete orders efficiently.
Gift Card Support in POS: Gift card support in the POS app enables store associates to handle gift card payments, purchases, and returns, streamlining the checkout process. Associates can easily apply gift card tenders, add value to cards, and redeem them for merchandise. With gift card returns, associates can issue refunds to new gift cards, offering customers a convenient option.
Support Layaways & Deposits in POS App: POS app supports partial payments/deposits while creating an order. An order is eligible for partial payments if it has online items. Partial payments can be done in two ways in the POS app: creating a layaway order and adding a deposit amount to an order. Only online orders define Layaway orders, while deposits can be a mix of in-store and online orders. The deposit must be more than the total of items in-store. If the deposit is less than 25% of the total for online purchases, a warning is shown.
Laway and Deposit POS App Flow: Customers can reserve items with a down payment and adjust deposit amounts as needed. The app supports various tender types, including Pay by Link for compatible versions, enhancing payment flexibility.
NRR Lowest Price Calculation in Point of Sale: Point of Sale calculates the lowest price based on these criteria: Store Historical Prices, Product Multi-Region Historical Prices, and Product Historical Prices. When the lowest price is found for a given number of days, that price is returned as the NRR lowest price.
Configure NRR Lowest Price Calculation: To populate lowest prices, a Point of Sale account (Merchant, Region, Locale) must set value types for tender types for returns without receipts.
Configure Member Pricing in Point of Sale: Offer discounted pricing to customers who belong to a qualifying customer group, such as loyalty program members. Configure the customer group in CMS, and the POS app automatically applies member pricing during checkout.
Configure Miscellaneous Tender in POS App: Point of Sale supports miscellaneous tender as a payment option in the POS app. This allows for more options if the more common or standard payment methods (like card, cash, check, finance, or PayPal) don't work for a merchant's specific payment types. Configure your store and register settings in CMS to support Mischellaneous Tenders.
Configure Multiple Tenders for Point of Sale: Accept payments across multiple credit cards and other tenders in a single transaction. Configure the supported tenders and customize their display order in your POS app.
Show Net Subtotal in Cart Summary and Receipts in POS: Show the net subtotal (subtotal after discounts) in the summary sections across the POS app and in paper and email receipts. With CMS settings, control the display text for net subtotal and subtotal and decide to hide or show subtotal and net subtotal in the POS app.
Configure PBL in Point of Sale CMS: Enable in-store and remote payment options with Pay by Link (PBL) to enhance customer convenience and flexibility. Streamline payment processes, reduce checkout times, and improve operational efficiency by configuring PBL in the tender display order, setting polling times, and customizing deep links and pending order confirmation layouts.
Configure a Payment Gateway for PBL in POS: Configure a payment gateway to support Point of Sale's Pay by Link functionality. PBL works with Adyen and Verifone payment gateway terminals.
PBL Order Status, Troubleshooting, and FAQ: Discover how different Pay by Link (PBL) order statuses, from creation to completion or failure, impact inventory management. Understand common PBL troubleshooting, frequently asked questions, and known issues and restrictions.
Point of Sale Pay by Link (PBL) Overview: Point of Sale's POS app offers Pay by Link functionality with two distinct payment flows. The In-Store Payment flow lets customers pay right away by scanning a QR code with their phone. The Remote Payment flow lets customers get an email link to pay later. Both payment flows are supported by Adyen and Verifone payment gateway terminals.
PBL POS App Flow: The POS App Flow enhances in-store and remote checkout experiences by enabling seamless payments through QR codes and email links. It automates payment status checks, provides real-time order updates, and efficiently manages deposits, returns, and exchanges, boosting customer convenience and associate productivity.
Generate a PBL Report in Point of Sale CMS: The Pay by Link report shows details that can help with tracking transactions and reconciliation. These details include the gross sales of a store and the sales/percentage of the different payment links.
Manage Tax Rates and Exemptions in POS App: Store managers can show and override taxes as needed, ensuring compliance with recent tax changes and special promotions. Customers can efficiently manage tax rates and exemptions with manager approval for overrides, and customize tax visibility and breakdowns in the Retail Cloud POS app.
Configure Tax Exemptions for Point of Sale: Merchants can apply tax breaks to customer carts during checkout when valid proof is provided. This ensures customers receive the appropriate tax exemptions, while merchants can efficiently manage exemptions through the CMS, even in offline mode.
Configure Line-Level Tax Display on Point of Sale Receipts: Display itemized taxes and regional fees directly beneath individual products on receipts. Configure which tax codes appear as line items to keep receipts clean and relevant.
Manage Tax During Checkout in the POS app: Store associates can use clear and flexible tools to handle tax during checkout, including tax indicators, breakdowns, exemptions, and overrides. This ensures accuracy and enhances customer service, providing a transparent and efficient shopping experience.
Tender Business and Personal Checks in the POS App: The POS app supports both personal and business checks as a tender type. For business checks, only the check amount and check number are required. For personal checks, users can turn on or disable verification. If verification is enabled, all fields—routing number, check number, account number, check amount, and license details—must be entered. If disabled, only the check number, check amount, and license details are required.
Set Item & Transaction Level Limits in the POS app: Control discounts applied in your POS app by setting maximum limits for items and transactions. These limits are checked against the order total after promotions. Require manager approval if the order total exceeds the set maximum discount amount or percentage.
Complete Sale Transactions in POS: Point of Sale's POS app streamlines the checkout process, enabling flexible and efficient sales transactions. Associates can accept various payment methods, including single and multitender options, ensuring a seamless and quick customer experience. Configure available tender types in CMS before running transactions.
Customize the Clienteling Layout in Point of Sale: Customize how clienteling displays in the POS app by configuring the layout through app config settings or by creating a custom clienteling profile layout. After you customize the layout, make clienteling accessible to store associates through the user icon or a deep link.
Configure Customer 360 Clienteling for Point of Sale: Configure the connector or service that powers each Customer 360 area in the POS app, giving store associates a unified view of customer data from Commerce or Service. The configured connector or service applies only to the Customer Profile, Address, and Wish List flows.
Ghost Email: Share collections and cart via email from any email ID of your choice in the Point of Sale (POS) app.
Point of Sale Loyalty Overview: Point of Sale supports loyalty integration. This integration facilitates the search for loyalty customers within the app, and shows and applies available rewards to the cart.
Point of Sale Loyalty SPIs: Use Point of Sale's SPI to connect your loyalty program to the POS app. Make it easier to find loyalty customers and show rewards.
Manage the Customers in Your Black Book: Add or remove customers from the Point of Sale black book with either the main black book screen or the customer’s profile.
Manage Store Tasks with Point of Sale: Create a list of tasks to help with task management and leverage the feature to keep track of any to-dos you might have.
Collections: The POS app lets store associates and managers create a collection of products. You can share collections directly with customers or curate it for browsing purposes. The collection feature is configured using a deep link, and then implemented in a layout or from a hamburger menu. To access a collection, tap on the deep link you created in the POS app.
Create and Manage Customer Quotes: Merchants can create and track customer quotes on the POS app. Each quote has a unique number and includes customer information. Store associates can work with customers on merchandise and pricing, either in-store or over the phone, and then email the quote for review or print it on A4 paper. Customers can save the quote, delete it, or complete the checkout process.
Collect Customer Preferences Using a Quiz: Anticipating customer needs by understanding their preferences strengthens their experience. You can configure Point of Sale to collect and store customer preferences in their profiles. To gather information about customers, create a preference quiz.
Configure Advanced Shipping Notice (ASN) Receiving: Set up accurate inventory receiving, check merchandise against prearrival notifications, and set reason codes for inventory mismatches in Point of Sale.
Inventory Bulk Quantity: When scanning in inventory items during Blind Receiving or a Cycle Count, the PS POS app allows the user to manually enter a quantity for a scanned item so that each individual item does not need to be scanned. This is most helpful in scenarios where a large number of the same item must be scanned.
Manage Inventory: Point of Sale inventory management provides a lightweight inventory management system that will allow you to manage inventory across stores, online, and digital warehouses.
Manage Inventory with Point of Sale: Use the Inventory Movement feature to access a product's current availability and adjust inventory buckets.
Inventory Management Overview: Point of Sale inventory management provides a lightweight inventory management system that will allow customers to manage inventory across stores, online, and digital warehouses.
Inventory Adjustments: Store inventory management lets merchants view and adjust product counts through the CMS. Full and delta inventory feeds allow for comprehensive or incremental updates from external systems. Merchants can also integrate with the Point of Sale platform to update store inventory via API calls. The system tracks inventory based on order details, decrementing counts for in-store purchases and allocating stock for online orders.
Inventory Buckets: Point of Sale supports the following inventory buckets - Sellable Quantity, Allocated Quantity, Safety Stock, Quantity On Hand, Quantity In Transit, Quantity On Order, Not for sale, Returned items, and Floor/Demo items.
Inventory Receiving: Inventory receiving methods enable stores to track and manage incoming merchandise efficiently. Blind receiving allows the addition of items to store inventory without an ASN, while store-to-store transfers optimize inventory levels based on demand. Corporate-initiated transfers and advanced shipping notices (ASN) provide centralized control and streamline the receiving process from warehouses or suppliers.
Sample Data Movement: This table walks you through a Point of Sale Store Lifecycle and how inventory buckets are impacted as different transactions are happening in-store.
Set Up Inventory Management: Enable Point of Sale inventory management and store-level inventory tracking in CMS to streamline inventory processes and improve stock accuracy. Follow the steps to configure and schedule store inventory feeds for automated updates.
Store Operations: Cycle count lets stores perform regular inventory audits, and then make any needed changes. With full cycle count, you can audit all of a store's products, and with partial cycle count, you can audit only select merchandise.
Inventory Transfer Out: Inventory Transfer Out enables stores to initiate transfers directly from the Retail Cloud POS. Corporate can also create transfer orders through CMS or file uploads, adjusting inventory based on demand and supply. By facilitating efficient inventory management, stores can promptly address surges in demand.
Inventory Types: Point of Sale supports both online and in-store inventory. Online inventory can be managed via Feed, CMS, and API.
Inventory Movement Glossary of Terms and Definitions: This article explains the methods Point of Sale uses to calculate inventory buckets within its inventory management system. Additionally, it includes a table that shows how these buckets are impacted by specific actions in the POS app.
Create Product Restrictions with Point of Sale: Configure rules that block specific products from being sold, returned, or included in inventory processing at selected store locations.
Inventory Management of Serialized Products: Point of Sale supports the management of serialized product inventory. In inventory processes such as transfers and receivings, any serialized products must have their serial numbers scanned or manually entered. The following inventory flows support serialized products: Blind Receivings, Store to Store (STS) Transfers, Return to Vendor (RTV), and Advanced Shipping Notice (ASN).
Inventory Management - Store to Store Initiated Transfers: Merchants can create Corporate Transfers (CTS) in the Point of Sale CMS automatically by uploading a CSV file with inventory transfer information. This action will initiate a store-to-store transfer. After the file is uploaded, it'll be sent to the store's POS app. Store associates can then start packing the products for the store-to-store transfer.
Set Up and Manage Checkout for POS: Set up and manage the checkout process for your point of sale system. POS streamlines the checkout process with flexible tender options and efficient order management. The system supports reward cards, manual discounts, cash rounding, and check acceptance, helping associates complete transactions quickly. Retailers can configure taxes, deposits, employee discounts, gift cards and pay by link improving the customer experience at the point of sale.
Configure Reward Card Support in POS: The POS app provides an option to purchase reward cards and redeem them as tender when placing an order. Configure reward card support in CMS setup.
Reward Card Support in POS: The POS app provides an option to purchase reward cards and redeem them as tender when placing an order. Purchasing a reward card is always associated with an order. If a customer’s purchase is more than a specific amount, a store associate can issue a reward card to the customer. Reward cards can be redeemed as a tender in any future purchases by the customer.
Manage Clienteling: Clienteling within the POS app allows enriched customer profiles to be viewed and added to after every interaction. Clienteling helps retail store associates provide enhanced personalization by providing a complete view of customers so they can improve the customer experience. Using personalization quizzes, store associates can build a full picture of customer preferences, allowing them to curate tailored product recommendations, shareable lookbooks and more.
Customer Search: Find customers as well as add new ones in the Point of Sale (POS) app.
Manage Store Operations in the POS App: Manage tasks using the Point of Sale (POS) app, such as auditing tills, managing cancelled cash transactions, and safe management.
Outlet Store Support in the POS app: Create and manage outlet stores in the Point of Sale (POS) app, providing customers with lower prices and everyday bargains.
Manage Safe Funds in Point of Sale: View safe funds within a store, check the safe balance at any time, and create a suggested bank deposit each day.
Manage Orders: Manage orders in the POS app to create customized orders, process them efficiently, and fulfill them accurately. Support specialized order types to meet diverse customer needs. Gain insights into sales and attribution through order tracking, enabling informed business decisions.d
Configure Add-On Products in the POS App: Configure and implement add-on products on the POS app. Add-ons are specific to a product in the cart. For example, a warranty for jewelry and furniture or an embroidery charge (SKU) linked to an item to be monogrammed are add-ons. Add-ons appear on the product details page (PDP) with an option to add them to the cart. You can also control whether add-ons are eligible for refunds during the return process.
Set Up Additional Charges for CRV, Liquor Tax, and Deposits in Point of Sale: Beverage retailers need the ability to charge and disclose additional charges like CRV, liquor tax, and deposits on the items that customers purchase. In the United States, the Container Deposit Legislation/Bottle Bill governs the additional charges. The Container Deposit Legislation/Bottle Bill generally requires a refundable deposit on certain types of recyclable beverage containers to maintain an increased recycling rate.
Set Up Clearance Items in Point of Sale: Clearance items are items in a store that are sold at a discounted price. They can be enabled by flagging certain variants of a product in your store's inventory feed. IItems like display models or floor models are examples of clearance items. License plating, or unique identification, of clearance items will be performed based on their serial numbers.
Create and Customize Orders: Custom orders in the POS app empower users to create personalized transactions that include additional charges, clearance items, and add-on products. With custom orders, you can accommodate specific customer requests and manage a wider range of sales scenarios. Tailor each transaction to meet individual customer needs, ensuring a seamless and satisfactory shopping experience. Setting up custom orders enhances flexibility and control over the sales process.
Set Up Non-Merchandise SKUs: POS enables you to configure non-merchandise SKUs, such as postage stamps and gift certificates, to meet your business needs. You can also configure the checkout rules that apply to these items. Control if these items are discountable or taxable, and set other rules.
Create Not on File Items: The Point of Sale app offers an option to add Not on File items (products not listed in the Feeds) into the cart. Store associates can continue to add these items to the cart and finalize the checkout process.
Create Custom Orders in the POS App: Point of Sale allows you to create orders for custom-made items by capturing product attributes through a layout. A new product is created at runtime in Point of Sale. You can create a custom order from a basic part or product to add specific fabrics, textures, and styles. Creating custom orders helps to deliver a personalized and unique product for each customer.
Add Product Special Instructions: Display special instructions on the product details screen when adding items to the cart using POS. Special instructions offer more product details. For example, you can display storage instructions. Ensure that users have all the information needed about a product before completing a purchase.
Require Billing Address for Orders: Configure POS to require a billing address before completing an order. Requiring a billing address ensures you have complete customer information for all transactions. This configuration is managed within the CMS. Streamline your checkout process and maintain accurate records by enforcing this requirement.
Set Up Special Fees: The POS app can support special fees that are levied only in certain stores based on the location of the store. These fees can include public improvement or franchise fees,
Integrate a Customizable Product WebView: Point of Sale's Design Your Own (DYO) feature lets merchants integrate a Customizable Product WebView. Users can launch a WebView on the POS app to create or alter products. Then, they can add the products to the cart for checkout.
Fulfill Orders: Buy online, pick up in store (BOPIS), buy online, fulfill in store (BOFIS), and reserve online, pick up in store (ROPIS) orders give customers flexible options to receive their purchases. Streamline the fulfillment of these orders in the POS app. Empower your staff to manage these orders efficiently, ensuring customer satisfaction and repeat business.
Use Reserve Online, Pick Up In Store (ROPIS): Point of Sale's Reserve Online, Pick Up In Store (ROPIS) feature lets customers reserve items online for in-store trials before buying. After reserving online, the store gets an order, allocates the items, and prepares them for fulfillment, similar to Buy Online Pick Up In Store (BOPIS). Once the order is ready, the customer receives a notification to try the items in-store before purchase.
Configure Wave Picking for Fulfillment Orders in Salesforce POS: To process up to 10 fulfillment orders in a single picking workflow, add the Picklist Management deep link to a layout in CMS. Wave picking supports pickup orders, shipping orders, and corporate transfers.
Manage Product Warranties in Point of Sale: Dynamic warranty management uses an SPI so the POS can send cart data to your warranty engine, receive eligible warranty SKUs, and replace prior warranty lines with the SPI result. Learn how the POS system identifies warranty products, the required CMS setup, and the associate flow during checkout.
Process Orders: POS app order processing lets you set up your application to process orders quickly and efficiently. The application supports editing orders, order notes, order statuses, and purchase orders. You can also set default shipping addresses, suspend and resume carts, and view order history.
Checkout Flow & Error Handling: Get details of the Modern POS checkout workflow and the interaction between different systems including the app, the Point of Sale, the customer cloud, and the payment service. Errors can occur during different steps of the checkout workflow. This article provides information on different types of errors that can occur, and how each type of error is handled.
Edit Orders on POS App: With the POS app, you can change an order after it's placed but before it's fulfilled. Update quantities, remove items, or apply discounts to meet your customers' changing needs. Quickly adapt to requests and ensure order accuracy, leading to increased customer satisfaction and efficient service.
Add Order Notes: The POS app allows associates to add notes to orders and to items in an order. Store associates have the ability to add notes during checkout, in the order details screen, and to a suspended cart. Notes are also visible when creating a quote.
Add Purchase Orders: Point of Sale's Purchase Order (PO) features enable merchants to manage inventory, track purchases, and arrange timely delivery of goods. They provide a record of transactions and help streamline the procurement process by outlining the terms and conditions of the purchase. Merchants may use POs to communicate their specific requirements to suppliers, including product details, delivery dates, and pricing agreements.
Set Default Shipping Addresses on POS App: Point of Sale allows merchants using NetSuite to set default addresses on the POS app. This can be done when adding a new shipping address in the cart for online products, signing up a customer, or updating a customer's profile address. When a shipping address is set as the default, it updates the customer's profile address both in the POS app and in NetSuite.
Order Statuses: Orders made with the POS app have a variety of statuses that can effectively track your order in the checkout process. Order statuses can also help you decide what actions need to be taken for a particular order, such as whether the order needs to be picked up or ship to home.
Suspend and Resume Carts: The Point of Sale platform supports a feature that allows store associates to save a cart and resume and complete it later. By saving a cart, the totals, discounts, customer information (including shipping/billing addresses), and shipping methods will be put on pause until the associate chooses to resume it.
View Order History on POS App: The POS app allows store associates to query the order history to list orders. Store associates may choose from several filters to narrow down the search. This screen may be accessed through a deep link. This article will go over the configuration needed to implement this feature as well as an overview of the app flow.
Product Bundles in Point of Sale: A product bundle groups a parent item with required child items. It sells, returns, and ships as one unit.
Priced Bundle Data in Orders and Returns: A bundle's lines appear in Point of Sale order and return data differently than a standalone product's lines do. Use these field definitions and grouping rules to identify a bundle's lines and reconstruct the bundle.
How Product Bundles Work in Point of Sale App: A product bundle pairs a parent item with a set of required child items and behaves as one unit everywhere it appears: product search, the cart, promotions, returns, and store fulfillment.
Support Specialized Order Types: Point of Sale supports specialized order types, including digital contracts, electronic contracts, gift registries, serialized products, and tariff surcharges. Retailers can manage gift registries directly on the POS app. They can also manage tariff surcharges in Point of Sale and configure tariff rates in the CMS. Activation codes are also supported via SPI.
Point of Sale Digital Contracts for Products: Digital Contracts let a customer review and sign a contract on the POS device during a sale. When a product in the cart requires a contract, the customer signs before checkout, and the app saves and delivers a signed PDF for the order.
Point of Sale Digital Contracts for Products Behavior: When a cart contains a product that requires a contract, the POS app lists the required contracts, the customer signs each one on the device, and the app saves and delivers a signed PDF before checkout. Sign all required contracts before payment.
Enable Electronic Contracts: The POS app provides an option to ask customers to sign an electronic contract within the app when they place a layaway order or add finance as a tender. Once the contract is signed, the app generates the PDF of those documents which can be printed from the app.
Manage Gift Registries on POS App: Gift registries are supported in the POS app through an SPI. Using the SPI, businesses can access gift registries. Shoppers can make purchases off the registrant's list that can be noted back for the correct amount updates. Registrants can also use the store POS to return registry items in one transaction, irrespective of how many orders those items originated from
Support Serialized Products for Sales & Returns: Point of Sale provide features to support the sale and return of serialized products. When a serialized product has been added to a cart or returned, users is prompted to scan or manually enter the product's serial number.
Managing Tariff Surcharges in Point of Sale: Manage tariff surcharges in the POS app so merchants can consistently apply them and shoppers have a clear understanding of the impact on their purchases. The POS dynamically calculates the tariff based on the order subtotal and updates the amount as items are added or removed. The tariff appears as a separate charge, distinct from the subtotal and tax.
Track Sales and Attribution: Store Associate Sales Attribution in Point of Sale helps you track which store associates are responsible for sales. Tracking sales attribution provides insights into associate performance. With these insights, you can identify top performers and areas where associates may need additional training. You can also use sales attribution data to incentivize associates and reward them for their contributions to the store's success.
Turn on Sales Attribution in Point of Sale: Set sales attribution at either the order level or the item level so associates can get credit for the sales they make and you can track their performance.
Enable Store Associate Sales Attribution: Give store associates credit for assisting customers with their purchases. By default, products added to the cart are attributed to the logged-in store associate, but you can change the default attribution to a different associate. You can also attribute individual products to specific store associates. This ensures accurate sales tracking and performance measurement.
Configure Product Warranties in CMS: Configure Point of Sale CMS settings so you can offer product warranties. Set up a custom connector to call the warranty SPI at checkout and create a warranty product class so the POS system can identify warranty products. Then configure approvals, deep links, and warranty checks for the associate checkout experience.
Perform Warranty Checks at the Point of Sale: Associates can run the warranty check during checkout so the POS calls the Warranty SPI. This check reviews eligible warranties and prompts associates to confirm them before adding them to the cart.
Promotions for Customer Groups: When you sign up a new customer in the Point of Sale (POS) app, the value entered in the Customer Group field saves to Point of Sale's backend. Customers can only be assigned to one group at a time. They cannot be part of multiple groups at the same time. For example, a customer can belong to the Teacher group or the Veteran group, but not both.
Analyze POS App Crashes: Send Point of Sale (POS) app crash details to the systel to determine the root cause.
View Advanced Shipping Notice Report in Point of Sale: View details of received inventory or start the receiving process from different stores. Access the report in Point of Sale CMS or configure a deep link in the POS app.
Access Associate Login Report in Point of Sale: View a store associate's ID, full name, and last login date and time. Use the report in both Point of Sale CMS and the Point of Sale (POS) app to monitor associate activity. Customize the report by date to view specific timeframes.
Access Customer 360 in Point of Sale: Use Customer 360° to see all the information about a customer that the merchant handles. This includes customer information and their history with your brand, past orders, items saved in the cart, loyalty details, and more.
Error Handling and Feedback Capture in Point of Sale: The Point of Sale (POS) app provides an option to see additional details of an error and send feedback and additional details about the error in case of any order and cart actions failure. The data sent as part of failure reporting is used for analyzing the POS app failures to further improve the robustness of the POS app. Store associates can enter comments as feedback and it'll be posted and visible on CMS. These errors are analyzed periodically by Salesforce. Customers interested in this feedback can also view it in our CMS.
NetSuite Postings in Point of Sale: From Point of Sale CMS, resend data about invoices, payments, and refunds to NetSuite, if the original posting failed. Use the Successful Orders report to open a webhook, which posts the order to NetSuite and creates the required artifacts.
View Offline Register Logs in Point of Sale: Access vital information about network connectivity mode changes in the the Point of Sale (POS) app. See the time that the offline or online switch happens, what the reason for the offline switch is, and any additional details of the offline switch.
POS App Register & Hardware Vitals: Monitor the status of individual registers, store connections, and offline readiness using the Point of Sale (POS) Vitals feature.
View and Manage POS App Reports: Gain a comprehensive view of your business by generating a variety of reports from the Point of Sale (POS) app. Gain insights into key performance indicators, monitor sales trends, and track inventory levels. Use this information to make informed decisions and improve customer experiences.
Viewing Cycle Count History in the POS App: Create cycle counts, show the history of cycle counts, and get completed cycle count reports in the Point of Sale (POS) app.
View Inventory Transfer History: Access a list of Store-to-Store, Corporate, and Return to Vendor (RTV) transfers in the Point of Sale (POS) app.
Manage Returns & Exchanges in Point of Sale: Point of Sale provides flexible return options, including Buy Online Return In Store (BORIS), appeasements, and No Receipt Returns (NRR), to meet customer needs. Point of Sale also validates refunds to prevent fraud. Shoppers can return and exchange products at the point of sale (POS).
Configure Appeasements in Point of Sale CMS: Use appeasements in the POS App to modify customer orders and receive price adjustments within a set time frame. Associates can efficiently process changes with approval policies and reason codes configured in the CMS, enhancing both customer satisfaction and operational efficiency.
Configuring Appeasements on the POS App: Store associates can provide a partial refund to provide appeasement to the customer at the item or order-level (for any reason, for example such as a price match, delayed shipment, damaged item, poor customer experience, or overcharge). If appeasements are enabled and configured in Point of Sale CMS, associates can modify an order via Order History on the POS app and start the appeasement flow.
Appeasement POS App Flow: Post-sale appeasements allow store associates to modify existing orders and apply discounts, ensuring customer satisfaction. Associates can search for orders and, if appeasement is enabled, apply item or order-level discounts within the defined policy. Price overrides are managed with authorization and reason codes, with the POS app reflecting the changes in the cart total and order history, and retain the original discount for cumulative adjustments.
POS App Appeasements Reporting and Known Issues: Understand the different reporting aspects across the Point of Sale Electornic Journal, Transaction Logs, and Successful Orders for post-sale appeasements.
Configure Adyen and CMS for Point of Sale Returns: Configure Adyen and CMS settings so store associates can process returns in the Retail Cloud POS app. To avoid multiple refunds for the same customer, set a delay of 10 minutes for unreferenced refunds in your Adyen merchant account, and allow offline credit card refunds. Also, enable returns in the Returns Policies configuration and store settings within CMS.
Returns & Exchanges in Point of Sale: Shoppers can return and exchange products in the POS app. Exchanges are defined by any return transaction that also includes a sale.
Configure No Profile, No Card, No Receipt Returns (NRR) in Point of Sale CMS: Enable a flexible return process in CMS without requiring a physical receipt or customer profile. Customers can return products based on a simple search, and you can set preferred refund methods and customize the NRR layout for efficient handling.
Get to Know No Profile, No Card, No Receipt (NRR) Returns: No Profile, No Card, No Receipt (NRR) returns allow retailers to process returns without the original order details. Point of Sale creates a new staged order with the items for return, which enables processing returns or exchanges, even without a receipt. Refunds for NRR returns are issued using the tender configured in the NRR policy.
No Profile, No Card, No Receipt Returns (NRR) in POS: Allow returns for customers who don’t have a purchase receipt or a customer profile. No Profile, No Card, No Receipt Returns (NRR) in Point of Sale are performed at the lowest historical price and only if the returning item is still available in the system.
NRR POS App Flow: Conduct returns for customers with no profile or no receipts in the POS app app.
Configure Offline Returns for CMS and Adyen: Enable returns and exchanges in the POS app using app configurations. Use app settings to control return reasons, supported exchanges, and determine default item selection on the refund screen. To allow unreferenced refunds and offline credit card refunds, configure Adyen with maximum offline refund amounts.
Offline Returns POS App Flow: This feature is used by a store associate when a customer wants to return products. The associate launches the Return deeplink and initiates a return by scanning the barcode on the receipt provided by the customer or scanning the item directly if no receipt is provided.
Offline Returns in the POS App: The POS app allows orders to be returned in offline mode. An order can be returned by scanning the order receipt or if the user doesn't have the receipt for the order, the return can be started by scanning the item directly.
Process BORIS Returns with NetSuite Connector: For merchants using a NetSuite connector, BORIS refunds aren’t supported directly. However, merchants can process BORIS refunds using Point of Sale SPIs.
Process BORIS Returns with Salesforce Order Management (SFOM) Connector: For merchants using an SFOM connector, BORIS returns can either be processed externally or through an unreferenced refund for No Receipt Returns (NRR). Returns via referenced funds and tender mapping aren’t supported.
Process BORIS Returns with BORIS SPI: For merchants using the BORIS SPI where the order master is managed by Point of Sale for in-store transactions but remains external for BORIS returns, we offer three methods for processing BORIS returns. Configuring returns with an external system via OMS isn’t supported.
Process BORIS Returns with SPI as External Order Master: For merchants using an SPI where the Order Master is external, we offer three methods for handling BORIS returns. Configuring returns with an external system via OMS isn’t supported.
Enable Shipping Fee Refunds for Point of Sale: Turn on shipping fee refunds so associates can refund or discount a shipment's shipping fee separately. Point of Sale prevents refunding or discounting the same shipment twice.
Supported Functionalities by Edit Order Types: POS app supports order edits and appeasements, each with its own set of functionalities. This table outlines the supported features for each type of order edit.
Validating Refunded Amounts via Adyen Refund Webhooks: Point of Sale implements a validation system to block multiple fraudulent refunds tied to a specific order number. This validation uses Adyen's refund webhooks to confirm the success of refunds. All refunds (referenced and unreferenced) are validated via these webhooks.
Set Up and Manage POS App: Use the POS app to manage clienteling, checkout, order fulfillment, returns, and daily store operations. Configure app behavior and access real-time store reports to support efficient workflows on the floor.
Configure POS App Timeouts for Security and Cart Management: Configure timeout sessions in the Point of Sale (POS) app to automatically log out users after a period of inactivity, enhancing security. Specify timeouts for cart items to clear abandoned carts, store associate logins to protect sensitive data, and customer profile logins to maintain privacy. Adjusting these settings helps maintain security and manage cart contents efficiently.
Configure POS Settings: Configure and customize the Point of Sale (POS) app to meet your specific business needs. Tailor the cart options, price checker, and product display labels, ensuring a seamless and efficient user experience.
Capturing Customer Information for Returns with Point of Sale: View and manage customer information for returns, both online and offline. Customize a layout so that Point of Sale (POS) app users can see the information during the return process, including customer name and email address.
Customizing Navigation Bars on Your POS App: Set up the navigation bar, hamburger menu, and tabs within the Point of Sale Point of Sale (POS) app. Control the tab display by selecting visibility options, such as always visible or visible to signed-in users only. Configure app settings like tab color, text color, and icon visibility to create a streamlined user experience.
Localize Receipts in POS App: Use Point of Sale (POS) App to localize the content of the paper receipt based on the user’s choice in the order confirmation screen.
Establish OneLogin with POS App: Integrate your Point of Sale (POS) app with OneLogin to validate store associate credentials. Verify secure communication with Salsesforce and streamline user management using your existing identity and access management tools. Configure your OneLogin portal and CMS settings to enable seamless authentication for both online and offline access.
Predictive Cash Tendering in Point of Sale: Point of Sale's Predictive Cash Tendering improves efficiency during the cash tendering process. Enable the feature to allow the POS app calculate up to five predicted cash-tender amounts. Select a predicted cash tender amount or manually enter it in the text field.
Configuring Price Checker in Point of Sale: Create an app that customers use to scan a product’s bar code to get the current price. Change the layouts, visibility settings, and other important settings.
Control Product Window Visibility Based on Product Attributes: In the POS app, the product window offers two options, adding the product to the cart and viewing the Product Display Page (PDP). Using the CMS, you can configure whether or not the product window appears when you scan a product. This is based on conditions you set by using the product’s attributes.
Configuring Product Display Labels in Point of Sale: Select which product identifiers can be shown throughout the Point of Sale (POS) app to help confirm the items in an order for a faster and more efficient checkout process.
Supporting PunchOut Webpages on POS App: Integrate web-based workflows, like adding custom products, directly into store transactions using the Point of Sale (POS) app. Launch preconfigured web pages from the POS app to securely pass data and trigger actions via URL parameters. The POS app receives a message upon completion, which streamlines tasks such as customer login and cart navigation, enhancing the in-store shopping experience.
Region Support in POS App: Localize the POS app to make sure that your users see the correct language and region. Change the language in the app by setting the language in the device or by using the region deep link to switch the app language, independent of the device's language.
Require Customer Information for Returns in the POS app: Collect customer information for all return types in the POS app and increase clienteling opportunities. Store associates can search for existing customer profiles and automatically prefill the return form with the customer’s information. If no profile is found, the store associate can create one for the customer. Additionally, if the original sales order included customer details, those fields also prefill the return form.
Configure Speech Recognition (Beta) in Point of Sale: Turn on speech recognition in the POS app to streamline workflows. With voice commands, users can efficiently access features, turning on hands-free operation, and enhancing accessibility. Configure custom voice commands and deep links in CMS to tailor the experience for different languages and actions within the app.
Create Web Authorization Token: Configure token fields to generate a web authentication token in the Point of Sale (POS) app. This token is then passed as an Authorization header in a later network call.
Provision Point of Sale on Android and Windows: Before you install Point of Sale on an Android or Windows device, provision your environments and complete prerequisites in Point of Sale CMS.
Archived Release Details: Get details of past changes made in each release of Point of Sale (formerly PredictSpring).
Build Feature Summaries: For past releases, get details of what it includes, what each new or updated features does, and how to configure it in Retail Coud CMS.
May Build Summary (10.0.1): Build summary for Modern POS version 10.0.1, including what new features and changes it contains
June Build Summary (10.1.1): Build summary for Modern POS version 10.1.1, including what new features and changes it contains
July Build Summary (10.2.1): Build summary for Modern POS version 10.1.1, including what new features and changes it contains
August Build Summary (10.3.1): Build summary for Modern POS version 10.1.1, including what new features and changes it contains
September Build Summary (10.4.1): Build summary for Modern POS version 10.4.1, including what new features and changes it contains
January Build Summary (10.6.1): Build summary for Modern POS version 10.6.1, including what new features and changes it contains. Version 10.5.1 was an internal-only release for work done during code freeze, intentionally skipped number for public release 10.6.1. Access all new features and enhancements in 10.6.1.
February Build Summary (10.7.1): Build summary for Modern POS version 10.7.1, including what new features and changes it contains.
March Build Summary (10.8.1): Build summary for Modern POS version 10.8.1, including what new features and changes it contains.
April Build Summary (10.9.1): Build summary for Modern POS version 10.9.1, including what new features and changes it contains.
May Build Summary (11.0.1): Build summary for Modern POS version 11.0.1, including what new features and changes it contains.
June Build Summary (11.1.1): Build summary for Modern POS version 11.1.1, including what new features and changes it contains.
July Build Summary (11.2.1): Build summary for Modern POS version 11.2.1, including what new features and changes it contains.
August Build Summary (11.3.1): Build summary for Modern POS version 11.3.1, including what new features and changes it contains.
September Build Summary (11.4.1): Build summary for Modern POS version 11.4.1, including what new features and changes it contains.
October Build Summary (11.5.1): Build summary for Modern POS version 11.5.1, including what new features and changes it contains.
January Build Summary (11.6.1): Build summary for Modern POS version 11.56.1, including what new features and changes it contains.
April Build Summary (8.10.1): Build summary for Modern POS version 8.10.1, including what new features and changes it contains.
February Build Summary ( 8.8.1): Build summary for Modern POS version 8.8.1, including what new features and changes it contains.
March Build Summary (8.9.1): Build summary for Modern POS version 8.9.1, including what new features and changes it contains.
May Build Summary (9.0.1): Build summary for Modern POS version 9.0.1, including what new features and changes it contains.
April Build Summary (9.10.1): Build summary for Modern POS version 9.10.1, including what new features and changes it contains
June Build Summary (9.1.3): Build summary for Modern POS version 9.1.3, including what new features and changes it contains.
July Build Summary (9.2.1): Build summary for Modern POS version 9.2.1, including what new features and changes it contains.
August Build Summary (9.3.1): Build summary for Modern POS version 9.2.1, including what new features and changes it contains.
September Build Summary (9.4.1): Build summary for Modern POS version 9.2.1, including what new features and changes it contains.
December Build Summary (9.6.1): Build summary for Modern POS version 9.6.1, including what new features and changes it contains.
January Build Summary (9.7.1): Build summary for Modern POS version 9.7.1, including what new features and changes it contains.
February Build Summary (9.8.1): Build summary for Modern POS version 9.8.1, including what new features and changes it contains
March Build Summary (9.9.1): Build summary for Modern POS version 9.9.1, including what new features and changes it contains
Release Details: For releases, get details of the new features, bug fixes, and outstanding open issues.
Release Notes for Modern POS Version 11.6.2: Release notes for Modern POS Version 11.6.2, including new features, bug fixes, and known issues. This release supersedes all of the previous releases including 11.6.1. The exact release version is 11.6.2 r27505 (SP). This release is identical to 11.6.1 with fixes related to gift card returns, card financing rewards, and custom IPA build crashes.
CMS for Point of Sale: Access the Point of Sale CMS to customize POS app settings. Access CMS using a corporate Gmail account, link non-Gmail accounts, and set up single sign-on (SSO) for added secruity and user access control.
Secure Access to CMS: Verify secure access to Point of Sale while maintaining Payment Card Industry (PCI) compliance. Single sign-on (SSO) provides an overview and checklist for security and encryption. Turn on Azure AD and OneLogin with Point of Sale CMS, which enhances security and allows only authorized users to access sensitive information.
Distinguish Between OCAPI and SCAPI Requests: Use the new method added to the dw.system.Request object to identify the SCAPI context. You can now distinguish between OCAPI and SCAPI requests in extension points (hooks). Direct access to the '_sfdc_mercury' header has been deprecated.
Track Internal User Access to Sensitive Business Manager Functionality: The Commerce Cloud Security model regarding actions taken by Salesforce employees on customer realms have been enhanced to include transparent logging of all sensitive areas. When any read or write action is taken on a sensitive area, the Business Manager username of the Salesforce employee, the area, and the action is recorded in the security log available for customer use. The goal of the security control is to make the actions of Salesforce employees, via observation or through changes of realm-specific customer information, more apparent.
B2C Commerce API Release Notes: Keep track of the new features and functionality that the B2C Commerce APIs offer. The following summarizes new features and updates by month.
Integrate Salesforce Payments into SFRA for a Seamless Checkout Experience: Streamline the checkout experience for shoppers with a native Salesforce Payments cartridge that supports multiple payment methods and third-party payment gateways. This integration reduces the complexity and cost of implementing payments and provides developers with extensive customization options.
Node.js 18 Upgrade: SFRA now uses Node.js 18. Node.js is used during the SFRA build process. The upgrade improves security, enhances UI tests, and updates several plugins and cartridges.
All-in-One Feature Cartridge Added to SFRA: The new all-in-one feature cartridge (plugin_cartridge_merge) makes it easy to install and use several optional SFRA features without the help of a developer. It also makes it easy to selectively disable optional features.
Support for Einstein Complete the Set Recommender: SFRA provides a new template that works with Commerce Cloud Einstein’s Complete the Set recommender. With this template, you can easily control the display of recommended products on the Product Detail Page.
Use Cases and Examples for B2B Stores: Learn how Salesforce Commerce can help you achieve your business goals. See step-by-step examples and videos that walk you through using Commerce App features to get the most value from your store.
