Offline POS guide
Guide du POS hors ligne : continuer à vendre pendant les coupures
Découvrez le fonctionnement d’un POS hors ligne, les données à conserver localement et les contrôles nécessaires.
Par Équipe produit EazSell · Publié le · Révisé le
La réponse courte
An offline POS keeps essential checkout functions available on the device during a connection problem, then makes pending work visible for review and synchronization. It should never hide whether an invoice is saved locally, submitted or accepted.
What an offline POS should do
A useful offline workflow lets staff find locally available products, build a basket, record the sale and produce the supported receipt output. Each transaction needs its own reference and a clear state so a retry is not mistaken for a second sale.
- Keep the local product and price data needed at checkout.
- Show queued, failed and completed states in plain language.
- Protect against duplicate submission when the network returns.
- Preserve a review trail for managers and support teams.
Offline selling is not the same as fiscal acceptance
A transaction saved on a device may still need a tax authority response. Country rules decide which documents may be created offline, how long they may wait and what must happen after connectivity returns. Confirm those rules before rollout.
- Ask which actions require a live response.
- Define who reviews unresolved items.
- Test a real outage and recovery before launch.
Questions to ask a provider
Ask for a live demonstration that begins online, loses connectivity and then recovers. The operator should be able to explain every status without reading a technical log.
- What remains available offline?
- How are retries and duplicates handled?
- What happens during a long outage?
- Which local fiscal rules limit offline use?
Run an outage test that looks like a real selling day
A polished demo can hide the difficult part: recovery. Use a pilot device with the merchant's catalogue, tax settings, receipt printer and user permissions. Begin a sale online, disconnect the device before payment, complete another eligible sale offline, restart the POS and then restore the connection.
The team should be able to identify every transaction after each step. Check that local records survive a restart, queued work keeps the same reference, retries do not create a duplicate invoice and a manager can separate completed work from items that still need attention.
- Record the time connectivity was lost and restored.
- Compare the POS queue, printed receipts and management records.
- Test failed and successful synchronization.
- Write down who decides whether an item is retried, corrected or escalated.
Decide what staff should say to the customer
Offline status is not only a technical concern. The cashier needs a simple explanation for the customer, especially when an authority confirmation, QR code or final invoice number is still pending. Agree on the wording before launch so staff do not accidentally describe a locally saved record as officially accepted.
The safest message is specific: explain what has been recorded, what document can be issued now and what will happen when connectivity returns. If local rules do not permit the transaction to continue, the POS should stop clearly instead of creating false confidence.
Comparer les choix pratiques
| State | What staff should understand | What to verify |
|---|---|---|
| Saved locally | The device has a local record, but external submission may not have happened. | The record survives restart and has a unique reference. |
| Queued | The POS plans to submit or synchronize the record when conditions allow. | Retry rules, timing and duplicate protection are visible. |
| Accepted | The required destination has confirmed the record where applicable. | The authority or system response is retained with the sale. |
| Needs attention | Automatic recovery did not finish and a person must review the item. | The owner, reason and next action are clear. |
Sources officielles et primaires
Ces sources étayent le contexte réglementaire de ce guide. Vérifiez toujours la version la plus récente avant toute décision de déploiement.
Note éditoriale : Ce guide est tenu à jour par l’équipe produit EazSell pour l’évaluation pratique. Les exigences doivent être confirmées auprès de la DGI et d’un conseiller local qualifié.