Published information

Frequently asked questions

What hospitality software, online cash registers, e-cash registers (e-pénztárgép), e-nyugta, invoices and NTAK each do, explained one at a time, with links to the official sources. Hospitality software cannot replace a legal cash register. There are also short answers on choosing a system, switching, limited pilots, rollback, and switching cost and exit. Steps and checklists are in Guides, a day by store type is in Store types, and what the software can do is in Features.

• How should you compare tills—why not start from the feature list?

  Compare from your real busy-day flows and risk points, not the feature list. Fill each cell with verified, failed, or still unknown only. Once you have screened vendors, check the feature pages for what is and is not included.

• Which five cost-and-exit items must be on one sheet—and are verbal “compatible / we support / we export” enough?

  Put five items on one sheet: hardware models, role-based training, support windows, one-off and recurring costs, and export samples that still open after you leave. Verbal compatible/support/export is not enough.

• What rollback items must be written before go-live—who decides, how long does the old system stay?

  Before go-live, write visible triggers, a decision-maker plus deputy, how long the old system stays and the cut-back order, and rehearse with people who will act. “Vendor says we can roll back” is not the same as your store can.

• What must a limited POS pilot spell out—and which three end conclusions are allowed?

  Do not “install for two weeks and see.” Write down scope, end date, who can stop it, and how to cut back. At the end, the outcome is one of three: keep the current system, expand or switch after conditions, or roll back.

• Can “migration is possible” go into the go-live plan without a sample run?

  No. Set the migration scope first, then check counts and identifiers on your own sample. Until the sample matches, “can migrate” does not belong in the go-live plan.

• Which venue page and which feature page should I read?

  What a type of store does in a day: the three Venues pages. Whether a feature exists: the six feature pages. How to do it: the three guide topics.

• How do you test a POS on a real trading day—and how do you record results?

  Have your own shift run a real trading day from start-up to close, not a showroom demo. Record each step as passed, failed, or still unknown.

• Can we check out offline? When does NTAK report?

  Whether you can keep checking out offline depends on the modules and setup enabled in your store; NTAK report status is followed up once you are back online and synced. Offline checkout still needs a later sync, and none of this is a certification claim.

• What should you prepare before switching a POS?

  Before switching, sort out five things: devices and network, menu and prices, accounts and permissions, fiscal and receipt settings, and a way back on cut day. Opening-day checks have their own guide.

• When should a restaurant switch POS—and when should it stay?

  First check whether your store shows real reasons to switch, then whether the conditions for keeping your current system still hold. The decision ends in one of three outcomes: keep using it, run a limited pilot, or switch once written conditions are met.

• Is core POS free? What costs extra? Why can’t I download?

  The six core functions on the Pricing page are marked Free, with a HUF 0 software usage fee; plugins, third-party services and hardware cost extra. The Download page lists Windows 10 and Linux clients, but the installers cannot be downloaded yet.

• Restaurant software, cash registers, e-receipts, invoices and NTAK: which is which?

  How restaurant software, online cash registers, e-receipts, invoices and NTAK differ in Hungary—check current NAV and NTAK pages for duties and dates.