You are being given this document because Fidelity are supplying an EPoS Solution to the organisation you support. This document aims to provide you with two things:-
- Essential information that will be required to allow a successful implementation of the Fidelity EPoS solution
- Information you will require to assist with the ongoing use of the system.
What Fidelity Supply
Fidelity supply POS Software and Back Office software that is written in house and POS Hardware sourced from leading UK POS Hardware suppliers. Fidelity also integrate with third party systems for solutions such as ordering and EFT payments.
Software that runs on the point of sale hardware
Total Control Premier (TCP)
Back of house software for product maintenance and reporting analysis
Instant CRM/Instant Loyalty (CRM)
Back of house software that provides Loyalty/Cashless/Membership functionality
Cloud hosted data analysis system
Bartender Automation Edition
Written by Seagull Scientific but supplied by Fidelity. Used for label production.
Third Party Integrations
Cloud Based Cashless Payments + Voucher rewards
Cloud Based Cashless Payments
Site Based Cashless Payments
Site Based Cashless Payments
Cloud Based Cashless Payments
Cloud Based Cashless Payments
Cloud Based Cashless/Loyalty Payments
The Fidelity EPoS Solution uses a Microsoft SQL server. This can be either a full version or the express version depending on the size of the system being installed.
An ‘Application Server’ will be defined that runs Services used for many functions. This is strongly recommended to be a server but can be on a desktop PC for a small system.
The POS Terminals communicate with each other via a bespoke protocol and to the database via the Application Server using a bespoke protocol. This is all done via TCP/IP. Static IP addresses are required for all POS terminals and the ‘Application Server’.
This specification is based on one server providing both Application Roles and hosting the SQL database. It is based 20 POS terminals and 5 client PC’s.
OS: Server 2008R2
.Net Framework 4.7.1
SQL: SQL Server 2008R2 (Express can be used however it has a 10gb Database limit)
CPU Type: Xeon (Quad Core)
CPU Speed: 2.0Ghz
DATA DISK: Separate HD for Data AND Separate HD for Log (50-100GB) (SSD?)
Requires a static IP address - manually assigned or DHCP reserved IP
Windows Server 2012 R2 or later
Intel Xeon Quad Core 2.8ghz
Raid 1 Array for the OS
Raid 5 Array for the Data
Client PC Requirements
A network connection to the SQL Database
Supported Operating systems:-
- Windows 7 All editions 32/64bit
- Windows 8/8.1 All editions 32/64bit
- Windows 10 32/64bit
- Minimum Version 13 Build 14
Microsoft .NET Framework
- Total Control Premier – .Net Framework 4.7.1
- Instant CRM - .Net Framework 3.5
POS Terminal Requirements
A standard installation requires:-
- One Ethernet port
- Static IP address - manually assigned or DHCP reserved IP
- 3 Power sockets (POS Terminal, Receipt Printer, Chip and Pin) – we strongly advise against the use of 4- way extension blocks
- VNC access from the server
As part of our support agreement we require the ability to access the system remotely. Our preferred method is either a VPN connection allowing us access or via Logmein Rescue. We are happy to adhere to local policies and all remote support sessions are logged against the relevant support tickets.
We also require VNC access from the entry point (e.g. application server) to the POS terminals.
Other methods can be discussed and agreed upon between yourselves and Fidelity’s Support Manager.
Ports Used – Fidelity Applications
Application and direction
For activating software licences
Communication to other GPoS Terminals
GPoS to App Server – Job Controller Service
Posting of sales data and send of programming updates
GPoS to App Server – Customer Accounts Service
Customer Accounts Transactions
GPoS to App Server – GPoS Loyalty Service
Instant CRM Customer lookup and transactions
TCP Client to SQL Database
Back of House Clients opening the SQL database
Default 1433 but can be specified as part of the connection string
Remote assistance (Internal Only)
Default 5900 – can be changed
Sending of e-mails to suppliers and sending reports via e-mail
Skorpio HHT / MISCommunicator Service
Handheld stock terminal – Communicates to the TCP Application server over WiFi – can be via a host desktop PC but this method
Ports Used – Third Party Applications
Where integration is used and not covered by this table additional information will be provided.
Software Licencing and de-licencing
How Fidelity Software is Licenced?
Fidelity software is licenced using a per client model. Each POS Terminal/PC to run the software will have a unique software licence code per application. This is tied to the hardware during registration and should be deactivated prior to disposal of any hardware or re-imaging of hardware. A service called ‘Fidelity Licencing Service’ is installed on each PC running Total Control Premier to provide low level hardware access for this.
If you intend on hosting a Fidelity application in a terminal services environment you should ensure that a user licence is purchased for each intended concurrent connection.
Installing and Activating Fidelity software
Fidelity software packages use a major minor version system e.g. x.x.yyyy x.x is the major version and xxxxx The major version must match the version of the database being used and all clients must be running the same major version. We would advise checking other client pc’s for the version or if in any doubt to speak to Fidelity.
When installing TCP on a back of house PC you do not need to install Microsoft SQL Server, if prompted as a pre-requisite answer yes to it being a pre-requisite and then No to installing it. From TCP version 2.06.xxxxx onwards SQL is not included as part of the installer. The Instant CRM Installer doesn’t include SQL Server.
How to activate:
Tick the box alongside the Package that you wish to activate.
Click next and you are prevented with a box to enter the serial number you have been provided with (8 digits). Un-tick the ‘Activate now using my Internet Connection’ box and click next
The next screen displays a long KeyNumber and a box for an activation code to be entered into. Click on the black surrounding the key code it will copy it to windows clipboard. This can be pasted into a file which can be emailed to our support team at email@example.com or it can be pasted directly into an e-mail.
Fidelity will then return an activation code to you which needs to be entered into the box below the key code (it can be pasted back in if required).
Once the code is entered click next and you will then get the message "Thank you for purchasing a fidelity product." If this errors you may need to check that you have the correct package selected and the activation code is correct.
- The key codes issued are only valid for the day they are issued on.
- Fidelity support are available 9:00 to 17:00 Mon-Fri for manual activations and aim to respond within 15 minutes of a request being received.
When running Total Control Premier for the first time you will be prompted to setup a connection to the database. We would recommend copying a TCpConnections.xml file off an existing workstation into the C:\ProgramData\Fidelity Systems\Total Control Premier folder.
Removing a Fidelity Licence from a PC
Navigate to the 'Activate Fidelity Software' application. This is found within the software’s 'Program Files' folder, accessible via the Windows start
For Example in the case of TCP, GPOS, Or CRM the activation wizard can be found in the
- TCP - Start Menu > All programs > Fidelity Systems > Total Control Premier > Activate Fidelity Software.
- CRM - Start Menu > All programs > Fidelity Systems > Instant CRM > Activate Fidelity Software.
- GPoS - Start Menu > All Programs > Fidelity GPOS > Activate Fidelity Software
Note:- TCP and CRM use V2 of the registration wizard. GPoS cannot be activated successfully using V2.x
Make sure the Software package you wish to de-licence is ticked, click 'Next' at which point you
should see the screen below:
There are now two options:
- Offline Deactivation – You should use this
- Online Deactivation – Not available to End Users
On Selecting Offline, The Registration Wizard will progress to a screen displaying the Removal Key
The key code *MUST* be sent to Fidelity, in order for them to reactivate the code for use on
another device. After transmitting this to fidelity, the code will be verified and the licence flagged to
allow reactivation on another device.
The preferred method of sending this is to E-mail it to firstname.lastname@example.org
To copy the code into an e-mail you have two options
- Copy the file to Clip Board, This can be done by clicking on the area containing the Key code. You can paste the code into an email.
- Save The Removal Code -It will give the option to save the removal code in the form of a Fidelity Token file (a .TOK file), this can then be e-mailed to Fidelity.
When removing TCP we also recommend taking a copy of the TCPconnections.xml file found in C:\ProgramData\Fidelity Systems\Total Control Premier to be re-used on a replacement PC.
Deactivating a PC that will not Boot
When a PC will not boot, it is still possible for us to deactivate the Licence and Flag it for reactivation.
In order to do this we require the Hard Drive’s physical serial number, which we validate with our
If the serial number provided DOES NOT Match an activation on our records or the code cannot be provided, we will NOT be able do a manual void of a licence and a new Licence would need to be purchased!
If Bartender is being used for label production, you will also need to deactivate it. This is done by loading Bartender and going to ‘Help’ then ‘Activation Wizard’. This is an online deactivation that does not require authentication.
There may also be label files stored on the PC, these will need copying off to be re-used again. The default location for these would be C:\Program Files (x86)\Fidelity Systems\Total Control Premier\Labels.
The Automation Edition of Bartender is required, and Bartender version 9.1 onwards is supported. If using Bartender version 9.x or 10.x you will need to enable Bartender compatibility mode from within Total Control Premier’s General Options
Appendix A – Verifone Transaction Flow