Who this guide is for
This guide is for store managers and buyers choosing a POS with inventory for a supermarket or retail store in Hungary. It is not a capability brochure and not a price list; the goal is to line up decision questions before contract or install.
Define the store boundary first
Start selection by writing one sentence on the traffic pattern, weighing needs, and stock accuracy the system must carry every day. If the boundary is vague, demos and migration plans stay vague; read every promise back as enabled for the store and deployment config.
Tasks × attention points (comparison table)
The table maps typical store tasks to what to ask and what to watch. There is no price column and no vendor ranking.
TaskAskWatch Daily checkoutWho opens the shift, how do you close, what happens on returns?Shift totals and receipt checks should be clear; do not invent menu paths Weighing / labelsWhere is weight captured, how does the label meet the counter price?Do not demand a specific scale model from a marketing page; boundary is per deployment StocktakeHow do you find book vs physical variance?Recording window and write-back rules must be explicit Purchasing / receivingHow do supplier lines land on the same item fact?Same catalog at counter and backroom Multi-store / HQDo you need a shared price and stock picture across sites?If rules are unproven, treat as unknown—do not assume copy-out Invoicing / data syncDo you need software connectivity for invoicing?See the features / FAQ channels for detail; this guide does not expand legal framingMigration-risk questions to ask early
Before you pick a go-live date, write down: which data moves (items, prices, stock, receipt history); what stays archived in the old system; who owns parallel-run days; what triggers rollback. Do not accept a “zero downtime” guarantee; continuity depends on preparation and parallel-run quality, not slogans.
What this page does not promise
Not a price list, not a package download URL, not a hardware-model catalog, and not a certification claim. For capability scope go to features; for daily steps go to the operations guide; for cutover timing go to the migration guide.