Choosing PIM Software in 2026: What Changed, and How to Decide

Most “which PIM should we buy?” guides are lists of logos. The more useful question in 2026 is what has changed underneath them, because two of the platforms people reach for first, Akeneo and Pimcore, have both changed the terms on which they are offered.

If you are on Akeneo 7, the date that matters is 30 September 2026. Start with that section below.

What changed

Akeneo 7 reaches end of support on 30 September 2026. That covers the PaaS edition Akeneo calls Flexibility and on-premise installs. After that date, in Akeneo’s words, it will “no longer provide technical support nor bug/security patches for that version”. The Community Edition carries on separately, but it moved to calendar versioning in 2026: only the latest release is supported, and breaking changes can arrive in any release. Akeneo’s focus is its SaaS product.

Pimcore’s free edition now has a revenue cap. From Platform Version 2025.1, the Pimcore Community Edition moved from GPLv3 to the Pimcore Open Core License, which Pimcore describes as free for companies earning under €5 million a year, with commercial licensing above that. Version 2024.4 was the last GPLv3 release.

The practical effect: “free, open-source PIM” is a narrower category than it was two years ago. For many businesses the real choice is now between running the software yourself, with the upgrade work that implies, and paying for a SaaS product that does it for you.

If you are on Akeneo 7

You have three realistic routes, and staying where you are is not one of them for long. Running a system that holds your product data past the end of its security patches is a risk that grows every month.

1. Move to Akeneo’s SaaS product. The least disruptive for your team, because the model and the concepts carry over. Budget for the subscription and for re-testing every integration against the SaaS APIs.
2. Move to the latest Community Edition. Only viable if you were not relying on Enterprise features, and it means committing to keep up with a release line where only the newest version is supported. That is ongoing engineering, not a one-off upgrade.
3. Replatform. Worth considering if Akeneo was already a poor fit, but it is the most work: taxonomy, attributes, data and every integration move together.

Whichever route you take, the expensive part is rarely the PIM itself. It is the integrations: the storefront, the ERP, and any retailer or marketplace feeds that depend on the PIM’s output.

The kinds of PIM, and who each suits

There is no best PIM, only a best fit, and the deciding question is who will operate it day to day.

Your commerce platform, for now. If you sell through one storefront and the same product is not being maintained in several places, Shopify or Adobe Commerce can hold your product data perfectly well. Buying a PIM too early is a common and expensive mistake.

Self-hosted, open or open-core (Akeneo Community Edition, Pimcore). Control and extensibility, for a business with someone technical to own it. Read the licence against your revenue, and be honest about who will do the upgrades, because under both products’ current release models that work does not stop.

Lighter SaaS PIM. Often the right answer for a growing catalogue whose real problem is that product data lives in spreadsheets. Less to configure and nothing to host. Check that it has connectors for the platforms you actually use.

Enterprise PIM and PXM (Akeneo’s SaaS, Salsify). For large catalogues, many channels and teams, and, in Salsify’s case especially, brands whose problem is syndicating product content out to major retailers and marketplaces rather than managing it internally.

Syndication for Australian retail and grocery (SKUvantage). If you supply Australian retailers, much of the product data exchange runs through local syndication. It sits alongside a PIM rather than replacing it.

Five questions that decide it

1. How many places does the same product have to be correct? One storefront: probably no PIM yet. Four channels: almost certainly yes.
2. Is the problem internal management or distribution? Managing data inside the business points to a PIM; getting it to retailers points to syndication.
3. Who will run it every day? A merchandising team needs a product they can use without a developer. An in-house engineering team can take on more.
4. Who does the upgrades? With self-hosted products this is now a standing commitment. With SaaS it is the vendor’s job.
5. What does the licence cost at your size, and at the size you plan to be? Revenue-based thresholds change the answer as you grow.

Where we fit

We implement and integrate PIM platforms, model the taxonomy and attributes, clean the data on the way in, and connect it to Adobe Commerce, Shopify and the ERP. More on our PIM implementation work, and on what ERP integration actually costs, which is usually the bigger number.

---

Sources: Akeneo PIM product support dates, Akeneo PIM on endoflife.date, and Pimcore’s announcement of the POCL licence.