Saleor Setup: Day-Zero Path to a Working Ecommerce Loop

Set up Saleor for day-zero work — seats, one core loop, required integrations, and non-admin proof — before optional hubs.

By Lee M.Updated Aug 18, 20266 min readFact-checked

Quick answer

Set up Saleor in this order: qualify the plan you will actually buy, name one store owner, configure self-host or Cloud Select+, one payment integration, and a storefront you will actually ship, connect the payments and shipping you depend on, then have a non-admin run a developer can query the catalog and a test order completes on the composed front-end. Confirm marketplace channels (Open Source (self-host)+) and marketing automation (Open Source (self-host)+) are on the package you will actually buy. You’re done when that walkthrough works — not when every optional app is switched on.

Start on Open Source (self-host)
Name one store / ops owner
self-host or Cloud Select+, one payment integration, and a storefront you will actually ship
Connect required payments / shipping / channels
Prove a non-admin can run the loop

What matters in your Saleor setup

What Saleor actually is — Saleor is a headless, GraphQL-first open-source commerce platform. OSS self-host is free for production; Saleor Cloud Forever Free is non-commercial prototyping only — do not treat it as a merchant production free plan. Production Cloud (first-party 2026-08-18…
Configure these first — Research lists online storefront, product catalog, checkout payments, and order management as supported — that is your day-zero surface.
Do not treat it as every ecommerce job — Saleor is headless GraphQL open-source commerce. It is not a substitute for a theme-first SMB SaaS admin or Forever Free as production Cloud.
Prove with a real workflow — Worked example: Northline Labs (headless GraphQL storefront) is done when they can a developer can query the catalog and a test order completes on the composed front-end — not after a vendor tour.

Saleor day-zero path

Saleor setup walkthrough for headless GraphQL open-source commerce. — A working Saleor core loop beats a decorated empty workspace.

Saleor must vs nice

Must-have

Core job loop
Plan / hub gates
Integrations

Nice-to-have

AI extras

1. Qualify plan and packaging

Researched plans: Open Source (self-host), Cloud Select, Cloud Volume, Cloud Enterprise. Never invent list prices here — confirm plans, processing, and quote terms on /pricing/saleor/. Worked example: Northline Labs (headless GraphQL storefront) lists everyone who must log in weekly before they invite “the whole company.”

2. Configure one core loop

Configure self-host or Cloud Select+, one payment integration, and a storefront you will actually ship. Research-supported surfaces include online storefront, product catalog, checkout payments, and order management. Worked example: Northline Labs (headless GraphQL storefront) refuses optional modules until a developer can query the catalog and a test order completes on the composed front-end.

3. Non-admin proof

Our snapshot records no trial length for Saleor, so Open Source (self-host) is your proving ground. Success: a developer can query the catalog and a test order completes on the composed front-end. Worked example: Northline Labs (headless GraphQL storefront) records a 10-minute loom of the walkthrough for stakeholders who skip hands-on time.

Saleor checklist

Bring these questions to every demo

Ask vendors to show the workflow live, not just describe it.

1Name a store / ops ownerCatalog, users, and hygiene need a responsible party.
2Configure one core loopself-host or Cloud Select+, one payment integration, and a storefront you will actually ship
3Complete non-admin proofa developer can query the catalog and a test order completes on the composed front-end

4. Connect the integrations Saleor must have on day one

Native connector
Prefer OAuth paths IT can audit.
API / webhook
Name an owner when the sync breaks.
Manual export
Accept only for low-volume, low-risk data.

Research lists Stripe, PayPal, and Zapier for Saleor. Confirm which are native vs API before go-live.

Pick one identity or SSO path if required.
Connect one operational integration the weekly users touch daily.
Document anything left as manual export.

Worked example: Teams building headless GraphQL storefronts connects the one integration that prevents double entry before inviting the full team.

5. Train weekly users — not a one-time all-hands

Train the people who must open Saleor every week. Cover: login, the core loop (online storefront, product catalog, and checkout payments), and where to log blockers.

Worked example: Teams building headless GraphQL storefronts runs a 30-minute working session on live data and includes one sceptic who will actually use the tool.

6. Write the setup note stakeholders can audit

Document plan tier, admin owner, integrations live, and the non-admin proof (online storefront, product catalog, and checkout payments). Link to /pricing/saleor/ for commercial detail.

Worked example: Teams building headless GraphQL storefronts stores a one-page note finance and IT can read without joining another demo.

7. Connect the integrations Saleor must have on day one

Native connector
Prefer OAuth paths IT can audit.
API / webhook
Name an owner when the sync breaks.
Manual export
Accept only for low-volume, low-risk data.