Handle an offline checkout safely

Before you start

• An authenticated POS session on the intended branch with offline mode enabled.
• The register explicitly permits a single Cash or Wallet tender; held-order payment also requires an already-synchronized server order.

Steps

1. Read the checkout connection message and remove any feature that requires a live decision.
2. Use only a single Cash or eligible Wallet tender when the screen explicitly permits offline queueing.
3. Submit once and retain the local queue reference; do not treat Payment queued as captured.
4. Keep the same user and branch, reconnect, then verify one matching order and payment before retrying.

Expected result

One eligible Cash or Wallet checkout is retained in the local queue and later reconciles to one server order and payment. The queue reference proves local storage only; it does not prove capture or server completion.

Permissions

• POS access for the active branch is required; business rejections may need a manager to correct the original order, payment, shift, or configuration.

Troubleshooting

Offline checkout does not offer Cash or Wallet, or POS rejects the order instead of queueing it.

Remove features that require a live decision and read the exact message. Only eligible single Cash or Wallet checkout can queue; Card, UPI, promotions, discounts, scheduled fulfilment, Khata, loyalty redemption, and split require connectivity. Business rejections must be corrected, not queued.

POS shows Payment queued, but the matching order or payment is absent after reconnection.

Keep the queue reference and do not submit another tender. Wait for sync, then compare the queue, Orders, and Payments for the same branch and amount. Retry only when the queue is clear and both server lists prove no record exists.

Related articles

Open in TajerGo

Sign in with the appropriate role and confirm your Business Account and branch before continuing.

/billing

Back to POS