How Checking for Updates Works
Access requirements. No PIN or role gate — anyone can tap this.
What it does depends on your store's setup, and the screen looks different too. Older ("legacy") stores show a configuration hash and "Last checked" time, and this button triggers a real on-demand check against the server. Newer ("live") stores show only "Updated" and skip the other two rows.
On legacy stores, this compares your terminal's configuration against the server and only downloads a full refresh if something's actually changed. On live stores, configuration already streams in continuously in the background — tapping this button doesn't re-fetch anything; it just re-checks the connection.
On a live-config store, this can report "up to date" without truly checking anything. If you were already connected earlier in this app session, tapping the button can say "Configuration is up to date" instantly — even if you're offline right now — because it's reusing an existing session rather than re-verifying the network.
You don't need to tap this for things to sync. Legacy stores check automatically every 15 minutes; live stores stream changes continuously with no polling at all. This button is just for when you don't want to wait.
Checking Your Configuration
Step 1
Go to Settings → Data.
Step 2
Tap "Check for update." The button reads "Checking…" while it works.
Step 3
A banner appears for a few seconds: "Configuration updated" if something changed, "Configuration is up to date" if nothing did, or "Failed to check for updates" if it couldn't complete.
What "Updated" and "Last Checked" Mean
Step 4
"Updated" is the last time this terminal actually pulled a real change — not just the last time it looked. "Last checked" (legacy only) is the last time it looked at all, whether or not anything had actually changed. On live-config stores, "Updated" means something looser — it's the last time the terminal successfully made contact with the sync service, not proof that anything actually changed.
What It Looks Like
Legacy stores show "Current configuration" (a hash), "Updated," and "Last checked." Live-config stores show only "Updated" — the button still works the same way you'd expect on either; it just checks something different underneath.
A hash or timestamp that's never been set shows "N/A" or "Never."
Troubleshooting
Says "Configuration is up to date" but you're pretty sure something changed: on live-config stores, changes stream in continuously in the background — you likely already have it, whether or not you tap this button.
Says "Configuration updated" but nothing seems different: on live-config stores, this can fire without any real data check — take it as "the terminal is connected," not necessarily "something just changed."
Tapped it while offline and it still said "Configuration is up to date": on live-config stores, this can happen if you were connected earlier in this session — it's not always a live network check. Don't rely on it to confirm you're actually online.
"Failed to check for updates": check your connection and try again — this message covers both a network issue and other failures, with no way to tell which from the screen alone.
You don't see a "Current configuration" hash or "Last checked" row: expected on live-config stores — those two only show for stores still on the older sync method.
Not sure if you even need to tap this: you usually don't — configuration syncs on its own either way (every 15 minutes on legacy stores, continuously on live ones). This button is just for when you don't want to wait.