• Cert++
  • Practice
  • Certle
  • Review
  • Tracks
  • Checklist
  • Guides
  • Upgrade
Cert++
  1. Home
  3. Salesforce Accredited B2B Commerce Administrator Professional

Salesforce Accredited B2B Commerce Administrator Professional

Checklist progress

0/184Learned

Salesforce Accredited B2B Commerce Administrator Professional

Study Checklist

  • Platform Administrator
  • Platform App Builder
  • Platform Foundations
  • Platform Developer
  • Platform Administrator II
  • Agentforce Sales Consultant
  • Agentforce Service Consultant
  • Platform Data Architect
  • Platform Development Lifecycle and Deployment Architect
  • Platform Identity and Access Management Architect
  • Platform Integration Architect
  • Platform Sharing and Visibility Architect
  • Heroku Architect
  • B2C Solution Architect
  • Experience Cloud Consultant
  • Agentforce Field Service and Operations Consultant
  • Agentforce Nonprofit Consultant
  • Data 360 Consultant
  • Omnistudio Consultant
  • CRM Analytics and Einstein Discovery Consultant
  • Platform User Experience Designer
  • Platform Strategy Designer
  • B2C Commerce Developer
  • JavaScript Developer
  • Omnistudio Developer
  • Platform Developer II
  • Marketing Cloud Engagement Administrator
  • Marketing Cloud Engagement Specialist
  • Marketing Cloud Engagement Consultant
  • Agentforce Sales Foundations
  • Business Analyst
  • Marketing Cloud Engagement Developer
  • Marketing Cloud Engagement Foundations
  • Agentforce Specialist
  • Agentforce Life Sciences Consultant
  • B2B Commerce Administrator AP
  • B2B Commerce Developer AP
  • Agentforce Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • MuleSoft Integration Foundations
  • MuleSoft Developer
  • MuleSoft Developer II
  • MuleSoft Platform Integration Architect
  • MuleSoft Platform Architect
  • Tableau Desktop Foundations
  • Tableau Data Analyst
  • Tableau Consultant
  • Tableau Server Administrator
  • Tableau Architect

Checklist progress

