A single number: how many Salesforce Commerce Cloud integrations are running on already-EOL or soon-to-EOL API versions. If it is anything other than zero, you have a clock running.
At a glance
The headline count of Salesforce Commerce Cloud (SFCC, formerly Demandware) integrations that are on an API version Salesforce has already retired, or is about to retire. It is the executive-dashboard rollup of the detailed API Version Status table, distilled to the one number a CTO or finance lead needs: how many things are about to break. The alert fires on anything above zero, because in SFCC an EOL is a hard cutoff, not a slow fade.
| What it counts | The number of connected integrations / API consumers whose current OCAPI or SCAPI version is past EOL, or inside the soon-EOL window. One integration, one count. |
| Why it matters | Salesforce deprecates roughly two OCAPI versions per year and stops serving them at EOL. Any integration left on a retired version stops working outright. This single number tells you whether you have outstanding technical risk that converts directly into downtime and lost revenue. |
| Reading the value | Zero is the only good value. Any positive number is a backlog of integrations that will break, ordered by urgency in the companion API Version Status card. A rising number over time means deprecations are outpacing your migration cadence. |
| What counts as “EOL-soon” | Versions inside the deprecation runway window where action is needed now to ship before the cutoff. The detailed per-integration runway lives in API Version Status. |
| OCAPI vs SCAPI | OCAPI integrations are the usual contributors, because OCAPI is on the version-deprecation treadmill. SCAPI consumers rarely appear here, SCAPI is the modern long-term surface without the same fixed retirement cadence. |
| Business impact | Each counted integration maps to a concrete failure mode: a dark storefront, a stalled OMS export, an inventory sync that stops, a broken Marketing Cloud feed. The count is a proxy for revenue and customer-experience exposure. |
| Unit | number (count of integrations) |
| Time window | Real-time (RT), the current state of every integration’s version |
| Alert trigger | >0, surfaced via sentiment_key: scc_deprecated_integration_count |
| Sentiment key | scc_deprecated_integration_count |
| Roles | owner, engineering, finance |
Calculation
Calculated automatically from your Salesforce Commerce Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
The same enterprise retailer as the API Version Status card: a single SFCC B2C realm, four storefront sites, a headless PWA Kit sub-brand, and three back-office integrations. Snapshot taken 12 Mar 26.| Integration | API surface | Version | Days until EOL | Counts here? |
|---|---|---|---|---|
| Inventory sync (3PL) | OCAPI | v20.x | -31 | Yes (past EOL) |
| Legacy storefront (RefArch-US) | OCAPI | v21.x | 49 | Yes (EOL-soon) |
| Legacy storefront (RefArch-UK) | OCAPI | v21.x | 49 | Yes (EOL-soon) |
| OMS order export job | OCAPI | v22.x | 217 | No (long runway) |
| Marketing Cloud connector | OCAPI | v23.x | 373 | No (long runway) |
| Headless sub-brand (PWA Kit) | SCAPI | current | n/a | No (SCAPI) |
| Integrations on EOL’d / EOL-Soon Versions | 3 |
- The headline number is 3, and that is a paging-worthy state. The alert fires at anything above zero. Three integrations on the danger list means three concrete failure modes are queued: a stalled inventory feed and two dark storefronts. A board-level audience does not need the version strings, they need this one number trending to zero.
- One of the three is already past EOL (the 3PL inventory sync at -31 days). A single past-EOL integration is arguably worse than two EOL-soon ones, because it has no runway left at all. The count treats them equally, so always drill into API Version Status to triage by severity.
- Long-runway and SCAPI integrations correctly do not inflate the number. The OMS job (217 days), Marketing Cloud connector (373 days), and the SCAPI sub-brand are healthy today and excluded. This keeps the count honest, it measures present risk, not future planning items.
- Watch the trend, not just the snapshot. If this number sat at 1 last quarter and is 3 now, deprecations are arriving faster than migrations are shipping. That is the signal to fund a dedicated upgrade sprint rather than absorbing version bumps into business-as-usual.
Sibling cards merchants should reference together
| Card | Why pair it with Integrations on EOL’d / EOL-Soon Versions |
|---|---|
| API Version Status (OCAPI / SCAPI) | The detailed breakdown behind this single number. Always drill here to triage which integration to fix first. |
| OCAPI / SCAPI Failure Rate Spike or Version EOL Imminent | The acute alarm. When one of the counted integrations actually starts failing, that card pages the on-call. |
| OCAPI vs SCAPI Usage Mix | A high OCAPI mix is the leading indicator of a future-rising count. Drives the strategic migration conversation. |
| Orders Awaiting Downstream Sync >24h | The downstream symptom when a counted OMS or CRM integration finally breaks. |
| Revenue at Risk (live) | Converts the count into a money figure, useful for justifying the migration budget. |
Reconciling against Salesforce Commerce Cloud
Where to look in Business Manager: SFCC’s admin tool is Business Manager, at a per-realm URL likehttps://<realm>.business.demandware.net. There is no single Business Manager report that says “you have three integrations on dying versions”, which is exactly why this rollup exists. To reconstruct the number by hand you would:
- Open Administration, Site Development, Open Commerce API Settings and read the
versionin each Shop / Data API client config. - Cross-reference every version against Salesforce’s published OCAPI deprecation schedule in the B2C Commerce release notes.
- Add the SCAPI consumers configured in Account Manager, which Business Manager does not list, and check whether any have been flagged for change.
- Count how many fall past or inside the EOL window.
| Reason | Direction of divergence |
|---|---|
| SCAPI consumers absent from BM. SCAPI clients live in Account Manager, so a Business-Manager-only audit undercounts your full API surface. | Manual BM tally lower than reality |
| Shared API clients. Several logical integrations can share one OCAPI client config; the card counts by observed consumer, which can differ from raw client rows. | Either direction |
| Schedule moves. Salesforce occasionally extends an EOL date. The card recomputes against the latest published calendar; a manual tally from an old schedule will not. | Card more current |
| Definition of “EOL-soon”. A manual count needs you to pick a window; the card applies a consistent runway threshold for every integration. | Either, depends on chosen window |
Known limitations / merchant FAQs
Why does the alert fire at greater than zero rather than at some higher threshold? Because in SFCC an EOL is a hard cutoff. There is no “a little bit broken”. One integration on a dead version is one storefront, feed, or job that will stop. The only safe steady state is zero, so any positive count is an exception worth surfacing. The count is 3 but one of them is already past EOL. Shouldn’t past-EOL be weighted more heavily? Conceptually yes, and that is exactly why this card is a rollup, not the whole story. The count treats every at-risk integration as one. Use API Version Status to see runway per integration and triage past-EOL rows first. What is the difference between “EOL’d” and “EOL-soon” in the count? EOL’d means the version’s support has already ended (a negative runway). EOL-soon means it is inside the action window where you need to ship a migration before the cutoff arrives. Both are counted here because both demand work now; the detailed card separates them by exact days remaining. Will SCAPI integrations ever show up in this count? Rarely. SCAPI is Salesforce’s modern long-term API and is not on OCAPI’s fixed deprecation treadmill. The overwhelming majority of contributors to this number are OCAPI integrations. Migrating an OCAPI integration to SCAPI is the durable way to remove it from this count for good. The number jumped from 1 to 4 overnight. What happened? Almost always one of two things: Salesforce published a new deprecation round that pulled several versions into the EOL-soon window simultaneously, or a previously-runway version crossed its date. Drill into the detailed card to see which versions moved, then check the published schedule for the deprecation announcement. Is this real-time? Yes. The count reflects the current configured version on every integration, recomputed against today’s date. There is no historical period to select, the time window isRT.
How do I get this number to zero?
Migrate each counted integration off its dying version, bumping OCAPI versions where a quick win exists and moving to SCAPI where it is the right strategic move. Prioritise past-EOL and storefront-facing integrations first. The number ticks down by one each time a migration ships and the integration starts calling a supported version.