How It Works
One pipeline from device to dashboard.
Four stages move your transaction data from the depot floor to a unified cloud — resilient to outages at every step.
Install at the depot.
The Windows agent runs in the background at boot, polling connected Microload and Accuload devices every 10 seconds. No port exposure, no tunneling — it reads devices over their local serial or network port.
Capture locally. Always.
Each reading is normalized into the unified schema and written to a local SQLite database with a sync queue. If the internet is down, capture continues uninterrupted and the queue simply grows.
Sync when online.
Every 5 seconds, when connectivity is available, the engine pushes pending records to the cloud. Responses are handled idempotently — created, processed, or already-exists all resolve cleanly, and failures stay queued for retry.
See everything.
The cloud deduplicates on machineId + transactionId and stores the durable record in PostgreSQL. Your web dashboard shows live machine status, transaction history, sync health, and analytics across every depot.
Sync Response Handling
Idempotent by design.
The agent interprets every cloud response deterministically. Duplicates are never re-sent; failures never get dropped.
| Response | Meaning | Agent Action |
|---|---|---|
| 201 | Created | Mark synced |
| 200 | OK / processed | Mark synced |
| 409 | Already exists | Mark synced |
| 500 | Failure / timeout | Keep pending |