Openfront Ecommerce
Multi-region catalog, storefront, checkout, orders, inventory, payments, and fulfillment.
Openfront Ecommerce is Openfront's commerce product. It combines a country-aware storefront, an operator dashboard, a Keystone GraphQL/data layer, and provider adapters in one source repository that the operator controls.
Before using real customer or payment data, verify cart ownership, adapter consistency, provider webhooks, type/build enforcement, and the complete checkout path in the deployed environment.
What the source covers
- catalog: products, variants, options, images, categories, collections, types and tags;
- regional commerce: stores, regions, countries, currencies, price sets/lists/rules and tax records;
- inventory and fulfillment: locations, stock movements, shipping profiles/options/providers, labels and fulfillment lines;
- checkout and orders: carts, addresses, payment sessions/collections, orders, immutable order lines, captures, refunds, returns, swaps and claims;
- business workflows: customer groups, business-account requests, invoices, checkout links, gift cards, discounts and draft orders;
- extensibility: API keys, OAuth apps/tokens, webhooks, payment/shipping adapters and Openship installation records.
Architecture
Ecommerce establishes the family pattern: thin App Router pages, operator work in features/platform, storefront work in features/storefront, schema and GraphQL operations in features/keystone, and provider code in features/integrations.
Its model names are specific to commerce. Other verticals reuse the boundaries, not the catalog/order vocabulary.
Main workflow
A store publishes products and regional prices. A guest or customer creates a cart, selects shipping and payment, and completes checkout. The server writes order and money snapshots so later catalog changes do not rewrite the sale. Operators fulfill, refund, return, swap or claim against that recorded order.
Setup, onboarding and deployment
Use Getting started for a source-backed local path. The checked-in onboarding seed creates the Impossible Tees demo across store, regions, products, variants, prices, categories, collections and provider records. Setup data does not prove external provider execution.
Read Deployment before choosing a host. Several package commands apply migrations as part of development or build, so release jobs need deliberate migration ownership.