Skip to content
Browse the library

Your data

Troubleshooting

The problems that come up most, and what each one usually means.

On this page

A scan finds nothing

Scanning resolves a code against barcodes first and SKUs second, so a code stored in neither field will not be found. Check the product for a typo, and check that leading zeros survived however the code got into the app.

A USB or Bluetooth scanner is read as a fast burst of keystrokes ending in Enter, of at least four characters. It is deliberately ignored while a text field is focused or a dialog is open, so it never eats what someone is typing; use the field in front of you in that case. Camera scanning needs a browser with barcode detection built in, camera permission, and a secure connection; where that is missing, typing the code always works.

A number looks wrong

Counted products hold whole numbers only. A spreadsheet’s “5.00” imports as five, but a genuine fraction such as 2.5 is refused rather than silently rounded. Switch the product to a measured unit if it really is measured.

If a quantity did not import, check whether the file also carried a stock breakdown column: the breakdown wins, and an unreadable one falls back to the plain quantity with a warning. If a recount added stock instead of setting it, the receive action was used rather than recount.

A cover column showing a dash is the log saying it cannot tell yet, not a product with infinite stock. A product sold as a kit shows what its components allow, not a balance of its own.

Changes are not saving

The banner along the bottom distinguishes three states: offline with changes held on the device, changes currently syncing, and changes that could not sync. The last one is not a connection problem; it offers a retry, and the safe response is also to download a backup from Settings.

Erasing, restoring, importing, committing a count, and committing a take-out each save a safety snapshot to your account first, so they need a connection. Ordinary stock edits and receipts still queue while offline.

If the app cannot load at all and offers to download recovery data, keep that file: it holds the operations it could not reconcile, for review.

Something has disappeared

A product that is gone from the list is most often archived; the Archived chip appears on the Products page as soon as anything is. A product that dropped out of a location filter may simply hold no stock there any more.

History older than the most recent few hundred entries is rolled into monthly archives; use Load older at the bottom of History, and note that the CSV export loads every month regardless of what is on screen.

Deleting a location does not delete its stock: the units move to “No location” and each move is written to the log, so they can be found and put somewhere real.