SALEOR-BASED / SOLUTION CONCEPT Independent storefront Enterprise purchasing

Connect commerce
and purchasing through
an owned platform

Use Saleor for product, checkout and order foundations, with a company-owned storefront; Catalog → Detail → Checkout → Orders → Account connect the buying journey while distinguishing native capabilities from enterprise customisation.

Product catalog Product details Cart and checkout Order operations Customer accounts
Proposed Saleor development · Sample interfaces and data · No real payments
COMMERCE LEDGER / CONCEPT DEMO
Conceptual commerce ledger with observation rings and an illustrative order matrix
LIVE / SIMULATED EVENTS NO REAL TRANSACTION
CATALOGSample catalog loaded 00:01
CHECKOUTSample checkout created 00:02
ORDERDEMO-2026-0001 created 00:03
ACCOUNTSample business account signed in 00:04
05
Core commerce domains CATALOG → ACCOUNT
01
Unified GraphQL layer API-FIRST CORE
03
Deployment models CLOUD / PRIVATE / HYBRID
06
Delivery stages BRAND → OPERATE
SCROLL
Saleor independent storefront architecture — Chinese-language solution illustration
Saleor independent storefront architecture · Illustration in Chinese, not a delivered interface
Saleor business procurement architecture — Chinese-language solution illustration
Saleor business procurement architecture · Illustration in Chinese, not a delivered interface

Interfaces, figures and prices are examples. Actual features, licensing and delivery scope are confirmed for each project.

01 / CORE COMMERCE DOMAINS SEC.01

Five commerce foundations for your own storefront

The interfaces below are solution concepts : products, IDs, amounts and accounts are fictional examples. They explain the proposed interaction structure and connect to no live catalog or payment service.

STOREFRONT / INTERFACE CONCEPT
CLICK TO SWITCH
ALL DATA · DEMO ONLY
store.example.com / catalogSample data · No real transactions

Product catalog

DEMO · 4 ITEMS SHOWN
Illustrative retail scene, not a product photograph
Sample product A · Standard item SKU-DEMO-001
Sample price · —
Illustrative warehouse shelving
Sample product B · Bundle SKU-DEMO-002
Sample price · —
Illustrative distribution centre
Sample product C · Bulk pack SKU-DEMO-003
Sample price · —
Illustrative logistics scene
Sample product D · Service item SKU-DEMO-004
Sample price · —

Product details

DEMO · VARIANT / ATTRIBUTE
Illustrative product context photograph

Sample product A · Standard item

Identifier SKU-DEMO-001
Product type / Attributes Sample model
Variant Specification 01 / 02
Customer pricing · Placeholder ¥ —

Cart and checkout

DEMO · NO PAYMENT
Sample product A · Standard item SKU-DEMO-001
× 2¥ —
Sample product C · Bulk pack SKU-DEMO-003
× 1¥ —
Sample delivery method SHIPPING / DEMO
—¥ —
Product subtotal · Sample ¥ —
Shipping / Tax · Sample ¥ —
Total · Sample only ¥ —
Demonstration only: no gateway call, real transaction or payment information collection

Order operations

DEMO · 4 RECORDS
DEMO-2026-0001Fictional business account
Created
Sample date
DEMO-2026-0002Fictional business account
Unconfirmed
Sample date
DEMO-2026-0003Fictional business account
Fulfilling
Sample date
DEMO-2026-0004Fictional business account
Draft order
Sample date
Illustrative states and progress, showing the proposed order lifecycle

Customer account

DEMO · NO REAL IDENTITY
ACCOUNT / SAMPLE

Account name Fictional business account

Account status Sample active state

Identity integration Customer identity / Proposed

Native account activation
ADDRESS BOOK

Billing address Sample address 01

Delivery address Sample address 02

Address count 2 sample records

Native address book
ORDER HISTORY

Previous orders 4 sample orders

Reorder Order to checkout

Order events Sample event history

Native order history
PRICING / ACCESS

Customer segment Sample segment A

