Saleor
saleor · Ecommerce
GitHub stars
23,398Stats updated
What is Saleor?
Saleor keeps commerce logic behind a GraphQL API so storefronts, dashboards, mobile clients, and other applications can use the same backend without inheriting a fixed presentation layer. Products, channels, inventory, checkout, promotions, orders, payments, and fulfillment form the core, with apps and webhooks handling integrations.
Saleor is a GraphQL-native, API-only platform for composable commerce. Its headless architecture lets developers configure and extend the commerce backend through APIs, webhooks, metadata, and apps.
Core capabilities
- Expose catalog, checkout, customer, order, payment, and shipping flows through GraphQL
- Configure per-channel products, pricing, currency, inventory, and availability
- Extend commerce behavior with apps, metadata, webhooks, and dashboard views
A commerce core presented through GraphQL
The API covers products, categories, collections, checkout, customers, orders, promotions, vouchers, payments, shipping, tax, and digital goods. Because the backend is API-only, teams can design the storefront and operator experiences independently while sharing the same rules and data.
- GraphQL
- headless
- checkout
- orders
Channels and apps provide the composition layer
Channels scope pricing, currency, availability, stock, and other market decisions for multiregion or multibrand use. Apps, metadata, asynchronous and synchronous webhooks, subscription payloads, API extensions, and dashboard iframes connect specialized services without folding every integration into the core.
- channels
- apps
- webhooks
- metadata
Where it fits
Use cases
- 01
Power a custom headless storefront
Build a web, mobile, or in-store customer experience against the GraphQL API while Saleor handles the underlying catalog, checkout, customer, order, promotion, payment, and fulfillment records.
- 02
Run commerce across regions or brands
Use channels to vary product availability, stock, pricing, currencies, shipping, and other market configuration while retaining one composable commerce backend.
- 03
Add a commerce integration as an app
Connect payment, tax, search, CMS, communication, analytics, or operational services through apps, webhooks, metadata, synchronous events, and dashboard extensions.