Apps & Integrations

Uber Eats

Planning to offer delivery? Maximise your to-go sales with Lolly and our delivery partner

Uber Eats

We have developed a completely seamless integration between the Lolly POS system and the UberEats delivery platform. From small single sites, to multiple location chains, we can help you easily get up and running with your meal delivery service.

Food delivery is a growing sector, and for many hospitality outlets it offers a brilliant way to extend their offering, reach new customers and generate more income.

The Lolly and UberEats comprehensive integration covers every stage of the process, from order & delivery, to payment and reporting.

Simple order acceptance on the Lolly Kitchen Management System

UberEats orders are sent directly to your Lolly kitchen video screens. This helps your kitchen and prep staff to effectively manage orders, saves employees time manually entering online orders, or working from multiple devices.

Real-time, synchronised inventory/stock management

Reduce errors. Even with rapid orders staff can keep track of stock availability, supporting better ordering and efficient stock management.

Live menu control

Products can be seamlessly added or removed between the Lolly system and UberEats platform. Items can be marked ‘out of stock’, even on a location basis, allowing for real-time menu visibility and updates.

Single end-of-day cash and payment reconciliation

Complete clarity, and no more complicated calculations. In-store cash intake and UberEats order payments can be synced.

Data and sales tracking

Include UberEats delivery orders to accurately review sales and generate precise reports.

Contact us to find out more about our integration with UberEats and introducing a meal delivery service into your hospitality business.

Featured Case Study

Lolly Supports Copper&Ink in its Mission to Create Home Away from Home

Situated in the heart of Blackheath village, Copper & Ink is a modern British restaurant with influences from classic French and Scandinavian cuisine. Their monthly changing five-course taster menu is created using the best seasonal produce. Chef Patron, Tony Rodd, and Head Chef, Rob Parks, bring their artistry together to produce stunning plates of food that are full of flavour and theatre.

Tony and his partner Becky wanted to bridge the gap between a traditional, stuffy high-end restaurant and a local, casual dining spot.

READ CASE STUDY

HOW CAN WE HELP?

GIVE US A CALL ON:

0800 038 5389

Additional Resources

Self-Serve

View Product

Kitchen Management System

View Product

Digital Signage

View Product

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