Restaurants

We made the booking system and the till talk

The tables are handled by easyTable, the till by Ancon. Both do their job well, and they did not know about each other. Ancon Table Booking is the layer between them.

Photograph: Boulebar, used with permission

easyTable Anvora Ancon

Both easyTable and Ancon are independent products. Ancon Table Booking is ours — an integration layer that holds them together, built and operated by us.

What we built

Two systems, three flows

A booking should become a check without anyone keying it in again. And what can be booked should match what is actually in the room — which is why products and tables travel the other way.

Table booking
Ancon Table Booking Bun · Hono · Postgres
Point of sale
  • Bookings become checks
  • Products
  • Tables
What we built around the booking

From the booking to the index

Everything below was built by Anvora: the booking flow the guest sees, the index the owner follows and the monitoring we keep an eye on the flow with.

The Boulebar booking flow: venue, experience, party size and date, and below it the open slots, with boule and food in either order
Boulebar · built by Anvora
Anconindex: the restaurants’ combined revenue index week by week, four years laid over each other
Anconindex · built by Anvora
Monitoring of the booking flow: incoming webhooks per hour over the last four days, split into new and changed bookings
Anvora
Why it holds
  • Realtime, not batched
    The index recalculates as orders land — Go on the backend.
  • Anonymised by design
    Group-level figures never store what identifies the individual restaurant.
  • Runs on Monday
    We operate the integration. Monitoring, upgrades and the boring work are ours.

Running a restaurant group with several systems that do not talk?

Book a call