Use an Event Shop

Overview

Use an Event Shop describes the attendee-facing flow for buying event merch outside the main registration form. The public shop is separate from attendee registration, but an order may still be linked to the buyer’s event rego when the buyer has one for the same event.

Shop availability depends on the partner’s Shop Config. The whole shop can have a global open and close window, and each listing can have a stricter purchase window. Some events require an event rego before checkout. Other events may allow standalone shop orders without a rego. The checkout screen should explain which rule applies before an order is created.

Public routes

Route	What it opens
/:eventSlug/shop	Public event shop storefront with search, sort, categories, item cards, and a cart modal opened from the cart button.
/:eventSlug/shop/checkout	Dedicated shop checkout with cart review, contact details, fulfillment, discounts, payment selection, proof upload, order review, and receipt state.
/transactions/event-shop	Buyer order list for shop orders tied to the signed-in account.
/transactions/event-shop/detail	Buyer order detail and ecommerce-style status timeline.

Browse and cart

The shop shows active listings grouped by category. Listings can come from registration add-ons, registration inclusions, or standalone merch created by the partner.

Shop state	What the buyer should expect
Active item	Buyer can add the item to cart if stock, purchase window, and eligibility rules allow it.
Sold out or unavailable	Buyer cannot check out the item until the partner changes stock or availability.
Rego required	Buyer must sign in and have an eligible rego for the same event unless the partner allows no-rego ordering.
Quantity limited	The buyer can be blocked by a per-cart limit, a total listing sale limit, or a stricter per-person lifetime limit across previous active orders.
Price changed	Checkout must refresh totals before payment.

For signed-in buyers, cart state is API-backed and persists across sessions and devices. Browser-local state is advisory only; checkout always uses the latest server validation.

Checkout

Checkout is separate from the browsing storefront. The buyer shops and manages the cart from the cart button on /:eventSlug/shop, then moves to /:eventSlug/shop/checkout for a rego-submission-style flow: Cart, Fulfillment, Payment, and Review.

Checkout collects purchaser details and pre-fills from the buyer profile or session wherever possible. Buyers should still review the details before submitting because the order snapshot is used for payment review, pickup, delivery, and support.

Checkout validates:

Validation	Why it matters
Event and shop status	Closed, not-yet-open, or disabled shops cannot accept orders.
Item availability	Inactive, expired, sold-out, or over-limit items cannot be purchased.
Quantity limits	Per-cart caps, total listing sale caps, and lifetime per-person caps are enforced by the API.
Rego eligibility	Registration-required items need a matching same-event rego.
Delivery selection	Delivery requires an enabled courier and a matching flat, region, or Philippines island-group rate.
Coupon and affiliate scope	Codes only apply when that specific coupon or affiliate is enabled for shop orders.
Payment availability	Payment provider and account must be active for the event.

The API calculates cart totals, delivery fees, platform fees, discounts, and final checkout totals. Do not rely on screenshots of browser totals if support needs to verify an order.

Pickup and delivery

Shop orders can be pickup, delivery, digital, claim-only, or a mix depending on item setup.

Fulfillment type	Buyer expectation
Pickup or claim	The buyer waits for a ready-for-pickup update and presents the order reference or QR at the shop claim desk.
Delivery	The buyer selects a courier/rate when available and provides delivery details. Preferred couriers may appear first.
Digital	The partner provides digital fulfillment instructions through the order update path.

Delivery destinations are available only when the event has delivery enabled and at least one active courier rate for the selected country or region. PH island group delivery rules apply only when the selected country is the Philippines.

Pickup release is handled in Shop Order Claim. Staff should not use attendee check-in as proof that a shop order was released.

Payment and status

Shop payments use the same shared rego payment UI as the attendee registration form. Buyers choose from event payment method cards, review the payment instructions and receiving account, enter a payment reference, and upload the same screenshot or receipt proof used by the rego checkout flow.

After checkout, buyers should use the shop order list and detail page to review:

Status area	What it shows
Payment state	Pending, submitted, confirmed, rejected, or other review state.
Order state	Paid, preparing, ready for pickup, released, shipped, delivered, cancelled, voided, or exception where applicable.
Fulfillment context	Pickup, delivery, courier, delivery region, or claim information.
Buyer-visible updates	Partner-authored updates similar to ecommerce order timelines.
Linked rego marker	Shows when the order is tied to a same-event registration.

If payment is rejected, the buyer should follow the order update instructions and submit corrected payment details only through the supported shop order flow.

Support checks

When helping a buyer, support should ask for the event name, shop order reference, buyer account, and payment reference if payment is involved. Then verify the order in Shop Orders, not from the public receipt alone.

Common mistakes

• Do not assume a shop order is an event registration.
• Do not assume a confirmed rego means a shop order is paid or released.
• Do not promise delivery to a region unless the checkout offered a matching courier rate.
• Do not assume an item can be bought again if the buyer already reached a lifetime per-person limit.
• Do not hand over pickup items before the order is paid and ready for release.