EPoS for Food-To-Go

Fast, intuitive pre-order, PoS, self-serve, payments and more…

Speed of service is critical for any food-to-go or quick service restaurant. A reliable and intuitive EPoS system that helps you process fast-paced sales and deliver high-quality products as quickly possible should be at the heart of your business.

Whether you are looking to keep a traditional manned till service or introduce a self-service, cashless environment, we have the best solutions to suit your unique business. We offer advanced EPoS (LollyPoS ) and self-serve PoS (LollyServe ) options. Our cloud-based software can be downloaded onto tills, kiosks, and tablets and integrated with secure, cashless payments – delivering systems that are attractive, easy to use and help increase footfall, whilst maximising your profits.

Beyond PoS, the Lolly Kitchen Management System (KMS) delivers real-time, seamless communication between front of house and kitchen/prep areas. Our dependable pre-order and delivery options ensure you can boost sales, as well as increase engagement and communicate with customers through a custom LollyLoyalty scheme.

Together, our seamless, end-to-end PoS and payment solutions help you create an enjoyable order and purchasing journey – bringing customers back time and time again to experience your service and food.

Improve staff to kitchen communication – linked LollyPoS and Kitchen Management System.

Easy updates – keep your menu up to date with seasonal dishes, daily specials and nutritional information.

Clear displays and intuitive software prevents staff or customer self-serve errors and saves time.

Accessible pricing – reliable hardware and software to rent or buy at affordable rates.

Keep track with back-office functionality and real-time reporting, including security features.

Reach new customers with our pre-order and delivery offerings. Retain them with our loyalty scheme.

“We met with an array of EPOS solution providers, large and small. Lolly’s system was superior on every count both front and back of house. The implementation from the Lolly team was equally as impressive – making our lives easier so we can get on and focus on quality food. They have a driving passion for new EPoS technologies and better customer service – bringing the future to the present.”

Dee Thaya, Founder at Flipside

HOW CAN WE HELP?

GIVE US A CALL ON:

0800 038 5389

FUNCTION PROVIDER	COOKIE NAME	DATA STORED	PURPOSE	DURATION
itslolly.com	_grecaptcha	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	To Distinguish between human visitors and bots	Persistent
	moove_gdpr_popup		Cookie set by the UK cookie consent plugin to record that you accept the fact that the site uses cookies.
	olfsk	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	Th is cookie is necessary for the login function on the web site.	2 Years
	hblid	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	Identifies the visitor across devices and visits, in order to optimize the chat-box function	2 years
	wcsid	Works by creating a unique id (UID) for each session and stores variables based on this UID.	A session identifier to keep track of a single chat session	Session
	_ok _okbk _okcs _okdetect _oklv	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	Identifies the visitor across devices and visits, in order to optimize the chat-box function	Session
	_okck	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	Identifies the visitor across devices and visits, in order to optimize the chat-box function	1 day
	_okdetect	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	Identifies the visitor across devices and visits, in order to optimize the chat-box function	Persistent
google.com	_GRECAPTCHA rc::d-#	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	To Distinguish between human visitors and bots	Persistent
	rc::a rc::b rc::c	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	To Distinguish between human visitors and bots	Session
doubleclick.net	test_cookie	Works by creating a unique id (UID) for each visitor and stores variables based on this UID.	To check if the user's browser supports cookies	1 Day

Host	COOKIE NAME	Purpose	DURATION
itslolly.com	_dc_gtm_UA-#	Used by Google Tag Manager to control the loading of a Google Analytics script tag.	1 day
itslolly.com	_ga	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.	2 Years
itslolly.com	_ga_#	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.	2 Years
itslolly.com	_gid	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.	1 day
itslolly.com	collect	Used to send data to Google Analytics about the visitor’s device and behavior. Tracks the visitor across devices and marketing channels.	Session

Host	COOKIE NAME	Purpose	DURATION
itslolly.com	_hjAbsoluteSessionInProgress	The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information.	1 day
itslolly.com	_hjFirstSeen	This cookie is used to determine if the visitor has visited the website before, or if it is a new visitor on the website.	1 day
itslolly.com	_hjid	This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.	Persistent
itslolly.com	_hjIncludedInPageviewSample	his session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.	1 day
itslolly.com	_hjTLDTest	When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.	Session

Host	COOKIE NAME	PURPOSE	DURATION
itslolly.com	_gcl_au	Used by Google AdSense for experimenting with advertisement efficiency	3 months
itslolly.com	_uetsid	Collects data on visitor behaviour from multiple websites, in order to present more relevant advertisements	Persistent
itslolly.com	_uetsid_exp	Contains the expiry-date for the cookie with the corresponding name	Persistent
itslolly.com	_uetvid	Collects data on visitor behaviour from multiple websites, in order to present more relevant advertisements	Persistent
itslolly.com	_uetvid_exp	Contains the expiry-date for the cookie with the corresponding name	Persistent

google.com	ads/ga-audiences	Used by Google AdWords to re-engage visitors that are likely to convert based on the visitor's online behaviour across websites.	Session
google.com	pagead/1p-user-list/#	Used for measurement of advertisement efforts and facilitates payment of referral-fees between websites	Session

bing.com	MUID	Enables user tracking across Microsoft domains	1 year