Start here
Treat offline behavior as a workflow to test, not a checkbox. Disconnect the test register during the vendor demo, complete the permitted transactions, reconnect it, and verify settlement and reporting. Keep a separate plan for internet failure, payment-provider failure, dead hardware, and total platform outage.
Separate the failure types
- Internet connection fails but local hardware works
- Payment terminal loses connection
- Register or tablet fails
- Receipt or kitchen printer fails
- POS cloud service is unavailable
- Store loses power
- Router, switch, or local network fails
Ask who carries the payment risk
Some offline card transactions are authorized only after reconnection. Ask about transaction limits, time limits, unsupported card types, declined uploads, duplicate prevention, and who absorbs loss. Get the answer in writing.
Write the staff response
- Who declares fallback mode
- What can still be sold
- Maximum offline transaction amount
- How receipts and order numbers are recorded
- How the kitchen or pickup area receives orders
- When card acceptance stops
- How deposits and inventory are reconciled afterward
Test restoration
The recovery step is where duplicates and missing sales appear. Verify queued transactions, deposits, tips, taxes, gift cards, inventory, online orders, and end-of-day reports after reconnecting.
Sources to confirm before buying
Features, terms, support, and compatibility can change. These links are starting points; the written quote and agreement control the actual purchase.