Customer pricing Segment display concept

Purchasing role Project-specific development

Configuration / Integration concept
01

Product catalog

Products, variants, attributes, categories, collections, channel visibility, media and metadata provide the catalog foundation.

PRODUCTS · VARIANTS · CHANNELS
02

Product details

Combine variant selection, attributes, channel prices and stock availability in a purpose-built product page.

ATTRIBUTES · MEDIA · PRICING
03

Cart and checkout

Saleor uses Checkout for both cart and checkout, with promotions, addresses, delivery and configurable completion flows.

CHECKOUT · PROMOTIONS
04

Order operations

Order editing, drafts, fulfilments, returns, activity and expiry settings provide the operational foundation.

ORDERS · FULFILLMENT
05

Customer accounts

Customer accounts provide activation, addresses, order history and reordering. Enterprise identity and purchasing roles need their own design.

ACCOUNTS · SSO · GROUPS
02 / PROCESS SIGNALSEC.02

Follow a purchase through its lifecycle

Animated points illustrate the proposed data flow, not real order timing or performance. Amber nodes identify custom work or external-system coordination.

010203040506 Select Cart / RFQ Checkout Order Fulfilment Reconcile CATALOGCHECKOUT / RFQCOMPLETIONORDERFULFILLMENTRECONCILE Native foundation Native + Custom Native foundation Native foundation Native + Integration External coordination
Catalog and details: native foundation Checkout also represents the cart Orders and fulfilment: native + integration RFQ and reconciliation: custom / external
EVENT STREAM / LOCAL SIMULATION SIMULATED
03 / OFFICIAL CAPABILITY CHECKSEC.03

Verify the foundation before defining custom development

Reviewed on 2026-11-15. Classifications use capabilities explicitly listed in Saleor's official feature pages and developer documentation. They correct a blanket assumption: customer segments and pre-acceptance approvals are officially listed, but actual availability must be checked against the chosen version and deployment rather than treating everything as custom development.

Native commerce foundations

A / NATIVE
NATIVEProduct catalog and detail models

The official product model includes Products / Variants / Attributes / Categories / Collections / Channels / Media / Metadata。

NATIVECart and checkout

Saleor has no separate Cart model; it uses Checkout for cart and checkout, with lines, completion, promotions and custom checkout flows.

NATIVEOrder operations

The official operations list includes order edits, activity, draft orders, fulfilments, returns and order expiry.

NATIVECustomer accounts

Customer accounts cover activation, addresses, order history and reordering. Permission groups apply to staff; merchant OIDC and procurement identity require separate validation.

Sources: Products / Checkout / Orders documentation and official Operations

Configurable / Partial coverage

B / CONFIGURABLE
PARTIALCustomer-specific pricing

The Operations page lists Customer groups and special pricing; Custom prices plus order-line overrides provide extension foundations. Validate the selected version, storefront configuration and contract-price governance.

PARTIALProcurement approval

The official capabilities include Approvals for approval before order acceptance and Draft orders for internal order review. Staff permissions do not constitute procurement roles; conditional routing and multi-party approval require implementation.

PARTIALQuote foundation

Draft orders are officially described as a way to send customer quotes, while Order expirations can expire quotes and release allocations. These foundations are not a complete RFQ application.

PARTIALChannels and currencies

Channels configure product availability, currency, prices and delivery. They provide a foundation for distinct commerce contexts, not an automatic enterprise contract-price system.

Sources: Checkout / Operations feature pages and order documentation

Project-specific development

C / CUSTOM BUILD
CUSTOMBULK ENQUIRIES / RFQ

Bulk SKU import, enquiry versions, negotiation, comparisons and quote-to-order orchestration require implementation using appropriate drafts, metadata, Apps and webhooks.

CUSTOMProcurement organisation

Design company membership, departments, cost centres, budgets, limits and separation between buyers and approvers.

CUSTOMPrice-list governance

Plan contract-price imports, validity periods, tiers and ERP synchronisation around the selected API version and business rules.

