WhoshouldIsee Tracks

Book a Demo

Please fill in the form, and we'll get back to you promptly with the information you need.

Choose Sectors:
Choose Products:
Thank you! Your submission has been received!
Something went wrong while submitting the form, please try again.

7 questions to ask if you're reviewing your hospitality technology provider

7 questions to ask if you're reviewing your hospitality technology provider

Changing hospitality technology provider is a significant decision.

For a busy hospitality operation, EPoS does not sit in isolation. It can connect with payments, finance, ordering, kiosks, kitchen systems, loyalty, reporting and other third-party platforms. The more complex your operation, the more important it is to understand not just what a new system can do, but how you will get from where you are today to where you want to be.

Whether you're actively planning a change or simply reviewing whether your current technology is still right for your operation, these are seven questions worth asking.

1. Can we take our existing data with us?

Your data is one of your most valuable operational assets, so data ownership, portability and migration should be discussed early.

Ask your prospective provider exactly what can be migrated, in what format, who is responsible for extracting and validating it, and what historical data you will retain access to.

Think beyond sales totals. Depending on your operation, this might include product and pricing information, customer or loyalty accounts, reporting structures, menus and other operational data.

Migration should also include a clear validation process. Lolly's documented university implementations, for example, include working with stakeholders to migrate and validate student account information before launch.

Ask: If we changed provider tomorrow, what data could we take with us, and what would the migration process actually involve?

2. What happens to our existing integrations?

This is potentially one of the biggest hidden complications of changing technology.

Modern hospitality operations increasingly rely on an ecosystem of connected systems. EPoS might need to communicate with payment providers, finance platforms, kitchen systems, kiosks, apps, digital signage, loyalty systems and other third-party software.

Before choosing a provider, map your existing integrations and establish:

- Which are already supported

- Which would need rebuilding or reconfiguring

- Whether APIs are available

- Who owns responsibility for testing them

- Whether additional development or third-party costs are involved.

Lolly's own platform uses a standards-based, API-led approach to integrations and has documented integrations into finance and institutional systems as well as connected products such as EPoS, self-service, kitchen management and digital ordering.

Ask: Show us how you'd connect into our existing technology landscape, not just how your own products work together.

3. How would a new provider minimise operational downtime?

A good demonstration tells you what the technology looks like when everything is working.

A good implementation plan tells you how the supplier gets you there safely.

Ask to see the actual proposed journey from contract signing to go-live. That should cover areas such as solution design, configuration, migration, testing, installation, training, go-live and post-launch support.

Consider whether a phased rollout is appropriate rather than changing an entire estate at once.

Lolly's documented implementation approach includes pre-installation testing, system validation and enhanced hypercare around go-live. Its university experience also includes phased deployments across multiple catering and retail locations.

Resilience after implementation matters too. Lolly's continuity approach includes Azure cloud hosting, monitoring, backup and recovery arrangements, support escalation and offline POS capability where configured.

Ask: What's your plan for keeping us trading while the transition takes place, and what happens if something doesn't go to plan?

4. Can the technology scale across our entire estate?

What works for one outlet might not work across 20, 50 or 100.

Multi-site operators should look beyond whether software technically supports multiple locations. The bigger question is whether it gives central teams visibility and control without removing the flexibility individual locations need.

Look at:

- central configuration

- estate-wide reporting

- permissions and user management

- integration across locations

- adding new sites and devices

- different concepts or service models within the same estate

- real-time sales and operational visibility.

This is an important part of Lolly's existing proposition. Its cloud-based Lolly HQ platform provides central management and reporting across connected estates, while documented deployments include Durham University, with 55 fixed tills and 38 mobile POS devices across 30 locations.

Ask: Don't just show us one site. Show us how we're going to manage the entire operation.

5. How are payments handled during the transition?

Payments cannot be an afterthought. Understanding how EPOS and payment technology will work together is essential when you're changing provider, particularly if you're also reviewing terminals, acquiring arrangements or payment gateways.

Ask:

Can existing payment arrangements remain in place?

Will terminals need replacing or reconfiguring?

Who coordinates the different parties involved?

How will payment functionality be tested before go-live?

How are reconciliation and reporting handled?

