One platform across borders, or one till per country?
A group opening in a second country has a choice: take the single-country till it already runs and redeploy it locally, or move to a platform that resolves the fiscal rules per site. Both work. The trade is depth in one market against simplicity across several.
Multi-country fiscal platform
One platform and one panel, with country behaviour (BE FDM, DE TSE, FR NF525, IT RT, TR ÖKC, NL Peppol, ES VeriFactu and TicketBAI) handled by adapters and profiles per market.
- Cross-border operations in one panel: Brussels and Istanbul side by side
- A new country goes live in days, not quarters: switch the profile, pair the device
- One audit log across every market, so group compliance is one report
- Menus, staff and price lists clone across borders with VAT classes re-resolved
- Country teams are not blocked on platform work, because adapters stay separate
- The trade: depth in any one market stops where its adapter stops
A single-country till per market
Take the strongest local till in each market, each one deeply wired into its own tax authority and payment processors.
- The deepest local features, the fiscal detail and the niche local integrations
- Often a lower price per market, since smaller-market systems cost less
- Local support in the same language, the same time zone and often the same payment terms
- No risk of a decision taken for another market landing on yours
- The trade: two countries means two platforms, two audit logs and two backlogs
When each one makes sense
Take option A when
Take a multi-country platform when you already trade in two or more countries, or when the next 12 to 18 months put a second-country opening on the plan. What you save on consolidation, one contract, one integration backlog, KPIs that compare, usually outweighs the depth gap in any single market.
Take option B when
Take a single-country till when there is no concrete plan beyond the home market, when a specific local detail (a fiscal nuance, a particular voucher provider, a local payment method) is central to how you trade, or when the local price is a hard constraint.
Frequently asked
Does a multi-country platform mean the same VAT rules everywhere?
No. Any platform worth the name resolves VAT, fiscal-device requirements, invoice numbering and e-invoicing format per country. The platform is uniform; the behaviour switches per site from the country profile. A vendor claiming one VAT engine for everyone is hiding the complexity rather than handling it.
What if I am in one country now but might expand later?
Take the multi-country platform if the expansion is on a dated plan, roughly the next 12 to 18 months. If it is still a maybe, a strong local till plus a clean route to export your data is the safer call, and you move when the second country becomes real.
How do staff and menus move between countries?
Menus clone with tax classes that re-resolve per market, so a 21% class in Belgium becomes 19% in Germany. Staff are less clean: Belgian Dimona, French DSN and Turkish SGK each file their own way, though contracts, shift patterns and pay structures are reusable. The country adapter decides what carries over and what is rewritten.
Architecture comparisons
Service starts at six.
Are you ready?
A live demo, thirty minutes. No slides: we build a scenario from your own restaurant, answer what you ask and talk pricing straight.