Outgrew the iPad till.
Phone-first floor, cloud-signed receipts, AI menu work and inventory variance — in one app on the device your team already owns. 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.
When the iPad dies, the floor stops
A till that lives on one device class is a single point of failure. Battery, drop, screen — and a Saturday rush is looking for the manager. A modern floor OS runs on every phone the team already carries; the till is wherever a hand is.
Inventory and AI as paid add-ons
Recipes that deduct stock and AI that reads a menu off a photo are not extras anymore — they are the baseline of running a kitchen without surprise variance and without typing 200 dishes by hand. They should be in the box, not on the upsell sheet.
Three line items on one bill
Subscription, payment processor, fiscal module — three vendors, three monthly invoices, three places to call when something breaks. One contract, one bill, one phone number on a Sunday is the bar.
Reservations and reports as separate SKUs
A floor OS sees a booking, a table state, a check, a close, an export. If those live in five products with five admin panels, your manager is the integration layer. They should be one continuous flow.
Same job, every day. Different cost.
How the same recurring jobs run on each system. Factual. Yours to verify.
- Open a phone tillBuy iPad, install app, charge nightlyOpen Vetka on the phone in your pocketHardware cost
- Add a dishType into back-office, save, syncPhoto of menu → AI extracts items, modifiers, allergens~4 hr / menu
- Daily closeRun report, sign manually, fileAuto at 23:59. Signed, archived, sent to accountant~30 min / day
- Track stockSeparate add-on, manual countRecipes deduct as you sell. Variance flagged dailyAdd-on cost
- Take a cardSeparate processor contractBundled into tier — 0.5% to 2.5% all-inVendor count
- Add a venueBuy second licence, second iPadNew location in Group, same loginOnboarding
- See an auditPull from archive, build packetOpen in a tab. Hash-chained, retained, readyHalf 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.