Craft Commerce is one of the best ecommerce solutions built on top of a CMS platform. It is powerful, flexible, and capable of handling everything from simple product catalogues to complex stores with bespoke pricing, subscription billing, and third-party integrations. But it shares a critical dependency with the underlying platform it runs on: the Craft CMS version.
When that underlying Craft installation falls out of date, the consequences for an ecommerce business can be immediate, expensive, and in some cases, not immediately obvious until something stops working.
The version dependency chain
Craft Commerce releases are tied to specific Craft CMS versions. Craft Commerce 4 requires Craft CMS 4. Craft Commerce 5 requires Craft CMS 5. You cannot run a current version of Craft Commerce on an outdated version of Craft CMS, and vice versa.
This means that when Craft CMS falls behind, Craft Commerce falls behind with it. And when Commerce falls behind, every plugin that extends Commerce (payment gateways, shipping integrations, tax plugins, subscription managers) also falls behind, because those plugins have their own version requirements.
What breaks first
Payment gateways are typically the first to cause visible problems. Stripe, PayPal, Braintree, and other payment providers update their APIs and deprecate old integrations on their own schedules. The Craft Commerce plugins that connect to these gateways need to be maintained and updated to keep pace with those API changes.
If your Craft Commerce installation is on an old version, the payment gateway plugin you depend on may no longer be maintained, may not support current versions of the payment provider's API, or may have known security issues that the provider has flagged as non-compliant. Payment providers will eventually disable old, non-compliant integrations.
When that happens, your checkout stops accepting payments. Every hour your checkout is down costs revenue.
Shipping and tax integrations
Shipping rate APIs and tax calculation services also update regularly. Integration plugins that are no longer maintained stop working when the underlying service makes API changes. Real-time shipping rate lookups can silently fail, falling back to defaults or showing errors at checkout. Tax calculations can become incorrect if the integration no longer accurately reflects current rates or rules.
The plugin cascade
Most Craft Commerce stores rely on more than just the base Commerce package. Custom discount logic, subscription billing, wholesale pricing, product configurators, review systems, and dozens of other features are typically handled by additional plugins. Each of those plugins has its own Craft and Commerce version requirements.
When an upgrade is deferred for long enough, the number of plugins that have moved ahead of the installed versions grows. Eventually, a single upgrade becomes a coordinated migration of the entire plugin ecosystem.
The cost of acting versus the cost of waiting
Upgrading a Craft Commerce store is a serious piece of work. It requires careful plugin auditing, compatibility testing, data migration checks, and thorough end-to-end testing of the entire purchase flow before anything goes live. Done properly, it takes time and costs money.
But a broken checkout costs money too, immediately and continuously. A payment gateway that stops working does not warn you in advance. It stops working, and until it is fixed, no orders go through.
The question is not whether an upgrade costs money. It is whether it costs less than the alternative.
If your Craft Commerce store is running on an outdated version of Craft CMS, or you are not certain what version it is on, get in touch and Karl will carry out a full audit of the installation and give you a clear picture of where things stand.