CUSTOMApproval orchestration

Amount, category and department routing, parallel approvals, rejection, audit trails, notifications and OA integration exceed a basic approval step.

Extension paths: Apps / Webhooks / Metadata / Synchronous callbacks / Identity integrations
BOUNDARY

Use Saleor's native commerce foundations as the core for products, checkout, orders and accounts. Focus custom work on enterprise identity and pricing governance, RFQ and approval orchestration, and external-system synchronisation using supported extension points and documented upgrade tests.

04 / PROPOSED EXTENSIONSSEC.04

Four proposed custom capabilities with explicit boundaries

This section describes proposed project scope rather than completed features or customer results. Each capability distinguishes reusable foundations from new implementation.

Illustrative procurement planning meeting
Proposed / Enterprise purchasing

Procurement organisation

Company entities, members, departments, cost centres, budget limits and buyer / approver separation require an appropriate organisation and identity model.

Native foundation Account and address foundations; merchant identity and staff permissions
Build Organisation model, role relationships, budgets and management views
Illustrative planning and review scene
Proposed / Bulk enquiries

BULK ENQUIRIES / RFQ

Design bulk SKU import, enquiry and quotation versions, negotiation, expiry and quote-to-order orchestration.

Native foundation Draft orders, quote expiry and metadata
Build Enquiry model, comparison, negotiation, bulk import and order orchestration
Illustrative reporting workspace
Foundation + Governance

Customer-specific pricing

Plan customer, channel and contract-price presentation and custom line-price rules. Validate price consistency between storefront and order.

Native foundation Customer segments, custom prices and channel pricing
Build Price-list imports, validity periods, tiers and ERP synchronisation
Illustrative collaboration and review scene
Foundation + Orchestration

Procurement approval

Build amount, category and department routing with parallel review, rejection, audit events and notifications; integrate OA or ERP where required.

Native foundation Order approvals and internal draft review
Build Conditional routing, review state machine, audit, notifications and OA integration
05 / TECHNICAL ARCHITECTURESEC.05

API-first layered architecture

Separate storefront and dashboard from the GraphQL commerce API. Add enterprise services through Apps, webhooks and metadata. This is an illustrative solution structure; select and test actual components per project.

L01 / EXPERIENCE
Company-branded storefront
NEXT.JSREACTAny suitable frontend Mobile web
STOREFRONT API
L02 / OPERATIONS
Saleor Dashboard
Products Order Customers Channels Extended views
REACT SPA
L03 / API
GraphQL API · Commerce operations
QUERYMUTATIONPERMISSIONSWEBHOOKS
API-FIRST
L04 / CORE
Saleor Core · Products / Checkout / Orders / Accounts
PYTHONDJANGOCHANNELSPROMOTIONS
OPEN SOURCE
L05 / DATA
Persistence and media storage
POSTGRESQLREDIS / WORKERSObject storage / Product media
PERSISTENCE
Your domain →GraphQL→Saleor Core→PostgreSQL→Webhooks→ERP / WMS

EXTENSION MECHANISMS

  • Apps: independently deployed applications for business integrations
  • Webhooks: send order and stock events to external systems
  • Metadata: attach project-specific structured fields
  • Synchronous callbacks : delegate supported pricing, tax or shipping decisions to external services

IDENTITY AND PERMISSIONS

  • OIDC / SSO: distinguish merchant authentication from customer login; validate providers and versions separately
  • Permission groups: permissions for staff and sales operations
  • Channels and access : validate APIs, roles and versions; channel configuration is not automatic tenant isolation
06 / SYSTEM INTEGRATIONSEC.06

Connect commerce to your existing systems

Define integrations around the customer's actual systems. These are common integration surfaces and proposed patterns, not completed customer projects.

ERP

Enterprise resource planning

Synchronise product and price master data, customer records and accounting references through Apps or integration services.

MASTER DATA / PRICE SYNC
WMS

Warehouse and fulfilment

Integrate availability, dispatch, multiple warehouses and return events with the appropriate webhook and API contracts.

