WATPOS Backroom

WISL Transaction Based Lottery

WISL Transaction Based Lottery(TBL) consists of embellishments to existing register functions and interactive facilities that provide the capability to conduct transaction based lotteries. The ability to offer entry into a lottery based upon transaction attributes presents promotional opportunities and encourages return visits to the store.

• WISL Price Checker Feature

WISL Price Checker consists of inquiry software running on specialized inquiry devices and accessing the retail management data base and advertising material.

Specialized inquiry devices provide the platform for offering price checking and other targeted inquiry features directly to store customers. The benefits are more responsive customer service and a reduction in store staff requirements for handling such inquiries.

• WISL On Account Processing Feature

WISL has developed the infrastructure to integrate on account processing into WATPOS.

Initiated by specifying a specific tender type, the customer ID is prompted and an invoice record is generated. Upon completion of the transaction the invoice is sent to a printer or if WISL eREP is installed the invoice may be directly e-mailed. Payment may also be processed through WATPOS, initiated upon receipt of a cheque the invoice number(s) are prompted and the total reconciled as part of generating a payment transaction.

• WISL Electronic Content Integration Feature

WISL has developed the infrastructure to integrate internet based content into WATPOS. Electronic content may be initiated at the register with payment handled through the facilities of WATPOS. Currently the following services have been integrated:

• Follett eBook
• Cafe Scribe
• CourseSmart
• Vendor Supplied PINs
• Campus ebookstore

• WISL e-Store Interface Feature

WISL has developed the infrastructure to interface with a third party e-Store. Transactional update of WISL supported data bases is handled together with a capability to generate and transmit transaction related e-mails.

• WISL Customer Loyalty Management Feature

WISL has developed the infrastructure to manage a customer loyalty program within the framework of WATPOS. The salient features are:

• Loyalty points may be assigned on various parameters including store, department, class, subclass, SKU, time, date.
• Loyalty points may be assigned based on different tender types (ie - reward customers for paying with cash, debit card, or Institution Card vs. credit card)
• Customers may perform balance inquiry at POS or via the internet.
• Loyalty program database is populated from Institution provided data (name, ID, PIN).
• Controls are in place to prevent "stockpile" of points over time.
• Customers earn or redeem points at specified external vendors.
• The following is a typical sequence of prompts at in  WATPOS for each transaction:
•          "Are you a member of the loyalty program?" Yes/No
•          If Yes, customer data is entered and points are earned according to the system setup.
•          If No, "Would you like to join?" Yes/No
•          If Yes, account is activated by cashier, otherwise transaction continues
• At the end of each transaction, WATPOS will prompt "Do you want to redeem some points"? Yes/No
• The receipt reports the customer's points balance at each transaction
• In the case where a customer has declined to join the program, the receipt prints the number of points that COULD HAVE been earned through the program.
• Customers may earn points without having their program ID Card present
• Customers must have their program ID Card or other photo ID in order to redeem points
• Customers can change their email address online as well as opt in and out of receiving communications from the program. 
• Where an Institution card and interfaces exist, the points balance will be stored as an alternate balance on the Institution card, as well as in WATPOS. The Institution card balance will be the actual balance
•          All transactions and points rules will use the balance per the Institution card
•          If the interface is down, points from transactions will be held in an offline file until the interface is back up at which point the offline transactions will be processed
•          emails will be sent alerting of the offline transactions and when the offline transactions have been processed