Next.js Saleor Commerce

[!TIP] Questions or issues? Check our Discord for help.

Why Paper?

Ship faster, customize everything. Paper is a new release—expect some rough edges—but every component is built with real-world e-commerce in mind. This is a foundation you can actually build on.

🛒 Checkout That Actually Works

The checkout is where most storefronts fall apart. Paper's doesn't.

• Multi-step, mobile-first — Each step is a focused form. No infinite scrolling on phones.
• Guest & authenticated — Seamless flow for everyone. Logged-in users get address book and saved preferences.
• International address forms — Country-aware fields that adapt (US states, UK postcodes, German formats).
• Connection resilience — Automatic retries with exponential backoff. Flaky networks? Handled.
• Componentized architecture — Swap steps, add steps, remove steps. It's your checkout.
• Multi-channel ready — Different currencies and shipping zones per channel.

🌍 Multi-Channel, Multi-Currency

One codebase, many storefronts. Channel-scoped routing means /us/products and /eu/products can serve different catalogs, prices, and shipping options—all from the same deployment.

📱 Product Pages Done Right

The hard parts are solved. Adapt the look, keep the logic.

• Multi-attribute variant selection — Color + Size + Material? Handled. Complex variant matrices just work.
• Dynamic pricing — Sale prices, variant-specific pricing, channel pricing—all reactive.
• Image gallery — Next.js Image optimization, proper aspect ratios, keyboard navigation.

♿ Accessibility Built In

Not an afterthought. Focus management on step transitions, keyboard navigation everywhere, semantic HTML, proper ARIA labels. Everyone deserves to shop.

🤖 AI-Ready Codebase

Built for front-end developers and AI agents. The codebase includes:

• AGENTS.md — Architecture overview and quick reference for AI assistants
• Skills system — Task-specific guides in .claude/skills/ for GraphQL workflows, component patterns, variant selection, and more
• Consistent patterns — Predictable structure that AI tools can navigate and modify confidently

Whether you're pair-programming with Cursor, Claude, or Copilot—the codebase is designed to help them help you.

⚡ Bleeding Edge Stack

• Next.js 16 with App Router and Server Components
• React 19 with the latest concurrent features
• TypeScript in strict mode—your IDE will thank you
• Tailwind CSS with design tokens (OKLCH colors, CSS variables)
• GraphQL Codegen for type-safe Saleor API calls

What's in the Box

Caching Architecture

Paper uses Cache Components (Partial Prerendering) for optimal performance—static shells load instantly while dynamic content streams in. Learn more in the Next.js documentation or see .claude/skills/caching-strategy/SKILL.md for project-specific implementation details.

The display-cached, checkout-live model ensures fast browsing with accurate checkout:

1
┌─────────────────────────────────────────────────────────────────────┐
2
│                         DATA FRESHNESS                              │
3
├─────────────────────────────────────────────────────────────────────┤
4
│                                                                     │
5
│   Product Pages          Cart / Checkout         Payment            │
6
│   ──────────────         ──────────────          ───────            │
7
│                                                                     │
8
│   ┌───────────┐         ┌───────────┐          ┌───────────┐       │
9
│   │  CACHED   │────────▶│   LIVE    │─────────▶│   LIVE    │       │
10
│   │  5 min    │  Add    │  Always   │   Pay    │  Always   │       │
11
│   └───────────┘  to     └───────────┘          └───────────┘       │
12
│                  Cart                                               │
13
│   Fast page loads        Real-time prices       Saleor validates    │
14
│                                                                     │
15
└─────────────────────────────────────────────────────────────────────┘

How It Works

Instant Updates with Webhooks

Configure Saleor webhooks to invalidate cache immediately when data changes:

1. Create webhook in Saleor Dashboard → Configuration → Webhooks
2. Point to https://your-store.com/api/revalidate
3. Subscribe to PRODUCT_UPDATED, CATEGORY_UPDATED, etc.
4. Set SALEOR_WEBHOOK_SECRET env var

