Founding Partner Rate30% off the monthly fee for 12 months — first 10 venues only.Built by operators · For operators

One venue. One operating record.

We ran restaurants for 15 years before we wrote a line of this →

The booking, the cover, the order, the kitchen, the payment, the labour and the margin — connected. Not seven systems that agree with each other once a month, badly. We run it in our own restaurant every service.

Walk a full Friday service end to end · or create an account to load the populated Copper Lantern demo venue, no credit card

this month intake — checking capacity

We're running it ourselves — and opening to our first external operators.

Every feature here has been used in a live service before it shipped. We don't publish other operators' numbers — when the first cohort goes live, their results appear here with their permission, not before.

The architecture

One ledger changes everything.

In most venues these are seven separate systems that agree with each other once a month, badly. Here they're one record moving through the night.

Booking
Cover
Table
Order
Kitchen
Payment
Labour
Margin

Nothing is typed twice

The booking becomes the cover, the cover becomes the tab, the tab becomes the payment. No nightly re-keying between systems.

Nothing disagrees

Bookings, till, kitchen, rota and finance read the same rows. There is no version of tonight that only one system believes.

Nothing goes missing

Voids, discounts, refunds and drawer movements are audit-logged against the staff member and the ticket that caused them.

One service, end to end

The same booking, all the way to the till.

This is the same record moving through a single Friday night. Every step below is a screen in VenueCore — not an integration, not a nightly sync.

  1. 19:00

    The guest books

    Direct, Google or a partner channel. Deduped against tonight's book, deposit rules applied, allergen notes carried on the record from the first keystroke.

  2. 19:42

    The host seats them

    The booking becomes a cover on the floor plan. Turn-time starts. The four-top next door already knows it can't be double-sold.

  3. 19:48

    The server takes the order

    Same menu the website published this morning. Allergen flags fire at the point of entry, not after the plate has left.

  4. 19:49

    The kitchen receives it

    On the pass in under a second, coursed and timed against the table's other seats — no re-keying, no printer roulette.

  5. 20:17

    The plate lands at the table

    The same coursing and allergen flags that left the pass travel with the dish, so the server knows exactly what — and who — it's for before it touches the table.

  6. 20:50

    The guest pays

    Card on the terminal, split how they like it. The tab, the tip and the covers are the same record the kitchen just cooked.

  7. 20:51

    The payment reconciles

    Matched to the ticket and the payout as it settles. Nothing waits for a Monday morning export to be believed.

  8. 23:15

    The manager closes the day

    One cash-up. Drawer counted, variance explained, voids and discounts signed against the person who authorised them.

  9. 08:00

    The owner opens their phone

    Sales, labour, discounts, voids, margin and anomalies for last night — already reconciled, because it was never in seven places to begin with.

That's VenueCore. One venue, one operating record, from the booking to the margin.

One venue. One operating system.

Three jobs. Not twenty-seven logins.

Everything VenueCore does serves one of three outcomes a venue actually gets judged on. The modules sit underneath — you don't have to think about them.

01

Fill the room

Reservations · Guest CRM · Floor plan

Every inbound channel lands in one funnel — direct, Google, partners, walk-ins and the waitlist. Deposits, preferences and visit history travel with the cover to the host stand.

02

Run the service

EPOS · KDS · Menu · Staff

One offline-first till, one kitchen display, one menu. Orders, fires, holds, voids and clock-ins all write to the same record as the booking that started them.

03

Protect the margin

Finance · Purchasing · AI · Loss prevention

Dish-level GP, live prime cost, supplier planning and audit-logged voids. The cash-up reconciles as the night runs, so the manager signs off variance instead of reconstructing it.

Full deep dive

The longer walk-through, module by module.

The film above is one night in a minute. This is the unhurried version — reservations, floor, till, kitchen, payment and finance, in the order a real service happens.

New — EPOS v2

A till your team can actually read at 11pm on a Saturday.

We rebuilt the point-of-sale from the ground up — taking the best of Lightspeed, Toast, Square, Clover and EPOS Now — into one dark, high-contrast, fully offline-first surface.

And unlike a traditional EPOS, this isn't where the system ends — it's where the ledger passes through.

