The short answer
An offline POS is a point of sale that keeps ringing up sales when the internet drops, saves each one on the device, and sends it to the server when the connection returns. In Hajza the device keeps its copy until the server confirms the sale was recorded, so a sale taken during an outage is not lost.
Why does a shop need one?
Load-shedding and patchy connections can take a shop offline for part of the day, and a customer at the counter will not wait for the router. A point of sale that needs the internet for every sale turns an outage into lost sales. An offline POS keeps the counter open and settles the records afterwards.
Offline POS, cloud POS or offline-first?
The three differ in where a sale is saved first, and what happens when the internet drops:
| Kind | Where a sale is saved | When the internet drops |
|---|---|---|
| Cloud POS | On the server, as it is made | The counter waits until the connection returns |
| Offline POS installed on one computer | On that computer | It keeps selling, but the records stay on that one machine |
| Offline-first cloud POS | On the device first, then the server | It keeps selling, then syncs, so every branch and the owner's phone see the sale |
Hajza is offline-first for product sales and stock: they keep working without a connection and sync afterwards. Appointments and service bills work online only.
What can you do offline in Hajza?
Sign in while you are online first. Hajza then keeps the point of sale on that device, so it opens without a connection. From there you can:
- Ring up sales of products, and take cash, card, bank transfer or a split of these.
- Print a receipt for the sale.
- Adjust stock, receive a delivery against a purchase order, and draft a new purchase order.
- Add or edit brands, categories and products, and sell a product you created offline. Photos are added once you are back online.
What still needs a connection?
Everything that depends on the server's live figures:
- Signing in, and the screens outside the point of sale and stock.
- Appointments and the booking timeline.
- Paying with store credit, which needs the customer's live balance.
- Transferring stock between branches.
- Receiving a purchase order that was itself drafted offline, until it has synced.
How does the sync work?
When the connection returns, or the next time the point of sale opens, Hajza sends everything it queued. New brands, categories and products go first, so the sales that use them can find them.
Every queued record carries its own key, so a sale sent twice is recorded once. The device deletes its copy only after the server confirms it, and an expired sign-in never counts as a success: the queue waits and asks you to sign in to sync.
If the server refuses a record, for example a sale of a product that was deleted in the meantime, it stays in a review list with the reason, and you decide what to do with it.
Do offline sales land on the right day?
Usually. Each sale keeps the time it was taken, and the server files it under that time when it syncs within three days and the shift that was open then is still open. A sale taken on Monday and synced on Monday evening, before the shift is closed, counts on Monday.
If that shift has already been counted and closed, or the sale syncs more than three days later, Hajza records it in the shift that is open when it syncs, and keeps the time it was taken on its activity record. A closed shift's cash count is never rewritten, so sync before closing the day where you can.
How does offline selling work with PRA e-invoicing?
In Hajza, PRA e-invoicing covers service bills, and service bills need a connection, so a bill is never held offline for PRA. Product sales, the ones you can ring up offline, are goods and are not sent to PRA at all.
If the internet is up but PRA's own server is slow or down, Hajza prints the receipt at once and the PRA invoice number appears when it is printed again after PRA answers. Failed sends are retried, and the PRA Invoices screen shows each bill's status. PRA's own point of sale component, for systems installed at the shop, likewise marks each invoice as synced or not yet synced.
Source: PRAL, POS Component and eIMS User Manual (PDF, January 2026)
What if two devices sell the last item offline?
Both sales are recorded, because both really happened. Stock stops at zero rather than going below it, and the sale is flagged so you can check the shelf. Offline selling can detect an oversell but not prevent it, because the devices cannot see each other until they sync.