Skip to main content

Maintain Your B2C Commerce Developer Certification for Spring ’26

Learning Objectives

After completing this unit, you’ll be able to:

  • Explain how B2C Commerce data ingestion into Data 360 enables near real-time segmentation and personalized storefront experiences.
  • Describe the Guided Shopping Agent template’s capabilities, setup, and how guided questions improve product discovery.
  • Describe how the Shop the Store feature enables store-aware product discovery in B2C Commerce.
  • Discuss how the Outbound Connections allowlist enforces security compliance.
  • Explain how Hybrid Authentication in B2C Commerce integrates third-party IdPs, eliminates double logins, and manages session persistence with refresh token TTL overrides.

Stay Current With Your Certification

Salesforce certifications hold the most value when you keep them relevant. To keep your B2C Commerce Developer certification current, complete this badge by the due date.

Interested in learning more about getting certified? Check out the B2C Commerce Developer certification.

Note

While anyone can earn this badge, it is designed for those who hold the B2C Commerce Developer certification.

As part of the Salesforce Credentialing and Certification Program, you agree to the terms of the Salesforce Credentialing and Certification Program Agreement. Review the exam policies in the agreement and the Salesforce Credentialing and Certification Program Agreement and Code of Conduct article before you continue.

B2C Commerce Developer Certification Overview

B2C Commerce Developers know how to:

  • Unify shopper, product, and engagement data with Salesforce Data 360 to power real-time insights and personalization.
  • Build responsive storefront experiences that adapt to shopper behavior using near-real-time segmentation and AI-guided discovery.
  • Simplify commerce architectures by using native platform capabilities instead of custom integrations.
  • Secure and modernize authentication, sessions, and integrations across hybrid and composable storefronts.

This badge highlights key updates you need to know for Spring ’26 to keep your certification current and your skills sharp.

Note

As of October 14, 2025, Data Cloud has been rebranded to Data 360. During this transition, you might see references to Data Cloud in our application and documentation. While the name is new, the functionality and content remains unchanged.

Ingest Commerce Data into Data 360 to Power Real-Time Personalization

B2C Commerce provides a native Data 360 connector that ingests three key types of data:

  • Shopper profiles
  • Product attributes
  • Engagement events

As a result, this creates an unified, continuously updated view of each customer.

Registered shopper profiles (such as name, email, and shopper ID) are automatically exported and ingested on a scheduled basis, helping establish a trusted, unified customer record. Product data ingestion also now includes both standard fields and custom attributes (like sustainability ratings or material types), enabling richer merchandising insights and more precise segmentation. At the same time, high-volume engagement events—such as product views, add-to-cart actions, and checkout activity—are streamed into Data 360 in near real time, capturing shopper intent as it happens.

Once ingested, this data is harmonized into Data 360’s data model, where identity resolution connects profiles, behaviors, and product interactions. This unified dataset powers dynamic segmentation that reflects the latest shopper activity.

B2C Commerce storefronts can then query these segments in near real time, eliminating delays from batch processing. As a result, experiences can adapt instantly—such as updating promotions, personalizing content, or triggering offers based on in-session behavior—delivering timely, relevant interactions across the storefront.

Use the Guided Shopping Agent Template to Improve Product Discovery

The Guided Shopping Agent template for B2C Commerce, available in Agentforce, provides a configuration-first way to deliver AI-powered, conversational shopping experiences. It includes out-of-the-box capabilities such as product search, FAQs, and cart interactions, along with rich UI elements like product carousels, product details, and multilingual support. These prebuilt, commerce-aware actions significantly reduce the need for custom development, enabling faster implementation and a clear path for extending functionality when needed.

The Agent Template for B2C Commerce lets you create an agent from a template or create one with generative AI.

Developers configure the agent in Agentforce Studio using the Guided Shopping template and connect it to B2C Commerce through Shopper APIs (SCAPI/OCAPI), secured with SLAS authentication. The agent interacts with shoppers through Enhanced Chat, supporting real-time conversations on storefronts or mobile apps. Setup includes enabling Agentforce and Einstein Generative AI, configuring SLAS credentials, defining context variables, and completing storefront-specific steps (such as Managed Runtime for PWA Kit or cartridge installation for SFRA). Supported actions vary by storefront, with Composable Storefronts offering expanded capabilities like cart and order interactions.

A key capability of the template is guided questions, which actively improve product discovery. When shoppers submit broad or ambiguous queries, the agent identifies the relevant product category and asks targeted follow-up questions based on product attributes like size, color, or use case. As shoppers respond, the agent builds conversational context across multiple turns, refining search results before executing queries. This approach mirrors an in-store associate, helping narrow options, increase relevance, and boost shopper confidence.

