Introduction

This document outlines the operation of Age Validation by Product within the Intouch system.
The following areas are covered by this document:

  • Resources: Setup of Age Group Dates and Age Group Rules, and the linking of Age Group Rules to Products.
  • SalesPoint: Calculation and display of age range and other guest details.
  • SalesPoint: Age Validation by Product.
  • ResPoint: Age Validation by Product.

Table of Contents

Overview Age Validation by Product allows the sale of certain products to be restricted based on the age of the guest.
Age validation can take two forms:

  • Display as a warning but allow the sale to continue, or
  • Display as an error and do not allow the product to be sold.


The guest's age can be calculated on:

  • The Day of Sale,
  • The Date of First Validity (the date of the event),
  • A Specific Date (i.e. 31 December 2017),
  • A Relative Date (28 August - in the current year / season).


Setup in Resources

The setup - in Resources - consists of three parts:

  • Maintain Age Group Dates: Define the specific or relative dates required by the age validation system.
  • Maintain Age Group Rules: Define the age validation rules. The elements that can be specified include:
    • The required action - display as warning or error,
    • The text shown when validation fails,
    • A minimum and maximum age range,
    • The age calculation method: date of sale, date of first validity or age group date.
  • Link Age Group Rules to Products: Specify which rules apply to which products.


Maintain Age Group Dates

When a specific or relative date is required by the age validation system. It is first defined as an Age Group Date. This date can then be linked and used by multiple age group rules.
Age Group Dates are maintained on the Setup tab page of Resources - in the Define area:

On this page you can add, edit and delete Age Group Dates.
To create a new Age Group Date:

  1. Select the Add menu item.
  2. The Add New Age Group Date form is displayed.
  3. Enter a (unique) description and any general notes that apply to this date.
  4. Specify the type of date. This can be either a Specific date or a Relative date
  5. If the date is Specific - press the Date edit field drop-down button, and select the required date.
  6. If the date is Relative - you must specify the day and month of the Relative Date, as well as the day and month for the Relative Date Cut Off.

    Press the calendar button, and select a date containing the required day and month. 
    Note: For the purpose of a relative date, the year is ignored.

    Further information on how relative date's work can be found below in the 'What is a relative date?' and 'How does Relative Date work, compared to Specific Date?' sections below.
  7. Press the Save button and the newly added Age Group Date is displayed.


What is a relative date?

A relative date allows the same day and month to be used to calculate the guest's age each year or season. For example: the age of a guest on 1 June, in the current year, may be required. Alternatively, the start of the ski season may always occur on the 1 November every year or the start of summer activities may always commence on 1 April.


The Relative Date Cut Off tells the system whether to work out the guest's age based on the day and month of the current year or the next year.

How does Relative Date work, compared to Specific Date?

The following examples demonstates the different between relative and specfic dates.
Peter's birthday is 1 May 2000.
Example 1: Specific Date = 1 July 2017.
Because this age range date is specific - we ascertain Peter's age on this (specific) date.
So Peter's age is 17 Years and 61 days - on this date. This is the age used by the system regardless of when the check is undertaken.

  • On 1 Jan 2017 - Peter's age is calculated as 17 Years and 61 days (on 1 July 2017)
  • On 31 Dec 2017 - Peter's age is calculated as 17 Years and 61 days (on 1 July 2017).
  • On 1 Jan 2018 - Peter's age is calculated as 17 Years and 61 days (on 1 July 2017).


Example 2: Relative Date = 1 July. Relative Cut Off = 31 December.
Because this age range date is relative - we ascertain Peter's age relative to the current year (season), which is derived based on the relative cut off (and the current date).

  • On 1 June 2017: Peter's age is 17 Years, and 61 days (calculated based on Peter's age on 1 July 2017).
  • On 31 Dec 2017: Peter's age is 17 Years, and 61 days (calculated based on Peter's age on 1 July 2017).
  • On 1 Jan 2018: Peter's age is 18 Years, and 61 days (calculated based on Peter's age on 1 July 2018).


Example 3: Relative Date = 1 July. Relative Cut Off = 30 September.

  • On 1 June 2017: Peter's age is 17 Years, and 61 days (calculated on 1 July 2017).
  • On 31 Dec 2017: Peter's age is 18 Years, and 61 days (calculated on 1 July 2018).
  • On 1 Jan 2018: Peter's age is 18 Years, and 61 days (calculated on 1 July 2018).


