# POS Purchasing Checklist

Use one copy for every shortlisted vendor. Mark **Pass**, **Fail**, or **Not proven** and attach evidence.

## Transaction and payment

- [ ] Unique transaction ID remains consistent across POS and payment records.
- [ ] Approved, declined, cancelled, timed-out, and duplicate attempts are handled safely.
- [ ] Offline transactions have a visible state and documented recovery path.
- [ ] Refunds reference the original sale and enforce approval limits.
- [ ] End-of-day totals reconcile with cash, gateway, and settlement records.

## Inventory and operations

- [ ] Stock timing is defined for sales, returns, voids, waste, and transfers.
- [ ] Multi-outlet stock remains traceable by location.
- [ ] Product, price, tax, modifier, and opening-stock imports are rehearsed.
- [ ] Peak-hour checkout performance is tested with representative data.
- [ ] Staff can follow a documented fallback when a dependency is unavailable.

## Access, audit, and data

- [ ] Every sensitive action records actor, time, reason, and approval.
- [ ] Roles prevent unauthorized discounts, refunds, voids, exports, and settings changes.
- [ ] Raw transactions, products, inventory movements, customers, and audit logs can be exported.
- [ ] API, webhook, retry, rate-limit, sandbox, and identifier behavior is proven.
- [ ] Data ownership, retention, deletion, and exit assistance are written into the contract.

## Commercial and rollout

- [ ] First-year cost includes subscription, hardware, migration, integration, training, and support.
- [ ] Support hours, response targets, backup, and incident escalation are documented.
- [ ] Price increases, renewal, cancellation, and data-exit terms are clear.
- [ ] A controlled pilot has measurable acceptance criteria.
- [ ] Expansion requires reconciliation, incident, support, and operator-readiness gates to pass.