STOCK / FULFILLMENT EVENTS
PSP

Payment providers

Connect the merchant's selected payment provider through a suitable payment App; this demonstration connects to no payment service 。

PAYMENT APPS / NO DEMO PAY
SSO

Identity and single sign-on

Design merchant SSO and customer login separately. Procurement buyers, approvers and administrators need explicit organisation roles and tests.

OIDC / PERMISSION GROUPS
OMS

Order management systems

Map order states, splitting, fulfilments and retained history to the customer's OMS rules.

ORDER LIFECYCLE
INV

Invoicing and tax

Plan invoicing data, tax classes and exemptions against the customer's jurisdiction and accounting requirements.

TAX CLASSES / INVOICE
MSG

Messages and notifications

Route order, review and quote-expiry events to agreed internal messaging channels.

WEBHOOK / NOTIFICATION
BI

Data and reporting

Send relevant commerce data to the customer's warehouse and define reporting measures with the business team.

DATA EXPORT / WAREHOUSE
07 / DEPLOYMENT & DELIVERYSEC.07

Three Deployment models deployment models, one delivery scope

Choose hosting around data ownership and operating requirements. Actual deliverables, schedule and acceptance criteria are agreed in the project scope.

Illustrative company office

Private deployment

Deploy to customer-controlled infrastructure. Define external integrations, network access and data flows explicitly; self-hosting does not remove those dependencies.

DOCKER COMPOSE / KUBERNETES
Illustrative development and operations scene

Managed hosting / Saleor Cloud

Evaluate a managed infrastructure service while retaining responsibility for the storefront and custom extensions. Confirm service scope, plans, costs and upgrade responsibilities.

MANAGED / CONTROLLED UPGRADE
Illustrative logistics and supply-chain scene

Hybrid deployment

Host core commerce in the selected environment and integrate customer-controlled data and enterprise services through documented APIs and events.

HYBRID / API + WEBHOOK
✓Storefront source, design system and component notes
✓Deployment scripts and environment configuration inventory
✓API documentation, extension contracts and integration mappings
✓Administrator guide, training and acceptance checklist
08 / HOW TO BUILD YOUR OWN STORESEC.08

Build your own storefront and connect purchasing with orders

A proposed six-stage path from brand planning to operations. Use native foundations where suitable, develop enterprise extensions, then validate integrations and handover.

01

Brand and domain

Define domain ownership, visual standards and applicable site requirements.

BRAND / DOMAIN
02

Products and channels

Model product types, attributes, variants, categories and collections; configure channels, currencies and prices.

MODEL / CHANNELS
03

Storefront buying journey

Connect catalog, detail, checkout, orders and accounts through the commerce API.

STOREFRONT API
04

Accounts and pricing

Configure accounts and addresses, validate pricing by version, and design staff and purchasing-customer identities separately.

ACCOUNT / PRICING
05

Procurement workflows

Build RFQ, approval orchestration, cost centres and ERP pricing integrations where required.

CUSTOM / APPS
06

Integration and handover

Validate payments, fulfilment and invoices, run agreed UAT, then hand over monitoring and operating procedures.

UAT / HANDOVER
09 / NEXT STEP

Agree the boundaries, then plan delivery

Review the customer's catalog, purchasing rules and integration scope. Identify native, configured and custom work, then define an implementation and acceptance plan. This page is a solution concept, not a quotation or project result.

Illustrative business cooperation photograph
DEMO ONLY

Interfaces, products, identifiers, amounts, order states and accounts are fictional. Photos illustrate business contexts, not actual SKUs or customer cases.

NO PAYMENT

This local introduction connects to no payment gateway, creates no real order, and collects no payment or identity information.

NO CLAIMS

No customer names, deployment counts, sales results or conversion claims are presented. This solution page has not been deployed.

SOURCE-BASED

Saleor capabilities were reviewed against official feature pages and documentation on 2026-11-15. Confirm actual availability for the selected release before implementation.