0/184Learned

  • The key architectural advantage of Salesforce B2B Commerce over standalone e-commerce platforms is that it is built natively on the Salesforce platform, inheriting CRM data, security model, and automation capabilities without custom integration.
  • How B2B Commerce differs from B2C Commerce in typical order complexity and pricing models (large or negotiated orders versus single-item retail pricing).
  • How B2B Commerce differs from B2C Commerce in intended buyer audience and purchasing relationships (individual consumers versus business buyers).
  • B2B Commerce storefronts render using the Lightning component framework within the Experience Cloud site.
  • The relationship between Salesforce B2B Commerce and Salesforce Order Management: B2B Commerce handles storefront and cart/checkout, while Order Management handles post-order fulfillment workflows.
  • When a prospect asks whether Salesforce B2B Commerce competes with Salesforce CPQ, the correct positioning is that they are complementary: CPQ handles complex quoting, while B2B Commerce handles self-service online ordering.
  • Why native CRM customer and product data on Salesforce reduces or removes the need for a separate customer–data integration layer for the B2B storefront.
  • B2B Commerce is built on Experience Cloud sites and relies on Experience Cloud guest user profiles for unauthenticated storefront access patterns.
  • How B2B Commerce licensing is structured relative to the core Salesforce platform: it requires an additional B2B Commerce license on top of the base Salesforce org.
  • A company currently uses a third-party e-commerce platform integrated to Salesforce CRM via middleware. When positioning B2B Commerce, the primary value proposition to emphasize is eliminating integration complexity by running the storefront natively on Salesforce data.
  • Core Salesforce objects that B2B Commerce extends or relies upon, including Account, Contact, Order, Product2, and Pricebook2.
  • B2B Commerce supports multiple stores within a single Salesforce org, enabling a multi-brand or multi-region deployment from one platform instance.
  • How Buyer Groups link buyers to catalog and price book entitlements in account-based B2B purchasing.
  • The business role of Buyer Groups in B2B Commerce for grouping buyer accounts that share catalogs, pricing, and policies.
  • How B2B Commerce leverages Salesforce's native security model (profiles, permission sets, sharing rules) to control buyer access rather than requiring a separate identity and access management system.
  • The two storefront framework options for B2B Commerce: Aura versus LWR (Lightning Web Runtime), including which is the modern default for new implementations.
  • The Experience Cloud external user license requirement for B2B Commerce buyers: Customer Community Plus or an equivalent external user license type.
  • Practical differences between Aura and LWR for B2B Commerce: performance characteristics, component library maturity, and implications for existing customizations.
  • How B2B Commerce differs from B2C Commerce in account structures such as buyer accounts, account hierarchies, and contract-driven purchasing.
  • How B2B Commerce buyer external user licenses relate to internal Salesforce user licenses (different license type and assignment model).
  • The steps to create a new B2B Commerce store in a Salesforce org using the B2B Commerce setup wizard, including selecting the store template and configuring initial store settings.
  • How Buyer Groups work in B2B Commerce: their business purpose and how they associate Buyer Accounts for audience and entitlement grouping.
  • How Buyer Accounts are configured in B2B Commerce: the relationship between a Salesforce Account record and the Buyer Account object, and how it controls purchasing access.
  • How Buyer Groups control which catalog and price book an entitled buyer sees in the storefront.
  • How pricing entitlements on Buyer Groups assign the correct price book and negotiated pricing context for a buyer.
  • The role of standard Salesforce price books in the B2B Commerce storefront: how the store selects among price books for cart pricing.
  • How catalog entitlements on Buyer Groups restrict which products a buyer can see in B2B Commerce.
  • How Price Book Entries supply unit prices for commerce products in the buyer's entitled price book.
  • How to configure tiered or volume pricing in B2B Commerce without code using price adjustment schedules and price book entries.
  • Account-based pricing in B2B Commerce: how to configure negotiated or contract pricing for specific buyer accounts using buyer group pricing assignments.
  • The standard out-of-the-box B2B Commerce checkout components (for example cart, delivery, payment, and review) and what each step is responsible for.
  • Limits and trade-offs of declarative (no-code) pricing configuration in B2B Commerce.
  • How checkout components are assembled declaratively on storefront pages using Experience Builder.
  • Built-in tax calculation options in B2B Commerce for no-code tax handling.
  • How configured delivery methods surface to buyers during the B2B Commerce checkout shipping step.
  • How to wire a payment gateway for credit card processing on a B2B Commerce store.
  • Supported out-of-the-box B2B Commerce payment types such as purchase order and invoice (non-gateway) checkout patterns.
  • What typically triggers downstream order-management and fulfillment processes after a B2B Commerce order is created.
  • How storefront checkout creates or updates Salesforce Order records when a buyer places an order in B2B Commerce.
  • How Delivery Method records and carrier metadata are configured for a B2B Commerce store.
  • How to connect a third-party tax provider through Tax Integration mapping in B2B Commerce without custom code.
  • How faceted search filters work on the B2B Commerce storefront and how indexing affects facet quality.
  • Where tax calculation mode and related tax integration wiring are configured at the B2B Commerce store level.
  • How to configure searchable fields and search indexes for the B2B Commerce storefront catalog.
  • Common store-level B2B Commerce settings on the store record such as default currency, language, and guest-browsing behavior.
  • The B2B Commerce Admin role versus a standard Salesforce Admin: what additional permissions or permission sets are required to manage the B2B Commerce app.
  • The difference between a B2B Commerce catalog and a standard Salesforce product collection: how Product Category and catalog assignment structure buyer-facing navigation.
  • A B2B buyer should see only the products and prices associated with their account's contract. Without writing code, the administrator configures this by assigning the buyer to a Buyer Group that is entitled to the appropriate catalog and price book.
  • How to enable and configure Guest Browsing in B2B Commerce, including the Guest User profile permissions required for unauthenticated catalog viewing.
  • How to configure multi-currency in a B2B Commerce store and which Salesforce org-level prerequisites must be met before enabling it.
  • How the Promotion object and supported discount types (e.g., percentage off, fixed amount off) model promotions in B2B Commerce.
  • How B2B Commerce layers catalog and category assignments on top of standard Product2 records for storefront display.
  • How buyers apply coupon codes at cart or checkout so an active promotion adjusts line totals in B2B Commerce.
  • Inventory integration patterns in B2B Commerce: treating items as always in stock versus performing real-time inventory checks.
  • How connecting inventory through CartValidation integration changes add-to-cart and availability messaging versus the default no-check pattern.
  • How to use the Purchase Order payment type at B2B Commerce checkout: capturing a PO number and completing the order without card data.
  • How minimum and maximum order quantity constraints are configured on individual products in B2B Commerce and how they are enforced when a buyer adds items to the cart.
  • Why PO-based checkout is a common pattern for established B2B account relationships (offline invoicing and negotiated terms).
  • How to configure reorder functionality in B2B Commerce so buyers can repeat a previous order directly from their order history.
  • Spending limits (credit limits) on Buyer Accounts: how to configure a maximum purchase amount that prevents a buyer from placing orders exceeding their authorized spend, and where this limit is set in the Buyer Account record.
  • Order on Behalf Of (OOBO) in B2B Commerce: how an internal Salesforce user such as a sales rep can place an order on behalf of a buyer account using the storefront, and which permission set enables this capability.
  • What the B2B Commerce Checkout Integration Framework is responsible for across tax, shipping, inventory, and payment providers.
  • Guest User profile and permission readiness as part of pre-launch deployment for B2B Commerce.
  • The end-to-end B2B Commerce store deployment lifecycle: the major phases from creating the store through data setup to audience-ready publishing.
  • The role of the Experience Cloud site in a B2B Commerce deployment: the site record, its status (Draft, Preview, Live), and how activation controls buyer access.
  • How the B2B Commerce store Publish action differs from Experience Cloud site Activation: publish rebuilds the storefront assets and search index; activation makes the site accessible to external users.
  • The supported deployment metadata types for moving a B2B Commerce store configuration between environments: which components can be deployed via Change Sets versus Salesforce CLI/Metadata API.
  • The purpose and process of rebuilding the B2B Commerce search index: when it must be triggered, what happens if it is stale, and how it is initiated from the store setup page.
  • Commerce data prerequisites before go-live: Buyer Group setup, catalog assignment, entitled price book, and at least one Product Category.
  • Limitations of Change Sets for B2B Commerce deployment: which supporting objects (Buyer Groups, Price Book assignments, CMS content) must be manually re-created in the target org rather than deployed via Change Set.
  • A company is deploying their B2B Commerce store from sandbox to production. The Change Set deployment completed without errors, but the storefront is not displaying products. The most likely cause is that product catalog entitlements, buyer group associations, or price book assignments were not recreated in production.
  • Core Store and Experience Cloud configuration prerequisites before a B2B Commerce store can serve buyers (for example a linked site record, catalog, and price book alignment).
  • Guest User profile setup as a prerequisite for unauthenticated catalog browsing on a B2B Commerce storefront.
  • The role of the Store object record in B2B Commerce: it is the parent configuration record that links the Experience Cloud site, catalog, checkout settings, and tax/shipping integrations.
  • How Experience Cloud language configuration drives the default locale presented on a multilingual B2B Commerce storefront.
  • How B2B Commerce translation support layers on Experience Cloud language settings for translated product and content fields.
  • Which B2B Commerce and commerce-related automation is typically included in metadata deployments (for example Apex classes, Flow definitions).
  • LWR versus Aura for B2B Commerce: differences in Experience Builder page composition and routing that affect deployment and maintenance.
  • The Salesforce B2B Commerce store template options available at store creation (e.g., Build Your Own vs. pre-built templates) and when each is appropriate.
  • Why store-specific linking records and some commerce entitlements often still require manual reconfiguration in the target org after deployment.
  • How Named Credentials are used in B2B Commerce to securely store the endpoint URL and authentication details for external integration services such as tax providers, shipping carriers, and payment gateways, without embedding credentials in configuration records.
  • How to configure a custom domain for a B2B Commerce storefront: the steps to register a custom URL in Salesforce and the role of My Domain in this configuration.
  • How Product Categories use the category object and hierarchical parent-child relationships in B2B Commerce.
  • How Product Variations work in B2B Commerce: the relationship between a parent (variation parent) product and its child (variation) products, and which attributes (color, size) drive variation selection.
  • How category assignments map storefront navigation and catalog sections to underlying B2B Commerce product data.
  • How to assign a Product2 record to a category in B2B Commerce: the ProductCategoryProduct junction object and its role in making products appear under the correct storefront category.
  • How ProductAttributeSet and ProductAttribute records define selectable variation dimensions (for example Size and Color) for B2B Commerce variants.
  • How ProductAttribute definitions link to child variant products so the storefront resolves a selected attribute combination to a SKU.
  • The CSV format and required columns for importing B2B Commerce products using the built-in product import tool: mandatory fields such as Name, ProductCode (SKU), and Price Book Entry.
  • A company sells shirts in multiple sizes and colors. To configure this in B2B Commerce without code, the admin creates a variation parent product, defines a ProductAttributeSet with Size and Color attributes, and creates child variant products linked to specific attribute value combinations.
  • Required Product2 and price-book fields administrators must supply so imported SKUs are valid for the entitled catalog.
  • Supported methods for bulk product data load into B2B Commerce (e.g., Data Import Wizard, Data Loader, built-in commerce product import tools).
  • How to load or update translated product content for multilingual B2B Commerce storefronts.
  • How product images and media are associated with Product2 records in B2B Commerce: the ProductMedia object and how it controls what image appears on the product detail page.
  • Which B2B Commerce product fields commonly support translation (for example Name and Description) and how translated values are stored.
  • The role of the ProductCatalog object in B2B Commerce: it acts as the top-level container for categories and products, and one catalog is assigned to a Buyer Group entitlement.
  • How boost rules promote selected SKUs higher in B2B Commerce storefront search results without code.
  • How to configure which product fields are indexed for storefront search in B2B Commerce, and what happens to search results if a required field (like ProductCode) is not indexed.
  • Category assignment requirements so a catalog entitlement surfaces products in the intended storefront navigation.
  • Price book entry requirements so entitled buyers see correct list or negotiated prices for visible products.
  • How bury rules suppress or demote products in B2B Commerce search results (for example low stock or discontinued items).
  • How to model cross-sell and upsell relationships using the ProductRelated object in B2B Commerce.
  • How a product's Available-to-Order and related settings control inventory signals shown on the product detail page.
  • A product must appear in the buyer's entitled catalog for it to be purchasable in B2B Commerce.
  • Where related products render on the B2B Commerce product detail page for buyers.
  • A product import fails with missing price book entry errors. The administrator must ensure that a Price Book Entry exists in the assigned Price Book for each product before the import will succeed.
  • The Unit of Measure (UOM) feature in B2B Commerce: how to configure multiple units of measure for a single product, and how this affects add-to-cart and pricing behavior.

