# Multi-Branch POS System Test Checklist

Use the same scenarios and data for every vendor. Mark **Pass**, **Fail**, or **Not proven**.

## Central control

- [ ] Products, prices, promotions, tax, roles, and configuration have versions and effective times.
- [ ] Distribution status identifies which outlets received each change.
- [ ] A bad change can be rolled back without manual edits at every outlet.
- [ ] Area managers can only access outlets within their scope.

## Outlet and offline recovery

- [ ] Transactions can be stored locally when connectivity fails.
- [ ] The queue shows state, event age, errors, and retry.
- [ ] Restarting a terminal does not erase transactions or create duplicates.
- [ ] A payment timeout can be checked before a cashier retries.

## Inventory and integration

- [ ] Sales, returns, voids, waste, receiving, and transfers have movement IDs.
- [ ] Partial receiving and transfer variance can be resolved.
- [ ] An ERP endpoint failure triggers a safe queue, alert, retry, and replay.
- [ ] The source of truth for every domain is documented.

## Reconciliation and rollout

- [ ] Orders, tenders, settlements, cash, stock, and journals can be reconciled.
- [ ] Raw transactions, payments, stock, audits, and configuration history can be exported.
- [ ] The pilot includes a representative outlet and a less reliable connection.
- [ ] Every wave has gates for reconciliation, incidents, support, and operator readiness.