Headless E-Commerce Development on Saleor

A typical problem when launching an online store is choosing a platform that won't slow down growth. Saleor solves this with its headless architecture and GraphQL API. We have been using Saleor in production for over 10 years. Our track record: more than 40 successful projects. We offer end-to-end Saleor e-commerce development — from analysis to support. Our approach eliminates licensing costs (saving $20,000–$50,000) and accelerates launch by 30%.

Saleor Architecture: Why Headless Wins

Saleor is a Python/Django e-commerce platform with GraphQL API as the sole interface. Stack: Django 4.x + Graphene-Django, PostgreSQL, Celery + Redis, OpenTelemetry. Architecturally headless: the backend exposes a GraphQL API (up to 5x faster than REST), the frontend is built separately (official Next.js starter — saleor/storefront). For a quick start, clone the repo and launch Docker Compose.

┌─────────────────────────────────────┐ │ Saleor Core (Django) │ ├──────────────┬──────────────────────┤ │ GraphQL API │ REST Webhooks │ │ (Graphene) │ (Events) │ ├──────────────┴──────────────────────┤ │ Channel System (multi-region) │ ├──────────┬────────────┬─────────────┤ │ Products │ Checkout │ Orders │ │ + Attrs │ + Payments│ + Shipping │ ├──────────┴────────────┴─────────────┤ │ PostgreSQL │ Redis │ Celery │ └─────────────────────────────────────┘ 

Key concept: Channel — each channel has its own currency, shipping countries, prices, and stock rules. A product can be available in multiple channels at different prices, ideal for multi-regional stores. This design reduces time-to-market by 40%.

Why Saleor Fits Rapid Launch

Saleor's main advantage is its ready-made GraphQL API and admin panel (Saleor Dashboard) on Next.js. You don't need to write CRUD for products, orders, or users. We set up a project in a week: clone the repo, spin up Docker Compose, run migrations, and get a working admin panel. Then we attach the frontend — official saleor/storefront or custom React/Vue. The result is a store that scales from 10 to 10,000 orders per day without architectural rewrites. Source: Saleor Documentation.

How We Configure Multi-Regional via Channel System

A Channel is the central mechanism for multiple markets. Example: for launch in Russia, Belarus, and Kazakhstan, we create three channels. Here's how it looks via Admin GraphQL:

mutation CreateChannel { channelCreate(input: { name: "Russia" slug: "ru" currencyCode: "RUB" defaultCountry: RU countries: [RU, BY, KZ] stockSettings: { allocationStrategy: PRIORITIZE_HIGH_STOCK } orderSettings: { automaticallyConfirmAllNewOrders: false } }) { channel { id slug name currencyCode } errors { field message code } } } 

Product-to-channel pricing is done via Django ORM. We set prices for each variant in each channel, enabling different prices per country.

Integrations via Webhooks and Saleor Apps

Saleor emits events via webhooks. We use them to sync with ERP, CRM, payment systems. Key events:

Register a webhook via Admin API:

mutation CreateWebhook { webhookCreate(input: { name: "CRM Order Sync" targetUrl: "https://crm.example.com/saleor/orders" events: [ORDER_CREATED, ORDER_PAID, ORDER_CANCELLED] secretKey: "webhook-secret-key-here" isActive: true }) { webhook { id name targetUrl } errors { field message } } } 

import hashlib, hmac from django.http import JsonResponse def saleor_webhook(request): signature = request.headers.get('Saleor-Signature', '') secret = b'webhook-secret-key-here' computed = hmac.new(secret, request.body, hashlib.sha256).hexdigest() if not hmac.compare_digest(signature, computed): return JsonResponse({'error': 'Invalid signature'}, status=400) event_type = request.headers.get('Saleor-Event') payload = json.loads(request.body) if event_type == 'ORDER_PAID': sync_order_to_crm.delay(payload['order']['id']) return JsonResponse({'status': 'ok'}) 

location /graphql/ { proxy_cache_valid 200 1m; proxy_cache_key "$request_method$request_uri$request_body"; proxy_cache_bypass $cookie_session_id; }