1. Create your account
For everyone: Sign up so the system knows who owns the business workspace.
For developers: Nest session cookie `pos_builder.sid` via POST /auth/register|login.
How POSai builds your system
This page is for everyone testing the product: business owners (plain language) and engineers (what the API does). You are not downloading a custom app file — you configure a private multi-tenant workspace, then run sales and reports inside it.
In one sentence
You describe your business → AI proposes a blueprint (modules + dashboard + sample data) → you approve → your workspace is ready to use (POS, products, customers, reports).
Step-by-step workflow
2. Start from Get started
For everyone: Open the single start hub. Choose Build with Us (template path) or Build with AI.
For developers: GET /setup → /setup/business-information or /setup/build-with-ai.
3. Pick a template (or AI describe)
For everyone: Template path: choose industry + name. AI path: describe the business in free text.
For developers: POST /businesses { templateId, applyTemplate } or AI setup-recommendation → approve.
4. Review proposed setup
For everyone: See and edit modules on the light setup preview (or AI proposal). This is the first-run gate.
For developers: GET /setup/preview or /setup/build-with-ai/preview — session drafts.
5. Accept and create live workspace
For everyone: Accept materializes features, dashboard, and brand to LIVE — then opens your store console.
For developers: BwU: applySetupPreview; BWA: approveRecommendation; route liveConsolePath.
6. Optional: System Studio
For everyone: Advanced: reconfigure staging modules and brand later. AI review is required only when publishing unpublished Studio changes.
For developers: GET/PATCH Studio staging; go-live with AI hash when dirty. Optional owner path.
7. Run the business
For everyone: Open the live dashboard or POS register to sell, restock, and report.
For developers: Live /b/:id console; /b/:id/sale is register layout; cashiers forced to POS on login.
Where does my “setup” live?
- AI recommendations — proposals from the builder (pending until you approve). Open AI setup or Saved setups inside a business.
- Applied workspace — enabled modules, dashboard layout, and sample products after approve. Open Configure studio (same preview for template, AI, and platform builds).
- Day-to-day tools — Sale, Products, Customers, Reports. This is how you “access your system” after build.
What testing means right now
You are testing a configuration-based POS SaaS, not a code generator that invents a brand-new app per merchant. AI recommends and materializes configuration on the shared platform. Flag-only industry extras (e.g. kitchen display) may show as “catalog” until deep modules ship.