Kapta · 15/09/2026
The system needs to know how many people each code can admit and how many have already entered. A booking-level code and a participant-level code require different rules; confirm the configuration using actual test tickets.
Does one QR code represent one person or the whole booking?
Do not infer that relationship from the ticket layout alone. Identify the object linked to the code and the participant types covered. A booking containing adults, children and a companion may need different entitlements. Admission decisions should use that information consistently.
Can only part of the group enter?
This can be a project requirement. Define how staff select the number entering, how the remaining allowance is updated and how the rest of the group uses the entitlement later. At a turnstile, authorisation should match the number of passages the equipment permits.
How can the whole booking be protected from accidental consumption?
Test one person arriving from a booking for four, followed by the others in two separate arrivals. The staff interface should clearly show the total, recorded uses and remaining allowance. Corrections should be traceable without deleting the history explaining the original decision.
What if some participants are cancelled?
Include changes to booking composition before and after partial admission. Define how entitlements are updated and how staff handle a change affecting someone already admitted. Kapta can scope the workflow around your actual group rules, avoiding assumptions that every booking is individual.
