Pimcore as an e-commerce system: the e-commerce framework and Coreshop

IMPORTANT LICENSE CHANGE AS OF PIMCORE 2025.1

With version 2025.1, Pimcore has replaced the GPLv3 license with the new Pimcore Open Core License (POCL). Version 2024.4 was the last GPLv3 version - new license and cost rules apply with immediate effect. A commercial license is mandatory for companies with an annual turnover of over €5 million. Existing GPLv3 installations will no longer be supported at the end of 2026. Pimcore is a product of Pimcore GmbH based in Salzburg. This article takes the current license model fully into account.

Introduction

Why Pimcore for medium-sized and enterprise companies?

For many companies in the DACH region, Pimcore is at the heart of their digitalization strategy - not despite, but because of its complexity. The platform combines product information management (PIM), digital asset management (DAM), content management and e-commerce in a standardized database architecture based on PHP and Symfony. For you as a decision-maker, this means that product data, media, prices and content exist once, are maintained once and are displayed consistently everywhere.

For companies with a structurally complex product catalog - many variants, multilingual markets, technical specifications, regulated content - this approach is strategically superior to a landscape of fragmented individual systems. However, the crucial question is not whether Pimcore is the right foundation, but which commerce architecture should be built on it.

The answer depends on four factors: Your growth objectives, available budget (one-off and ongoing), compliance requirements (GDPR, NIS2) and the desired level of independence from technology providers. This guide provides you with the basis for an informed decision.

License model

The new Pimcore license model: What decision-makers need to know now

With Pimcore Platform Version 2025.1, Pimcore has completed one of the most significant updates in its history: The Community Edition will no longer be released under the GPLv3 license, but under the new Pimcore Open Core License (POCL). This change has a direct impact on your investment and operational planning.

What has changed - and why

GPLv3 has long been regarded as a mark of quality for genuine open source software. In the enterprise context, however, it increasingly became a problem: license contamination risks (own extensions could unintentionally fall under GPLv3 obligations), complex legal audits and uncertainties in SaaS and PaaS operations slowed down acceptance among larger companies and their legal departments.

POCL solves these problems with a hybrid model: the source code remains publicly accessible and customizable ("source-available"), but the viral copyleft obligations of GPLv3 do not apply. Own extensions and business logic do not have to be disclosed - a decisive advantage for companies with proprietary processes.

partner-platinum

The three Pimcore editions at a glance

Edition

Community Edition

Professional Edition

Enterprise Edition

License

POCL (source-available)

POCL commercial

Costs

Free of charge up to € 5 million annual turnover

from € 8,400 / year

from € 25,200 / year

Target group

Startups, SMEs in the growth phase

Mid-market, companies with a turnover of over € 5 million

Enterprise, complex multi-channel setups

Need for action for existing installations:

Anyone currently running Pimcore ≤ 2024.4 under GPLv3 will receive security updates until the end of 2026 - after which support for these versions will end. A controlled migration path to POCL should be planned now, not under time pressure.

Positive for decision-makers:

POCL creates legal certainty. No license contamination, no obligation to disclose own extensions, clear compliance basis for NIS2 requirements. The Enterprise Edition also includes software insurance and clear IP ownership rights - an argument for internal legal and risk teams.

Consequential effect for the entire ecosystem:

As POCL is incompatible with GPLv3, all GPLv3-licensed Pimcore extensions must also be commercially relicensed in order to remain usable in a POCL environment (Pimcore ≥ 2025.1). This applies to well-known extensions such as CoreShop, which has also switched to an open core model with its own commercial license (CCL - CoreShop Commercial License). When planning the budget for new projects, these license costs must always be taken into account at the level of the extensions used - not just the Pimcore platform license itself.

Architectural model 1

The Pimcore e-commerce framework: Foundation for individual solutions

The native Pimcoree-commerce framework is the platform's original commerce layer. It provides abstract base classes for product catalogs, pricing, shopping cart abstraction and checkout frameworks - but deliberately does not provide a ready-made storefront, no order management backend and no out-of-the-box payment integration.

Decision criterion: When is the framework the right choice?

The native framework is primarily suitable for highly customized B2B applications that do not follow a standard store paradigm: Configurator solutions, project-based pricing or internal ordering systems. The framework can also be used in B2C commerce as a basis for ticketing or booking systems if a product catalog, a shopping cart and a project-specific ordering process outside of the standard are desired.

Strengths from a decision-maker's perspective

Maximum design freedom

No restrictive conventions. Data model, pricing logic and business processes can be fully modeled according to your own requirements.

No additional vendor

The framework is a direct Pimcore component - no external project roadmap, no dependency on third-party releases.

Minimal overhead

No unused feature ballast. Ideal as a lean backend for external commerce platforms or as an API product data layer.

