Local-first core
Completed bills and core sales records are designed to stay on the active browser/device. This reduces dependence on a constant cloud connection for day-to-day local records.
RESTAURANT RELIABILITY GUIDE
Offline Restaurant Billing: What Local-First Really Means
Free Restaurant Billing stores core records locally and uses service-worker caching for the merchant app, but not every connected feature is an offline feature. Treat offline operation as a workflow to test on your exact device—not as a blanket promise that every module works without internet.
Core local records and connected services are different
Connected features
Authentication, cloud backup/sync and customer-facing connected ordering flows can require internet. A local-first product should not be described as completely cloud-free.
Test before a busy shift
- Open the merchant app and complete your normal sign-in/setup while online.
- Create a sample item and bill using the same device you will use at the counter.
- Temporarily disconnect the network and test the exact billing/printing steps you expect to use.
- Reconnect and verify any connected/cloud state you rely on.
- Export a backup before changing browser profile, clearing site data or replacing the device.
Do not confuse offline billing with multi-device cloud sync
The current free plan is designed around one active device for new accounts after the connected-services trial. Local records do not automatically appear on another device. Cloud and Cloud Plus are separate connected capabilities; core billing remains available under the free-plan rules.
Test the workflow with your own restaurant setup
Start with core billing free, verify your device/browser/printer combination, and keep regular backups of local records.