How can we help?

The till can use its saved catalogue and save sales locally during a connection outage on a prepared device. Offline does not mean that every online service is available. The connection indicator and the order-sync status are separate: Online does not confirm that every local sale has reached the server.

Prepare this till while connected

1. Sign in to the intended shop, open Till (ePOS) and check the till point and outlet. Prepare each device and browser/app separately; another device does not share this till’s local sales.
2. Let the catalogue finish loading. Open Service → Overview, review Catalogue status, its last-sync information and counts, and check that the products and options staff need can be found. Offline stock and customer information are saved snapshots, not live availability.
3. Review Local storage in Service. Resolve unavailable-storage warnings before relying on local sales. Keep the same browser profile/app and website address. Do not use a fresh/private browsing session as your prepared till.
4. Check your scanner with the intended product codes and confirm its selected product/option. Set up the intended printer route and verify a receipt on the actual device before relying on it. Confirm that any local printer connection remains available if the internet fails; an internet outage and a local-network outage are different.
5. Agree which payment methods staff may use during an outage and how they will reconcile sales afterwards. A working catalogue or cash sale does not establish that a card terminal can authorise payments.

What remains available offline?

Search products and scan barcodes

Offline capability: Available from the catalogue already saved on this till. Barcode matching uses its saved SKU list.

What to check: Search by product name or enter/scan its code. Check the exact option and price. Newly added or changed items may require a connected catalogue refresh. Scanner connection and input setup still matter.

Edit the basket

Offline capability: Add/remove cached products and options, change quantities and edit a line price locally.

What to check: Review quantities, options and To Pay before receiving money. A local basket change does not update catalogue prices in Builder.

Manual discounts

Offline capability: The offline Discount screen provides percentage and money-off controls; these are different from online discount codes.

What to check: For a percentage discount, enter the intended percentage, apply it and check the displayed discount and To Pay. Until the offline money-off calculation has been corrected and checked, avoid the fixed-sum basket discount. If shop policy permits a line-price adjustment instead, enter the intended final line price and review the whole basket.

Existing customer lookup

Offline capability: Search and select customers already present in the saved customer list.

What to check: Enter at least three characters and check the selected customer. Missing customers cannot be fetched while offline; creating/editing customer accounts needs the connected customer workflow.

Customer-group / special prices

Offline capability: Choosing a customer offline does not fetch their group-price overrides.

What to check: Do not assume the displayed price is the customer’s current group price. Reconnect for normal group pricing, or use a shop-authorised checked line-price adjustment. Recheck every affected option.

Sell on account / receive an account payment

Offline capability: These are different tasks. An On Account sale can be offered for a selected cached customer with positive remaining credit. Receiving money against an existing account balance requires ShopTill-e to be available.

What to check: Cached credit is not a fresh balance across other tills. Use On Account only under your shop’s agreed outage policy and reconcile after reconnecting. Defer account-balance payments until connected.

Gift vouchers and discount codes

Offline capability: New voucher/code validation requires the server. The voucher control is hidden offline; the offline Discount screen uses manual amounts instead of code validation.

What to check: Defer voucher redemption and code-based offers until connected. Scanning a voucher is not the same as scanning a product. Do not assume a voucher or code already on an open basket has been freshly revalidated.

Order history and email receipts

Offline capability: The ordinary Orders and Email controls are hidden offline. Local sales on this device can still be inspected in Service.

What to check: Use Service → Orders & backups for local records, not as a complete customer/server order history. Find the confirmed server order after reconnecting before emailing its receipt.

Print a receipt locally

Offline capability: The till can build a receipt from local sale data and cached/inline receipt templates, using its configured browser or native/local printer route.

What to check: The printer, its connection, permissions and any app bridge must work. Use the saved sale’s receipt/reprint action; do not take payment again because paper did not print. Some images may be unavailable if not cached.

Save and reconnect

Offline capability: Sales are queued in this device’s local order storage. The app attempts queued uploads when connectivity returns, while it is running.

What to check: Wait for the actual saved result. Keep this till available, then inspect pending/failed/confirmed records and match server orders; reconnection is not a guarantee that every sale was accepted.

First launch is not the same as a prepared session

A new device, a cleared browser profile or a till never opened successfully online has no assured offline app or catalogue to load. Connect, sign in and prepare it first. A previously prepared till can use a cached app and catalogue when they are still present, but do not close or refresh an operating offline till just to test that fallback. A cached staff PIN unlock is not a replacement for a fresh server login.

When the connection fails

1. Read the connection indicator and separate sync message. Keep the current page and device available.
2. Use the table above to choose a task supported by this till’s saved data. Check the basket and payment evidence before completing the sale.
3. Read the actual result. The order was saved offline or a local-save/pending message means local storage, not server confirmation. Keep its reference.
4. If you see Order not saved or Sale not saved, keep the basket and download the offered recovery report. If money was already received, do not charge again. Use payment-review guidance for an uncertain card attempt.

When connectivity returns

1. Keep the same till open and complete any legitimate sign-in it requests.
2. Review the sync message and Service → Orders & backups. Pending sales are retried automatically, but some failures need attention. Sync pending orders in Service can request another pass; it does not itself prove success.
3. Match the local reference, amount and payment evidence to the corresponding Builder order. Check all affected records, not only the latest sale.
4. Before retrying failed orders, read their errors and check for an existing server order. Do not retry an incomplete-order or uncertain-payment warning blindly. Preserve a private JSON backup and give support the exact warning and references when reconciliation is needed.

Protect local work

Do not clear site/browser storage, delete local records, change profiles or reinstall the app to remove a warning. These actions do not synchronise sales. Use Service and local-order backups to inspect/export the affected records, and receipt troubleshooting when the sale is saved but output is missing. Keep recovery files private.