Outgrew the spreadsheet till.
A floor OS that grows from solo café to multi-venue without re-platforming. The till that already knows the rules.
What a modern floor OS does in 2026.
This is the objective standard — not Vetka's claim, the baseline a serious operator should expect from any till sold today. Read it as a checklist. Tick what your current system already does.
Runs on phones your team already owns
No fleet of proprietary tablets to buy, charge and replace.
Cloud signing on every receipt
No fiscal box per device. Compliance signed in the cloud, country-correct.
Snap a menu, AI does the data entry
Photo → categories, prices, modifiers, allergens. Five minutes, not five hours.
Recipes deduct stock as you sell
Variance flagged at the daily threshold. Theft visible before payroll closes.
Tips routed by hours, section or role
Logged as a separate ledger line. Tax-clean, payroll-clean, dispute-clean.
Card + cash + tap-to-pay in one screen
No mode switching mid-queue. Apple Pay and Google Pay first-class.
Day close generated automatically
Hash-chained, signed, retained. Auditor opens in a tab.
Multi-location ledger when you need it
One product, one bill, one portfolio view. Add a venue, not a vendor.
Tick what your current till does.
Your score
0/8
Vetka does all 8. Your gap is the case for switching — read it back to yourself before you talk to us.
Problems we hear from operators ready to switch.
Generic failure modes from owners who outgrew their first POS. We don't name the system — if any of these match your Tuesday, you're the reader we wrote this for.
Hardware-light, kitchen-empty
A clean phone-first till that worked solo. Then the kitchen got a printer, then a screen, then needed routing — and the till had no answer. Course-aware kitchen display, station routing and recipe deduction are the kitchen layer. They should be in the box.
AI menu and stock as adjacent products
Menu entry was clipboard-and-keyboard. Stock counts were spreadsheet-and-coffee. Photo-of-menu OCR and recipes-that-deduct-stock are how a 2026 floor OS removes the boring labour. They are the default, not the upgrade.
Multi-venue when the time comes
The first venue worked. The second venue revealed how much was tied to one config. Multi-location ledger, role-based admin, group-wide AI brief — that is the layer that turns a single venue into an operation.
Audit-readiness as configuration
A till that signs receipts is not the same as a till that runs an audit. Hash-chain, retention period, country-correct export, monthly accountant delivery — these are the system. They should be on by default, not opt-in.
Same job, every day. Different cost.
How the same recurring jobs run on each system. Factual. Yours to verify.
- Phone tillPhone app, light back-officePhone + iPad + web. Same UXWorkflow
- Kitchen displayPrinter-only or basic screenCourse-aware KDS, station routingKDS subscription
- AI menuManual entry, one item at a timePhoto → categorised, priced, modifier-mapped~4 hr / menu
- Recipes deduct stockAdd-on or spreadsheetSale fires, recipe deducts, variance flagsAdd-on cost
- Multi-venuePer-venue licence, separate setupNew location in Group, same loginOnboarding
- Daily closeOpen back-office, run reportAuto at 23:59. Signed, archived, sent~30 min / day
- AuditPull export, build packetOpen in a tab. Hash-chained, retainedHalf a day
We don't pull customers.
We're here when you outgrow.
If your current till runs the floor, the kitchen and the books without your team noticing it's there — stay. We don't cold-call, we don't cut commercial deals to flip you. The day your old system costs you a Saturday night, this page is still here.