Leverage Salesforce CMS features that power product-based use cases to deliver business value.

0/16

The role of Salesforce CMS in B2B Commerce: it serves as the content management layer for storefront banners, hero images, promotional content, and product media.

Learn this concept
Unseen

Creating a Salesforce CMS Workspace for B2B Commerce content governance (banners, hero media, product-related assets).

Learn this concept
Unseen

Connecting a CMS Workspace to the B2B Commerce storefront's Experience Cloud channel so published items can render on the site.

Learn this concept
Unseen

How CMS Single Item, collection, and related CMS components bind workspace content into Experience Builder pages for B2B Commerce.

Learn this concept
Unseen

The relationship between CMS Channels and Experience Cloud sites: a CMS Workspace must be connected to the storefront's Experience Cloud channel before published content can appear on the site.

Learn this concept
Unseen

Common Salesforce CMS content types used on B2B Commerce storefronts (Image, Document, custom types) and how merchandisers author them.

Learn this concept
Unseen

How to configure a promotional banner on the B2B Commerce storefront home page using a Salesforce CMS image and the CMS Single Item component in Experience Builder.

Learn this concept
Unseen

A merchandiser wants to update the homepage banner without involving a developer. The correct approach is to update the CMS image asset in the Salesforce CMS Workspace and republish, so the change reflects on the storefront without a code deployment.

