Zeplo Admin documentation

The staff side of table booking, in a browser.

Before you start

  • Node and a modern build toolchain to compile the React project
  • Somewhere to host static files, plus a backend to hold the bookings
  • A browser. It is web-only — the guest-facing Zeplo mobile app is a separate product
  • Someone comfortable with TypeScript, if you intend to change how your restaurant works

A web-only React project you host yourself. The Zeplo mobile app is a separate product.

What it does not do

  • It does not include a backend. It is a web-only React project; the bookings live in a backend of your own.
  • It is the staff side only. The guest-facing booking app is Zeplo, a separate product.
  • It does not take payments, and it does not run your kitchen or your stock.

What is in the download

A React and TypeScript project: the floor-plan view of the evening, booking creation and movement, guest history and notes, service periods, capacity limits, blackout dates and staff accounts with permissions.

Web-only, hosted by you. No backend is included and the guest-facing mobile app is separate.

Building it

Install Node, install dependencies and run the development server. The project reads as ordinary TypeScript; there is no code generation step to understand first.

Build the static output and serve it from your own host, behind authentication. This is staff software and should not be on a public URL.

Connect it to the backend holding your bookings before putting it in front of the floor team.

Setting up a service

Enter service periods and capacity limits before the first booking. A floor view built on the wrong capacity is worse than a paper diary, because it is believed.

Give every member of staff their own account. Guest history and notes are only useful when it is clear who wrote them.

Add blackout dates as soon as you know them. The most expensive booking a restaurant takes is the one on the night it is closed.

Licence, updates and support

  • One licence covers 1 application you build and publish.
  • 1 year of updates, from the date of purchase.
  • 1 year of email support.
  • Instant download + licence key by email
  • 30-day money-back guarantee

Questions this page does not answer go to support@webkoding.com. If you bought from us and cannot find your licence key, look it up here.

Common questions

Is this the guest app?

No. This is the staff side, in a browser. Zeplo — the Flutter booking app the guest uses — is a separate product; buying one does not include the other.

Can I buy it right now?

Not yet from us. The listing is with the marketplace reviewers, and an item on sale on the author’s own site during review is rejected. The price on the product page is the price it will be.

Does it include a backend?

No. It is a web-only React project you host yourself; the bookings live in a backend of your own.

Do staff have separate accounts?

Yes, with separate permissions. A host taking bookings at the desk and a manager changing capacity limits should not be the same login.

Is the source readable?

Ordinary TypeScript rather than a black box — which is the point. Changing how your restaurant works should not mean fighting the code.