README

Commerce that works with your language and stack



  GraphQL native, API-only platform for scalable composable commerce.





 Get to know Saleor: 
  Talk to a human
   | 
  Talk to the API





  Join our community: 
  Website
   | 
  Twitter
   | 
  Discord



   Blog
   | 
  Subscribe to newsletter





  
    
  
  
    
  
  
    
  
 
   
 


 Table of Contents

- What makes Saleor special?
- Why API-only Architecture?
- Features
- Installation
- Documentation
- Saleor Platform
- Storefront
- Dashboard
- Contributing
- License

 What makes Saleor special?

- Technology-agnostic - no monolithic plugin architecture or technology lock-in.

- GraphQL only - Not afterthought API design or fragmentation across different styles of API.

- Headless and API only - APIs are the only way to interact, configure, or extend the backend.

- Open source -  a single version of Saleor without feature fragmentation or commercial limitations.

- Cloud native - battle tested on global brands.

- Native-multichannel - Per channel control of pricing, currencies, stock, product, and more.

 Why API-only Architecture?

Saleor's API-first extensibility provides powerful tools for developers to extend backend using webhooks, attributes, metadata, apps, subscription queries, API extensions, dashboard iframes.

Compared to traditional plugin architectures (monoliths) it provides the following benefits:

- There is less downtime as apps are deployed independently.
- Reliability and performance - custom logic is separated from the core.
- Simplified upgrade paths - eliminates incompatibility conflicts between extensions.
- Technology-agnostic - works with any technology, stack, or language.
- Parallel development - easier to collaborate than with a monolithic core.
- Simplified debugging - easier to narrow down bugs in independent services.
- Scalability - extensions and apps can be scaled independently.

 What are the tradeoffs?

If you are a single developer working with a small business that doesn't have high traffic or a critical need for 24/7 availability, using a service-oriented approach might feel more complex compared to the traditional WordPress or Magento approach that provides a language-specific framework, runtime, database schema, aspect-oriented programming, and other tools to a quick start.

However, if you deploy on a daily basis, reliability and uptime is critical,
you need to collaborate with other developers, or you have non-trivial requirements you might be in the right place.

 Features

- Enterprise ready: Secure, scalable, and stable. Battle-tested by big brands
- Dashboard: User-friendly, fast, and productive. (Decoupled project repo )
- Global by design Multi-currency, multi-language, multi-warehouse, tutti multi!
- CMS: Manage product or marketing content.
- Product management: A rich content model for large and complex catalogs.
- Orders: Flexible order model, split payments, multi-warehouse, returns, and more.
- Customers: Order history and 

Top issues

Discussions

Latest release

What's Changed
 Fix product filters generating SQL that makes Postgres scan the catalogue by @wcislo-saleor in https://github.com/saleor/saleor/pull/19998


Full Changelog: https://github.com/saleor/saleor/compare/3.23.47...3.23.48