Guided questions rely on well-structured product data and are enabled by configuring the Product Search Assistant topic in Agentforce Studio. Together, these capabilities allow developers to deliver more accurate, personalized, and conversational product discovery experiences with minimal custom effort.

Enhance Product Discovery in Your B2C Store

B2C Commerce introduced general availability (GA) support for store-aware product discovery, officially enabling shoppers to determine in-store product availability directly within online search and category results. This capability lets shoppers select a preferred store and discover products available at that location, supporting Buy Online, Pick Up In Store (BOPIS) and similar omnichannel journeys earlier in the shopping experience.

This feature builds on the Shop the Store capability and is now production-ready for broad use.

Historically, omnichannel logic in B2C Commerce was most visible at checkout, where shoppers select fulfillment options like ship-to-store or in-store pickup. With this release, omnichannel moves upstream into discovery. For developers, this shift means:

  • Store inventory now influences search and browsing, not just fulfillment.
  • BOPIS becomes a discovery experience, not a last-step decision.
  • This GA feature is the standard, supported way to implement store-aware search logic.

This is no longer a pilot or workaround—it’s the recommended approach for omnichannel discovery.

When you enable Shop the Store, B2C Commerce filters search and category results using store inventory lists associated with a shopper’s selected location. Shoppers can choose a store and browse products available at that location, search online and refine results based on store-level availability, and select pickup from their preferred store during the shopping flow.

Search requests can reference one or more store inventory lists, allowing products to display if they’re available in any of the selected stores.

Search sorting remains focused on non-inventory attributes, such as price or brand. Einstein search suggestions aren’t filtered by store availability.

By moving omnichannel logic into search and browsing, you can deliver more intuitive, location-aware shopping experiences that reflect how customers actually shop—online and in store, together.

Establish Security Compliance with the Outbound Connections Allowlist

B2C Commerce includes an Outbound Connections allowlist, a configurable security feature that must be enabled before it blocks outbound network calls to any destination not explicitly approved.

All external calls—from custom code, jobs, and integrations—must now target endpoints that appear on the allowlist. The feature is managed in Business Manager through a new Outbound Connections screen, which surfaces recently used endpoints and allows administrators to approve or add destinations.

This change represents a significant strengthening of B2C Commerce platform security—but it can also disrupt your existing integration if not handled proactively.

For developers, this means:

  • Existing integrations can fail silently or be blocked if endpoints aren’t allowlisted.
  • Third-party services such as payment gateways, tax engines, ERPs, shipping providers, and marketing tools must be reviewed and approved.
  • Security compliance becomes a shared responsibility between developers and administrators.

Outbound connections are denied unless explicitly allowed.

B2C Commerce evaluates all outbound network requests against the allowlist. If the destination endpoint is not approved, the request is blocked. This ensures tighter control over where data can be sent from the platform.The Outbound Connections allowlist is a foundational security change. By enforcing explicit trust boundaries, this update helps secure commerce environments—while reinforcing the need for you to plan, document, and maintain external integrations carefully.

Use Hybrid Authentication to Unify Login and Session Management

Hybrid Authentication (Hybrid Auth) is a platform-native solution in B2C Commerce that unifies authentication across headless (SCAPI-based) and legacy storefronts (SFRA or SiteGenesis). It synchronizes SLAS-issued JWT tokens with traditional session IDs (dwsid), ensuring shoppers remain logged in as they move between experiences—eliminating double login issues in hybrid storefronts.

Hybrid Auth also integrates with third-party Identity Providers (IdPs), enabling social logins (such as Google or Facebook) while maintaining seamless session continuity. Regardless of where authentication begins, SLAS acts as the federation layer, ensuring sessions remain consistent across both headless and legacy environments.

To further enhance session management, Hybrid Auth supports refresh token cookie TTL overrides. This allows developers to control how long sessions persist for guest and registered shoppers, balancing security and convenience while maintaining consistent session behavior across storefront architectures.

Sum It Up

In this badge, you learned how recent B2C Commerce updates make it easier to build smarter, more responsive storefronts without adding complexity. You learned how native engagement event ingestion and near-real-time Data 360 segmentation let your site react to shopper behavior as it happens, not hours later.

You also learned about key platform improvements—from Hybrid Authentication and social login support that eliminate double logins, to security enhancements like outbound connection allowlisting and session TTL controls. Taken together, these updates reduce custom work, improve the shopper experience, and give you more confidence as you build secure, scalable, and personalized commerce solutions.

Resources

在 Salesforce 帮助中分享 Trailhead 反馈

我们很想听听您使用 Trailhead 的经验——您现在可以随时从 Salesforce 帮助网站访问新的反馈表单。

了解更多 继续分享反馈