The shopper journey
Routes: the tenant storefront and /account/* · Audience: customers, not staff
1. Who the shopper is
A customer of one store, not a user of Orbit. They sign in on the storefront's own login page, see only their own orders, and never meet the admin application.
| Shopper | Org user | |
|---|---|---|
| Signs in at | /account/login on the tenant | /login |
| Sees | One store | The whole workspace |
| Governed by | Customer identity | RBAC permissions |
2. The journey
3. The account area
| Page | Route |
|---|---|
| My orders | /account/orders |
| Saved addresses | /account/addresses |
| Preorders and support | /account/preorder-requests · /account/support |
| Checkout | /account/checkout |
4. Field reference — the login form
The storefront login takes an email or a phone number — the field's placeholder is
[email protected] or +91 98xxx xxxxx.
The form carries a honeypot
Its first text input is name="_hp", a hidden bot trap. Anything automating this form must leave it
alone: filling it makes the request look automated and the login is refused with no visible
error — the page simply stays on the sign-in screen.
5. The admin contract
| Prerequisite | Without it |
|---|---|
| A published storefront | Nothing to browse |
| Payment gateways | Checkout cannot complete |
| Delivery configuration | No fulfilment option |
| Customer accounts enabled | No account area |
6. Downstream
Everything a shopper does arrives in the orders workbench or the preorder queue.
7. Don't confuse this with…
| Thing | Where |
|---|---|
| Shopper account (this page) | The customer's own area |
| Orders workbench | The store's view |
| Org user | An Orbit user with permissions |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| Login appears to do nothing | The honeypot was filled, or the credentials are wrong |
| A storefront link 404s | Storefront URLs are project-prefixed |
| No account area | Customer accounts are not enabled |