Preview and publish the online storefront

Outcome

You will apply storefront branding (logo, colour, organiser name), open the anonymous storefront preview, verify the event renders correctly with bilingual titles and prices, and publish the event so it appears on the public storefront.

Before you start

• Sign in to the RushTik admin as an organiser-owner or organiser-admin.
• Complete UG-CP-001 and UG-CP-002 — you need an event with ticket types.
• The event must be in Draft or Scheduled status before publishing.
• Commission is collected from prepaid credit before tickets are issued. Issuance hard-blocks when the prepaid balance is 0 MMK or below; existing valid tickets are never affected.

Steps

1. Apply storefront branding

In the admin sidebar, select Storefront, then Branding. Upload a logo, set the organiser display name, and pick a primary colour. Select Save.

Expected result: a toast confirms the branding is saved. The logo and colour preview appears on the branding page.

2. Open the storefront preview

In the sidebar, select Storefront, then Preview. Select Open preview to open the storefront URL in a new browser tab.

Expected result: the storefront home opens in the new tab. The BrandBar at the top shows your logo, organiser name, and primary colour. No login is required — the page is fully anonymous.

3. Verify the event renders correctly

On the storefront home, toggle the EN/MY language switch in the BrandBar. Click the event card to open the event detail page.

Expected result: the event detail page renders the banner, bilingual event name (English and Burmese), description, date, venue, and ticket type rows with integer-MMK prices. The Burmese name renders with no tofu boxes. The "Buy tickets" CTA is visible.

4. Review the publication panel

Return to the admin console. Open the event detail page and review the publication panel.

• Prepaid credit balance: confirm the balance is above 0 MMK.
• Publication warnings: confirm there are no blocking warnings.

Warning — prepaid credit hard-block (Rule 9): RushTik collects the platform commission from prepaid credit before tickets are issued. If your prepaid balance is 0 MMK or below, ticket issuance is hard-blocked. New ticket sales stop; existing valid tickets are never affected. Buy a prepaid credit pack before publishing if the balance is low.

Expected result: the publication panel shows a positive prepaid balance and no blocking warnings.

5. Publish the event

On the event detail page, find the Transitions card. The card lists the allowed next statuses as buttons. Select On sale to publish the event.

Expected result: a toast confirms "Event transitioned to on_sale". The status badge on the event detail page changes to On sale. The event now appears on the public storefront list for anonymous buyers.

Troubleshooting

• Preview tab shows a blank page: the tenant slug may not resolve. Confirm the storefront URL uses the correct <tenant-slug>.rushtik.app format. In local development, check the Host header configuration.
• Burmese name does not render on the storefront: confirm the Name (Burmese) field is filled with valid Burmese Unicode. The storefront uses Noto Sans Myanmar; do not paste Zawgyi.
• "On sale" button is not available: the event may be in a status that does not allow the on_sale transition. Check the state machine — the transitions card only shows valid next statuses. Move the event to Scheduled first.
• "Issuance hard-blocked" warning on publish: your prepaid credit balance is 0 MMK or below. Buy a prepaid credit pack (see UG-MR-001), then return here and publish. Existing valid tickets are not affected.

Related guides

• UG-CP-001 — Create and publish an event
• UG-CP-002 — Configure ticket types, zones, capacity, and pricing
• UG-MR-001 — Buy a prepaid credit pack