This document is designed as information for Epos providers who have been asked by a mutual client to integrate their systems with IndiCater or for IndiCater clients who want more info before approaching their Epos provider.
Benefits of an EPOS Integration
The Client will benefit from an Epos integration by their Outlets not having to manually enter their sales data into IndiCater (where it can be used in Profit reporting), and also to ensure that this income data is recorded accurately.
Additionally, the Client will be able to use the sales data in conjunction with their use of the IndiCater Recipe module to identify unexplained stock loss, and also the automatic calculation of theoretical margins.
Depending on the functionality of the Epos provider, the recipe data in IndiCater can be made available to the Epos system through the IndiCater API so that allergen data can displayed from the terminals in order to satisfy customer queries at point of service (see also the Allergen Compliance Fact Sheet for other allergen sharing solutions).
The default and most cost effective method for integration is via an API. The Epos provider can either use the IndiCater API to push their sales data to or IndiCater can pull this data from the Epos providers API. Additionally, with regards to allergens, IndiCater can make our API available to the Epos provider for them to pull the data from. Alternatively, a bespoke integration can be developed with data being transmitted to the Epos provider’s FTP or SFTP.
Both parties need to mutually agree the best method for mapping of Outlets, sales categories etc., but the key link between the Epos and IndiCater is the PLU reference for each sales item. For the Client, if there is a single PLU for the same product across all their Outlets then a single recipe dish can be created by the customer in a central recipe bank – alternatively if there is a different PLU for the same sales item in multiple outlets then they will need to create multiple recipes. Most Epos companies integrated with IndiCater act as the Master for the PLU, though some clients prefer IndiCater to be the Master by creating the PLU in the recipe as well as VAT tagging, kitchen printer data etc., and then transmitting this data to the Epos company.
To help us understand how the EPOS company currently works please supply the information below. We will then arrange a call to discuss and agree the scope of the integration project and the most appropriate method. We’ll then create a project scope document to share with the client and Epos provider with an indication of costs.
EPOS Supplier Information
Client company name
EPOS company name
Technical contact name, email address and telephone number
Account Manager name, email address and telephone number
- How many terminals in total?
- Are there any mobile devises that are linked to fixed terminals?
- Is a PLU the same for the same product in different Outlets?
- Are customer discounts used in transactions?
- Does the Epos company 24-hour period differ from yours?
- Will there be any open checks at then end of a day that won’t be transmitted?
- Will PLUs always be unique (i.e. not reused if archived)?
- Is any wastage data recorded on Epos?