Outgrew the regional till.
A floor OS built for cross-border operators — same product, same support, same bill from Berlin to Zagreb. 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.
A till tuned for one regulatory regime
A regional product handles its home market well. The day you open a second venue across a border, the answer is "we are working on it" — and you re-buy the stack. A floor OS designed for Europe handles every fiscal regime as a configuration of one product.
AI menu and inventory as nice-to-haves
Photo-of-menu OCR and recipe-deducted inventory are not premium features anymore. They are how a serious operator avoids a Saturday spent typing a menu and a Sunday spent counting bottles. They should be the default.
Hardware-first onboarding
Tablet, terminal, printer, certified bundle — three weeks before you ring your first sale. A floor OS opens on the phone in your pocket on day one. Hardware is optional, not the on-ramp.
Local payments, distant support
A till that integrates one local processor and one local format works until the operator opens venue two in another currency. One pan-European processor, one bundled card share, one phone number on a Sunday is the bar.
Same job, every day. Different cost.
How the same recurring jobs run on each system. Factual. Yours to verify.
- Open in a new countryRe-onboard, learn local stackPick country in CountryPicker. Same productRe-purchase
- AI menuManual entry per languagePhoto → categorised, priced, mapped, multi-locale~4 hr / menu
- Inventory varianceManual count, paid moduleRecipes deduct, variance flagged dailyModule cost
- HardwareCertified terminal + printerPhone in your pocket. Optional iPad / KDSHardware budget
- ComplianceLocal format, set up by supportCloud signing, country-correct, day oneDays of waiting
- 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.