Where Does Toast POS Store Menus and Sales?
Where Toast POS keeps sales and menus on Android devices, and what lives in Toast Web cloud instead.
Last updated
Toast splits register duty between handheld and cloud. Menus and settings are edited in Toast Web and pushed to devices. Sales upload to reports as they happen. The Android terminal keeps a working copy and an offline queue in private app storage you cannot browse.
That private area needs no backup routine. The cloud reports are the record. For device swaps, sign into Toast on the new hardware and let menus sync. Old handhelds should stay online until the queue drains. Package names vary slightly by Toast build, so avoid hard coding the data path in scripts.
Where Toast POS stores this, by platform
/data/data/com.toast.pos (private, plus Toast Web cloud)
Menus and reports live in Toast Web cloud. Queue and cache sit privately on the device. Keep the terminal online until offline payments upload. Package suffix varies by build.
Toast Web cloud (device cache private)
Kitchen and guest facing displays pull from the same Toast cloud account. History and menus follow the login, not the device. Verify in Toast Web Reports after hardware swaps.
Frequently asked questions
How do I back up Toast menus and sales?
Menus, taxes, and staff live in Toast Web and sync down. Past sales live in reports in the cloud. The handheld holds a queue and cache in private storage. Do not clear app data with pending offline payments, since the queue cannot be browsed or recovered by hand.
Do offline Toast payments survive losing signal?
Briefly, in a protected queue inside private storage. The register uploads when back online, and reports update in Toast Web. Verify in Reports before closing. Wiping the device with unsent payments loses them, so keep the terminal online at close.
Notice an outdated path? Let us know.