Example 4: Relative Date = 1 July. Relative Cut Off = 30 June.

  • On 1 June 2017: Peter's age is 17 Years, and 61 days (calculated on 1 July 2017).
  • On 31 Dec 2017: Peter's age is 18 Years, and 61 days (calculated on 1 July 2018).
  • On 1 Jan 2018: Peter's age is 18 Years, and 61 days (calculated on 1 July 2018).
  • On 1 April 2018: Peter's age is 18 Years, and 61 days (calculated on 1 July 2018).


Example 5: Relative Date = 1 July. Relative Cut Off = 30 March.

  • On 1 June 2017: Peter's age is 18 Years, and 61 days (calculated based on on 1 July 2018).
  • On 31 Dec 2017: Peter's age is 18 Years, and 61 days (calculated based on on 1 July 2018).
  • On 1 Jan 2018: Peter's age is 18 Years, and 61 days (calculated based on on 1 July 2018).
  • On 1 April 2018: Peter's age is 19 Years, and 61 days (calculated on 1 July 2019).


Maintain Age Group Rules

In Age Group Rules we define the age validation rules used by the system.
Age Group Rules are maintained on the Setup tab page of Resources - in the Define area:

On this page you can add, edit and delete Age Group Rules.
To create a new Age Group Date:

  1. Select the Add menu item.
  2. The Add New Age Group Rule form is displayed.
  3. Enter a (unique) description and any general notes that apply to this rules.
  4. Enter the 'Display Text' that should be shown to the operator or guest when the age group rule fails the age validation.
  5. Specify the age range that applies to this rule.
    Note: Either Minimum or Maximum can be left blank if appropriate (i.e. must be under 12 or move be 65 and over).
  6. Check the 'Use Rule in Age Range Calculation' if the rule is to be used work out the age range of a guest - as displayed on the sales screen in SalesPoint - see the Display Age Range (and other details) against Person in SalesPoint section for further details.
  7. Select a Scanning Pass Status if this rule is to be used by Scanload when calculating a guest's age range - see the A Note on the Use of Age Group Rules in Age Range Calculation section for further details.
  8. In Validation Action - specify what action is required when validation fails:
    1. Display as Warning … and allow the sale to continue, or
    2. Display as Error … and do not allow the sale to proceed.
  9. In Validation Based On - specify what type of date validation must be based on:
    1. Date of Sale
    2. Date of First Validity (the date of the event / activity).
    3. Age Group Date (a specific or relative date).
      Note: You are required to select and link an age group date to the rule.
  10. Press the Save button and the newly added Age Group Rule is displayed.


A Note on Age Range Validation

There are three basic types of age ranges:

  • A span: i.e. must be 12 - 13 years of age.
  • A minimum: i.e. must be 65 and over.
  • A maximum: i.e. must be under 16.

It is important to understand where a minimum starts and a maximum ends. Let's take the 12-13 age range as an example:

  • On the day before their 12th birthday they cannot purchase (11 years, 11 months, 30 days).
  • On their 12th birthday they can purchase (12 years, 0 months, 0 days).
  • On the day before their 14th birthday they can purchase (13 years, 11 months, 30 days).
  • On their 14th birthday they cannot purchase (14 years, 0 months, 0 days).


If we express this in terms of minimum/maximum in years and months we get - Min: 12 years 0 months / Max: 13 years 11 months. As an operator might not realise that this is the case, the system automatically treats a maximum age entered as only a year, as to the end of that age.
Consequently - our three examples can be entered as:


A Note on the Use of Age Group Rules in Age Range Calculation

As detailed above, the Edit Age Group Rule form contains an Age Range Calculation section.

The 'Use Rule in Age Range Calculation' checkbox controls whether the rule is used when working out the age range of a guest - as displayed on the sales screen in SalesPoint. Please see the Display Age Range (and other details) against Person in SalesPoint section for further details on this feature.
The 'Scanning Pass Status' field specifies controls whether Scanload must use this age group rule to calculate a guest's age range, when returning the OK status of a pass.
Scanload is responsible for verifying whether a pass is valid for use. It returns this result to a gate or associated mobile device (i.e. iPad). When an OK result is obtained (i.e. the pass is valid for use), Scanload also returns the 'age range' of the guest (when available) for display by the gate or mobile device. Typically this is returned as: OK (pass status id = 1 = no age / pass type was found), OK - Adult (id = 2), OK - Child (id = 3), OK - Youth/Teen (4), or Senior (5).
Scanload applies the following rules when obtaining the OK status of a pass:

  • The system will look for the first instance, where the guest's date of birth falls within the min/max age range of the rule.
  • If a rule is found, then the pass status linked to the rule is returned.
  • If a rule is not found, then the previous hard coded logic is used, which calculates the pass status based on the pass_type saved against the pass in the database: adult = 2, child = 3, youth or teen = 4, and senior = 5.


