Profile

The Profile page allows authenticated buyers to view and update their account profile information. The page reads from and updates the underlying Salesforce User record, including fields such as:

• First name
• Last name
• Phone number
• Primary address information

The buyer’s email address is displayed as a read-only field and cannot be modified through the storefront profile experience.

This flow demonstrates how a headless storefront can render buyer profile experiences, including account information and profile management workflows.

Load the Buyer Profile

1. Call the following endpoint when the profile page loads:

   GET /services/data/v68.0/sobjects/User/{userId}?fields=FirstName,LastName,Email,Phone,Street,City,State,PostalCode,Country

2. Use the response to populate the buyer profile form.

3. Handle missing fields gracefully. Some fields can be omitted from the response because of field-level security (FLS). Default missing values to empty strings or null values instead of treating them as application errors.

4. Use the retrieved profile data to render:

   • First name
   • Last name
   • Email address
   • Phone number
   • Address information

Save Profile Changes

1. Update the editable profile fields.

2. Submit the profile update request by calling:

   PATCH /services/data/v68.0/sobjects/User/{userId}

3. Include only modified fields in the request body.

4. After the update succeeds, merge the submitted field values with the response payload. Some fields can be omitted from the response because of field-level security (FLS). Merging the submitted values prevents masked or restricted fields from disappearing from the profile form after the update.

5. Refresh the profile state using the merged field values.

6. Display a confirmation message indicating that the profile was updated successfully.

Choose a Profile API Approach

The storefront can retrieve and update buyer profile information using either SObject REST APIs or Commerce Connect APIs.

• Use SObject REST APIs when the storefront requires access to a broader set of User fields.
• Use Connect REST APIs with GET /commerce/webstores/{webstoreId}/myprofile when the available Commerce profile fields satisfy your storefront requirements.

• To add support for additional buyer profile attributes, integrate with the Salesforce Contact record instead of the User record. This pattern is commonly used for B2C storefront implementations where customer profile data is primarily managed on the Contact object.

• REST API Developer Guide: Get Field Values from a Standard Object Record
• REST API Developer Guide: Working with Records
• Connect REST API Developer Guide: When to Use Connect REST API

j

Get Started with B2B Commerce

B2B Commerce Data Model

B2B Data Deployment

Implementation Lifecycle: Personas

B2B Commerce APIs

B2B Commerce Headless Storefront Implementation Overview

B2B Commerce Headless API Architecture

B2B Commerce Headless Flow Orchestration

Storefront (Home)

Product List Page (Category/PLP)

Product Detail Page (PDP)

Cart

Checkout

Order Confirmation

Orders (History)

Login

Register

Profile

B2B Commerce Extensions

Integrations

Set Up Payment Processing

Cart and Checkout Features

Commerce SFDX Environment Setup

Build Custom Components

Implement Custom Self-Registration for a B2B Store

Headless Guest Support for Cart and Checkout APIs Using JWT

Commerce LWR Storefront Performance Best Practices

Image Optimization Best Practices

Custom Rules for Product Readiness