Documentation / Storefront
Storefront
Domains, theming, markets, currencies, search and the PWA shell.
Your storefront exists from the moment provisioning finishes. This section covers making it yours.
Addresses and custom domains
Every workspace gets yourslug.tenza.app permanently — it keeps working even after you add your own domain, which makes it a reliable fallback when a DNS change goes wrong.
- In Settings → Domains, add the domain you own.
- Create the DNS records shown. The panel verifies them live rather than asking you to guess.
- TLS is issued automatically once verification passes. There is nothing to upload.
Adding a domain does not move your storefront — it adds an address. Both resolve to the same tenant, which is resolved from the request host.
Theming
Theme settings live in Settings → Storefront: palette, typographic scale, logo, favicon, hero treatment and the navigation structure. Changes apply to the server-rendered pages immediately; there is no build step to wait for.
Markets and currencies
A market is a country or region with its own pricing, currency display and shipping rules. Your default market is set at provisioning; add more in Settings → Markets.
| Setting | What it controls |
|---|---|
| Default currency | The currency prices are stored and displayed in when no market override applies. |
| Default market | The market used when a visitor’s own market cannot be determined. |
| Enabled markets | Which markets can be selected, and therefore which shipping lanes must exist. |
| Time zone | The zone reports, schedules and order timestamps are presented in. |
Search and merchandising
Products are indexed for search as they are published. Autocomplete and the results page are both served from that index, so an unpublished product can never appear in either. Category curation and ordering are in Catalog → Storefront categories.
Progressive web app
The storefront ships an installable PWA shell with a service worker. The worker is served with no-store headers so an update reaches devices on the next visit rather than sitting in a cache for a week.
Apps
Installed apps can inject widgets at defined storefront points — the checkout summary, the cart drawer footer, below the product price, below the hero. Browse and install them from Apps in your admin: view the manifest, install, configure the settings it declares, then enable. Settings are validated against the app’s own schema on save, so a misconfigured app is refused rather than half-applied.
Something wrong or missing on this page? Tell us — documentation corrections are treated as bugs.