Use Branding & Themes for the global visual identity and Templates for the active kiosk screen shell. Saving either surface updates the Location configuration; there is no separate Publish button.
Save global branding
- Open Kiosk > Branding & Themes.
- Choose the theme template and home layout.
- Set the primary and accent colors, brand name, tagline, logo URL, and hero image URL.
- Review the welcome, menu, and checkout previews.
- Select Save changes.
The saved theme, layout, colors, name, tagline, logo, and hero are returned by the kiosk runtime. Restore previous branding is available only for the most recent change held by the current page session; do not treat it as a permanent version history. Device-level theme or layout overrides win over global values.
Activate and understand a template
Open Kiosk > Templates and select a template. Selecting a different template immediately saves kiosk_template_id and changes the active Location configuration. The page offers a one-step restore to the previously selected template during that session.
Templates can implement only selected screens. A screen listed as Custom uses that template's renderer; every other screen safely falls back to the built-in kiosk UI with the current design tokens. This is why welcome and menu can look highly customized while checkout uses the standard flow. Table Order Kiosk uses its required table-order template instead of the general walk-up selection.
Template copy fields save as they are edited. Template-specific content includes the welcome headline, subtext, eyebrow, badge, primary CTA, support text, feature message, and logo scale.
Upload or generate template assets
Each template exposes named slots such as logo, hero, pattern, category strip, or promo banner. Uploading a slot saves the returned URL into the tenant's template asset map immediately. Reset slot removes the custom URL and returns that slot to its registry placeholder; it does not delete unrelated slots.
The template upload endpoint accepts one image up to 12 MB and checks the reported image MIME type. It currently writes under the application's local public/uploads/kiosk-assets directory. That storage is not durable on a serverless production filesystem, so production use requires a persistent asset origin before operators depend on uploaded files surviving a deployment.
AI asset generation also writes a local public file. When OPENAI_API_KEY is unavailable or mock image generation is enabled, the result is a generated mock SVG, not a model-created production image. Check the returned source, preview the asset, and only then apply it to a slot.
Verify the guest result
Reload a controlled kiosk after saving. Confirm the active template, branding, custom screens, fallback screens, product images, and checkout flow. An already-open kiosk does not receive a pushed live-update event from these pages; it reads the configuration when its runtime data is loaded again.