StallStall
Documentation
Getting started with Stall
Start beside your existing shop with two products and a Stripe test payment. A fresh Stall installation has no sample products, stock or orders. You can open the desk before connecting providers; purchases need both Pier and Stripe.
Prepare and publish products
Open Shop desk → Products as an owner or administrator. Product details and prices live in Stall; the matching SKU and stock live in Pier. Connect Pier before publishing an available product.
Orders, shipping and refunds
Open Shop desk → Orders as an owner or administrator. Each card shows the customer's details, purchased lines, exact AUD total and current state. Approvals apply to the saved revision you reviewed. If the order changes during review, refresh and review it again.
Pier and Stripe connections
All values are private configuration. Never paste a session cookie or key into a URL or Git. Locally place only the needed variables in an owner-readable .dev.vars file (ignored by Git); preserve the settings RER setup generated. Stop and restart rer dev after changing configuration. For deployment, supply these variables from your secret manager; deploy.json declares them as secrets.
Move products into Stall
The first move-in kit imports listing metadata from a deliberately small Shopify product CSV subset. It uses Base import-kit for a read-only dry-run, exact reviewed fingerprint, retained source bytes, resumable journal and strict undo. It never imports inventory, customers, cards, orders, images, options, tax settings or fulfilment settings, and never writes to Pier.
Backup, restore and customer details
Stall archives contain business records and customer information. Store them privately. Products, orders, recorded approvals, provider references and import custody travel with an archive. Authentication records, sessions, sign-in links, agent credentials and private configuration do not. A destination keeps its own owner and authentication records.
Agent commands, approvals and recovery
Use POST /api/stall/commands with JSON { "type": "…", "payload": { … } }. Human requests use their native session cookie and this installation's Origin. Agent requests use Authorization: Bearer … with the owner's preparation credential stored privately. Every handler checks current role/session or grant; changing an operator's role or revoking its grant removes authority.
Stall guides
Stall is a shop of your own for an Australian maker or retailer whose stock lives in Pier. Customers pay through your Stripe account; you manage products, orders, shipping and refunds at the Shop desk.
Source and boundaries
Stall was generated and assembled from the committed runeditrun/base foundation at ada9f574d8a7247edc3a1180b593ad182b1fbb37, then converted with Base's package-mode exporter. The exact published CLI pin is @runeditrun/rer 0.2.22. The copied runtime, auth, mail, import-kit and D1 transport remain MIT source. composition.lock.json records foundation origins.