Learn this concept
Unseen

How CMS Connect differs from Enhanced CMS in the context of B2B Commerce: CMS Connect is a legacy mechanism for pulling content from an external CMS, while Enhanced CMS is the native Salesforce content management system.

Learn this concept
Unseen

Experience Cloud guest user object and field permissions required for public CMS-driven storefront sections.

Learn this concept
Unseen

How product images are managed in B2B Commerce using Salesforce CMS versus using direct URL references on the ProductMedia object: the trade-offs for governance and CDN delivery.

Learn this concept
Unseen

CMS Workspace content visibility controls that gate which B2B Commerce audiences see specific CMS items.

Learn this concept
Unseen

How the storefront locale or buyer language preference selects which CMS language variant renders.

Learn this concept
Unseen

Creating language variants of CMS content items in Salesforce CMS for multilingual B2B Commerce experiences.

Learn this concept
Unseen

How to use CMS Collections in Experience Builder to dynamically surface a curated group of CMS content items (such as a set of promotional images or news articles) on a B2B Commerce storefront page without code.

Learn this concept
Unseen

Publishing CMS content from the workspace so updates reach production B2B Commerce pages without code deploys.

Learn this concept
Unseen
  • How Experience Builder is used to customize B2B Commerce storefront pages: dragging and dropping Lightning components, configuring component properties, and publishing changes.
  • The Buyer and Buyer Manager roles in B2B Commerce: the distinction between a Buyer (can browse and purchase) and a Buyer Manager (can manage sub-buyers, approve orders, and access order history for their team).
  • How account hierarchy is used in B2B Commerce: a parent account's Buyer Manager can view and manage orders placed by all child account contacts, enabling enterprise purchasing governance.
  • How to configure self-registration for a B2B Commerce storefront: the Experience Cloud self-registration page, the default account assignment for self-registered users, and the record type implications.
  • What the B2B Commerce Buyer permission set grants to external users and when administrators assign it.
  • How Delegated External User Administration works in the context of B2B Commerce: a Buyer Manager can add and manage new buyer users within their account without involving a Salesforce admin.
  • Which standard Experience Builder components render cart line items, quantity editors, and roll-up pricing on the B2B Commerce cart page.
  • Where coupon or promotion code entry is surfaced on the B2B Commerce cart experience and how it ties to active promotions.
  • The standard ordered checkout steps in B2B Commerce (for example shipping, delivery, payment, review/place order) and how buyers progress through them.
  • Which Salesforce objects power the B2B Commerce Order History experience and how status fields mirror the Order record.
  • Which portions of the B2B Commerce checkout flow can be rearranged or toggled declaratively in Experience Builder versus requiring custom development.
  • How List and ListItem records model buyer-created wish lists in B2B Commerce.
  • How to expose Order History in B2B Commerce storefront navigation using Experience Builder pages and menus.
  • How buyers add list lines to an active cart or move wish-list quantities into checkout in B2B Commerce.
  • Which standard Experience Builder components render product identity, rich description, and media on a B2B Commerce PDP.
  • Which standard Experience Builder components render price, negotiated adjustments, and add-to-cart actions on a B2B Commerce PDP.
  • How navigation menus are configured in a B2B Commerce Experience Cloud site: creating Navigation Menu items in the Navigation Menu setup and mapping them to storefront category pages.
  • How category facets and sort controls on the B2B Commerce search results page interact with indexed product attributes.
  • How to use Salesforce Reports and Dashboards to monitor B2B Commerce storefront activity: which standard objects (Cart, Order, CartItem) can be used as report source objects.
  • How Customer Community Plus versus other community licenses interact with B2B Commerce Buyer entitlements in typical storefront designs.
  • Using Flow to send branded order confirmation or fulfillment kick-off actions tied to B2B Commerce orders.
  • How to configure B2B Commerce store themes and branding in Experience Builder: setting colors, fonts, and logos through the Experience Builder theme editor without custom CSS.
  • How the Account Switcher feature works in B2B Commerce for buyers who belong to multiple buyer accounts: buyers can switch their active purchasing account without logging out, and the storefront re-evaluates catalog and pricing entitlements for the selected account.
  • What historical buyer interaction data Einstein Product Recommendations needs before recommendations become useful on a B2B storefront.
  • How to enable Einstein Product Recommendations components on B2B Commerce PDP or cart pages.
  • Where Buyer Managers view pending B2B Commerce order approvals in the storefront and which actions they can take.
  • How to validate search index freshness when storefront faceting or sorting behaves unexpectedly after catalog changes.
  • B2B Commerce Cart object lifecycle states (for example active, closed, processing) and what transitions a cart through checkout.
  • How buyers maintain multiple shipping or billing ContactPointAddress records for their B2B Commerce account.
  • How B2B Commerce persists in-progress carts across sessions and how buyers resume an active cart from the storefront.
  • Troubleshooting an empty B2B Commerce storefront: verifying catalog entitlement on the buyer's Buyer Group.
  • Troubleshooting an empty B2B Commerce storefront: verifying an entitled price book is assigned for the buyer context.
  • Troubleshooting an empty B2B Commerce storefront: confirming the commerce search index was rebuilt after catalog changes.
  • Troubleshooting an empty B2B Commerce storefront: confirming products are assigned to categories in the entitled catalog.
  • The ordered sequence of checkout integrations in B2B Commerce (tax, shipping, payment) and which step runs before order finalization.
  • Troubleshooting tax at B2B Commerce checkout: validating Tax Integration metadata on the store.
  • How to pinpoint which checkout integration is failing using order summary or integration debug signals in B2B Commerce.
  • Troubleshooting tax at B2B Commerce checkout: verifying product tax codes or classification fields required by the tax engine.
  • Troubleshooting tax at B2B Commerce checkout: ensuring the configured tax provider or service is active and reachable.
  • Diagnosing broken B2B Commerce search: verifying catalog fields are included in searchable field configuration.
  • Diagnosing broken B2B Commerce search: validating search index freshness and last-build status.
  • Diagnosing broken B2B Commerce search: confirming the buyer's entitled catalog still matches the indexed catalog scope.
  • Resolving guest catalog errors in B2B Commerce: Guest User access to Salesforce CMS objects or assets powering merchandising content.
  • Resolving 'User not associated with a Buyer Account' in B2B Commerce: linking the contact to an Account that owns a Buyer Account record.
  • Resolving 'User not associated with a Buyer Account' in B2B Commerce: assigning the external user to a Buyer Group with valid entitlements.
  • Troubleshooting payment failures in B2B Commerce: validating Payment Gateway records and credentials via Named Credential.
  • Troubleshooting payment failures in B2B Commerce: reading integration or platform event logs for decline and timeout errors.
  • Troubleshooting payment failures in B2B Commerce: confirming the store references the intended active Payment Method.
  • How to use the B2B Commerce Store Administration checklist to identify launch blockers: each checklist item represents a required configuration step, and red indicators highlight incomplete configurations.
  • Troubleshooting missing PDP images in B2B Commerce: validating ProductMedia references a live CMS asset or URL.
  • Troubleshooting Experience Cloud site failures for B2B Commerce: site status (draft versus active) and guest access configuration.
  • Troubleshooting missing PDP images in B2B Commerce: confirming the CMS item is published to the storefront channel.
  • Diagnosing missing shipping methods in B2B Commerce checkout: Delivery Method active flags and store assignment.
  • Diagnosing missing shipping methods in B2B Commerce checkout: verifying shipping integration mapping returns eligible methods for the cart.
  • Troubleshooting wrong storefront prices in B2B Commerce: confirming the Buyer Group references the intended price book.
  • Troubleshooting wrong storefront prices in B2B Commerce: verifying the buyer's Buyer Group membership and entitlements.
  • Troubleshooting wrong storefront prices in B2B Commerce: checking Price Book Entry currency, quantity breaks, and effective dates.
  • Troubleshooting order approvals in B2B Commerce: confirming the intended user holds Buyer Manager permissions.
  • Troubleshooting B2B Commerce variants: confirming the variation parent is entitled in the catalog and active for commerce.
  • Troubleshooting B2B Commerce variants: validating attribute values map to real child SKU records.
  • Troubleshooting B2B Commerce variants: ensuring child SKUs include price book entries in the buyer's entitled price book.

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Salesforce Accredited B2B Commerce Administrator Professional studiers. 593 members and growing.

Go to Discord

How the storefront locale or buyer language preference selects which CMS language variant renders.

Explainer

Learn More

Practice Question

Keep going

Next conceptCreating language variants of CMS content items in Salesforce CMS for multilingual B2B Commerce experiences.

Checklist progress

0/184 (0%)

0 of 184 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Salesforce Accredited B2B Commerce Administrator Professional studiers. 593 members and growing.

Go to Discord

Explainer

Language mapping connects your CMS content languages to Salesforce storefront languages, allowing buyers to see content in their preferred language. This system ensures that when a buyer visits your storefront, the CMS renders the appropriate language variant based on their locale or language preference settings.

Core information
  • Language mapping creates connections between CMS directory languages (like "fr" in AEM) and Salesforce language codes (like "French"), enabling multi-language storefronts from a single CMS connection
More details and nuances
  • Language mapping must be enabled in the CMS connection settings, and each mapped CMS language must also be explicitly enabled in Experience Builder Settings > Languages or the mapping will not function