* B2C Commerce *

*** Important Update: Associate a B2C Commerce instance to your Managed Runtime production environment(s) by Sep 29, 2026 ***Salesforce is limiting how Managed Runtime (MRT) determines production environments. Currently, you can set any environment to production, regardless of whether it’s connected to an instance. This creates a lot of traffic, which harms the accuracy of monitoring and incident response for everyone on the platform.

To reduce traffic and improve capabilities, Salesforce is limiting which environments can be flagged as production. Starting September 29, 2026, an environment can be flagged as production only if it’s associated with a Staging or Production B2C Commerce instance.

Log Center logs and Log Center metrics aren't affected by this change. Both stay independently configurable on any environment, regardless of instance tier.

To keep production monitoring and related features on these environments, associate each one with a Staging or Production B2C Commerce instance before September 29, 2026.

1. Open Runtime Admin and go to the Environment Settings for the environments listed above.
2. Associate the environment with a Staging or Production B2C Commerce instance.
3. Confirm the production flag is still on after you save the association.
4. Redeploy the current bundle in that environment. This ensures the change takes effect immediately rather than waiting for your next scheduled deployment.

If you don't associate an instance by the deadline, you will lose production monitoring. Your Log Center logs and Log Center metrics settings won't change.

Need help?

Contact Salesforce Customer Support if you have questions about which instance to associate.

#B2C Commerce #B2B Commerce

Secure your Agentblazer Status and stay ahead of the curve.

More content has been added to the Champion, Innovator, and Legend trails! Plus, the new change log feature makes it easy to track what’s new to grow your skills and keep pace with AI. 

 Skill up today:

trailhead.com/agentblazer 

🤖 Build real expertise for the Agentic AI era. 

Trailhead Journeys are now available across 10 Salesforce products empowering you to move from fundamentals to advanced expertise with a progressive, step-by-step curriculum. 

Newly added journeys:

• ⚡ Headless 360 platform
• 📈 Agentforce Marketing
• 👥 Agentforce Service 
• 🛒 Agentforce Commerce
• 🔌 Omnistudio

Skip the search. Start the journey 👉 trailhead.com/trailhead-journeys

I have created an API Client under Account Manager

In Business Manager for my user under  Manage Access Keys I created "Agent User Login and OCAPI"

When I test making a call to https://[sandbox domain]/dw/oauth2/access_token?client_id={API Client ID}

with header info:

basic_auth_token = b64encode(

            bytes(f"{business_manager_username}:{business_manager_password}:{api_client_password}",

                  "utf-8")

        ).decode("ascii")

headers = {}

authorization = f"Basic {basic_auth_token}"

headers["Authorization"] = authorization

headers["Content-type"] = "application/x-www-form-urlencoded"

headers["Cache-Control"] = "no-cache" 

and

data = {

"grant_type": "urn:demandware:params:oauth:grant-type:client-id:dwsid:dwsecuretoken"

}

I keep getting HTTP 400 with error message:

"Client id 'client id' has invalid credentials to use grant type 'urn:demandware:params:oauth:grant-type:client-id:dwsid:dwsecuretoken'."

anyone can pinpoint what I am doing wrong?

@* B2C Commerce * 

We're building out Headless 360 learning on Trailhead and want your input. 💙  

We're running a short survey to understand what you want to learn, how you like to learn, and which use cases matter most to your work. 

👉 Take the Headless 360 survey now through July 28.

Thank you for taking the time to provide this valuable feedback! 🙌