Create and test a waiting room

Create the first room around a test product. Have theme access, stock for the test, and sufficient plan allowance ready.

Details: choose the protected product, variant, collection, or Online Store scope. Give the room a recognizable name and review the schedule in the timezone shown by the app.
Shopper access: choose admission order and set the rate, queue capacity, and active-admission limit. Understand these controls before raising them.
Appearance: add the store’s branding and shopper messages. Check countdown, waiting, and admitted states in the desktop and mobile previews.
Review: inspect the scope, schedule, capacity, plan limits, and supported-checkout acknowledgement. Resolve warnings before publishing.
Save and reopen: leave the draft, return to it, and verify the important values are still correct. Refresh an outdated schedule before publishing.
Publish deliberately: use the app’s confirmation and wait for its result. If it reports pending publication or a recoverable issue, use that recovery flow rather than creating duplicate rooms.

Verify the test

Open the protected product through the normal storefront route in a separate shopper session. Join the room, refresh once to check reconnect, and follow the admitted journey back to the store. Test the intended cart and checkout path without placing a real order unnecessarily.

Check the room’s live view and usage afterward. Finish the test through the room controls when you are done; merely closing the browser does not end a room.

Next: launch-day operation.

Need detail on a specific step?

Details: scope, pre-queue, schedule, and safety cutoff.
Shopper access: restricted and priority access, inventory and quantity limits.
Appearance: all four editor tabs and publishing design changes.
Review: supported checkout and failure mode, progress and reconnect.

You can also start from a Recipe. A recipe prepares a configuration for review; it does not replace the publish checks.