Sync & Offline
What happens when you make changes without signal, and how PourCost reconciles when you reconnect.
Updated May 6, 2026
PourCost is offline-tolerant. You can build cocktails, scan invoices, and edit ingredients on a basement walk-in with no signal. Changes queue locally and replay when the network returns.
What works offline
- Reading inventory, cocktails, and previous invoices.
- Editing existing data and creating new ingredients/cocktails.
- Capturing invoice photos (OCR processes when you reconnect).
What needs a connection
- First sign-in on a device.
- Catalog search (we don't bundle the full catalog locally).
- Recipe library adoption.
Conflict resolution
If you edit the same record on two devices while one is offline, PourCost applies last-write-wins on a per-field basis when the offline device reconnects. The change you made most recently sticks. We're moving to per-field merging for ingredient and recipe data; for now, last-write-wins is the rule.
Tip
If a sync seems stuck, pull-to-refresh on any list view forces the client to retry. The little dot in the header turns from amber (pending) to green (synced) when the queue is empty.