Published information

Guides

Practical guides for restaurant operators in Hungary comparing POS systems, planning migration and rollback, and protecting daily service. Steps and checklists live here; for one-question answers see the FAQ.

• What to check on opening-day POS

  On opening day, verify POS stability in four blocks: 30 minutes before service, before first ticket, before lunch/dinner peak, and at close. Each item says where to look in the admin or on the till.

• What to prepare before switching POS

  Before cutover, clear devices/network, menu prices, accounts/permissions, visible fiscal-ticket items and rollback mindset; separate from the opening-day checklist.

• Restaurant POS selection checklist

  Index only: stay or switch, a real service day, migration sample, rollback, cost and exit, and three allowed conclusions. Steps live in the linked articles.

• When to switch POS—and when to stay

  Decide whether to switch or stay using clear trigger signals. If a change is still on the table, check capability boundaries on the feature pages.

• Test a real service day, not a demo

  Skip the showroom. Shift staff run open-to-close. Only passed, failed, or still unknown.

• Migration: fix the scope, then run a sample

  Fix the scope before cutover, then match counts and identifiers on a shop sample. Until that sample exists, “we can migrate” is not a plan.

• How to roll back: triggers, decision maker, cut-back steps

  When you must stop, who may decide, and how long the old system stays—write a rehearsable rollback sheet, not a verbal deal.

• What to cost for a POS switch: hardware, training, support, fees, exit

  Put five items on one sheet: model numbers, who trains whom, which hours are supported, how much it costs, and how data leaves with you.

• Three conclusions: stay, limited trial, or switch on conditions

  Close selection with only three outcomes: stay, limited trial, or switch when conditions are met. Before you lock the call, check capability boundaries on the feature pages.

• How to compare tills—not the feature list

  Compare restaurant POS on your own workflows and risks—not a feature checklist alone. After shortlisting vendors, confirm capability boundaries on the feature pages.

• Peak continuity: which steps to test when busy

  Open-table, edits, kitchen send, pay, split and void must be run by on-shift staff when busy; verbal promises do not count as verified.

• Shift handoff and day-end: open tickets must not break

  Open tables cannot be ownerless when people change; handoff and day-close need an on-the-spot checklist, not later memory.

• Payment exceptions: decline, interrupt, mismatch

  Classify decline, interrupt and mismatch before acting; this guide does not promise any acquirer brand will always succeed.

• When kitchen print fails: keep selling

  If kitchen tickets fail, stabilize service first: stop chaotic sends, set print or handwritten fallback, reconcile before handoff. Scope: kitchen feature page.

• Limited pilot first: scope, dates, rollback

  Do not “install for two weeks and see”. Write pilot scope, end date, who can stop, and how to cut back.

• How to manage orders and refunds

  How to check orders, refunds and voids in the back office. Taking orders and refunding happen on the till, and refunds follow the shop’s authorization. See the ordering and after-sales feature pages for scope first.

• How to set payment methods, tax rates and surcharges

  Configure payment methods, tax rates and surcharges as settlement basics; payment exceptions are another guide; fiscal/NTAK roles: see the FAQ and the Fiscal and NTAK feature page.

• LAN multi-till and terminal registration: how to manage

  How multiple cashiers register on the store LAN, who approves, and how to recover credentials. Pairing and troubleshooting steps are in the article; capability bounds are on the kitchen and terminals feature page.

• Members, discounts, stored value, and coupons: how to manage

  How to line up members, discounts, stored value, points and coupons in admin; playbook detail follows store enablement. Scope: members feature page.

• Stock on hand, inbound, and sales lines: how to manage

  How to manage stock levels, inbound and sales detail—without mixing it up with cashier item-pick pricing. The feature page shows what it can do; this guide shows how.