Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Get Started with B2C Commerce
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Shopper Registered Event

            You are here:

            1. Salesforce Help
            2. Docs
            3. B2C Commerce for Merchandisers and Administrators

            Shopper Registered Event

            The system fires a B2C Commerce shopper registered event when a new customer profile is successfully created and committed. This event contains core customer information needed by external systems. Unlike replication events, which operate at the organization level, the shopper registered event is site-specific, so you can register and route it independently per site.

            Available in: B2C Commerce release 26.7 and later.

            Event ID

            Event ID Description When fired
            sf.cc.shopper.registered Shopper registered successfully When a customer profile is successfully created and the transaction is committed

            HTTP headers

            The shopper registered event uses the standard Commerce Cloud platform headers documented in Common HTTP Headers for B2C Commerce Events, with x-sf-cc-event-id set to sf.cc.shopper.registered.

            JSON payload structure

            Field Type Required Description
            customerId string Yes Unique identifier (UUID) for the customer
            registrationDate string Yes ISO-8601 timestamp when the customer was created
            loginId string Yes Customer's login identifier
            customerNo string Yes Customer number assigned by the system
            email string No Customer's email address (included if profile exists and email is not blank)
            firstName string No Customer's first name (included if profile exists and first name is not blank)
            lastName string No Customer's last name (included if profile exists and last name is not blank)
            phoneMobile string No Customer's mobile phone number (included if profile exists and phone is not blank)
            sites array of strings Yes List of site IDs where the customer is registered. Site names are normalized by stripping the Sites- prefix and -Site suffix.

            Example: full shopper registered event

            
{
"customerId": "abc123-uuid-def456",
"registrationDate": "2026-06-15T10:30:00Z",
"loginId": "john.doe@example.com",
"customerNo": "00000001",
"email": "john.doe@example.com",
"firstName": "John",
"lastName": "Doe",
"phoneMobile": "+1-555-0100",
"sites": ["RefArch", "SiteGenesis"]
}

            Example: minimal shopper registered event

            
{
"customerId": "minimal-uuid-123",
"registrationDate": "2026-06-15T10:30:00Z",
"loginId": "john.doe@example.com",
"customerNo": "00000001",
"sites": ["RefArch", "SiteGenesis"]
}

            Shopper registered implementation notes

            • The event is fired asynchronously after successful customer creation and transaction commit.
            • Optional fields are only included if they have non-blank values.
            • Site IDs are normalized by removing the Sites- prefix and -Site suffix (for example, Sites-RefArch-Site becomes RefArch).
            • The event is site-specific, so you can register different connectors for different sites.
            • The event is controlled by a feature toggle that's enabled by default.
            • If event serialization or firing fails, the customer creation process still succeeds.
             
            Loading
            Salesforce Help | Article