What this helps you do

Respond safely when Upstorr says the item, stock, or saved view changed after your page loaded.

Before you start

This warning usually means the protection worked. Another sale, return, staff member, device, or browser tab saved newer information. Upstorr stopped your older screen from silently overwriting it.

Steps

  1. Read which record or quantity changed.
  2. Copy any important unsaved text somewhere temporary if the page says reloading will discard it.
  3. Select Reload latest when offered, or refresh the page.
  4. Read the newest saved values.
  5. Compare them with what you intended to change.
  6. Re-enter only the change that is still correct.
  7. Select Save once and wait for confirmation.

Why this happens

Imagine two staff members open stock when it says 10. A sale reduces it to 9 on the first screen. The second screen still shows 10 and tries to set it to 12. Without a warning, that old screen could erase the sale. Upstorr asks the second person to reload and decide using 9.

The same protection can apply to products, inventory, saved views, deletion, and other records whose newest version matters.

Know what reloading removes

  • Inventory reload can discard unsaved corrections for the selected location.
  • A list edit may preserve pending changes and ask you to review the refreshed rows before pressing Save again.
  • A saved view reload replaces the old view setup with its newest filters, sort, and columns.
  • A delete action may require a reload so you confirm the exact newest record before permanent removal.

Read the warning because the safe behavior depends on the page.

What happens next

After reloading, you work from the newest confirmed version. A new Save succeeds only if the record has not changed again and every update is acknowledged.

Common problems

  • The warning returns immediately: Another process is still changing the record. Find the active sale, import, integration, or staff edit before retrying.
  • My unsaved numbers disappeared: The confirmation warned that reload would discard them. Recount or compare with the newest saved values before re-entering anything.
  • Some bulk changes saved and others did not: Keep the confirmed successes. Correct and retry only the changes still shown as pending.
  • Delete is blocked by a version warning: Reload, verify the newest record and its connections, then decide again.
  • I am the only staff member: Another tab, POS device, customer order, return, import, or automated update can also create a newer version.