Start by checking whether your store has real signals that a switch deserves a serious look, then whether the conditions for keeping your current system still hold, and only then decide. There are only three ways to close the decision: keep the current system, run a limited pilot, or switch once written conditions are met. “Go live and figure it out later” is not one of them.
Write one real store incident (order change, payment, or day-end) instead of “the system is bad.” A sales demo, a feature list, or a new rule alone is not a switch reason.
- Keep using: the shift can open, take money, fix mistakes, and close; workarounds are written and controllable; the disruption, training, cost and unknowns of a swap are not worth it. In that case, record keep-using as a reasoned decision.
- Limited pilot: scope, dates, rollback path, and who expands or stops it on which signals are written down; it is not “install the whole store” or a vendor promo trial.
- Switch after conditions: live-day and failure tests pass; hardware and support boundaries are clear; migration and exit are checked in-house; rollback is rehearsed; open items become tickable conditions, and until they are all ticked there is no cutover date.
For what is and is not included, see Features; for what different store types do in a day, see Venues. The reasoning and worked examples are in two guides: When to switch POS vs keep using and Three outcomes.
General product information, not legal or purchasing advice, and no guarantee that trading continues uninterrupted during a switch. Last checked: 2026-09-27.