Photo: free stock photography (Unsplash licence) — see imprint
They solve the same problem from different ends
JTL grew out of a merchandise-management system and its shop is strongest when JTL-Wawi runs your warehouse. OXID has deep roots in German mid-market B2B and a loyal agency network. Shopware started as a shop and has been building outward into apps, APIs and cloud. Which end you come from usually decides which one feels natural.
The ecosystem is the product
For any of these three, ask a duller question than 'which has feature X': who will still be maintaining my shop in 2031, and how many of them are there? Developer availability, plugin vendor health and agency choice are what you are really buying, and on that axis Shopware's momentum is currently the strongest of the three.
Where JTL genuinely wins
If JTL-Wawi already runs your warehouse, picking, shipping and returns, the shop that talks to it natively removes an entire integration project. That is a real, quantifiable saving and we would not pretend otherwise just because we prefer Shopware.
Where Shopware pulls ahead
The app system and API surface, the CMS, the headless story, and a developer pool that is simply Symfony developers rather than specialists in a niche. If you expect to build something unusual — a configurator, a portal, a second channel — that gap widens every year.
- JTL wins if JTL-Wawi already runs your warehouse.
- You are buying an ecosystem and a hiring pool, not a feature list.
- For unusual builds, Shopware's API surface pulls ahead.
Frequently asked questions
All three are credible, and where you come from usually decides. JTL grew out of merchandise management, OXID out of German mid-market B2B, Shopware out of the shop itself. Ask the duller question instead: who will still be maintaining this in 2031, how many of them are there, and how easily could you replace your agency? That is what you are actually buying.
Probably yes, and we say that as a Shopware agency. If JTL-Wawi already runs your warehouse, picking, shipping and returns, the shop that talks to it natively removes an entire integration project — a real, quantifiable saving. The counter-argument only starts when you need something unusual on the storefront that the Wawi coupling cannot reach.
In practice, yes — because a Shopware developer is largely a Symfony developer, and that hiring pool is wide. OXID and JTL work needs someone who knows that specific world, and there are fewer of them each year. If you plan to build something unusual — a configurator, a customer portal, a second channel — availability becomes a schedule risk long before it becomes a technical one.
Not from the roadmap slide. Count the agencies that would quote you, count the plugin vendors that shipped an update this quarter, and check whether hiring for it means finding a specialist or a mainstream developer. Then ask your current agency what happens if you leave them. One healthy vendor and three willing agencies is a risk, whatever the feature list says.
We do this for a living — Shopware, Node.js, React, ERP integration and automation for B2B.
Talk to an engineer