Full data sovereignty

Self-hosted, EU-capable, GDPR-compliant. No data leaves your infrastructure without your explicit control.

Restriction:

The native framework is hardly being actively developed any more. For new projects with complete store requirements - shopping cart, checkout, order management, payment processing - it is not a complete solution. In these cases, CoreShop or a headless commerce layer are recommended.

Architectural model 2

CoreShop: The integrated store layer for Pimcore - now with a commercial license model

CoreShop is a stand-alone e-commerce framework that is based on the Pimcore framework and extends it into a fully-fledged store system. It delivers what the native framework only provides as a framework: ready-made order management, connection to payment gateways via the Payum abstraction library, shipping rules, tax zones, multi-currency capability and voucher systems - manageable directly from the Pimcore backend.

Important about the payment architecture: Payum is a payment abstraction library, not a payment service provider (PSP). The actual payment processing takes place via a connected payment gateway - such as Stripe, Mollie, Heidelpay or Unzer. The choice of PSP is free and project-specific; Payum merely standardizes the interface to these services.

"CoreShop offers the deepest native integration in Pimcore - product data, commerce logic and content in a single system, without synchronization effort."

The strategic argument for CoreShop

The decisive structural advantage lies in the native data architecture: CoreShop products are genuine Pimcore objects. There is no data copying, no synchronization between systems, no consistency risk. Product data, variants, prices and assets live once and are used consistently everywhere. This feature significantly reduces system complexity and therefore ongoing maintenance costs.

CoreShop is particularly well positioned for the DACH B2B market: Customer group prices, net/gross display, complex tax rules, individual conditions per customer and channel-specific catalogs can be configured granularly - without developer intervention for standard adjustments.

License costs and the vendor lock-in question

Due to Pimcore's switch to POCL, CoreShop also had to adapt its license model: GPLv3 and POCL are incompatible and may not be operated together in one environment. CoreShop has therefore also introduced an open core model with its own commercial license (CCL - CoreShop Commercial License), which is available via the Pimcore Store. For companies that use Pimcore Professional or Enterprise, the CCL is required for the productive use of CoreShop.

This raises the question: Is there a vendor lock-in here? The honest answer is: partly yes. The source code remains accessible and customizable, but the licensing commitment to the Pimcore ecosystem stack of platform (POCL) and extension (CCL) creates a real dependency on two licensors. A complete switch to another commerce platform would not technically force a data migration, but it would eliminate the native integration - and thus the essential added value of the combination. Compared to the previously free GPLv3 situation, this is a strategically relevant difference that must be taken into account in the architecture decision.

Coreshop-logo_200x100

Deepest Pimcore integration

Products as native Pimcore objects - no synchronization, no risk of data copying.

No transaction fees

Fixed license costs instead of revenue-based scaling - predictable even with strong growth.

B2B suitability

Customer groups, individual conditions, net/gross - B2B logic without custom development.

Double license requirement

As of Pimcore 2025.1, both the Pimcore platform license (POCL) and the CoreShop CCL are required - both subject to a fee.

Ecosystem dependency

Binding to two licensors (Pimcore + CoreShop) creates a structural dependency that must be taken into account when deciding on the architecture.

Storefront effort

No ready-made modern frontend. Requires Twig development or a separate headless frontend layer.

Recommendation: CoreShop is the right choice if ...

... your company operates in the DACH market, data sovereignty and GDPR control are non-negotiable, you cannot tolerate revenue-based license costs and the B2B share of your commerce model is high. The prerequisite is that the combination of Pimcore platform license and CoreShop CCL is accepted as a calculable, fixed cost factor - and that a development budget is available for the storefront.

Architectural model 3

Pimcore + SaaS/PaaS: Maximum commerce maturity, controlled data exchange

An increasingly widespread enterprise approach combines Pimcore as the central PIM/DAM master with a specialized SaaS or PaaS commerce platform - such as Shopware 6 (Cloud), BigCommerce, Commercetools or Salesforce Commerce Cloud. Pimcore handles product information management and asset management; the external store is responsible for all transactional commerce processes.

This approach corresponds to the composable commerce paradigm: clearly defined API boundaries, specialized systems for specialized tasks, no monolithic compromise. However, it brings with it an often underestimated complexity: content maintenance.

What SaaS/PaaS platforms offer that Pimcore-native approaches do not

Commerce-Innovation

BNPL, subscriptions, native checkout optimization - SaaS providers continuously invest without you bearing the costs.

Payment ecosystem

Ready-made payment gateway integrations, country-specific methods, PCI DSS compliance out-of-the-box.

Infrastructure

Auto-scaling, monitoring, security patches - the provider bears the operational burden, not your IT team.

The four strategic risks from a decision-maker's perspective

