Your country edition
Restaurant QR menus and ordering across EU markets
Choose the restaurant’s EU member state so currency, locale, time-zone options, payments, and restaurant tax settings follow the venue instead of assuming every EU country works the same way.
EU signup requires a supported member state. Currency can be EUR, PLN, SEK, DKK, CZK, HUF, or RON depending on that country; staged signup availability may vary.
Illustrative workflow · Product behaviour described on this page
Country-specific currency
The selected member state determines the new restaurant currency; MenuBeacon does not assume EUR.
Local formatting context
Currency, dates, and times follow the restaurant locale and configured time zone.
Restaurant-owned commerce
Eligible online payments use the onboarded restaurant Stripe account, never an unconnected platform fallback.
The operational problem
“EU” is not one restaurant currency or one operating context
A Polish menu should not silently become EUR, and a Portuguese schedule should not inherit a German time zone. MenuBeacon stores the member state separately from the EU market and applies that country’s configured currency, locale, and time-zone choices.
What changes
Member-state context without separate software stacks
Restaurants use the same MenuBeacon workflow while their own country context controls formatting and eligible commerce settings. The restaurant remains the seller and controller of its operating choices.
How it works
Choose the member state before building the restaurant
The member-state selection supplies the market defaults the rest of setup relies on.
-
1
Choose European Union
Start with the EU market, then select the actual member state where the restaurant operates.
-
2
Confirm local defaults
Review the restaurant currency, locale, address, and available time-zone choices during setup.
-
3
Build and test the workflow
Create menus and tables, then test ordering, kitchen status, and receipts before launch.
-
4
Onboard optional services
Connect the restaurant Stripe account and configure only eligible payment and tax tools the venue will use.
Country-aware foundation
Market and member state stay separate for a reason.
- 27 supported EU member-state configurations
- Per-country currency, locale, and time-zone rules
- Member-state selection required at signup
Clear responsibility boundaries
MenuBeacon is restaurant software, not the seller or a tax adviser.
- Restaurant remains seller to its guests
- VAT registration and filing remain with the restaurant
- Stripe and tax features require completed restaurant setup
Good fit for
Use it where it removes a real handoff
- Avoid assuming every EU venue uses EUR
- Keep local formatting tied to the restaurant
- Use one menu and order workflow across supported member states
Straight answers
MenuBeacon European Union questions
Does every EU restaurant use EUR in MenuBeacon?
No. The selected member state determines the configured currency. Supported non-euro currencies include PLN, SEK, DKK, CZK, HUF, and RON.
Why does signup ask for a member state?
EU is the commercial market, not a country. The member state supplies the restaurant currency, locale, time-zone options, and other country context.
Can an EU restaurant take online payments?
Eligible Pro restaurants can do so after connecting and completing onboarding for their own Stripe account and enabling the relevant settings. Staged market availability may vary.
Does MenuBeacon handle the restaurant’s VAT filing?
No. The restaurant remains responsible for registration, configuration, filing, and payment. Eligible restaurants may configure Stripe Tax on their connected account.
Start with the member state, then build the service flow
Create the restaurant with the right country context and test the full guest and kitchen journey before launch.
Start freeWant to look around first? Open the live demo — a fully set-up restaurant, no sign-up.
Free plan available · No guest app required · Clear plan and market limits