VenueCore EPOS v2 — dark tactile pro theme with orange pay button, blue send-to-kitchen and coloured line-item state rails

Dark tactile pro theme

High-contrast charcoal shell with warm orange primary CTAs and electric blue send-to-kitchen action. Easier to read across a 12-hour shift.

Line-item state rails

Every ticket line shows a coloured left rail — pending, sent, held, voided — so servers see at a glance what's fired and what isn't.

Morphing primary CTA

One dominant orange Pay button and a distinct blue Send to Kitchen. No more hunting for the right action mid-service.

Live status footer

QZ Tray connectivity, network heartbeat and till clock pinned to the base. Click-to-reconnect if the printer bridge drops.

Included — no extra rota subscription

The staff rota app is built in.

Your team installs VenueCore Staff on their own phone and gets their rota, swaps, clock-in and training in one place. It reads the same ledger as the till and the back office — so rostered hours, worked hours and sales all agree without a single export.

Works on iPhone and Android. Staff only ever see rota, training and their own hours — never the EPOS or back office.

Rotas staff actually read

Publish the week once and every phone updates. Shifts, breaks, sections and who they're on with — no photos of a laminated sheet in a group chat.

Availability and swaps in-app

Staff send availability and request swaps from their phone; managers approve in one tap. Every change is logged against the shift.

Clock-in that feeds payroll

PIN-guarded clock-in on the till writes the same hours the rota planned, so variance shows up on the day — not on payday.

Training built into the same app

EPOS Academy, allergen and service modules with pass scores on each person's record, so new starters are till-ready before their first service.

The SFBB pack, digitised

Fridge and freezer temps, hot holding, cleaning, opening and closing checks — seeded per venue and recorded on a kitchen tablet or the staff phone app.

Missed is provable, not absent

Checks are generated ahead of the shift, so anything not done shows as missed. The database stamps its own received time, so a late sync can't read as on-time.

Out-of-range forces an action

A temperature outside range or a "No" answer can't be saved until a corrective action is recorded against it.

EHO export in one tap

Manager sign-off closes and freezes the trading day. Export a single day or a 4-week pack as PDF with every out-of-range entry flagged.

Included — no separate compliance app

Food safety records, on the same system.

The paper diary on the kitchen wall becomes a live record: temps, checks, corrective actions and manager sign-off — head chef and manager gated, with an EHO-ready export whenever an inspector walks in.

Works on kitchen tablets and staff phones. Sign-off stays manager-only.

Underneath the three outcomes

Twenty-seven modules. One system to learn.

Twenty-seven modules across six pillars, all writing to one ledger — the booking, the cover, the dish, the labour minute, the pound. Offline-first EPOS, kiosk, QR, allergens, tronc, Xero and void/drawer anomaly detection, wired together rather than integrated after the fact. See every module →

Reservations

Direct, Google, Resy and partner inbound — deduped, deposit-aware, never double-booked.

Learn more
Floor plan

Drag-and-drop seating wired to bookings. Turn-times update live as covers seat.

Learn more
Menu

One source of truth, pushed to web, POS, KDS and printed specials in seconds.

Learn more
Staff

Forecast-aware rosters with Working Time Regulations checked live, time-clock, and one-click payroll exports for Gusto, ADP, Sage and Xero.

Learn more
Guest CRM

Unified guest profiles, visit history, preferences and tags — synced to host stand, POS and your white-label email.

Learn more
Finance

Live P&L, dish-level GP, supplier OCR and deposits reconciled to the cent.

Learn more
EPOS

Offline-first till with audit-logged voids, manager-approved refunds and a reconciliation engine that catches skim before close.

Learn more
AI intelligence

Nightly anomaly scans, menu engineering and labour-vs-sales math — built in, no API keys to manage.

Learn more
New
AI Performance Coach

Scores every customer-facing team member on spend per cover, tip %, upsell ratio and voids — then tells the GM who to train this week and how.

Learn more
New
AI Supplier Planner

Reads inventory, incoming POs and forecast covers to draft a net-required purchase list per supplier — exportable as CSV or PDF in one click.

Learn more
White-label

Your domain, your emails, your data. Run one room or twenty from one console.

