How a storefront design connects to ReAI.
ReAI is both a data source and commerce platform. The website can stay independent, with its own repository and deployment.
Follow the flow
- Git owns design, navigation and explanations. A purely static website needs no commerce integration.
- The management API lets an authorized operator manage the Site, products, publication and commerce rules.
- The Site API delivers only this Site’s published data to the Worker. Its credential is separate from a user’s management credential.
- ReAI checkout handles contact, delivery and payment status. Orders, invoices and accounting follow-up stay in the platform.
Independent website, shared business data
A design change deploys only this website. Product and price changes happen in ReAI. A catalog failure is shown as a failure; production never substitutes a local catalog that pretends to be live.
Point of sale in the same platform
ReAI brings together online commerce, point of sale and accounting. In-store sales are handled by the point of sale, with receipts, payments and accounting follow-up in ReAI. You do not need an expensive integration between separate point-of-sale and accounting systems. The Site API on this website serves the storefront; point of sale is used in ReAI.
HTML first, JavaScript for interaction
This store sends HTML from a Cloudflare Worker. It needs no large JavaScript application to display products. Images use suitable sizes, and images lower on the page load on demand. Small scripts handle the cart, swatches and signup. You can choose another framework; the Site API does not tie you to this design.
Cache catalogs, fetch availability fresh
storefront gives one coherent catalog with products and collections, avoiding a request for each collection. The delivery API supports ETags for catalog data. Availability is fetched separately without caching, ideally in one batch for the page’s variants. Checkout revalidates prices and stock. This test store does not cache its HTML or JSON responses.
Fetch the data your design needs
Use product details for product pages, collections for navigation and availability for variant selection. Descriptions are delivered as text and sanitized HTML. The Site API exposes the website’s published data. Other backend functions belong to the management API and require authorized server code; a public website must not gain access to private accounting.
What the Site API must not give the browser
Internal tenant IDs, costs, margins, warehouse counts, bank and accounting data do not belong in public delivery data. The management API has wider capabilities and requires user/tenant access. This playground shows only Site delivery data.
From payment to follow-up
A created checkout is not a paid order. ReAI handles payment outcomes and subsequent order/invoice flow; use platform status before fulfillment. Invoice, payment and settlement are different steps. Adyen fees and reconciliation must not be treated as if a return URL automatically posted everything.
One private repository per client
Each client website has its own permissions, instructions and deployment. You can share repository access with the client and deploy design changes without deploying other clients’ websites.
Browser → demo Worker → /site/v1/** (Site credential)
Operator → /api/** + X-Tenant-Id (management credential)
Browser → ReAI hosted checkout → Adyen
ReAI → payment status / order / invoice follow-up