Dashboard overview
The current operator routes and the boundary between dashboard UI and commerce operations.
The dashboard is the authenticated operator surface for Openfront Ecommerce. App Router pages delegate to feature slices under features/platform; Keystone models and domain mutations remain in features/keystone.
A visible dashboard control does not prove its backend transition, provider call, or authorization. Test the exact action, wrong-role case, retry, and failure state before relying on it.
Current route groups
- Catalog: products, product categories and collections.
- Orders: list, detail, creation and fulfillment pages.
- Markets: regions, countries, currencies, shipping options and store settings.
- Inventory and fulfillment: inventory, shipping and shipping-provider pages.
- Commerce: payment providers, discounts, gift cards, claims, price lists and invoices.
- Access and extension: users, API keys, apps/OAuth, business-account requests and system settings.
- Reporting: an analytics route and dashboard summary components.
Generic Keystone list pages also expose models permitted by the current role. Those pages are useful for administration, but sensitive lifecycle changes should still use a named operation rather than unrestricted field edits.
Setup order
- Create the first permitted dashboard user.
- Run the onboarding flow against an isolated database.
- Verify store, region, currency, country and price relationships.
- Review products and inventory.
- Configure only providers you can test end to end.
- Exercise cart -> checkout -> order -> fulfillment/refund with synthetic data.
Customization
Change screens inside the relevant features/platform/<domain> slice and keep route pages thin. If you split the dashboard into another application, preserve session or bearer-token scope, CSRF/origin policy, tenant filters and narrow lifecycle mutations.