Tuesday. Wednesday. Seven in the evening. The shift after ten. Every venue has those days and hours that are hard to fill, and that's where Omakasia goes looking for reservations. A promotion in Omakasia isn't "a discount": it's a discount for that day and that time slot, and for nothing else.
The table knows that reservation brings the promo and deducts it from the bill. The event is charged at the till with its deposit already deducted. Nobody has to remember anything or take anything into account: not the waiter, not you.
That is why the booking link is yours and not a portal's: a reservation that comes in through a portal comes in without the promotion, and fills the slot that already filled up on its own.
You create the promotion. Omakasia generates the posts for your social media; you just publish them. And reservations come in where there was no way before.
In a normal booking engine, the customer books a table and that is it. In Omakasia they book the promotion or the event you saw in the post: it travels inside the link, is sealed into the reservation and reaches the till.
A promotion is for a specific day and a specific slot: the slow Tuesday, the first hour. An event has its sessions, its seats, its price and its deposit. Both are drawn in your reservation book.
Posts for Instagram, Facebook, X, TikTok and Substack with your photos, your logo and your palette, and the text written with the real data (seats left, dates). You publish them on your social media. Nothing to design.
The link in the post carries the promotion inside. Whoever taps it books the slot with the promo, or their seat at the event, and pays the deposit through your payment gateway.
The offer is recorded in the reservation. If you have the POS, the bill already comes out with the promo or with the event deposit deducted: nobody has to remember. And Omakasia counts how many reservations each network brought.
Reminder, guarantee, no-show penalty. Protects what you already had.
All of the above. Plus a reservation that didn't exist before, in the slot you wanted to fill.
The reservation book, the till and the menu, on real Omakasia screens.
Every reservation feeds the customer's profile: visits, spend per visit, allergens, language, consent. And from there you write to them when the time is right:
Email campaigns are part of the Reservations module. No need to subscribe to Mailchimp or the like.
“Close on Saturday.” “Open the nine o'clock on Thursday.” “Move the Puigs to table 4.” “Cancel Marta's reservation and let her know.” Slinky understands the sentence, checks your venue's real data, shows you what it is going to do and with which sources, and touches nothing until you confirm. For the delicate bits (cancelling, notifying) it makes you type the word. And everything has undo.
When the phrasing doesn't sound right, it asks the AI with the context of your booking engine, without personal data. And it answers whatever you ask it about your diary.
With any module, your venue has its page at omakasia.com/yourvenue: photos, who you are, where, when, the guides you are in, what has been written about you, the menu, the events and the Book button. It is rendered on the server with structured data, in the languages you publish, and links to your website if you already have one: it does not compete with it, it complements it.
Not per reservation and not per payment. The deposit is charged by your payment gateway (MONEI with Bizum, Stripe or Mollie) and goes into your account. It does not pass through Omakasia, so there is nothing to deduct.
See the price ›Four modules. Each one can be subscribed to on its own. €20 a month each.
Reservation book, reservation types, deposit through your payment gateway, promotions and events, social media posts, CRM and campaigns.
Till, handheld ordering, kitchen display by stations, QR menu with mini website and receipt ready for Veri*Factu. Tied to reservations.
A bar's accounting: purchases, sales, banks and reconciliation, VAT and tax forms. It receives the POS sales already closed.
Your website made by talking: you describe your venue, upload photos, choose between three proposals and change it by talking. With reservations and menu plugged in.
Castellano, català, valencià, euskera, galego, English, français, Deutsch, português, 中文, 日本語. Menus translated with AI.
If a venue is full, another venue in the group takes the reservation. How it works ›
Import customers and reservations from CSV or by pasting. It recognises the columns and avoids duplicates.
It runs in the browser: iPad, phone, computer. Every door (backoffice, POS, kitchen) one click away.
MONEI with Bizum, Stripe or Mollie. Deposits, table QR and gift cards go into your account.
Nothing is published or changed without pressing the button. No surprises.
Owner, manager, floor, handheld ordering. With a PIN on the POS to know who charges.
The first time, the app shows you where everything is.
When one restaurant in the group is full, the guest sees right away which other venue has a table and how many minutes away it is, and books there without typing anything again. One guest profile for the whole group, gift cards and points valid at every venue, campaigns to the whole group and a management dashboard with the reservations saved. Each venue is still its own.
Everything we offer groups ›From which venue to which, how many guests.
Visits, spend and allergies per restaurant.
With settlement between companies.
Comes with Reservations. The group, free.
Missing something? Want it your way? Tell us and we build it for you. On an express timeline. And free: it's included in the fee.
A feature you are missing that helps everyone: we build it and you have it.
Your receipt, your menu, your way of working. We adapt it to your venue, not the other way round.
No "development hours" and no "custom module". It is included in the €20 a month.
That is why Omakasia is built with AI: we can afford to do it.
Omakasia was built by AI agents, and they are the ones who support you: they know every screen because they wrote it. And there is always a person behind them for what AI should not decide on its own.
From the app itself, as they come up. No ticket, no queue.
They are logged with date and cause, and fixed at the root, not with a patch.
Whatever you ask for is noted down and built. Free and on an express timeline.
No setup fee, no cost per user or per table. Monthly payment only. Excluding VAT.
Why so cheap? Because it is built entirely with AI. We'll explain ›
In an omakase restaurant you do not choose: you trust the chef. Leave it in our hands.