Skip to content
Smart Lead Tech
Home
Services
Our work
Saudi Arabia
About us
Blog
Contact us
🇸🇦العربيةContact now
Smart Lead Tech

Smart software solutions

Follow us

Company

  • About us
  • Our work
  • Our services
  • Saudi Arabia
  • Restaurant POS
  • Contact us
  • Book a call

Quick links

  • Blogs
  • Pricing
  • Refund policy
  • Privacy policy
  • Terms and conditions
  • Data deletion

Contact us

  • Egypt — Head Office

    Office 6, Bldg 23, Makkah Al-Mukarramah St., Omraneya, Giza 3540203, Egypt
  • Saudi Arabia — Branch

    Bldg 2646, Secondary 123, Street 7697, Ishbiliyah Dist., Jubail 35416, Kingdom of Saudi Arabia
  • Email address

    help@smartleadtech.com
  • Phone number 🇪🇬

    +20 102 201 4671
  • Phone number 🇸🇦

    +966 53 044 7112

© 2026 Smart Lead Tech. All rights reserved.

  • Smart Lead Tech Information Technology LLC·Commercial Register ⁦61239⁩·Tax ID ⁦774-391-316⁩

  • Smart Lead Tech Software Establishment·CR ⁦7054902585⁩·VAT

Flutter for POS systems: offline-first done right

POS apps do not run in perfect conditions. The internet drops, power cycles, and the branch still must sell. This note captures the pattern we use on TtaKkaa Cashier to keep operations smooth regardless of connectivity.T…

11/05/2024 — 8 min read

Flutter-built POS application

POS apps do not run in perfect conditions. The internet drops, power cycles, and the branch still must sell. This note captures the pattern we use on TtaKkaa Cashier to keep operations smooth regardless of connectivity.

Three principles

  1. Local source of truth: SQLite is authoritative; the network is just a sync.
  2. Events-first: every sale/refund/discount is logged as an event, not a row mutation.
  3. Sync is never in the user path: background queue — we do not block receipts on network.

Stack

  • Drift (SQLite) for local persistence.
  • Riverpod for state management.
  • WorkManager for smart sync the moment network returns.
  • Laravel 11 on the far side, consuming event batches.

Conflict resolution

We use a minimal CRDT for stock line-items: additions / deductions are associative, so even multi-branch offline operations merge cleanly.

Common challenges

  • Thermal printer: ESC/POS over Bluetooth works even offline.
  • Barcode scanner: listen directly to USB-HID events.
  • Product updates: applied on reconnect with resolvers so pending tickets are not broken.

Takeaway

A POS app is not "an online mobile app" — it is a tiny distributed system inside one branch. Plan for that and your system will stay up in the worst cases.

Share

Projects related to this article

  • POS SystemsFlutter

    TtaKkaa Cashier — Restaurant POS Suite

    End-to-end POS for restaurants & cafés: tables, kitchen, inventory, live reports.

    Show more
    TtaKkaa Cashier POS application screen
  • POS SystemsFlutter

    TtaKkaa Kitchen — Restaurant Kitchen Display Suite

    A professional Kitchen Display System (KDS) for real-time order flow: display, prep and dispatch — synchronised over WebSockets.

    Show more
    TtaKkaa Kitchen System — chef-facing order display
  • POS SystemsReactLaravel

    TtaKkaa Admin Panel — Multi-tenant POS Control Centre

    Multi-tenant control centre for stores, branches, invoices and subscription plans across the entire TtaKkaa POS suite.

    Show more
    TtaKkaa Web Admin Panel — multi-store control centre

Related Blogs

  • Three devices — a cashier terminal, a kitchen display and a customer phone — running one Flutter codebase

    One codebase from the cashier to a salon marketplace: 10 lessons from two years of Flutter

    The TtaKkaa ecosystem alone is four apps: cashier, kitchen display, customer app and store dashboard. Add Beauty Map and Home Beauty for beauty services, and Meshareeb for beverage delivery in Kuwait. All Flutter. Here a…

    02/24/2026 — 8 min read

  • Diagram of a language model connected to POS and inventory systems through MCP servers

    MCP for the CTO: letting AI safely “touch” your POS, inventory and CRM

    For years the problem was the same: the model is smart, but isolated. It knows everything about the world and nothing about your inventory. Model Context Protocol (MCP) is the open protocol that ended that isolation in a…

    08/05/2026 — 9 min read

  • A Saudi e-invoice with a QR code next to a POS screen

    ZATCA e-invoicing phase 2: what we learned integrating POS and inventory systems with Fatoora

    No feature is requested by a Saudi merchant before “is the system connected to ZATCA?”. Phase 2 of e-invoicing (integration) turned the invoice from a printed slip into a digitally signed XML document reported to the Zak…

    09/11/2026 — 9 min read