LIGHTNING
FOR INDEPENDENT RETAIL AND HOSPITALITY

Serve the customer. Keep the systems in step.

Make booking, ordering and finding your business easier. We scope websites and connections between sales, stock, bookings and accounts, so the details your team needs are easier to find and repeated admin takes less of the day.

Four things that go wrong while you are serving

01

Bookings arriving down four different pipes

A table booked over the phone, another in an Instagram DM, a third through the website form and a walk-in party of six at the door. In a shop it is the same shape: a click-and-collect order sitting in the system, an item promised over the counter and a DM asking you to put one aside. Whoever is nearest the diary or the notepad writes it down. By Friday nobody fully trusts the table plan, and two of those covers were never really there.

02

No-shows with nothing holding them

A party of eight books for Saturday night. Prep is bought against it and an extra person goes on the rota. No deposit taken, no confirmation asked for, no simple way to release the table once it is clear nobody is coming. In the shop the same money sits behind the counter as a special order nobody has come back for, off the shelf and off the website while it waits. The cost is paid long before the table sits empty.

03

Till, stock count and online shop disagreeing

The EPOS says four, the shelf has one and the website has just sold two. The marketplace listing is still showing it as available. Someone loses a Monday reconciling it by hand, then a customer gets an apology for an order that cannot be fulfilled. Wastage on one side, refunds on the other, both out of the same margin.

04

Every enquiry ends up with the owner

The phone rings mid-service. Messages arrive at eleven at night. The function enquiry with real money attached, or the message asking whether you can order in forty of something, waits until Tuesday because it came in on a channel nobody owns. Staff cannot answer it without you, so it sits, and some of it quietly goes somewhere else.

The owner of an independent deli behind the counter, holding the phone to one ear while a customer waits to pay at the till.

Systems that hold the diary and the stock count

01

A site that takes the booking, not just the enquiry

Tables, deposits, click-and-collect, pre-orders and gift vouchers handled on the page the customer is already looking at. Opening hours that match the ones Google is showing, an accurate menu or product list and a checkout that works one-handed on a phone in the street. Not a form that lands in a mailbox nobody reads on a Saturday.

Websites and digital platforms
02

One queue for the phone, the DMs and the inbox

Enquiry routing can bring booking questions, order queries and messages into a clearer queue, with someone responsible for each next step. We check which channels your existing tools support before proposing a connection. Any automated answering is scoped around the questions it can handle and a clear route to your team.

Phone, email and CRM
03

Till, stock and online shop reading the same number

We connect the EPOS, the stock count and the online shop so one sale moves one figure, and a low line comes off sale instead of selling twice. The delivery tablets count too: orders landing on screens the till never sees, and a menu change that has to be made on each one before it is true everywhere. Where a supplier feed or a well-kept spreadsheet is the real source of truth, we build around it rather than insisting you abandon it.

Integration and migration
04

The chasing that happens without anyone remembering

Deposit requests, booking confirmations, the reminder the night before, the release of a table nobody confirmed, the collection-ready message, the nudge before a special order goes back on the shelf. Each one currently happens only if somebody remembers in the middle of a service or a delivery. Written down once, they run whether the room is full or the shop is empty.

AI and automation
05

Found by someone standing outside

The Google listing, the map pin, the opening hours over a bank holiday, the photographs and a review request that goes out after a good service rather than only after a bad one. Then the plain numbers afterwards: bookings taken on the site, deposits held, collections completed, so the next piece of work is chosen on what happened rather than on a hunch.

Growth and performance
An independent shop owner serving at the counter

We look at your week before we quote

We start with one trading week, not a wish list. How a booking taken on the phone at four o'clock reaches the table plan. What happens to an item promised to a customer at the counter, and to a message that arrives at midnight. Where the till and the online shop stop agreeing, and who is expected to notice. What we are looking for is the handful of points where a person has to retype something: the phone booking copied into the paper diary, the DM copied into the booking system, the website order checked against a shelf by eye, the deposit chased by hand. Those are the points that fail at seven o'clock on a Saturday, not the till or the booking software you already pay for.

Your accounts, logins, card processing and customer list stay in your name. A first piece of work is one visible thing, either the bookings or the shop. It is scoped and priced before it starts, with a named person you can ring during service. If the booking system you already pay for would do the job once it is set up properly, we will say so and quote for the setting up instead.

One thing fixed before the next

Start with whichever one costs money every week: bookings that do not stick or a shop that cannot be trusted on stock. One piece, built and then run through a full trading weekend before anything else is scoped.

  • 01A walk-through of one full trading week, first call to final till reading
  • 02Bookings and deposits taken on your own site, not on a platform charging per cover
  • 03Staff able to answer a booking or a function enquiry without ringing you
  • 04Till, shelf, website and delivery apps working from one stock figure
  • 05Confirmations, reminders and release rules written down and running
ONE DIARYphone, DMs and walk-ins in the same place
ONE STOCK COUNTno Monday spent reconciling the shelf by hand
ONE NAMEsomeone you can ring mid-service, not a ticket queue
NO LOCK-INyour card processing, your listings and your customer list

Before you start. Practical questions, answered.

What to consider when deciding whether this work is right for your business.

01

Do the takings from Square and the invoices in Xero ever agree without somebody keying them?

Usually not on their own, and the daily till total is where it goes wrong. We work from the settled payout rather than the till reading, post it into Xero as a sales journal split by category, and match each payout against the bank line. Anything that will not match sits in a queue for someone to look at.

02

We reconcile the Deliveroo and Just Eat statements by hand every time. Can that stop?

Yes, and it is the job most owners hate. Each platform publishes a remittance statement; we read it, match every order line against the till, and net off commission, refunds and rider adjustments so the payout is explained line by line. Orders that appear on the statement but never on the till are flagged, not absorbed. automating the reconciliation

03

We get booking enquiries on Instagram and voicemail during service. What happens to those?

Often they are found after the table has gone. The reliable fix is to stop taking bookings in a channel nobody watches: the enquiry lands in ResDiary or OpenTable wherever it came from, and whoever covers messages works one queue rather than several apps. Anything unanswered by the end of service gets chased.

04

Our customers ring to ask if something is in stock. Can the website answer instead?

Yes, if the till is the master of stock and the website follows it. Shopify and WooCommerce both accept a stock feed, so the count that leaves the shop floor is the count the site shows, and click and collect fulfilment draws from the same pool. Lines that fall under their reorder point are hidden rather than oversold. shops and stock feeds

05

We already pay for Epos Now across the sites. Would you want to replace it?

No. The till is the last thing you should change in a trading business, and a mid-season migration causes exactly the disruption you are trying to avoid, so use the product you already pay for. The gap is almost always what happens after the sale, where the export has to reach the accounts. If it truly cannot export, we will tell you plainly.

06

Do our Deliveroo and Uber Eats contracts stop us using our own customer data?

Often, in part, and it is worth reading before anyone builds a mailing list. The platforms treat the customer as theirs, so the order data you receive is limited by design. What you can own is the customer who walks in or books direct, captured at the table with consent recorded against the record. We keep those sources apart.

You cannot be the switchboard, the diary and the stock system for ever. Every booking that goes missing and every line that sells twice is the same thing: a system nobody has been given the time to fix. The diary and the count are where a busy day stops paying for itself.

Start with the change you want to make.

Tell us what you use now, where the work slows down and what a better result would look like. We will explain the next step, with any paid work agreed before it starts.

Talk to Lightning