Offline continuity
The internet goes down. The line doesn't.
Offline-first by architecture — not a cached menu and a prayer.
What's inside
Every module, one line each.
Keeps working
Cash sales, carts, and the guest queue run entirely at the register.
Queued replay
Offline actions journal locally and replay in order on reconnect.
Conflict repair
Two registers sold the same package offline? Reconciled, not oversold.
Safely paused
METRC lookups and card flows wait for connectivity — by design, not by crash.
Honest status
Staff see queue depth and sync state right on the register.
The whole story
Built for the day your ISP has a bad one.
Ironclad's register is offline-first: the source of truth for an in-flight sale lives at the counter, not in a distant region. When connectivity drops, cash sales keep closing, carts keep building, and Guest Flow keeps moving. Every action is journaled locally and queued — the same journal that powers the audit trail powers the outage.
We're equally honest about what pauses. Live METRC patient lookups and card-present flows need the network, so they wait — visibly, with the register telling staff exactly what's queued. On reconnect, mutations replay in order with conflict repair, so overlapping offline sales against one package reconcile instead of overselling. The day ends with books that agree and a METRC trail with no holes.
Next step