The University of Waterloo Point of Sale System (WATPOS) was originally developed by the University's Information Systems Development Group and is now supported and exclusively marketed by Waterloo Information Systems Limited. WATPOS provides both Point of Sale and Backroom functions for a store environment. The Point of Sale portion runs on virtually any platform that affords browser based access with a touch screen display integrated with scanner, keyboard, card reader and receipt printer that provides sale transactions, returns, voids, payments on account, and etc. The Backroom portion runs on virtually any platform that affords browser based access, and provides reporting, data-transfer, and support functions for the Point of Sale devices.


Server: Open Systems

bulletUNIX; AIX, Solaris
bulletWindows Server
bulletLinux; Redhat

WISL Software Modules

bulletWISL Register Software

Third Party Software

bulletIBM’s UniVerse DBMS or other multivalue DBMS
bulletAccuSoft’s terminal emulation package – AccuTerm

WATPOS Backroom

There are a number of backroom procedures including the setting of various register parameters, maintenance of plu, department and other files, system interfaces and reporting that are grouped together in the WATPOS Backroom.

Summary of Features

bulletOn-line parameter updating and maintenance
bulletCustom receipt (slip) design
bulletDiscounting by item, department and/or transaction
bulletMultiple tenders in one transaction
bulletUp to 3 levels of taxation with optional compounding
bulletOn-line product inquiry
bulletEntry of line items by keyword
bulletA wide range of reports and reporting options
bulletMultistore capabilities


Available Optional Software Modules

bulletWISL 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.

bulletWISL 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.

bulletWISL 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.

bulletWISL 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:

bullet Follett eBook
bullet Cafe Scribe
bullet CourseSmart
bullet Vendor Supplied PINs
bullet Campus ebookstore
bulletWISL 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.

bulletWISL Customer Loyalty Management Feature

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

bullet Loyalty points may be assigned on various parameters including store, department, class, subclass, SKU, time, date.
bullet 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)
bullet Customers may perform balance inquiry at POS or via the internet.
bullet Loyalty program database is populated from Institution provided data (name, ID, PIN).
bullet Controls are in place to prevent "stockpile" of points over time.
bullet Customers earn or redeem points at specified external vendors.
bullet The following is a typical sequence of prompts at in  WATPOS for each transaction:
bullet          "Are you a member of the loyalty program?" Yes/No
bullet          If Yes, customer data is entered and points are earned according to the system setup.
bullet          If No, "Would you like to join?" Yes/No
bullet          If Yes, account is activated by cashier, otherwise transaction continues
bullet At the end of each transaction, WATPOS will prompt "Do you want to redeem some points"? Yes/No
bullet The receipt reports the customer's points balance at each transaction
bullet 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.
bullet Customers may earn points without having their program ID Card present
bullet Customers must have their program ID Card or other photo ID in order to redeem points
bullet Customers can change their email address online as well as opt in and out of receiving communications from the program. 
bullet 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
bullet          All transactions and points rules will use the balance per the Institution card
bullet          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
bullet         emails will be sent alerting of the offline transactions and when the offline transactions have been processed