Skip to main content

Scanning and barcode input

Across the warehouse the operator identifies the same things the same way — cells, containers, products, and pack types are all recognised from a barcode. This article describes how a code is entered, and how a single scan lands in the right place.

Ways to enter a code​

How a scan is captured depends on the device:

  • Built-in scanner (PDT). The operator aims the terminal's scanner and pulls the trigger; the code drops into the field that is currently active.
  • Camera (Client). On a phone or tablet the device camera reads the code. The camera is only requested on screens where a scan is expected — on screens that do not need one it stays off, so the operator is not interrupted by a camera prompt.
  • Attached scanner (Client). When a ring or handle scanner is paired with the device, it feeds the code straight into the active field without opening the camera.
  • By hand. When a barcode is damaged, missing, or unreadable, the operator types or pastes the code into the field instead of scanning.

One scan, the right field​

A scan is resolved by context — it fills whichever field is active and is interpreted by what the code belongs to:

  • a cell or container code fills the source or the target, depending on which one the screen is waiting for;
  • a product barcode identifies the SKU — see SKU selection;
  • a pack barcode sets the pack type.

The on-screen scanner button starts a scan for the field that is active, so the operator can drive source, target, product, and pack-type selection from a single button without tapping into each field first.

When a scan does not resolve cleanly​

A code is not always enough on its own — it may be unknown to the system, match several products, or not be valid for the current operation. In those cases the operator is guided through a short dialog before continuing — see Barcode resolution.