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.
We do this for a living — Shopware, Node.js, React, ERP integration and automation for B2B.
Talk to an engineer