Storefront

Status: Implemented / controlled release

What it does

Resolves tenant identity, branding, contact/location, catalogue groups, storefront capabilities and the transaction journey appropriate to the tenant.

Benefits

• one tenant-branded customer entry
• capability-aware journey selection
• multi-vertical authority

Typical usage

1. Open /t/[slug] or public/QR entry
2. Resolve tenant/capability authority
3. Browse resources/services/items
4. Continue through the supported transaction journey

Roles

Guest, Customer, Owner (configuration)

API families

• /api/v1/public/tenants/:slug/storefront
• /api/v1/public/tenant/:slug/storefront
• /api/v1/public/catalog/:tenantSlug

Endpoint presence does not automatically make an endpoint a Partner API. See API → API Overview.

Configuration

• Tenant slug
• Branding
• Business locations
• Vertical/storefront authority

Current limitations / release notes

The architecture is multi-vertical; ongoing work continues to make each vertical visually and behaviorally more distinct.

Related modules

Branding, Discovery, Booking, Catalogue & Orders, Checkout