Demo guide
A complete working store on the native Gax backend. The catalogue, stock, cart, checkout and orders are real services writing to PostgreSQL 18 — the shop, the stock and every order are synthetic.
- Native catalogue, variants, media and inventory services
- Cart sessions, exact-money pricing and stock movement
- Guest checkout with held QA policy and idempotent placement
- Native admin: orders, products, stock, people and approvals
- No payment provider — the only method is a held test order
- No fulfilment, print or shipping integration
- No customer accounts, coupons or live marketing pixels
- No page analytics until a visitor allows them (see privacy)
- Nothing here is a live shop, price or promise
The shop is open to explore. Admin access is by invitation. Use your invited operator email to sign in.
For a guided walkthrough of the admin, ask about a guided walkthrough.
Place a demo order
-
Open the Studio tee
Choose a colour and size, set a quantity and add it to the cart. Sold-out combinations are disabled from live stock.
-
Review the cart
Change quantities or remove a line. The totals are recalculated by the native pricing service on every change.
-
Check out with the test order
Use the prefilled synthetic address, keep Demo test order — no payment selected and place the order. The confirmation shows the real order number.
-
Inspect it in the native admin
Invited operators open /admin/, sign in with their invited operator email and the code sent to it, then open Orders. The same order, its exact money and its stock movement are there.
Sign in to the admin
The shop is open to explore. Admin access is by invitation. Use your invited operator email to sign in.
-
Request a code
Open /admin/ and enter your invited operator email. Click Send sign-in code.
-
Read the code
Open the sign-in email sent to your operator address and copy the eight-digit code from the newest message.
-
Verify
Paste the code into the admin and continue. The session is an ordinary native operator session; sign out when you are done.
-
Approve with a second person
Sensitive changes keep their two-person rule. An approval needs a second invited operator: sign in separately as them and approve the pending request — self-approval is refused by design.
It runs on its own PostgreSQL instance and its own operator set. Do not enter real personal data, real addresses or any card details: there is no card field, and the address you submit is stored in the demo database.