Building an Offline-First Retail Hub in Rust: How ApexEdge Keeps Stores Selling When the Internet Dies

If you’ve ever built retail software, you know the happy-path demo is the easy part. The hard part is everything around it: internet goes down, HQ APIs lag or fail, terminals still need to sell, receipts still need to print, and nothing can be lost. I built ApexEdge , a RUST-powered store hub orchestrator that sits between POS/mPOS clients and HQ systems: POS/MPOS <-> ApexEdge <-> HQ Repo: https://github.com/AncientiCe/apex-edge This post is about the actual engineering problems I had to solve, and the architecture patterns that made the system reliable in production-like conditions. The Core Constraint: Stores Must Keep Selling Retail can’t block on cloud availability. That drove my first principle: The store hub is the source of operational truth during a transaction. In practice, that means: local persistence for catalog/prices/promos/customers/config, local cart + checkout orchestration, local document generation (receipt, merchant copy, kitchen chit, etc.), async sync with HQ, not