# Ticket threshold setup and buyer-view check card

Fill this in before changing a live offer. The card records configuration and observed display; it does not recommend a price or predict how a platform handles earlier orders.

| Field | Planned value | Observed / owner |
| --- | --- | --- |
| Event and ticket type | ____ | ____ |
| Mechanism | Price rule on one type / later type becomes visible / other: ____ | ____ |
| Provider and control used | ____ | ____ |
| Trigger unit | Tickets sold / tickets remaining / date / other: ____ | ____ |
| Threshold and current count | ____ / ____ | ____ |
| Current buyer-visible offer | Ticket name: ____  Price: ____ | Confirmed: ____ |
| Intended next buyer-visible offer | Ticket name: ____  Price: ____ | Confirmed: ____ |
| Other conditions | Sale window: ____  Visibility/access: ____ | Confirmed: ____ |
| At transition, signed-out buyer page | Name: ____  Price: ____  Availability: ____ | Checked by/time: ____ |
| Overlap or missing offer | None / describe: ____ | Fix owner: ____ |
| Started checkout or earlier-order behavior | Provider documentation reviewed / unknown | Follow-up owner: ____ |

If the buyer view differs from the plan, stop additional edits until the assigned owner checks counts, rule order, visibility and sale dates. Keep any real buyer or order details in the approved ticketing system, not on this card.