The MobiTaste feature list, in one page

Restaurant software vendors list 80 features and ship 12; the rest live on the roadmap. MobiTaste is the other shape: a short list of features that all work today, all included from Starter at $10 a month. This page is the map; each tile links to a deep-dive that explains the mechanism, the trade-offs, and the limits.

Three anchor features

Printable QR menu, multi-language. One QR per table, printed from the dashboard, A6 PDF. Menus run in Turkish and English from a single editor, with shared prices and per-locale text. The guest scans, the page loads in well under a second on 4G, and there is no app to install. The QR menu deep-dive covers the print step, the editor, and the URL contract.

Live order board for the kitchen. A kanban view of new, in progress, and ready tickets that runs in any browser. New orders appear in under one second over normal Wi-Fi. No dedicated KDS device required; a $150 Android tablet or an old iPad works. The order board deep-dive covers the latency, the role model, and the hardware pattern.

Waiter approval, on every first order. The kitchen sees nothing until staff taps Approve on the first order from a new table token. Stops prank scans without slowing real service. The approval deep-dive explains the gate, the audit log, and when to flip the setting off.

Supporting features in every tier

Call-waiter button: a tap from the guest rings a soft tone on the floor tablet and shows the table number.

Idle session expiry: a table sits idle for 30 minutes (configurable 10 to 90), and the QR cart clears so the next party starts fresh.

Table state sync: a table goes Occupied when any of its orders are in flight and Available when all are settled. Managed by the order state machine, not a manual button.

Audit log: every menu, price, table, and staff change writes a row with the user, the timestamp, and the device. Retained 12 months on Starter and Growth, 36 on Pro, unlimited on Enterprise.

Multi-language menu: Turkish and English on every tier; add a third or fourth language on Growth and above without paying per language.

Allergen flags: small badges (gluten, nut, dairy) next to each item, scoped per-locale so the label reads in the guest’s language.

Modifiers and option groups: size, sugar, milk, temperature, with localized labels.

Role-based staff access: owner, manager, server, kitchen. The kitchen role does not see prices; the owner sees everything.

What is on the roadmap

Adisyo webhook integration, iyzico pay-at-table, Logo accounting CSV-to-API upgrade, two-factor login, more locales. The full status moves on the changelog page after launch. No quarter-by-quarter commitments here; we ship when each piece is real.

How it fits with what you already have

The features pair with your existing card terminal, your POS if you run one, and your kitchen printer if you keep one. The POS comparison guide walks the boundary in detail. The pricing page lists every limit by tier.

Where to start

If you run a single venue under 20 tables, start with the QR menu and the order board. If you face the street or run hotel F&B, add waiter approval from day one. For a full operational walkthrough, the restaurant use case is the closest fit.