· Ordina
Welcome to Ordina
Why we decided to build a table-ordering platform starting from Italy.
There's a precise moment, in every dining room, when service can break. It's when the waiter passes the same table twice, when an order gets lost between the POS and the kitchen, when a party of eight would just like another bottle of water. In those instants the room isn't slow — it's jammed. Ordina was born to untangle those knots.
Why start from Italy
Italian hospitality isn't a monoculture. A trattoria in Bologna, a wine bar in Milan, a pizzeria in Naples speak different operational languages. Generalist tools, often designed for Anglo-Saxon chains, don't hold up against our complexity: coperto, service charge, allergens, variants, splitting the bill alla romana. We chose to start from Italy because the problem is densest here — and therefore the solution is most interesting.
What "table ordering" means to us
Ordina is not a PDF menu behind a QR code. It's a software layer that lives alongside human service, not as a replacement. The guest orders when they want, the kitchen receives clean tickets, the waiter goes back to being a waiter: welcoming, advising, telling stories. When digital works, it disappears.
Our values
Three things are non-negotiable:
- End-customer privacy. No invasive tracking, no dark patterns. Whoever orders at the table shouldn't feel like a metric.
- Operator autonomy. A restaurant's data belongs to the restaurant. Full stop.
- Craft quality. We'd rather do fewer things, done well, than ship an endless feature suite nobody uses.
What you'll find here
On this blog we'll share notes from the kitchen: product decisions, lessons learned in the field, practical advice for people who work the floor. No growth hacking, no fluff. If you're a restaurateur, a server, or simply someone who cares about how we eat out, welcome.
See you at the next post.