Kapta · 15/09/2026
An integration project can specify different zone entitlements and re-entry rules. Before implementation, translate each product sold into an explicit access list: where the visitor can enter, for how long and how many uses are allowed.
How should general admission differ from an additional zone?
Map products or extras to access entitlements. A general admission ticket should not gain access to a restricted zone simply because its code is recognised. Test a basic product, an add-on and a package with several entitlements separately.
Does leaving allow the visitor to come back?
Define the commercial rule: no re-entry, same-day re-entry or a limited number of uses. If the decision depends on an earlier exit, specify how that exit is recorded. Without that event, the system cannot reliably infer whether the visitor remains inside.
What is anti-passback?
It is a rule intended to prevent another entry while an entitlement is still recorded as being inside. It needs a consistent model of entries, exits and exceptions. Specify and test it within the project, including groups and companions, before presenting it as an available feature.
Where should a multi-attraction operation start?
Create a matrix with products as rows and zones as columns. Add validity, usage allowances and re-entry rules to every authorised combination. Kapta can use this matrix to assess the FareHarbor–access connection and identify dependencies on existing software and equipment.
