Salesforce just broke your site… or fixed it. The truth is: you don’t even know when it happens.

Salesforce just broke your site… or fixed it. The truth is: you don’t even know when it happens.

Salesforce just broke your site… or fixed it. The truth is: you don’t even know when it happens.

  • Jonatan Jumbert

  • 3 minute read

Let me tell you a story.

I was doing routine maintenance when I found a job in our production instance throwing errors.

At first, I thought it was our fault. Maybe a bug in our code.
But I remembered this same error from months ago.

Back then, I opened a case with Salesforce. Their answer?
“It’s not your code. It’s our platform. A bug in Elasticsearch.”

They gave us a temporary patch. And they said the permanent fix would come in release 25.9.

Now it’s September. So the question is simple: has Salesforce already deployed 25.9 to our production? If yes, that bug should be gone.

The problem: most people don’t know when deployments happen

Salesforce Core (CRM) is easy: three updates every year (Spring, Summer, Winter).

But B2C Commerce is a different game.

  • Monthly releases from January to October.

  • No releases in November or December. Black Friday and Christmas are too risky for big changes.

And here’s something most people ignore: deployment dates are not fixed in stone. They can shift by 1–2 weeks. Salesforce updates the official calendar as soon as there’s a change.

The release naming

The logic is simple: year + month.

  • 25.9 → September 2025 release.

  • 25.10 → October 2025 release.

  • 26.1 → January 2026 release.

The deployment process

This is how releases roll out:

  1. First, On Demand Sandboxes (ODS).

    • They are updated in the 2:00 AM – 7:00 AM window:

      • ODS-US → EST

      • ODS-AP → JST

      • ODS-EU → BST

  2. Then, production instances by region. This is what we call the major release.

    • Production deployments also happen in the 2:00 AM – 7:00 AM window, local POD time.

  3. If something goes wrong or a fix is needed, Salesforce pushes a minor release later.

That’s why sometimes you see a bug “magically” disappear, or a feature suddenly break after midnight.

Why this matters

If you don’t know the deployment calendar, you’re blind.

Maybe you’re waiting for Salesforce to fix a bug.
Maybe you suddenly get errors in production.
Or maybe you’re preparing a big launch, and the platform changes right under your feet.

Knowing the official dates means you’re ready.

Where to find the official schedules

Good news: Salesforce publishes them in advance. Not just for this year, but for the next one.

👉 B2C Commerce Deployment Schedule 2025
👉 B2C Commerce Deployment Schedule 2026

Yes, dates can move by 1–2 weeks. But Salesforce updates them quickly.

So do yourself a favor: save these links, check them regularly, and add the dates to your calendar.

Final thought

Salesforce B2C Commerce deployments are not “nice to know.” They’re critical.

You don’t want to:

  • Open tickets for bugs already fixed in the next release.

  • Miss the date when a permanent fix goes live.

  • Or get caught by surprise in production.

Releases are predictable if you pay attention.
The only question is: will you?

👉 Check the dates. Save the links. Be ready.