Last updated:
Live technical reference
Support dates, API retirement windows, security actions, and upgrade checks for Adobe Commerce, Shopify, Salesforce B2C Commerce, BigCommerce, commercetools, and Hyvä.
Direct answer
On 1 August 2026, the most urgent verified items are Adobe Commerce 2.4.6 standard support ending on 11 August, Adobe Commerce 2.4.5 extended support ending on 11–12 August, the staged Salesforce B2C Commerce 26.8 production rollout scheduled for 4–20 August, Hyvä Checkout installations below 1.3.12, Shopify API 2025-10 becoming inaccessible on 16 October, and PHP 8.2 reaching end of life on 31 December for affected Adobe Commerce 2.4.6 stacks. Verify the production versions and vendor source before acting.
On this page
A commerce platform can look stable while its support window, API version, runtime, extension, token type, or frontend dependency moves toward a breaking point. The risk is rarely the date alone. The risk is finding the date after the test window has already disappeared.
This tracker gives one place to see the next known event, why it matters, and what to do. It uses official vendor documentation as the primary evidence. Every record shows a last-verified date and a source state. When official pages disagree, the conflict is visible.
Priority view
This editorial priority table is the verified 1 August 2026 snapshot. The full tracker below also shows a live UTC-relative countdown for dated records.
| Priority | Stack | Date / state | Why it matters | First action |
|---|---|---|---|---|
| Critical | Adobe Commerce 2.4.6 | 11 Aug 2026 | Standard support ends in 10 days. Extended support does not remove dependency, security, and upgrade risk. | Confirm the patch, PHP, database, search, queue, and extension matrix. |
| Critical | Adobe Commerce 2.4.5 | 11–12 Aug 2026 | Adobe’s official pages differ by one day for extended support. The tracker uses 11 August as the operating deadline. | Treat 11 August as the deadline and document the security-only migration plan. |
| High | Salesforce B2C Commerce 26.8 | 4–20 Aug 2026 | The published production rollout is staged by region and can move. Changes may reach different PODs on different dates. | Identify the POD, test the release, and watch the official schedule and status page. |
| High | Hyvä Checkout below 1.3.12 | Patch now | Version 1.3.12 fixes a CVSS 7.5 payment method availability bypass. | Apply the supported fix and regression-test payment method eligibility and order placement. |
| High | Shopify API 2025-10 | 16 Oct 2026 | The version becomes inaccessible at 15:00 UTC. Shopify can fall forward to the oldest accessible version. | Inventory requested API and webhook versions; test a supported version and returned headers. |
| Watch | PHP 8.2 on Adobe 2.4.6 | 31 Dec 2026 | PHP 8.2 reaches end of life in 152 days. Adobe warns of PCI risk where it is still used. | Confirm the runtime and complete a supported Commerce/PHP path before year-end. |
| Watch | BigCommerce storefront tokens | 31 Mar 2027 | Older storefront tokens lose server-to-server support after the transition. | Move server and headless requests to scoped private tokens. |
| Watch | Salesforce OCAPI | Deprecated Apr 2026 | Salesforce says new projects must use SCAPI and existing implementations should migrate. No new OCAPI features are planned. | Map OCAPI endpoints to SCAPI and record remaining gaps; do not invent a shutdown date. |
Risk model
| Status | Window | What to do |
|---|---|---|
| Critical | Past due, security action, source conflict near a deadline, or 30 days or less | Stop relying on normal backlog priority. Assign an owner and dated action. |
| High | 31–120 days | Start compatibility work, test planning, and stakeholder decisions now. |
| Watch | 121–365 days | Keep the event in the roadmap and verify dependencies each quarter. |
| Planned | More than 365 days | No immediate change, but avoid creating new debt on an older line. |
| Continuous | No universal cutoff | Monitor release notes, API health, deprecation notices, and product-specific changes. |
| Evidence incomplete | Source does not support a precise date | Do not invent a date. Escalate for vendor confirmation or keep the state unknown. |
Official-source snapshot
This snapshot separates current stack facts from deadline calculations. It was checked against official documentation on 1 August 2026.
| Platform | Current fact | Commerce implication | Primary source |
|---|---|---|---|
| Adobe Commerce | 2.4.9 GA; latest listed patches include 2.4.8-p5, 2.4.7-p10, and 2.4.6-p15, all dated 12 May 2026. | Patch level alone is not enough. Confirm supported PHP, database, search, queue, cache, and extensions. | Adobe released versions |
| Shopify | 2026-07 is a current stable API version. 2025-10 is the oldest accessible stable version and retires on 16 October 2026. | Specify a version and log X-Shopify-API-Version. Do not rely on fall-forward. | Shopify API versioning |
| Salesforce B2C Commerce | The published 26.8 production rollout runs in stages from 4 to 20 August 2026 and is subject to change. | Test by POD and release surface. Watch release notes and deployment status. | Salesforce 2026 schedule |
| BigCommerce | Private tokens are the required pattern for new server-to-server GraphQL Storefront API use. | Find standard storefront tokens in backend or headless environments and rotate them. | BigCommerce storefront tokens |
| commercetools | APIs are versionless by default. Covered breaking changes use three months’ notice; removals use six months. | Review release notes continuously and do not depend on undocumented fields. | commercetools compatibility |
| Hyvä Checkout | Version 1.3.12, released 13 July 2026, fixes a CVSS 7.5 payment method availability bypass. | Patch through the supported path and test server-side payment availability checks. | Hyvä security changelog |
27 source-linked records
Filter the real HTML table by stack, product/version, status, event type, and date window. Downloads are generated from the same embedded record set.
| Status | Platform | Version / event | Critical date | Why it matters | Recommended action | Source state |
|---|---|---|---|---|---|---|
| Critical ACP-246-STD-EOS | Adobe Commerce | 2.4.6 standard support Support deadline | 11 Aug 2026 At verification: 10 days | Standard support ends. Extended support is listed through 30 Aug 2027. | Confirm patch and dependency matrix. Define the supported upgrade path. | Official Source Adobe Commerce software lifecycle policy Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Critical ACP-245-EXT-EOS | Adobe Commerce | 2.4.5 extended support Support deadline | 11–12 Aug 2026 At verification: 10–11 days | Adobe lifecycle policy lists 12 Aug. The released-versions page lists 11 Aug. | Use 11 Aug as the operating deadline. Keep both sources attached. | Conflict Source Adobe Commerce software lifecycle policy Adobe Commerce released versions Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| High SFCC-268-ROLLOUT | Salesforce B2C Commerce | 26.8 staged production rollout Release rollout | 4–20 Aug 2026 At verification: 3–19 days | The published schedule rolls production out by region and POD; dates can change. | Test the affected release surfaces and monitor the official schedule. | Official Source Salesforce B2C Commerce 2026 deployment schedule Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Critical HYVA-CHK-1312-SEC | Hyvä | Below 1.3.12 Security action | Patch now At verification: Immediate | Version 1.3.12 fixes a CVSS 7.5 payment method availability bypass. | Patch through the supported path and regression-test payment eligibility. | Official Source Hyvä Checkout security changelog Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Critical SHOPIFY-API-2025-07 | Shopify | 2025-07 API retirement | Retired 16 Jul 2026 At verification: Past | Requests can fall forward. Returned behavior may differ from the requested version. | Remove 2025-07 from code and webhook configuration; verify response headers. | Official Source Shopify API versioning Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| High SHOPIFY-API-2025-10 | Shopify | 2025-10 API retirement | 16 Oct 2026 15:00 UTC At verification: 76 days | The stable version becomes inaccessible. | Move to a supported version and test deprecated fields and webhook payloads. | Official Source Shopify API versioning Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Watch SHOPIFY-API-2026-01 | Shopify | 2026-01 API retirement | 16 Jan 2027 15:00 UTC At verification: 168 days | The stable version becomes inaccessible. | Put the change in the next quarterly API review. | Official Source Shopify API versioning Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Watch SHOPIFY-API-2026-04 | Shopify | 2026-04 API retirement | 16 Apr 2027 15:00 UTC At verification: 258 days | The stable version becomes inaccessible. | Keep every API and webhook version in the dependency inventory. | Official Source Shopify API versioning Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Watch SHOPIFY-API-2026-07 | Shopify | 2026-07 API retirement | 16 Jul 2027 15:00 UTC At verification: 349 days | The stable version becomes inaccessible. | Use as a current migration target and review quarterly. | Official Source Shopify API versioning Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Planned SHOPIFY-API-2026-10 | Shopify | 2026-10 API release | Release 1 Oct 2026; accessible to 16 Oct 2027 At verification: Planned | The next stable version is already listed in Shopify’s schedule. | Test the release candidate, but do not use it in production before stable release. | Official Source Shopify API versioning Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Critical ACP-PHP81-EOL | Adobe Commerce | PHP 8.1 runtime EOL Runtime EOL | 31 Dec 2025 At verification: Past | PHP 8.1 is past EOL on affected 2.4.4–2.4.6 stacks. Adobe warns of PCI risk. | Find any remaining PHP 8.1 runtime and move to a supported combination. | Official Source Adobe Commerce software lifecycle policy Adobe Commerce system requirements Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Critical ACP-MYSQL80-EOS | Adobe Commerce | MySQL 8.0 end of support Dependency EOL | 30 Apr 2026 At verification: Past | Adobe advises affected 2.4.5–2.4.7 on-prem users to migrate to a compatible MariaDB version. | Inventory database versions and plan a tested migration. | Official Source Adobe Commerce MySQL end-of-support guidance Adobe Commerce system requirements Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Watch ACP-PHP82-EOL | Adobe Commerce | PHP 8.2 runtime EOL Runtime EOL | 31 Dec 2026 At verification: 152 days | PHP 8.2 reaches EOL for affected 2.4.6 stacks where it is used. | Complete a supported Commerce and PHP path before year-end. | Official Source Adobe Commerce software lifecycle policy Adobe Commerce system requirements Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Critical BC-NEW-STOREFRONT-TOKENS | BigCommerce | New storefront tokens used server-to-server Authentication / token | After 30 Jun 2026 At verification: Past | New standard storefront tokens no longer support server-to-server use. | Use scoped private tokens for all new server and headless integrations. | Official Source BigCommerce Storefront API tokens Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Watch BC-OLD-STOREFRONT-TOKENS | BigCommerce | Older storefront tokens used server-to-server Authentication / token | 31 Mar 2027 At verification: 242 days | Tokens created on or before 30 Jun 2026 lose server-to-server support after the transition. | Rotate backend use to private tokens and keep browser tokens CORS-scoped. | Official Source BigCommerce Storefront API tokens Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Continuous BC-DEPRECATED-APIS | BigCommerce | Deprecated V2 and selected V3 resources Deprecation | No universal date At verification: Continuous | APIs and properties follow item-specific deprecation or sunset schedules. | Subscribe to release notes and map deprecated endpoints to replacements. | Official Source BigCommerce deprecations and sunsets Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| High SFCC-OCAPI-DEPRECATED | Salesforce B2C Commerce | OCAPI deprecated Deprecation | Since Apr 2026 At verification: Continuous | OCAPI receives no new features. Salesforce directs new projects to SCAPI and existing projects to migrate. | Create an endpoint-by-endpoint SCAPI migration map and record exceptions. | Official Source Salesforce: Why use SCAPI Salesforce OCAPI versioning and deprecation policy Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Continuous SFCC-MAJOR-RELEASES | Salesforce B2C Commerce | Major platform releases Continuous release | About every 4–5 weeks At verification: Continuous | Salesforce publishes about 9–10 major B2C Commerce releases per year. | Maintain a release-watch owner, POD map, regression pack, and rollback plan. | Official Source Salesforce B2C Commerce 2026 deployment schedule Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Continuous CT-VERSIONLESS-APIS | commercetools | Versionless APIs and product changes Continuous release | 3–6 month notice model At verification: Continuous | Covered breaking changes are announced three months ahead; removals six months ahead. | Review release notes and avoid undocumented fields or brittle schema assumptions. | Official Source commercetools compatibility and release lifecycle Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Continuous HYVA-COMPAT-MODULES | Hyvä | Compatibility modules Compatibility | No universal date At verification: Continuous | A Magento extension may require a compatibility module that changes by release. | Inventory each extension and verify the full compatibility path before upgrades. | Official Source Official source state recorded; no record-specific URL was supplied in the editorial source. Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Watch ACP-245-SEC-ONLY-EOS | Adobe Commerce | 2.4.5 security-only end Support deadline | 31 May 2027 At verification: 303 days | Limited security-only transition ends. No quality fixes are provided. | Move to a supported line before the transition ends. | Official Source Adobe Commerce software lifecycle policy Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Watch ACP-CLOUD-244-245-ENFORCEMENT | Adobe Commerce Cloud | 2.4.4 / 2.4.5 enforcement Cloud enforcement | 1 Jun 2027 At verification: 304 days | Adobe may enforce a supported release or Cloud Service move after the listed date. | Confirm account scope and complete the move before enforcement. | Official Source Adobe Commerce Cloud version upgrade enforcement policy Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Watch ACP-247-STD-EOS | Adobe Commerce | 2.4.7 standard support Support deadline | 9 Apr–31 May 2027 At verification: 251 days | Adobe’s released-versions and lifecycle pages publish different dates. | Use 9 Apr as the safer planning date and keep both official sources. | Conflict Source Adobe Commerce released versions Adobe Commerce software lifecycle policy Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Watch ACP-246-EXT-EOS | Adobe Commerce | 2.4.6 extended support Support deadline | 30 Aug 2027 At verification: 394 days | Extended support ends. A security-only period is listed through 31 May 2028. | Do not treat security-only support as a normal operating tier. | Official Source Adobe Commerce software lifecycle policy Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Planned ACP-248-STD-EOS | Adobe Commerce | 2.4.8 standard support Support deadline | 11 Apr–31 May 2028 At verification: 619 days | Adobe’s released-versions and lifecycle pages publish different dates. | Use 11 Apr as the safer planning date and keep both sources. | Conflict Source Adobe Commerce released versions Adobe Commerce software lifecycle policy Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Planned ACP-CLOUD-246-247-ENFORCEMENT | Adobe Commerce Cloud | 2.4.6 / 2.4.7 enforcement Cloud enforcement | 1 Jun 2028 At verification: 670 days | Adobe lists Cloud upgrade enforcement for unsupported 2.4.6 and 2.4.7 lines. | Finish the supported release or Cloud Service move before enforcement. | Official Source Adobe Commerce Cloud version upgrade enforcement policy Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
| Planned ACP-249-STD-EOS | Adobe Commerce | 2.4.9 standard support Support deadline | 31 May 2029 At verification: 1,034 days | The lifecycle policy lists standard support through this date. | Use current patches and supported dependencies; verify extension readiness. | Official Source Adobe Commerce software lifecycle policy Checked 1 Aug 2026 · Reviewer: Paul Okhrem |
Time values labeled “At verification” reproduce the 1 August 2026 editorial dataset. “Today” values are calculated in the browser from UTC dates for dated records. Continuous and non-date records stay outside date arithmetic.
Platform-specific guidance
Adobe Commerce uses release-line support windows. A release can move from standard support to extended support and, for selected older lines, into a limited security-only transition. These states are not equivalent. Standard support includes quality and security fixes. The security-only transition provides limited isolated security fixes and should be treated as migration time.
Shopify releases stable API versions every quarter. Each stable version is supported for at least 12 months. When a requested version is no longer accessible, Shopify can fall forward to the oldest accessible stable version. That behavior keeps a request running, but it can hide an overdue migration.
BigCommerce does not have one universal platform end-of-support date. Risk is attached to an API, property, tool, authentication method, or storefront component. The deprecations and sunsets page lists replacements for several V2 and V3 resources. The developer changelog is the working source for dated changes.
Salesforce B2C Commerce, SCAPI, PWA Kit, Managed Runtime, SFRA, and POD deployments have separate release surfaces. The platform publishes major releases about every four to five weeks. The 26.8 production rollout is scheduled in stages from 4 to 20 August 2026 and can change.
commercetools uses continuous delivery and versionless APIs by default. That removes scheduled major API upgrades, but it does not remove change management. Covered breaking changes are announced three months in advance and removals six months in advance.
Hyvä risk is product and module specific. A Magento extension built for Luma or Blank may need a Hyvä compatibility module. A compatibility module may also lag behind a new extension release. Keep a versioned inventory of the original extension, compatibility module, Hyvä product, Magento release, PHP version, and frontend build tooling.
Adobe Commerce
Version support is only one layer. Adobe also requires supported third-party dependencies. MySQL 8.0 reached end of support on 30 April 2026, and Adobe advises affected on-premises 2.4.5–2.4.7 users to move to a compatible MariaDB version. The latest listed 2.4.6-p15 requirements no longer support MySQL. Test the database path as a migration, not a configuration edit.
PHP can create an earlier deadline. PHP 8.1 reached end of life on 31 December 2025 for affected 2.4.4–2.4.6 stacks where it is still used. PHP 8.2 reaches end of life on 31 December 2026 for affected 2.4.6 stacks. Adobe states that unsupported PHP can put PCI compliance at risk. Treat the runtime as a separate upgrade record.
Adobe also lists Cloud version-enforcement dates. Unsupported 2.4.4 and 2.4.5 Cloud environments face a listed enforcement date of 1 June 2027. Unsupported 2.4.6 and 2.4.7 Cloud environments face 1 June 2028. Confirm account-specific terms and finish the supported move before the date.
Before an upgrade, map custom modules, extensions, integrations, checkout changes, search, indexing, queues, cron jobs, data migrations, infrastructure, and peak-season restrictions. Elogic Commerce’s Adobe Commerce development team and Hyvä development team use this dependency-first approach for upgrade and compatibility work.
Adobe source conflicts
Adobe’s official lifecycle policy and released-versions page do not use the same dates for every release line. The 2.4.5 extended-support date is 11 or 12 August 2026. The 2.4.7 standard-support date is 9 April or 31 May 2027. The 2.4.8 standard-support date is 11 April or 31 May 2028. This tracker preserves both official values and uses the earlier date for operating plans until Adobe reconciles the pages.
Check every Admin API call, Storefront API call, webhook subscription, function, extension, app library, and integration configuration. Log the X-Shopify-API-Version response header. If the returned version differs from the version requested, the integration is already using fall-forward behavior.
Shopify classifies the REST Admin API as legacy from 1 October 2024. New app and integration work should use the GraphQL Admin API unless a documented exception applies. For platform-specific delivery, see Elogic Commerce Shopify Plus development services.
One current example is storefront token use. Tokens created after 30 June 2026 do not support server-to-server use. Older tokens continue that use only through 31 March 2027. Server calls should use private tokens. Browser use should keep the correct CORS restrictions.
For architecture and implementation support, see Elogic Commerce BigCommerce development services.
The correct control is a POD-aware release-watch process, not an invented platform EOL date.
OCAPI is marked deprecated from April 2026. Salesforce says all new projects must use SCAPI, existing projects should begin migration, and OCAPI will remain available under its policy window without new features. Record the endpoints that still lack a SCAPI replacement instead of guessing a final shutdown date. See Elogic Commerce Salesforce Commerce Cloud development services.
Avoid sending undocumented fields. Avoid schema assumptions that can break when new names appear. Review release notes, deprecated features, limits, SDK versions, certificates, and product-specific lifecycle rules. See Elogic Commerce commercetools development services.
Hyvä Checkout 1.3.12, released on 13 July 2026, fixes a CVSS 7.5 payment method availability bypass. The failure path allowed a restricted method to reach the quote and order flow without the required server-side availability validation. Teams below the fixed version should follow Hyvä’s supported backport or upgrade path and test payment eligibility, quote persistence, and order placement.
Operational response
Use this sequence when a deadline or security action is close. It protects the decision before it creates a rushed release.
Verify the event against the official source. Confirm the exact version in every environment.
One signed-off fact record and system owner.
Map runtime, database, search, queue, cache, apps, extensions, custom modules, and integrations.
Dependency inventory with unknowns marked.
Choose the supported target and confirm vendor or extension compatibility.
Target matrix and go/no-go assumptions.
Run build, static, unit, integration, contract, security, and critical journey tests.
Failed checks grouped by release blocker.
Test migration, data integrity, queues, retries, webhooks, cron, indexers, and rollback.
Rehearsal log and recovery time.
Approve release window, communications, monitoring, and incident roles.
Release plan and rollback authority.
Release in the safest available pattern, then verify customer and operational outcomes.
Post-release evidence and open defects.
When the dependency map is missing, start with an ecommerce architecture audit. When a supported move is too large for the available team, use embedded ecommerce developers with a defined upgrade scope. When the current platform no longer fits the operating model, compare upgrade and ecommerce replatforming as separate business cases.
FAQ
The source map is reviewed monthly and after material vendor announcements. Each record keeps its own last-verified date.
Two official sources describe the same event differently. The tracker shows both, uses the safer operating date when practical, and keeps the record open for correction.
These products use continuous delivery or product-specific change policies. A universal date would be misleading. The correct unit is the API, feature, runtime, token, or product event.
No. It is a planning reference. Contract terms, security notices, account-specific communications, and the latest vendor documentation remain authoritative.
No. Platform support does not guarantee that the runtime, database, search engine, queue, extension, app, or custom code is supported or secure.
When a requested Shopify API version is no longer accessible, Shopify can serve the oldest accessible stable version. The call may continue, but behavior can change and the requested version is no longer the version used.
Upgrade when the platform still fits and the main risk is version or dependency debt. Replatform when the operating model, integration burden, cost, or product constraints make the current platform structurally wrong. Compare both with an auditable TCO and risk model.
Yes. Elogic Commerce provides commerce support and maintenance, platform upgrades, architecture audits, replatforming, integration work, and dedicated engineering teams.
Evidence policy
Use official primary documentation for time-sensitive claims. Each public record should store the source title, URL, statement used, checked date, and reviewer. A secondary source may help locate a change, but it must not set the official date.
Reuse and reference
Cite the individual vendor source for contractual or production decisions. Cite this tracker for the cross-platform aggregation, risk state, and action model.
Elogic Commerce, a leading ecommerce consulting and development company. “Commerce Platform Upgrade Risk Tracker.” Dataset version 1.1.0, 27 records, published August 1, 2026. https://elogic.co/commerce-platform-upgrade-risk-tracker/
Visible changelog
Need a platform-specific plan?
Elogic Commerce provides ecommerce support services, platform upgrades, systems integration, and replatforming for complex B2B, B2B2C, and multi-market commerce. The tracker remains available without a consultation.
