What the terminal accepts when scanning
A product always takes priority over a location. There are no type prefixes; the system determines the type from what it finds in the database.
Step by step — type a code manually
If a label is torn or faded, or the scanner cannot read it, type the code.
- Press F2. Without a keyboard, expand the button row in the bottom bar with the gear icon (tooltip More buttons) and tap F2; its tooltip says F2 — Keyboard.
- A visible field appears in the scan area, with a keyboard icon and the hint Scan location or product. Focus moves there automatically.
- Type the code at a normal pace. The terminal recognizes from the typing speed that you are entering it manually, not scanning, and will not send it after a fraction of a second. You can pause halfway to check the label; nothing is submitted.
- A circle appears in the field and slowly fills. When full (about 10 seconds after the last character), the code is sent automatically. To send sooner, press Enter or tap the circle. To correct a mistake, press Esc or tap the X in the field.
- Press F2 again to return to the scanner. The field disappears and scanning goes back to the hidden buffer.
Step by step — scan with the camera
- Check for a camera icon on the right side of the scan banner. If it is missing, the company has not enabled camera scanning for this mode; you cannot enable it from the terminal.
- Tap the camera icon. A view from the rear camera opens.
- Place the code inside the wide, low decoding window. It is deliberately shaped this way because location codes are long and one-dimensional.
- After reading the code, the terminal behaves exactly as if you used the scanner. It will not read the same code twice within 2 seconds.
Recognition order
The scanned code is always checked in the same order. These are not steps for you to perform; they are the system’s order for determining what the code means:
- Product — exact EAN match in your company. A product always wins.
- Location — match by location code. If the location is mobile, the terminal treats it as a basket/cart, not an ordinary shelf.
- Waybill — used if neither of the above matches.
The last option is a fallback, not a validity check: a code that matches nothing else is treated as a waybill.
No prefixes
Baskets, carts, shelves, and racks are all locations. Their code shape does not distinguish them; the system uses location-type flags. Do not look for L- before a location or P- before a product — no such convention exists here.
These codes really do have a defined form:
| Code | Meaning |
|---|---|
WMS-EV-… | Workflow trigger from a printed sheet; intercepted before it reaches the mode |
WMS-CL-… | QR code for a customer label. Only in Packing: prints the label on the station printer without interrupting packing; refused in any other mode. A code that leaves the packer to enter a parcel count, size, or weight opens a calculator screen (when the station has a printer and the carrier and customer address are valid). In order: How many parcels?, then for each parcel Parcel size (S, M, L tiles — parcel lockers only; each parcel may differ) and Weigh parcel (kg, decimal key, up to 2 places; carrier limit shown in the hint). Entered values appear above the calculator; tap one to edit it. The last step is Print label; Cancel creates nothing. Scanning is paused while the calculator is open, so a scanned code cannot be entered as a weight. After this scan, the camera preview closes automatically: codes are printed beside one another on a sheet, and an open camera would immediately read the next one. A short high-pitched tone confirms the label was sent to the printer; you can hear it with voice turned off, provided sounds (F3) are enabled. |
EMPTY | Stocktake: mark a location as empty |
S / M / L | Packing: parcel size |
MB-{number} | Master carton |
A company can also define custom trigger codes entered manually. These are matched against the full value, not just its beginning.
Three equivalent ways to scan
Scanner — the default. The terminal keeps a hidden field focused and restores focus to it every 100 ms, so scans go to the right place even if someone clicked the background. The scanner sends the entire code at once. It is submitted immediately when the scanner sends Enter, or after about 0.12 s if it does not. This works with the factory DataWedge settings; you do not need to enable “Send ENTER key” in the profile. In this mode, the on-screen keyboard does not appear, whether you touch the screen or scan. It appears only where you enter text: in F2 and in dialog text fields.
Keyboard (F2) — the field is visible. The terminal watches typing speed to determine who is entering the code:
- Scanner (the entire code arrives at once): submitted after about 0.12 s, faster than before.
- Person (typing with pauses): the code is NOT submitted after a fraction of a second. A circle grows in the field; when full (10 s), the code is sent. Enter or tapping the circle sends it immediately.
A pause while manually transcribing a code therefore no longer submits half of it. Esc clears the field.
Camera — the camera icon in the scan banner. It uses the rear camera by default. Its decoding window is deliberately wide and low because location codes are long and one-dimensional. The same code will not be read twice within 2 seconds.
When a scan is rejected
- A save is in progress — the scan is rejected and you hear a warning. It is never silent.
- A trigger confirmation is waiting — scanning the same code again confirms it; any other code is rejected with a warning.
- A dialog is open — the scanner is paused unless that dialog expects a scan as a valid answer (for example, in the quantity keypad, another scan means one more unit).
Scan history
The bottom bar has History: the last 50 codes, with mode and time. It is stored only in device memory and disappears after a reload.
Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.
Book a demo