Saleor

A plugin architecture eventually ties a store to one language and one runtime. Saleor avoids that by making a GraphQL API the only way into the commerce backend, configuration and extension included.

Extensibility runs through webhooks, attributes, metadata, apps, subscription queries and dashboard iframes rather than in-process plugins. Apps deploy independently of the core, so upgrades stop colliding with extensions and custom logic can be scaled or debugged on its own. The tradeoff is acknowledged, since a solo developer running a low traffic shop may find a service oriented setup heavier than a traditional framework.

The commerce model itself covers the parts most catalogs need.

• Native multichannel: pricing, currencies, stock and product availability are controlled per channel.
• Product management: a rich content model aimed at large and complex catalogs.
• Orders: split payments, multi-warehouse fulfilment, returns and a flexible order model.
• Promotions: sales, vouchers, cart rules and gift cards in a single engine.
• Payment orchestration: multi-gateway support and an extensible payment API for any method.
• Translations and SEO: a fully translatable catalog with headless freedom over markup.

Version 3.x is the production line, with the dashboard and the storefront kept in their own repositories. Docker Compose instructions cover self-hosting, and Saleor Cloud offers developer accounts plus a CLI that bootstraps a storefront against your GraphQL endpoint.