The navigation Refresh button and User Hub → Refresh data both run the same hard-refresh routine despite the softer User Hub description. It clears the local cart and Sell workspace state, personal theme and UI-scale overrides in this browser, all session storage, browser caches, and registered service workers before replacing the current URL with a cache-busting parameter. It does not intentionally delete completed sales, catalog records, customers, inventory, or other server records. Never use it during an active or uncertain payment.
Step by step
- Before any refresh, stop and classify the problem. If a payment was submitted, a terminal is processing, a confirmation is unclear, or the customer may already have been charged, do not reload or retry. Check the processor/payment evidence and receipt status first or escalate.
- Record the active business, location, register, user, route, exact error text, and current time. Capture a privacy-safe screenshot when useful. This context can disappear after a reload and is essential for support.
- Protect in-progress work. Complete or deliberately save the cart where supported, copy any unsaved notes or form values, and close dialogs that have an explicit Save/Cancel decision. A local autosave is not enough before Hard refresh because its cart/Sell keys are cleared.
- Use a screen-specific Refresh, Retry, or refetch control first when it clearly reloads only that view’s data. Wait for the request to finish once. Do not hammer Refresh or repeat a submit action while the first request may still be running.
- If the issue is a stale visual route and no transaction or unsaved work is at risk, perform one normal browser/app reload. Reopen the same route and verify the business, location, register, user, and register-session state before continuing.
- Use CentriPOS Hard refresh only when a normal reload did not recover the app or support directs it. On desktop, use Refresh at the bottom of the navigation rail or User Hub → Refresh data → Refresh. On mobile, open More and choose Refresh. All three call the same cleanup routine.
- Expect Hard refresh to remove the browser-local cart and Sell workspace state, the local app-theme and app-ui-scale values, all session-storage values, Cache Storage entries, and service-worker registrations. It then waits briefly and replaces the current route with an _app_refresh timestamp. Do not expect the previous draft cart or modal state to return.
- After the app reloads, confirm identity and operating context before touching records. Re-select the business, location, or register if prompted; confirm whether the register session is open; restore the intended personal appearance if the cleared local override mattered.
- Return to the failed screen and test the smallest safe read-only action first. Do not repeat a payment, refund, import, sync, message, order submission, or other write until you have checked whether the original request completed on the server or external provider.
- If the issue remains, stop cycling refreshes. Contact support with the captured context, what control you used, whether it was a page refetch, normal reload, or Hard refresh, and what changed afterward. Include identifiers that are safe and relevant, but never passwords, API keys, full card data, or OAuth tokens.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Screen-specific Refresh / Retry | Reloads the current screen’s query or retries that view when implemented; it is normally the least disruptive option. |
| Normal browser reload | Reloads the application route but does not intentionally run the CentriPOS cleanup routine. |
| Navigation Refresh | Desktop rail action whose tooltip is Hard refresh app; it runs the full cleanup routine. |
| User Hub → Refresh data | Runs the same Hard refresh app routine even though the card says Reload the latest records without leaving this page. |
| Mobile More → Refresh | Mobile entry point to the same Hard refresh routine. |
| Hard refresh cleanup | Removes app-theme, app-ui-scale, local cart state, Sell workspace state, every session-storage value, Cache Storage entries, and registered service workers in this browser. |
| _app_refresh | Timestamp query parameter added when the routine replaces the current URL, helping bypass stale route assets. |
| What is not intentionally deleted | Completed server-side sales, customers, catalog, inventory, and other tenant records are not the target of client-state cleanup. Verify uncertain writes before retrying. |
| Active payment stop condition | Never refresh while terminal or processor outcome is pending or unclear; reconcile first to avoid duplicate charges or receipts. |
| Context recheck | Confirm account, business, location, register, and session after any reload before resuming work. |
| Escalation evidence | Screen/route, time, user, business/location/register, exact error, privacy-safe image, action already attempted, and whether external processing may have occurred. |
| No exact screenshot | The approved Amelia Grant Harbor & Hearth manifest contains no privacy-safe exact Hard refresh sequence, so this guide intentionally publishes without an unrelated image. |
Expected result
The same CentriPOS route reloads with the intended business context and current saved data while unsaved work is either preserved by the supported flow or deliberately discarded.
Troubleshooting
- Capture the exact screen, time, expected result, and smallest repeatable steps.
- Remove unnecessary customer and payment information from screenshots.
- Include only safe receipt, order, or record references when contacting support.
CentriPOS API explorer · API Center administration