Learn more
Built in — no API keys

The midnight paperwork, already done by the time you get in.

Not a chatbot bolted on the side. Each one reads your own bookings, tickets, recipe costings, stock and rota, which is the only reason the output is worth acting on in the morning.

  1. Each morning

    Tomorrow's supplier order, drafted

    Reads current stock, incoming purchase orders and forecast covers, then drafts a net-required order list per supplier — exportable as CSV or PDF.

  2. Each week

    Who to coach, and on what

    Scores every customer-facing team member on spend per cover, tip percentage, upsell ratio and voids, then tells the GM who to coach and on what.

  3. After close

    Voids and drawer gaps flagged

    Scans the night's voids, discounts, refunds and drawer movements for patterns that don't match the rest of the room, and surfaces them for review.

  4. Ongoing

    Which dishes to cut or reprice

    Ranks every dish by contribution and popularity against real recipe costings, so the menu gets cut and repriced on evidence rather than instinct.

  5. Ongoing

    Overstaffing caught before payroll

    Puts rostered hours next to forecast and actual sales by daypart, so overstaffing shows up before payroll does.

How it works

From kickoff to first service in under a week.

01
Map your venue

Import covers, sections and stations in an afternoon. We mirror how the room actually runs.

02
Connect the rails

POS, payments, accounting and Google Reservations link in under a day. No middleware.

03
Run service

Front and back of house work off the same data. Owners see numbers update live, not at month-end.

The whole venue. Finally, in one system.

We've built one of the most comprehensive hospitality operating systems available — designed to run the venue from the first booking to the final pound reconciled.

And every Monday we report your week back to you honestly — including when our own advice didn't move the number.

Reservations
Floor
EPOS
Kitchen
Payments
Staff
Finance
Intelligence
It started behind the pass

We didn't build this to sell software. We built it to run our own rooms.

Fifteen years running restaurants. What wore us down wasn't the trade — it was that the technology sold to make the trade easier quietly made it harder. One system held the bookings. Another held the till. Another held the staff. Another held the finances. Not one of them understood the whole restaurant, so the owner became the middleware: the double-booked six, the ticket the kitchen never saw, the drawer £40 light with nobody to ask, the Monday spent making four systems agree about Friday.

So we built the system we wanted to run our own venues on — one operating record the whole room writes to. Every screen exists because a shift went badly without it.

And before we asked anyone else to trust it, we put it into live service in our own restaurant. It still runs there tonight.

  • 15 years

    running restaurants before writing a line of this

  • Live every service

    used in our own venue nightly, not demoed in a spec doc

  • Operator support

    migration handled by people who have worked a section

Pricing

Priced like infrastructure. Not per cover.

One flat platform fee — replaces booking, POS, KDS, CRM, scheduling, finance and loss-prevention tools. Card processing is built in at 1.69% + 15p in person, 1.99% + 20p online — one rate, one invoice, no separate acquirer contract.

Recommended
Professional

The full operating system for a single venue.

£599/mo
  • Reservations · Floor · Menu
  • EPOS + KDS + cash-up
  • Guest CRM · Staff · VAT
  • AI Performance Coach
  • AI Supplier Planner
  • AI loss-prevention engine
£995 one-time onboarding
Group

For operators running multiple rooms.

£799/mo · per venue
  • Everything in Professional
  • Multi-site reporting + group P&L
  • Central menu management
  • Enhanced AI insights across venues
  • Advanced permissions · SSO ready
  • Priority support
£2,995–£9,995 implementation

Setup fee waived on a 24-month agreement — limited launch offer.

The honest pitch

What full deployment actually does to a venue's P&L.

UK hospitality is brutal right now. We're not selling magic — we're showing the arithmetic on a median independent when VenueCore is used end to end, not as a replacement till.

Demo walkthrough
"Six restaurant logins replaced by one. Bookings, the floor and payroll finally agree on what actually happened tonight."
CL
Illustrative scenario
Illustrative single-site restaurant
Ship tonight

Ready to run the whole venue from one system?

Trade your tab-soup for one platform. 14 days free, no credit card, and migration handled by a real human who has worked a section.

Start free trial