Adobe Commerce 2.4.6 is out of standard support. Now what?

Two things ended on 11 August 2026 and they are not the same thing. Adobe Commerce 2.4.6 came to the end of its three-year standard support window. Adobe Commerce 2.4.5, which had already left standard support on 12 August 2025, came to the end of its extended support window on the same day. If you run 2.4.5 you are now in a security-only transitional period. If you run 2.4.6 you are in extended support, which Adobe’s lifecycle policy describes as "one year of additional support at no additional cost" covering "quality and security patches for the core application".

The dates below are from Adobe’s own release versions table and lifecycle policy page, both read on 20 August 2026. Adobe moves these, so check them again before you build a plan on them.

It is 1 June 2027, and it only bites if you are on Adobe Commerce Cloud. The lifecycle policy says that starting 1 June 2027 Adobe "will no longer maintain Cloud environments running unsupported Commerce versions and will be forced to take appropriate action", that this "includes suspending traffic to the affected infrastructure", and that "as a result, your ecommerce storefront will go offline". That is a hard consequence with a date on it, which is more than the 11 August milestone carries.

Line that up against the version table and the picture gets specific. A 2.4.5 store has isolated security fixes to 31 May 2027 and the enforcement date lands the very next day. A 2.4.6 store is inside extended support until 31 August 2027 and has security fixes to 31 May 2028, so the enforcement language should not reach it until its own window closes, but Adobe has not published a store-by-store reading of that and we would not plan a business on our interpretation of it. If you are on Cloud, get your own end date in writing from Adobe before you set a budget.

On-premise and self-managed Adobe Commerce stores have no traffic-suspension mechanism pointed at them. What they have instead is an unpatched core after the security window ends, which is a slower and more embarrassing problem.

The honest answer is that the date forces a decision and a budget line, not a migration. Every agency page published this spring implied otherwise, because a deadline is the cheapest sales trigger in this industry. Here is the split.

It does not force you to leave Adobe Commerce. Upgrading 2.4.6 to 2.4.9 keeps you supported until 31 May 2029 and is a smaller project than a replatform for most stores. It does not force you off Cloud. It does not invalidate your extensions overnight.

What it does force is that your extension vendors stop testing against 2.4.6, because they follow Adobe’s support matrix and not yours. That is the failure mode that reaches a distributor first: a payment extension or a tax connector ships a version that requires 2.4.8, you cannot take it, and a security patch you actually need arrives inside it. Nothing announces this. You find out at the point you need the patch.

The ERP integration is the long pole, not the storefront. If you are running Adobe Commerce in front of Acumatica, note that Acumatica’s own commerce connectors page names native connectors for Amazon, Shopify and BigCommerce, and describes Adobe Commerce as reachable "through supported integrations", which means a third-party product or a build. Whatever you decide about the storefront, that integration is the piece with the schedule risk and the piece nobody has a clean estimate for.

A twelve-month calendar that actually fits the dates, starting from today, 20 August 2026:

Most 2.4.6 stores, honestly. If Adobe Commerce is doing the job, if your customisation is contained, and if your complaint is the upgrade treadmill rather than a capability you cannot reach, then upgrade to 2.4.9, take the support window to 31 May 2029, and spend the money you saved on the ERP integration instead. Nobody in this market is paid to tell you that.

Stay and upgrade if your B2B behaviour is already built and working: contract pricingContract pricing is a price that applies to one customer or one group of customers rather than to everyone. In B2B it is normal for the same product to have a different price for every account on the book. resolving correctly per customer, quote to orderQuote to order is the process where a buyer asks for a price, a person or a system prepares a quote, and the accepted quote becomes an order. In much of B2B it is the normal way to buy, not an exception. running through the platform, punchoutPunchout is a way for a buyer to shop on a supplier’s website from inside their own procurement system. The buyer clicks out, builds a cart, and the cart is returned to their system as a requisition for approval. endpoints your buyers already point at. Rebuilding all of that to land on the same behaviour twelve months later is a lateral move with a project risk attached.

Leave if the reason has nothing to do with the date. The real reasons to leave Adobe Commerce are that your total cost is dominated by keeping the platform current rather than by selling, that you cannot find or keep the developers, or that a specific B2B mechanic your buyers need is a custom build on Adobe and product on something else. If one of those is true, the deadline is a useful budget trigger and not a reason.

We are not going to tell you which one you are from a page. That is what the diagnostic is for, and it asks about your pricing, your catalogue shape and your ERP rather than your version number.