The Tillee system consists of software that runs on a Windows-based POS, a site controller (either as a device or as a virtual machine), gateways and servers. The configuration server is used to define the POS functions, and this is downloaded to the site controller which acts as a local database in the store. The POS module communicates via the site controller and gateways to the external servers. The gateways act mainly as data switches but also have monitoring, maintenance and diagnostic support functions.
At the POS, the software transparently picks up barcode scans and receipt data and correlates products with barcodes so that promotions can be identified by barcode but validated by receipt records.
When a loyalty card is scanned the POS module captures it and prevents the POS software from receiving it. This makes loyalty scanning a simple in-line 'scan anytime' process that does not interrupt normal flow. A small popup on screen informs the operator of customer details and gives any promotion options.
As each receipt is processed Tillee can add promotional or loyalty messaging to the footer that is either predefined or obtained live from remote servers. This can include QR or 1D barcodes, graphics and text. Some loyalty programs offer live points updates, and some promotional schemes act according to product categorisation (e.g. buy a baby product, get a baby related promotion).
The POS software is compatible with a wide range of POS types. Typically the POS will use a roll-fed thermal printer such as the Epsom TM-T88 series printers. There are several models of printer driver use; Windows drivers, OPOS drivers, and direct POS output. If a POS can use the standard "Generic / Text Only" printer driver or write to a serial port directly then integration is a very simple process. Other cases can be supported but must be evaluated more fully.
If the POS uses sheet paper printers, such as laser printers, then we can provide a driver to use there too. There are some caveats on formatting and this needs to be evaluated on a case by case basis if receipt data must be collected.
For some POS types using unconventional technologies we can explore API solutions so that integration costs are minimal. This is also necessary if a program demands capabilities from Tillee that can only be fulfilled before payment but after the transaction is finalised; for example validating and immediately applying a discount due to qualifying items in the transaction.