What happens if connectivity or a supplier fails?

Lolly supports integrated payments through approved payment providers and its documented approach includes assisting with triage between POS, terminals, acquirers and networks when payment issues occur. Its tender documentation also specifies PCI-DSS Level 1 certified payment providers, encryption/tokenisation and P2PE protection.

Ask: Who is accountable for making sure customers can continue to pay throughout the change?

6. What training and implementation support will our teams receive?

A successful implementation isn't finished when the technology switches on.

The people using it need the confidence to operate it.

Ask whether training is provided for different user groups, including front-of-house teams, managers and system administrators. Also establish whether training happens before, during or after go-live and what resources remain available afterwards.

Lolly has documented both onsite front-of-house and remote management training in university implementations. Its training materials cover day-to-day PoS activity such as transactions, cashing up and issue reporting, alongside separate back-office training.

Training should also acknowledge the reality of hospitality: teams change, new starters arrive and knowledge needs to be maintained after the initial rollout.

Ask: How will you make sure our people are confident on day one, and how will we train people who join six months later?

7. What support will we have once we're live?

The relationship shouldn't end at go-live.

Understand who you contact, when support is available, what happens when an issue crosses several technologies and how problems are escalated.

This becomes particularly important when EPoS, payments and third-party integrations are all involved. You do not want several suppliers pointing at one another while sites are unable to trade.

Lolly operates a dedicated technical helpdesk, with remote software support from its Braintree head office, while its wider positioning is built around supplying, installing and supporting integrated EPOS, self-service and payment solutions through a single technology partner.

Ask: When something goes wrong at a busy site, who owns the problem and gets it resolved?

Where do you start?

As a customer-first business, Lolly specialises in guiding hospitality operators through a smooth, well-managed transition. Whether you’re actively planning a switch or just weighing up your options, get in touch with our team. We’re here to answer your questions and help you map out the right move for your estate.

Frequently Asked Questions

Do you offer technical support for Kitchen Management systems?

Yes, our technical support team is available to assist you with any questions or technical issues related to Kitchen Management systems.

Is setup assistance provided for hospitality EPoS terminals?

Our Electronic Point of Sale devices are designed to work out of the box with minimal configuration, for most catering or hospitality businesses, but if you have any issues, our technical support team is on hand to assist.

Is installation assistance available for Pre-Order Pods?

Yes, we can offer installation services for Pre-Order Pods to ensure that they are set up correctly.

Can Self-Serve solutions be customised to match my brand?

Yes, our Self-Serve interfaces can be customised with your branding and photography, ensuring a consistent customer experience.

Do you offer technical support for EPoS terminals?

Yes. Our superb technical support team is available to assist you with any questions or technical issues related to your EPoS devices.

Do you offer technical support for Lolly's integrated payment service?

Yes, we provide comprehensive technical and customer support to address any payment-related questions or issues.

How is the Lolly kitchen management system different?

Lolly’s kitchen management systems uniquely integrate advanced software across their technology range (including EPoS, advanced Self Serve Kiosks, innovative Robot Waiters and more) to help streamline communications, reduce wait times, and elevate staff and customer satisfaction.

Related Posts

See all posts
kitchen management systems
April 4, 2025

Kitchen Management Systems: Functionality, Features, and Benefits

Discover how Kitchen Management Systems are simplifying ordering processes, streamlining digital communications between front-of-house EPoS devices and back-of-house ordering screens within foodservice establishments.

Read more
Press Releases
December 17, 2025

Moving from Ambition to Impact in Hospitality Technology

As the hospitality sector moves through another year of rapid technological evolution, one thing has become clear: while innovation continues at pace, the gap between promise and real-world delivery is widening. 2025 has been dominated by conversation, ambition and expectation, but 2026 will be defined by outcomes.

Read more
October 27, 2026

Exploring Hospitality Technology: Alex’s Three Days at Lolly

Earlier last month, Lolly welcomed Alex for a three-day work experience placement, giving her the opportunity to explore a range of departments across the business. From software development and project management to finance, payments and marketing, she gained valuable insight into how a hospitality technology company operates. In this blog, Alex shares her experience, highlights the skills she developed, and reflects on the career paths she discovered during her time with the team.

Read more