Skip to main content

Errors and how to handle them

The system stops the operator when an action cannot go through. Errors fall into a few kinds, each with a clear response. This article describes how an error appears and what to do; the exact limit that triggered it — how much may be received, moved, or placed — is described in each flow.

How an error appears​

  • Blocking dialog — the action waits until the operator answers (for example, an ambiguous barcode); they pick an option or cancel.
  • Inline message — a short localised message by the field or at the top of the screen; the operator corrects the input and retries.
  • Error mark (quick save) — in +1 mode a rejected scan shows an error mark in the animation slot instead of the added quantity; switch to confirm-on-save for the detail.
  • Stay-on-screen — a failed verification (a wrong cell or container scan) keeps the screen in place and shows the mismatch.

Kinds of error​

  • Fix and retry — the value or target is not allowed: over a limit, below the available stock, or a mismatched scan. The fact is not saved; the operator corrects it and tries again. The limit itself belongs to the flow — over-receiving in receiving, source stock in relocation, the planned quantity in putaway.
  • Disambiguate — the scan does not identify one item: unknown, ambiguous, or out of context. Handled through Barcode resolution.
  • Escalate — the operator cannot resolve it alone: a product missing from the catalogue, a barcode already tied to another entry, or a document that is not on the PDT. Contact the right person (below) and do not force the action.

Who to contact​

  • Shift supervisor — missing documents, a receipt that is not on the PDT, work organisation.
  • Catalogue owner — unknown products and barcode conflicts.
  • Document owner — items that do not belong on the current document.