POS & retail

POS when the internet fails: design checkout for recovery

Keep sales moving while making the boundary between a saved sale, a paid sale and a synchronized sale explicit. Offline operation needs a recovery process as much as a checkout screen.

Illustrative concept: POS when the internet fails: design checkout for recovery
ASHA TECH Illustrative concept · Sample data

This is the English briefing. The full Thai guide includes additional examples and checklists. ไทย ↗

The practical takeaway

Give each sale a persistent unique identifier. Re-sending a queued sale must not create a second order or stock movement.

Define the records and rules

Give each sale a persistent unique identifier. Re-sending a queued sale must not create a second order or stock movement.

Connect the operational workflow

Show the cashier what is stored locally and what still needs synchronization. A local record alone does not confirm a card or bank payment.

Checks before implementation

After reconnection, reconcile totals, payments and inventory. Test interrupted sync, duplicate submission, device restart and conflicts between branches.

Further reading from primary sources

These references support the standards and integration topics discussed. Workflow examples and figures illustrate system design.

Sources checked: 11 October 2026. Confirm current API access and requirements before implementation.

Start with your idea

What you want your business to do
starts with a conversation today.

Have an idea or a task a system could help with? Tell our team—no technical vocabulary needed.

ASHA TECH · DIGITAL ASSISTANT

Asha, your tech assistant

Automated assistant • Available around the clock

YOUR IDEA. OUR NEXT BUILD.

Tell me your idea
Asha is here to help

Web, apps, ERP or IoT
Start a conversation anytime

Automated assistant
Ready for your next idea

What shall we explore?

Pick a topic to start
Answers from our service information • Automated assistant