Asosiy kontentga o'tish
← Back to blog
TechnologyEnglish2026-06-108 min

Offline-First POS — How RAOS Works Without Internet (Tauri + SQLite)

Technical deep-dive into RAOS offline-first architecture. Tauri framework, SQLite local database, Outbox pattern, event-sourcing for financial data.

The Connectivity Challenge

In Central Asia, reliable internet connectivity remains a challenge. Even in Tashkent, Uzbekistan's capital, connections can drop during weather events or maintenance. In rural areas and smaller cities, the situation is more pronounced.

For retail businesses, every minute of POS downtime means lost sales. A cloud-only POS system that stops working when the internet drops isn't just inconvenient — it's a direct hit to revenue.

RAOS takes a different approach: offline-first. The system is designed to work without internet as the default mode, not as a fallback.

Architecture: Tauri + SQLite + Outbox

Tauri Framework. RAOS desktop app is built on Tauri — a modern framework written in Rust. Unlike Electron, Tauri produces lightweight binaries (~10MB vs ~150MB) with native performance.

SQLite Local Database. All data resides on the device. Products, prices, customers, transactions — everything is stored locally. The app never needs to query a remote server to process a sale.

Outbox Pattern. Every transaction is appended to an Outbox table. A background sync worker monitors connectivity and pushes Outbox entries to the server when internet is available. If a push fails, it retries with exponential backoff.

Event Sourcing for Financial Data. Financial transactions use event-sourcing — never last-write-wins. This ensures data integrity even when multiple devices sync after extended offline periods. Each transaction has a unique idempotency key to prevent duplicates.

Conflict Resolution Strategy: - Financial data → Event sourcing (immutable events, server reconciles) - Non-financial data → Last-write-wins (timestamps) - Every sync operation uses idempotency keys

What Works Offline

Full offline capability: - Product sales and payment processing - Inventory viewing and deduction - Cashier shift open/close - Receipt printing (local printer) - Barcode scanning - Discount application - Customer data viewing

Requires internet (queued when offline): - Soliq.uz fiscal receipt submission (queued, auto-sent on reconnect) - Multi-branch synchronization - AI report generation - Telegram notifications

The key principle: sales are NEVER blocked by internet issues. Everything that requires connectivity is queued and processed asynchronously.

Why This Matters for Uzbekistan

RAOS is currently the only POS system in Uzbekistan with full offline capability. Billz, iDokon, and YesPOS all require constant internet connectivity.

For a retailer in Namangan or Bukhara where internet drops 2-3 times daily, this isn't a nice-to-have — it's essential. Even in Tashkent's bazaars where Wi-Fi is unreliable, offline mode ensures zero lost sales.

The technical investment in offline-first architecture pays dividends in business reliability. A POS that works 100% of the time, regardless of connectivity, is a POS that protects your revenue.

Try RAOS free for 30 days: raos.uz

Try RAOS free for 30 days

Get started →
offline POSoffline-first architectureTauri POSSQLite POSworks without internet