The order to do it in
Nothing here needs an engineer
- Step 1
Get your menu in
Import from a website, paste it as text, upload a CSV or a photo of the printed menu, or pull it from your POS if you have one.
- Step 2
Print the codes and put them out
One code per table, generated for you. Stand them, stick them, or print them onto the menu itself.
- Step 3
Open the kitchen screen
Any screen you already have in the kitchen. Tickets land on it the moment a guest submits.
- Step 4
Connect how you take money
Your own Stripe, Square, Clover or SumUp account, so payments settle where your money already settles. Or keep taking payment at the till and mark bills paid from the floor.
- Then
Let it watch a few services
Once orders are flowing, the reporting has something to read. The first insights arrive after enough covers to be worth acting on — not before.
How long each part takes
Staged, not switched on all at once
- Tonight15–30 minutes
Menu on, codes on the tables
Upload a PDF, a photo or a URL and the menu is read into dishes, prices and categories for you to correct. Print the codes, and guests can order.
- This weekAn hour or two
The diary and the kitchen
Declare your sittings and how many covers each takes, put the booking link on your site, and open the kitchen screen on whatever tablet is already in the pass.
- When you are readyDays, spread out
Suppliers and the shelf
Add your suppliers and their catalogues, then map dishes to ingredients. This is the slow one — a full menu is days, not minutes — but it is what makes food costs real rather than remembered.
- NeverNot required
Replacing your till
Your EPOS stays where it is. AtTable is the guest-facing layer, the kitchen screen, the diary, the shelf and the numbers on top of them.
Read more
Everything below exists today
- DocumentationSetup, configuration and the day-to-day of running the dashboard.
- API referenceWebhooks: we post a signed event to a URL you own, with verification examples.
- Common questionsPricing, contracts, hardware, data, and what happens if you leave.
- How it worksThe whole loop, from a guest scanning a code to the change you make next week.