Note: If modifications are made to the linking of pass statuses to age group rules, then a restart of Scanload is required for the changes to take effect.

Link Age Group Rules to Products

The age validation rules that apply to a product are specified on the Age Group Rules tab page of the Edit Product form.

On this page, you can add, edit and delete the Age Group Rules linked to the Product.
To link an Age Group Rule to a Product:

  1. Select the Add Age Group Rule menu item and the Select Age Group Rule form is displayed.
  2. Select a rule and the Add Product Age Group Rule form is displayed.
  3. Specify whether the rule applies:
    1. Onsite (i.e. in SalesPoint and ResPoint).
    2. Online (i.e. on the client web site).
  4. Press OK and the rule is displayed linked to the Product.

The following should be noted:

  • Links are not saved until the Save button or the Prev / Next button is pressed on the Edit Product form.
  • An Age Group Rule can be linked to multiple Products.
  • Multiple Age Group Rules can be linked to a single Product.
  • The same Age Group Rule cannot be linked to the same Product multiple times.
  • When multiple Age Group Rules are linked to a Product, only one rule must be met for the product to be allowed to be sold.
  • Deleting a Product automatically deletes any links, but leaves the actual Age Group Rules untouched. The same logic applies when deleting an Age Group Rule.
  • When you copy / paste a product, and the product has linked age group rules, you are asked if you want to paste the age group rules to the new product.


Display Age Range (and other details) against Person in SalesPoint

The details displayed against a person on the Sales screen is configurable via the Manager setting: SalesPoint - Program Features | Guests | Person Details Display.
Five options are available:

  • A = Age Range,
  • D = Date of Birth,
  • G = Gender (text),
  • N = Gender (initial),
  • C = Gender (icon).

Default = AG = Age Range and Gender.
See Settings Maintained via Manager - for SalesPoint: for further details.
The following example shows the display for Age Range, Date of Birth and Gender icon (ADC):

The following example shows the display for Gender (text) and Age Range (GA):

Note: Elements are only show where the associated element (i.e. date of birth or gender have not been captured for that guest.
The Age Range (text) associated with a person is derived by applying the following logic to the guest's date of birth:

  • Ascertain if the guest's age falls within the min/max values of an Age Group Rule flagged for use in age range calculation. Note: rules are checked in display order.
  • If a matching rule is found, then the description of the age group rule is used as the guest's age range.
  • If a matching rule is not found, then the following (hard coded) age ranges are used:
    • <= 12 : Child,
    • 13-18 : Youth,
    • 19-64 : Adult,
    • >= 65 : Senior.


Age Validation in SalesPoint

Age Validation is applied in SalesPoint when:

  • Adding a product to a guest - via selection, lookup, scanning or drag and drop.
  • Adding a guest to a product - via guest card/pass scan or lookup by guest.
  • Switching to the Payment Screen.
  • Selecting Save and Clear.


It should be noted that the system does not attempt validation until the guest and the product are linked. In addition, the system does not attempt to apply validation in every possible sequence where a product and guest are combined, rather it applies validation in the common paths, then allows Switch to Payment and Save & Clear to ensure validation occurs before sale finalisation.

Age Validation Error

The following sequence demonstrates an Age Validation Error.

  1. Guest John Smith is added to the sale, via card scan or guest lookup.
  2. The operator selects to add a product to the guest, which requires the guest to be 12-13 at the time of sale, where the age group rule is configured in Resources as an error.
  3. As the guest does not pass this age validation rule, an Age Validation Error message is shown.
  4. The operator selects the OK button, and the product is NOT added to the sale screen. This product cannot be sold to this guest.


Age Validation Warning

The following sequence demonstrates an Age Validation Warning.

  1. Guest John Smith is added to the sale, via card scan or guest lookup.
  2. The operator selects to add a product to the guest, which requires the guest to be 12-13 at the time of sale, where the age group rule is configured in Resources as an warning.
  3. As the guest does not pass this age validation rule, an Age Validation Warning message is shown. In this case, the operator must decided whether the sale can proceed.
  4. If the operator selects No, the product is not added to the sale.
  5. If the operator selects Yes, the product is added to the sales screen, with an 'Age Warning' modifier against the sale line.