The EZ-Links Interface works with Abacus 21's Legacy System Retail Point-of-Sale.

Setups (which must be manually kept in sync with the corresponding ones on EZ-Links) include the following:

• Directory Path where the EZ-Links 'Checked-In' Players are to be 'deposited'.
• Definition of the 'Courses' and their ProShop alignment.
• Batch job to 'populate' Abacus Members into EZ-Links.
• Item Codes (for POS) corresponding to the various Greens Fee Types that will come from EZ-Links (the rates themselves are 'inherited' from EZ-Links, and can vary within the same Item per transaction).
• Item Codes (for POS) corresponding to the other Charges (such as Cart Fees) that will come from EZ-Links (the exact fees themselves are 'inherited' from EZ-Links, and can vary within the same Item per transaction).
• A 'Default Item Code' to be used when the 'mapping' of Item Codes from EZ-Links to Abacus fails to find a match.

The Interface recognizes that not all Players in a TeeTime (Foursome) may check in at the same time.

• Whenever Player(s) check-in (to EZ-Links), a transaction(s) is written out to the Interface-Exchange file-records.
• The Abacus side of the Interface has a program that is constantly monitoring those files-records -- and when it notices a new entry, immediately converts it to an Abacus-related 'TeeTime Checked-In' file (for access by POS).
• At the Header Screen within Retail POS, the Counter Person can enter 'EZ' -- which immediately displays all Checked-In Players (and their respective TeeTime-Fee information).
  • This information is dynamically available to any/all POS Stations in a respective ProShop (cognizant of conflict control).
  • The Counter Person can 'tag' one or more of the Checked-In Players (including those spanning multiple contiguous or scattered TeeTimes) for 'transfer onto' the POS Ticket.
  • All such tagged Player TeeTimes are sucked into the POS Ticket -- adding lines to the Ticket.
    • Though typically done at the start of the Ticket, it can be done anytime (including after several Merchandise etc. Items have been added).  Similarily, normal sale Items can be added after the TeeTime Fees are dragged in.
    • The Lines that are created include the exact Time of the TeeTime (and the Player Name) -- along with the Price that was 'derived' from EZ-Links (despite whatever Price for the mapped Item that might have been set up in Abacus.
    • TeeTimes brought in in this matter can not normally be modified (Quantity or Price) -- and require a special privilege in this regard.

The EZ-Links Interface is a 'one-way street', meaning that information ONLY flows from EZ-Links to Abacus.

• Aside from a provision to initially 'populate' the 'Members' from Abacus into EZ-Links' Player file, EZ-Links has no capability of accepting 'dynamic' feedback (from Abacus-to-EZLinks).
  • Consequently there is no Member add/modify/delete re-fresh (after the initial 'population').
  • EZ-Links does not accept an acknowledgement back from Abacus POS that the Checked-In transaction was either picked up, still latent, accepted, or (POS) voided -- all of which technically should be communicated back to the TeeTime System.
  • Any change to a TeeTime (within EZ-Links) after Player check-in is not reflected to Abacus.

If interested, please call for further details.