Tickets & admissions
An admission product sells entry rather than an object: a workshop place, a cinema seat, a museum day pass, a ten-visit climbing card. Each paid ticket becomes a pass with its own code. Capacity is held per event, so a product can carry a Saturday matinee and a Sunday evening performance with different seat counts, and each sells out separately.
Plans: All plans
Prerequisites
Section titled “Prerequisites”- A product whose primary commerce kind is Admission, with a price.
- At least one event. An admission product with no event has nothing to sell.
- Nothing else. Admissions are a base feature on every plan.
Set up an admission product
Section titled “Set up an admission product”-
Create the product under Catalog → Products and set its price.
-
In the Commerce panel, set the primary kind to Admission.
-
Set Inventory mode to Capacity (events / seats) and Decrement on to Redeem.
-
Fill in the admission policy:
Field Required Notes Pass type Yes Single entry, Multi-entry, Timed session, or Open day Max redemptions For multi-entry How many entries the pass is worth. Minimum 1 Duration (minutes) For timed sessions How long the session lasts. Minimum 1 Require attendee name No Asks the shopper for a name per ticket at checkout -
Save admission policy.
-
Add the events, one row each:
Field Required Notes Starts at Yes Date and time Capacity Yes Seats or places. 0 means none available Name No A label the shopper sees, such as Saturday matinee -
Republish the product.
The four pass types
Section titled “The four pass types”| Pass type | Admits | Typical use |
|---|---|---|
| Single entry | Once | A concert, a one-off workshop |
| Multi-entry | Up to Max redemptions times | A ten-visit card, a five-class pass |
| Timed session | Once, for Duration minutes | A 90-minute escape room, a swim slot |
| Open day | Once, any time on the event’s day | A museum day pass |
What happens when a ticket is bought
Section titled “What happens when a ticket is bought”Once the order is paid, MyShopie issues one pass per ticket: three tickets on one order produce three codes, not one code with a quantity of three. The passes land in the customer’s account and in the order’s own record, and the codes are what gets scanned.
If Require attendee name is on, the name captured at checkout travels with the pass, so the door list shows who each ticket belongs to.
Checking tickets at the door
Section titled “Checking tickets at the door”Open the POS app’s admission screen and scan or key in the pass code. The response is one of three things:
- Accepted — the pass is valid and had redemptions left; one is counted.
- Already redeemed — a single-entry pass that has been used, or a multi-entry pass with no redemptions left.
- Not found — the code does not belong to this store.
Redemption is a server-side check, so two staff members scanning the same code at two doors cannot both let the holder in.
Field reference
Section titled “Field reference”| Field | Scope | Effect |
|---|---|---|
| Pass type | Policy | How many entries and on what basis |
| Max redemptions | Policy | The redemption budget of a multi-entry pass |
| Duration (minutes) | Policy | Session length for timed sessions |
| Require attendee name | Policy | Collects a name per ticket at checkout |
| Starts at | Event | When the event begins |
| Capacity | Event | How many passes the event can sell |
| Name | Event | The label the shopper picks from |
| Inventory mode | Product | Must be Capacity for events to limit sales |
| Decrement on | Product | Redeem counts the entry at the door |
Common problems
Section titled “Common problems”The product cannot be bought. It has no event, or every event’s capacity is zero or sold out.
The event does not appear on the storefront. It starts in the past, or the product has not been republished since the event was added.
A ten-visit pass is refused on the second visit. The pass type is Single entry. Change it to Multi-entry and set Max redemptions.
Capacity is not going down. That is correct for Decrement on → Redeem: the count moves at redemption. Issued passes are tracked against the event’s capacity separately, so the event still sells out.
No attendee names on the door list. Require attendee name was off when the tickets were sold. Turning it on now affects only new orders.
How is a ticket’s stock controlled? By the event’s capacity, not by a stock count. Set the product’s inventory mode to Capacity and give each event a capacity; the event sells out when that number of passes has been issued.
What does a multi-entry pass do? It allows more than one redemption from the same code. Set the pass type to Multi-entry and the maximum redemptions to the number of entries the ticket is worth — a ten-visit pass is max redemptions 10.
Can I collect each attendee’s name? Yes. Tick Require attendee name on the admission policy and the shopper is asked for a name per ticket at checkout.
How is a ticket checked at the door? Scan or key the pass code into the POS app’s admission screen. A valid, unredeemed pass is accepted and the redemption is counted; an already-used single-entry pass is refused.
