Before addressing limits, Shopify is an excellent choice for most standard applications.
For a B2C retailer up to roughly two to three million euros of annual revenue in a European single-market setup with a simple pricing model, there are rarely economically better alternatives.
The reasons Shopify eventually becomes constrained are surprisingly consistent.
First: PSD2-compliant payment flows with installment options. Klarna, Mollie, and other providers offer Shopify apps, but deeply integrated control (installment terms dependent on cart value, prioritization of payment methods by margin, bespoke fraud-scoring overlays) approaches the boundaries of app APIs. In a headless architecture, the checkout itself is programmable.
Second: B2B requirements. Net-price display, customer-specific price lists, multi-tier volume pricing, customs and surcharge disclosure for cross-border orders. Shopify Plus B2B has made progress; for European mid-market with individual framework contracts, the model often remains too generic.
Third: Regulatory checkout obligations. European jurisdictions impose specific requirements on the order process: right of withdrawal per Consumer Rights Directive, mandatory disclosures for e-commerce under country-specific civil-code provisions, the order-button conformity (e.g. §312j German BGB, Article L221-14 French Code de la Consommation), legally binding terms-and-conditions inclusion. Standard Shopify meets the obligations in principle, but specific industries (pharmaceuticals, food with declaration requirements, medical devices, age-verified products) need divergent flows, and the correct handling of the right of withdrawal for digital content presents Shopify templates with trade-offs.
Fourth: Deep integration into existing systems. ERP connectivity with real-time inventory sync, customer-specific assortments based on account membership, integrated CRM data flows. Shopify Plus supports these, but the cost of deep integration often exceeds the cost of a bespoke headless build.
Headless commerce separates the storefront (what the customer sees) from the commerce engine (products, orders, payments, inventory). The storefront communicates with the engine over APIs and can be designed freely.
Commerce engines in the European market:
Storefront frameworks:
The Next.js + Medusa combination is currently the most frequently deployed stack in European projects — good documentation, reasonable learning curve, economically tractable.
A realistic timeline for a Shopify-to-headless migration:
That is six months of concentrated effort for a mid-size store. Shorter timelines are feasible only with material quality trade-offs.
Shopify Plus fees vary with GMV, typically in the low four figures per month. App subscriptions and transaction-linked payment fees accrue on top.
A headless setup has a higher initial investment (development over six months), then markedly lower recurring cost (hosting, occasionally commerce-layer licensing). Break-even typically sits in year two of productive operation.
Economically, migration makes sense at the point where you plan at least three years of horizon and at least one of the four triggers applies.
We work both on Shopify (for classical B2C retailers who want to stay inside the platform) and on headless stacks — primarily Next.js + Medusa — as part of our e-commerce services. The decision emerges in the complimentary online scoping session — outcome-open, not biased to the vendor's default preference. Delivery interlocks with our software development and UI/UX design practices.
Work contracts with fixed price per sprint. Source code and infrastructure access at the customer. Working-language project management. GDPR-aligned architecture with EU-region hosting. Fifteen days of free post-delivery bug-fixing after each acceptance.
If you are currently weighing stay-on-Shopify versus a headless migration, do not start with "which platform is better". Start with "which concrete problems are we not solving today that will cost more in two years". A structured scoping session sorts that question in two hours. For the contractual structure of a platform migration, the fixed-price versus time-and-material framework offers useful grounding — migrations benefit particularly from a clearly bounded sprint-package model.
Sometimes yes. Shopify Plus materially expands configurability and can make sense for twelve to twenty-four months while you assess whether a real headless migration is necessary. Plus fees are not the obstacle if they secure the time to migrate.
Fundamentally yes, via a strangler pattern: pieces of the store move to the new architecture, the rest stays on Shopify initially. This is more demanding in parallel operation, but lowers big-bang risk.
Stripe, Mollie, Klarna, and PayPal collectively cover roughly ninety percent of relevant payment methods in the European market — card, direct debit, instant transfer, invoice purchase, installment. Combining two or three providers is the economical midpoint between coverage and complexity.
For the initial migration, two to four engineers plus project management plus design. For steady-state operation, often half an engineer plus external support for special requirements.
With clean migration (redirect mapping, structured-data preservation, performance improvement), typically yes. A short ranking dip is normal; recovery typically completes within six to twelve weeks. Without clean migration, a longer-lasting drop threatens — which is why SEO migration belongs in every headless transition as a mandatory work package.