Store Setup / Onboarding

CP tracks the SaaS lifecycle; Runtime Admin runs the store.

This skeleton guide explains the current handoff from CP registration through provisioning and Runtime Admin login. It does not expose tokens, passwords, or internal operations.

1. Register or sign in

Merchants start in CP. CP stores account, store lifecycle, billing, and domain status.

2. Commercial event starts provisioning

A paid event activates the subscription and hands the store to the existing provisioning path. Current Stage 3 does not add a real gateway.

3. Setup link sets Runtime Admin password

When the store waits for first login, a setup link lets the merchant set the Runtime Admin password for that store.

4. Runtime Admin handles store operations

Products, orders, payment/shipping runtime configuration, theme operations, and plugin operations remain in Runtime Admin.

What CP continues to show

  • Merchant dashboard and store lifecycle status.
  • Billing records and current subscription context.
  • Domain request/status workflow and platform notes.
  • Generic links to Runtime Admin and the storefront when store URLs exist.