What this cutover guide covers
This guide gives store managers a frame for replacing POS and inventory: prepare, parallel run, rollback. It is not an installer-package page and not an “available to download” claim; concrete install steps are per deployment config and contract.
1. Prepare — checklist
- Write down which data sets move (items, prices, stock, needed receipt history) and which stay archived.
- Name the store owner, HQ owner, and on-site support window.
- Align hardware and network prerequisites with the supplier—this page does not list models.
- Define “ready for parallel day” criteria (e.g., item match, trial totals) before you pick a date.
- Procurement / obtain path: use the neutral “how to obtain” CTA; do not expect a public package URL on this page.
2. Parallel run — rules
- Decide how many days old and new systems run in parallel, and which traffic lanes use which system.
- At the end of each parallel day, compare sales and stock totals; do not advance to the next day on unresolved variance.
- Staff record only on the assigned system; write the dual-entry rule down.
- Do not promise zero downtime; parallel days reduce risk—they do not erase it.
3. Rollback — triggers and steps
- Pre-write rollback triggers (e.g., daily variance above threshold, a critical receipt type missing, counter trade cannot be recorded).
- When a trigger fires, stop new-system traffic lanes and return to the old system per the written plan.
- After rollback, log which lines went to “pending” and who reconciles them.
- Only retire the old system after parallel days close without unresolved variance—the calendar date is not a slogan.
What to avoid
Avoid “package already downloadable,” hardware-certification, and “guaranteed zero downtime” claims. Capability scope belongs on features; daily tasks on the operations guide; selection questions on the selection guide.