Editing a product
Everything about one product, on two tabs: Details is what it is, and Variants is what you actually sell and what it cost you. The heading counts the variants so you can see at a glance whether it's sellable at all.
Listing
What the product is. The fields differ depending on where the product came from, and that difference is the important thing on this page:
| Field | Your own product | A catalogue listing |
|---|---|---|
| Title | Required — it's yours. | Title override, optional. Leave it blank and the catalogue name is used, so a card renamed at source stays correct on your shop. |
| Type, URL slug, Image | Yours to set. Choose and position image opens an editor: pick the file, drag to frame it, Zoom, and an Image shape that follows the Type. Use image uploads it at once; the product only points at it once you press Save product, and Remove likewise waits for the save. | Not shown. The catalogue supplies them, and letting a shop re-type them is how a card ends up filed under the wrong set. |
| VAT | Both. Standard rate unless the item is one of the few that is not: printed books are Zero rate. Every sale records the rate it was sold at, so changing this later never alters a past order. | |
| Sort order, Active, Featured | Both. Untick Active to pull it off the storefront while keeping it and its stock. Its page is then gone, not merely unlisted — an old link to it returns "not found", so nobody reaches it from a bookmark or a search result either. | |
Categories & filters
Which of your categories and filter options this product is tagged with — what shoppers use to narrow a grid, and what a discount can be scoped to. Build the options themselves under Filters.
Description
Your own copy about this product, in HTML. If your plan includes multiple languages you get a box per language; leave one blank to show nothing in that language rather than falling back.
Inventory protection
Only if your plan includes it, and only worth using on something that will be fought over. Two separate controls that work in opposite ways — one throttles the product, the other throttles the person.
| Field | What it does |
|---|---|
| Release batch | Expose only this many units at a time, holding the rest back. Blank releases everything at once. |
| Cooldown | How long to wait before the next batch is released once one sells out. Blank means 24 hours; the shortest this screen can express is an hour. |
| Max per customer | The most one account may ever buy online. Lifetime, not per order, and counted on orders that were actually paid. |
What drip release looks like from the shop floor
Say you hold five and set a batch of one. A shopper buys one, and then:
- Nobody can buy another — not the person who bought, and not anyone else. The cooldown belongs to the product, not to a customer, so it turns everyone away equally. (Turning away only the buyer is the per-customer cap's job.)
- Your stock still says four. That's the point — this is a throttle, not a sell-out, and your books are untouched.
- The variant row reads "Out of stock", because it reports the released ceiling rather than the stockroom. A scalper watching the page learns nothing about how many you really have.
- When the cooldown passes, one more goes on sale — a batch, not the backlog. The release runs on a nightly job, so a cooldown that expires at 3pm frees the next batch on that night's run, not the same afternoon.
Where the per-customer cap actually bites
Not at add-to-basket. A shopper who has had their one can still put a second in the basket; the refusal comes at the checkout review, where the line is marked and says Limit 1 per customer — naming the number, so they know what happened.
And it is a real stop, not a warning: the card box is not rendered at all while a review is unpayable, so there is nothing to pay with. Somebody else, meanwhile, can buy theirs perfectly normally.
Pre-order
A future release date turns the product into a pre-order, with the badge and date shown to shoppers and an optional Cancellation fee (%), which replaces the fee in Settings for this product; 0 uses the Settings fee. Neither is kept until the Cancellation fee in Settings is ticked for pre-orders. Collection in store only lives here too and is not only for pre-orders: tick it and the product cannot be posted, so an order holding it is collected — the checkout says so, and anything else in the same order is collected along with it.
Event requirements
Only if your plan includes Events. Sell this only to people who have been to your events. The product stays listed, in stock and priced for everyone; what changes is that a shopper who does not qualify sees your own sentence where the Add to basket button would be, and cannot put it in a basket by any route — not from the product page, not from a grid, and not by keeping it in a basket from before you set the rule, because the checkout checks again. Leave the whole panel blank to sell it to anyone.
| Field | What it does |
|---|---|
| Games that count | A tick-box per game, listing the games on your events exactly as you named them when creating events — nothing to type. Tick every spelling you have used — an event matches on its game name exactly as it was saved, so "MTG" and "Magic: The Gathering" are two different games here. |
| Events they must have attended | How many of those games' events a shopper needs under their belt. Blank or 0 turns the game rule off. A weekly night counts once per week attended, so "3" means three nights. |
| Within the last | How far back to count, from Any time through every month up to 24 months (2 years). Any time counts every night they have ever been to; pick a window and only nights inside it count, so a regular keeps their place and somebody who drifted away has to come back before they qualify again. It applies to the count above and not to the specific events below. |
| Or specific events | Tick particular events instead of, or as well as, a game count. Having been to any one of the ticked events is enough. If you set both a game count and specific events, a shopper must meet both. Type in Filter by title to narrow a long list — it only hides rows, so an event you have already ticked stays ticked and stays visible whatever you type. |
| What to tell someone who cannot order it | Shown in place of the Add to basket button, on the product page and in the mini-basket if they try from a grid. Leave it blank for a standard message. It is your text, so write it in the language your shoppers read — it is not translated. |
What counts as "attended"
A confirmed booking on a date that has passed, and — if you set a window — not longer ago than that. Nothing else. A ticket for next week's event does not unlock anything until the night has been and gone; checking somebody in on the league screen is not required, so this works whether or not you run a league. Bookings made before the customer registered, under the same email address, count too. A booking that was cancelled does not.
To give somebody credit for a night they came to, add them as an attendee on that event under Events › the event › Attendees — a night that has already run is filed under Past Events. Pick them out of your customers rather than typing a bare email, so the booking is on their account.
Letting somebody through anyway
On their customer record, tick Exempt from event requirements and Save changes. They can then order anything gated this way, without attending. Untick it to put them back behind the gate; it takes effect on their next page load, not their next sign-in.
Save, and delete
Save product commits the Details tab. Deleting is at the bottom, asks first, and takes the variants and their stock with it — if you only want it off the shop, untick Active instead.