Without webhooks? TTL handles it—cached data expires naturally after 5 minutes.

Why This Is Safe

• Saleor is the source of truth: checkoutLinesAdd calculates prices server-side
• Cart always fetches fresh: Users see current prices before checkout
• Payment validates: checkoutComplete uses real-time data

📚 Deep dive: See .claude/skills/caching-strategy/SKILL.md for the full architecture, Cache Components (PPR), webhook setup, and debugging guide.

Quick Start

1. Get a Saleor Backend

Option A: Free Saleor Cloud account (recommended)

Option B: Run locally with Docker

2. Clone & Configure

1
# Using Saleor CLI (recommended)
2
npm i -g @saleor/cli@latest
3
saleor storefront create --url https://{YOUR_INSTANCE}/graphql/
4

5
# Or manually
6
git clone https://github.com/saleor/storefront.git
7
cd storefront
8
cp .env.example .env
9
pnpm install

Edit .env with your Saleor instance details:

1
NEXT_PUBLIC_SALEOR_API_URL=https://your-instance.saleor.cloud/graphql/
2
NEXT_PUBLIC_DEFAULT_CHANNEL=default-channel  # Your Saleor channel slug

Finding your channel slug: In Saleor Dashboard → Configuration → Channels → copy the slug

3. Run

1
pnpm dev

Open localhost:3000. That's it.

Development

Commands

1
pnpm dev                    # Start dev server
2
pnpm build                  # Production build
3
pnpm run generate           # Regenerate GraphQL types (storefront)
4
pnpm run generate:checkout  # Regenerate GraphQL types (checkout)

Project Structure

1
src/
2
├── app/                    # Next.js App Router
3
│   ├── [channel]/          # Channel-scoped routes
4
│   └── checkout/           # Checkout pages
5
├── checkout/               # Checkout components & logic
6
├── graphql/                # GraphQL queries
7
├── gql/                    # Generated types (don't edit)
8
├── ui/components/          # UI components
9
│   ├── pdp/                # Product detail page
10
│   ├── plp/                # Product listing page
11
│   ├── cart/               # Cart drawer
12
│   └── ui/                 # Primitives (Button, Badge, etc.)
13
└── styles/brand.css        # Design tokens

For AI Agents

If you're working with AI coding assistants, point them to:

• AGENTS.md — Architecture, commands, gotchas
• .claude/skills/ — Task-specific guides (GraphQL, components, checkout, etc.)

Environment Variables

1
# Required
2
NEXT_PUBLIC_SALEOR_API_URL=https://your-instance.saleor.cloud/graphql/
3

4
# Optional
5
NEXT_PUBLIC_STOREFRONT_URL=   # For canonical URLs and OG images
6
REVALIDATE_SECRET=            # Manual cache invalidation
7
SALEOR_WEBHOOK_SECRET=        # Webhook HMAC verification
8
SALEOR_APP_TOKEN=             # For channels query

Payments

The checkout architecture supports Saleor payment apps like Adyen and Stripe. The heavy lifting is done—integrating your gateway requires minimal work compared to building from scratch.

Customization

Paper works as a reference implementation and as a starting point for your own storefront. Start here:

• Colors & typography → src/styles/brand.css
• Components → src/ui/components/
• Checkout flow → src/checkout/views/SaleorCheckout/

The design token system uses CSS custom properties—swap the entire color palette by editing a few lines.

Next Steps

Features planned for future development:

• Filtering logic iteration. Fetching attributes from API for dynamic product filters.
• Customer Profile. Implementing new Past Orders and Address Book for signed-in customers.
• Paper App. Iteration on the revalidation logic and supported webhooks, providing a Preview in storefront feature in Saleor Dashboard.
• Opinionated model for standard content. Moving currently hardcoded stuff like Credibility or Free checkout information to API models.

License

FSL-1.1-ALv2 (Functional Source License, Version 1.1, ALv2 Future License) — use it, modify it, ship it. Build your storefront, run your business. The license converts to Apache 2.0 after two years.

Want to offer it as a managed service? Let's talk.