Gadero sells more than 20,000 timber products — decking boards, garden sheds, fully configurable log cabins — across four countries, each with its own languages, taxes, and pricing. It runs on commercetools. Lavazza Netherlands, where 90% of transactions are B2B coffee orders wired into an ERP, runs on BigCommerce, a SaaS platform in the same family as Shopify Plus. Both choices were right, and for the same reason: the platform followed the operating model, not the other way around.
We build on commercetools and on SaaS suites like Shopify Plus and BigCommerce, so we have no license revenue riding on this comparison. What follows is the set of questions we actually work through with clients before anyone signs anything.
Two different bets
Shopify Plus is a bet that your commerce needs are close enough to everyone else’s that a shared, opinionated platform — storefront, checkout, admin, app ecosystem — gets you to market faster and cheaper than anything you could build. For most B2C brands, that bet pays off.
commercetools is a bet in the opposite direction: that your catalog, pricing, or channel model is unusual enough that owning the commerce logic is worth running an engineering effort. It gives you APIs — products, carts, orders, prices, promotions — and deliberately no storefront. Every screen your customer sees, you (or your partner) build and operate.
Neither bet is “more modern.” The question is which one matches how your business actually works.
Where Shopify Plus genuinely wins
Be honest about this list first, because if you’re on it, you can stop reading and save a lot of money:
- Standard B2C selling. Products with a handful of options, list prices, discount campaigns, one checkout flow. Shopify’s defaults encode years of conversion optimization you’d otherwise have to rediscover.
- Speed and team size. A Shopify Plus store launches with a small team and an agency; the platform handles hosting, PCI scope, checkout uptime, and upgrades. commercetools launches are engineering projects measured in months, not weeks.
- Marketing-led operations. Theme editing, campaign apps, and a mature admin mean merchandisers ship changes without a deploy pipeline.
- Moderate B2B. Shopify’s B2B features — company profiles, price lists, payment terms, quantity rules — now cover straightforward wholesale (“same catalog, negotiated prices, invoice payment”) well.
The traditional objections have also weakened. Checkout is extensible through Checkout Extensions and Shopify Functions rather than locked, and recent product-model updates lifted the long-standing 100-variant ceiling. Don’t choose commercetools because of a limitation blog post from 2021.
Where commercetools earns its complexity
The cases where we recommend commercetools share a pattern: the commerce logic is the business’s competitive behavior, and it doesn’t fit a template.
- Deep or structural catalogs. Product types with typed attributes model things like Gadero’s configurable log cabins or technical B2B assortments cleanly. When EKI needed customers to configure rubber and foam products dimension-by-dimension with live price calculation, the answer was custom logic no product template ships with.
- Layered pricing. Different prices per channel, customer group, country, and currency, selected by rule at request time — plus tiered volume pricing. If your price list is an ERP export with thousands of rows per customer, this is your daily reality.
- Serious B2B structure. Business units with nested companies, buyer roles and permissions, quote negotiation flows, order approval rules. GOED sells 120,000 healthcare products to both consumers and healthcare professionals, with insurance authentication in the flow — that is not a theme customization.
- Many touchpoints, one backend. Web, apps, marketplaces, in-store systems, vending — all consuming the same cart and pricing APIs. You integrate at the API level (synchronous API extensions for validation, event subscriptions for everything downstream) instead of through an app store.
- Owning the roadmap. No platform release cycle gates your features. That cuts both ways: nothing ships unless your team ships it.
The team question nobody prices in
License fees are the visible cost; the structural cost is organizational. commercetools requires a standing engineering capability — in-house, a partner like us, or both — for as long as the platform lives. Storefront, integrations, and operations are yours. Shopify Plus requires the opposite discipline: accepting the platform’s opinions, and solving edge cases with apps or Functions rather than rewrites.
A rough sanity check we use: if you can’t name who will own the platform’s code in year three, don’t choose commercetools. If your last three growth initiatives died waiting for platform workarounds, don’t stay on a template.
On fees themselves: Shopify Plus is a subscription plus payment-related costs; commercetools licenses are enterprise agreements that typically scale with usage. Both change their terms often enough that anything more specific here would be stale — model your own three-year numbers with current quotes, and include the engineering line for both options honestly.
A short rubric
Choose Shopify Plus when:
- B2C or straightforward wholesale, catalog fits option-based modeling
- Time-to-market beats differentiation in commerce logic
- No standing engineering team — and no desire to fund one
Choose commercetools when:
- Pricing, catalog, or B2B structure is genuinely non-standard
- Multiple channels or brands must share one commerce backend
- Deep ERP/PIM/OMS integration is the core of the work
- You have (or will fund) engineering ownership for years
If you’re mid-table — complex catalog but thin team, say — the honest answer is usually Shopify Plus now with clean data discipline, and a migration later if growth forces it. Platforms are more replaceable than they used to be; data models are not.
If the answer means replatforming
Whichever direction you land, don’t plan a big-bang cutover from whatever you run today. We’ve written up the phased approach we used at Gadero and GOED — see commercetools migration with the strangler fig approach, and the commerce platform engineering work it belongs to. If you want the comparison run against your actual catalog and org chart rather than in the abstract, that’s a conversation we do regularly.
