Hassounh is a private, Arabic-first Flutter desktop application that digitizes the complete front-of-house and back-of-house workflow for a local cafeteria (كافتيريا حسونة). The app runs fully offline on Windows and pins a right-to-left Arabic interface built on the Cairo font family. The product is organized feature-first (auth, cashier, kitchen, menu, tables, inventory, expenses, suppliers, employees, day close, reports, pre-orders, printing, remote auth, and users), with each feature split into data, domain, and presentation layers on top of flutter_bloc/Freezed, go_router, and get_it. The core daily flow revolves around day shifts ('الوردية'). All sales, expenses, kitchen tickets, and supplier payments belong to an open shift; at close, the app compares the expected cash-drawer balance against the actual counted cash, records any shortage or surplus with a mandatory reason, and permanently freezes the shift's records. The cashier and kitchen screens drive point of sale: menu browsing by category, item sizes with per-size pricing, sauce selection, cart management, and takeaway or table orders that print instantly and appear live on the kitchen board. Menu and table management — category/item/sauce CRUD with reordering and search, plus numbered table ranges with individual enable/disable and per-table statistics — keep the storefront configurable. The back-office modules keep operations auditable. Inventory tracks products and balances across warehouse and restaurant locations with add, deduct, transfer, and consumption operations logged end-to-end. Expenses use versioned records: every edit creates a new version, and deletions are soft (excluded from totals but retained in the log). Supplier invoices follow an open-to-closed lifecycle with purchase operations, partial goods receipts, payments with printable attachments, and an immutable chronological audit log that records who changed what and when. Daily and monthly sales reports break out items sold, payment methods, and per-day totals with printable تقفيلة statements. A dual authentication model keeps everything offline — local users with super-admin/manager/cashier roles and local session storage — while menu editing and pre-orders require a separate online session with automatic token refresh and graceful fallback to a cached menu copy when offline. The local Drift/SQLite schema is versioned (v10) with migration records, integrity checks, and automated database backup; printing binds each document type (food, drinks, invoices) to selected Windows printers, and shifts and reports can be exported so nothing is locked inside the app.