EazLink guide
Offline fiscal hardware for retail branches
What retailers, dealers, and branch teams should plan when weak connectivity can interrupt fiscal receipts at the counter.
Short answer
Offline fiscal hardware is a local branch device for fiscal work that should not wait on a perfect internet connection. It keeps branch settings, certificate related work, pending sales, receipt proof, and sync behavior close to the POS, while head office still gets visibility when the device is online.
What to remember
- A branch device is useful when fiscal proof must survive weak networks, busy checkout hours, and uneven local IT support.
- Hardware should make the branch easier to support, not turn fiscal work into another mystery box.
- Dealers need plain status for device health, queue depth, certificate readiness, and last successful sync.
- EazLink Hardware gives stores local continuity while keeping the cloud view useful for head office and partners.
The branch problem
Retail branches rarely fail in tidy ways. The router drops during lunch. The tax platform slows down. A certificate needs attention. The checkout PC is shared by several people. A cashier is trying to serve customers while finance asks why yesterday's receipts are missing.
If every fiscal action depends on a clean internet path and a healthy checkout PC, the branch carries too much risk. A local device gives the store a controlled place to receive the sale, protect certificate related work, store pending transactions, and sync proof when connectivity returns.
What the device should do
The device should keep branch fiscal work close to the POS. It should persist the transaction before the sales system treats it as safely received. It should protect certificate and signing related work in a controlled environment. It should preserve queue and proof records so the branch is not relying on memory or screenshots.
It also needs to make support easier. A dealer should be able to see whether the problem is power, network, queue depth, certificate readiness, local storage, or an authority response. If the device only adds another black box, it has missed the point.
- Local persistence before the POS treats the sale as received.
- Certificate related work and branch settings kept close to the store.
- Queue status, retry history, and last sync time for support teams.
- A controlled operating environment instead of relying only on a shared checkout PC.
When software alone may be enough
Some branches have stable connectivity, clean desktop environments, and modest sales volume. A software setup can be enough there, especially when the customer has IT staff nearby and the fiscal process is not time sensitive.
Hardware becomes more attractive when branches are far from IT support, connectivity varies during the day, certificate handling needs tighter control, or dealers need a standard installation they can explain quickly.
When to talk to EazLink
Talk to EazLink when store continuity matters as much as tax proof. That is usually the case for retailers, distributors, petrol stations, pharmacies, and dealer networks where branches cannot stop selling every time the internet misbehaves.
EazLink Hardware gives the branch a local fiscal path. The cloud layer still gives head office status and proof. Dealers get a support view they can use without sending engineers into every store.
When to consider hardware
- Branches lose internet during business hours and still need to issue receipts.
- Certificate handling or signing work should stay close to the branch environment.
- The POS machine is shared, old, locked down, or hard for partners to support.
- The dealer needs a repeatable branch package instead of a custom install each time.
- Head office needs visibility even when the branch works offline for part of the day.
Quick questions
Does hardware replace EazLink cloud?
No. Hardware supports local branch continuity. The cloud layer still helps with visibility, onboarding, partner support, and proof history.
Can the hardware work with ERP and POS systems?
Yes. It is designed for branch rollouts where ERP, POS, and local sales systems need a more dependable fiscal path.
What should dealers ask before selling hardware?
Ask about branch count, network quality, receipt timing, certificate handling, local IT access, and who will support the device after go-live.
What makes hardware useful to finance?
Finance does not buy hardware for the box. Finance cares that receipt proof, queue status, and audit history are still visible after a weak-network day.
Sources: Oracle · Microsoft Learn · Square Support · Oracle Help Center. Used for factual background only.