1. ongoing license costs scale with success. SaaS models with transaction or revenue-based rates become more expensive as business grows. A 5-year TCO calculation often shows that the initial price advantage over open source alternatives is lost after three to four years.

2. data synchronization creates operational complexity. Product data, prices, stock levels and category structures must be reliably synchronized between Pimcore and the commerce platform. Tools such as the Blackbit Data Director perform this task efficiently - but require initial setup and ongoing monitoring.

3. digital sovereignty is limited. US SaaS providers are subject to the CLOUD Act. For companies with sensitive customer data in the DACH region, a careful data protection impact assessment and, if necessary, an EU data processing agreement are mandatory - and not always sufficient.

4. the CMS gap is systematically underestimated. SaaS and PaaS commerce platforms generally only offer simple CMS functions - sufficient for product descriptions and landing pages, but not for complex storytelling, multi-level campaign structures, regulated content or multilingual editorial processes. If Pimcore is to be used as a CMS, either a separate CMS (e.g. Storyblok, Contentful) must be integrated into the stack - or a separate integration of the Pimcore CMS into the SaaS platform must be developed. Both mean additional integration effort and ongoing maintenance costs, which are often not included in project planning.

Pimcore-logo_200x100

Recommendation: Pimcore + SaaS/PaaS is suitable ...

... for companies with an international roll-out, fast time-to-market requirements and the will to purchase commerce innovation instead of developing it themselves. Prerequisite: The integration budget for PIM synchronization and CMS integration is fully calculated, the data protection issue has been clarified with legal certainty and the CMS requirements have been realistically assessed.

Architectural model 4

Pimcore + Vendure: Headless commerce with complete sovereignty

Vendure is a modern, TypeScript-based headless commerce framework (MIT license) based on Node.js, NestJS and GraphQL. In combination with Pimcore, it creates a fully open-source composable commerce architecture that combines enterprise commerce functionality with complete data sovereignty and no ongoing license costs.

Why Vendure as a strategic alternative to SaaS

Vendure delivers exactly what the native Pimcore framework does not: a complete API-first commerce engine with native GraphQL interface, order management, payment processing (Stripe, Mollie, Braintree and more via plugin), fulfillment logic and a modern admin UI. The plugin system based on NestJS allows the implementation of any business logic without framework conflicts - proprietary processes remain completely under your control.

For your company, this means: the flexibility and depth of a self-developed commerce backend, but on a proven, actively maintained open source foundation - without the effort of building a framework from scratch.

Vendure_logo

The architecture in the triad

Pimcore

PIM/DAM master. Product data, variants, assets, multilingual content - maintained once, consistent everywhere.

Vendure

Commerce engine. Shopping cart, checkout, payments, order status, fulfillment, customer accounts - API-first via GraphQL.

Front end

Decoupled storefront (Next.js, Nuxt, SvelteKit). Maximum performance through SSR, static generation and edge caching.

The cost argument for decision-makers

Pimcore + Vendure is the only fully open-source enterprise commerce stack with no ongoing platform license costs. No transaction fees. No revenue share. No scaling surprises as business grows. The total cost of ownership over 5 years is regularly below that of a SaaS platform for comparable commerce volumes - with the same or greater flexibility.

The trade-off: the initial investment in development and integration is higher than for a SaaS solution. Three systems need to be designed, integrated and operated. This requires an experienced commerce engineering partner and a clear operating strategy - based on a Kubernetes-based DevOps stack, for example.

Recommendation: Pimcore + Vendure is the right choice if ...

... you want to make a long-term investment in a scalable, sovereign commerce architecture, want to strategically avoid ongoing license costs, prioritize headless performance and maximum frontend freedom - and have a partner who is responsible for the operation of this stack. Particularly suitable for growing mid-market companies that do not want to risk an expensive platform migration in three to five years.

Next step

Platform choice or relaunch with new architecture? Let's make the right decision together.

Whether you want to introduce Pimcore, migrate an existing solution to POCL or convert a current store to a composable architecture - each of these decisions has strategic, technical and commercial dimensions that need to be carefully weighed up.

Blackbit supports medium-sized and enterprise companies in the DACH region in precisely these areas: from neutral architecture consulting and technology selection to implementation and ongoing operation on our Kubernetes-based DevOps stack.

Platform selection & architecture consulting Neutral evaluation of the four architecture models based on your specific requirements, your product catalog and your growth strategy - without product commitment.

Relaunch with architectural change

From inventory analysis and migration strategy to implementation: we support the transition from monolithic to composable architectures without interrupting operations.

POCL migration & license audit Code analysis, license risk assessment and migration path for existing Pimcore installations based on GPLv3 - before the end of support at the end of 2026.

Pimcore in e-commerce: Which architecture supports your growth?

A strategic technology comparison:

4

11

2025

DACH