GraphQL-native API as the single entry point
The frontend fetches exactly the fields it needs in one request, reducing traffic and speeding up product cards and catalog rendering.
eCommerce
Saleor is an open-source composable ecommerce platform with a GraphQL-native API. It separates the storefront and backend, so the frontend can be changed without rewriting the core, while business logic can be added alongside it through webhooks and apps.
Composable architecture and a single GraphQL endpoint eliminate over- and under-fetching: the frontend gets exactly the needed data in one request, and loose coupling provides replaceability without rewriting.
Industry solutions
Capabilities
The frontend fetches exactly the fields it needs in one request, reducing traffic and speeding up product cards and catalog rendering.
Storefront design and UX can change without a core release, so new promo pages and redesigns ship in days, not months.
One backend serves different countries and brands with separate prices and stock, so you can enter a new market without a separate installation.
Business logic lives in microservices alongside the platform, so core upgrades do not break customizations and support costs go down.
A TypeScript team gets autocomplete and type checking, reducing integration errors and speeding up developer onboarding.
Marketing launches promotions through the API and dashboard without involving development, enabling faster response to demand.
Adding local payment methods by market improves checkout conversion without rewriting checkout.
One platform version and auditable code provide portability and vendor independence when the project is handed over to another team.
Internal tools are embedded directly into the admin panel, so operators work in one window with fewer context switches.
Approach
We do not fork or patch the Saleor core. Saleor stays on the standard upgradeable version, while business logic is moved into separate microservices nearby, so platform updates do not break your custom work.
Where a mature international solution exists, we use it instead of inventing our own protocol or platform. Before writing code, we study how the problem is already solved in the industry.
The solution is loosely coupled and documented: it can be handed over between teams and contractors without rewriting. You are not tied to us.
AI compatibility
Saleor positions itself as the first fully open end-to-end AI-native commerce stack: from the agent entry point to the storefront and transactional core (saleor.io/blog/end-to-end-agentic-commerce).
Saleor was first to integrate OpenAI's ACP and Stripe, enabling direct sales through AI agents inside ChatGPT scenarios (saleor.io/cloud/agentic-commerce-protocol).
Through the Model Context Protocol, an AI client works with Saleor products, orders, and customers, letting an LLM agent read and update catalog data directly.
A self-documenting, strongly typed schema gives the agent an explicit contract for operations (checkoutCreate, checkoutComplete), reducing query generation errors.
160+ webhooks and subscriptions let you connect AI services (recommendations, antifraud, content) reactively, without changing the core.
News
deliveryOptionsCalculate replaces implicit shipping webhooks. Search has been redesigned (prefixes, operators, ranking); gift cards are paid via the Transaction API.
Saleor released Paper — a production-ready storefront with a mobile multi-step checkout. It includes an AGENTS.md with rules for AI tools (Cursor, Claude, Copilot).
Saleor shipped an official Adyen integration for international payment acceptance and refunds. It is implemented through the App model rather than a built-in core plugin.
An MCP server launched, giving LLMs access to store data (channels, orders, products, stock) over Streamable HTTP. Read-only, no mutations; Saleor 3.21+ and Saleor Cloud.
Projects
Contacts
Leave your current contact details and describe your task. We will come back with clarifying questions and a proposal for the next step.