Write two separate decisions
A fictional workshop might need four paying participants to be worthwhile but have only eight usable workstations. Four is an operating threshold; eight is a resource limit. Combining them into one setting obscures what should happen before the threshold is reached and after the limit is reached. Describe both in customer-facing language so someone does not mistake an early reservation for an unconditional promise that the session will run.
Treat status as part of the promise
Trafft’s settings documentation describes pending behavior for group bookings when a minimum above one has not yet been reached. That is a documented concept, not a confirmation of your notification or payment configuration. Decide what the customer should be told while the session is pending. Avoid writing a confirmation message that promises a definite session if the operating process still allows cancellation for insufficient attendance. Review the actual wording alongside the status rules.
Test the threshold transitions
Prepare fictional headcounts just below, exactly at and above the minimum, while remaining below the maximum. Then test the last available seat and an extra participant. State which transitions should change status and which should reject attendance. Finally remove a participant after the minimum was met. The behavior after a reduction is a separate question; do not assume that the initial threshold logic proves every later change behaves appropriately.
Keep policy and software aligned
Decide who contacts participants if a session cannot proceed and how any payment or refund process is handled under your established policy. This guide does not prescribe legal terms or claim a particular automated refund behavior. The practical requirement is consistency: the advertised class, booking status and staff instructions should describe the same commitment. If that consistency cannot be established, do not hide the uncertainty behind a generic booking-success screen.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Trafft booking settings — Merchant documentation · trafft.com · Merchant-controlled · checked 2026-09-23
- Trafft resource allocation — Merchant documentation · trafft.com · Merchant-controlled · checked 2026-09-23