Two scans or one — the remembered basket
The standard flow is EAN plus location. For single-item orders, the interface remembers the basket, leaving only the EAN scan.
Standard flow: two scans
- Scan the EAN — the screen shows the item to put away, a suggested location, order details, and the order’s remaining products.
- Scan the location — rules are checked, stock is moved, and the item is closed.
There is no session between the two steps. You can leave, return, or refresh; nothing stays locked.
Short flow: remembered basket
This applies only to single-item orders. After the first manual placement into a basket, the interface remembers its code and adds it to every following scan. From then on, you scan EANs only and placement happens automatically.
When the remembered basket changes or disappears:
| Situation | What happens |
|---|---|
| You manually place an item in a different basket | The new basket is remembered |
| The basket breaks a rule — for example, packing starts from it | The remembered value is cleared; the next scan asks for a location again |
| The code cannot be recognized | It silently returns to the two-scan flow |
| You log out — with the button, through inactivity, when the session expires, or by logging out in another tab | The remembered value disappears |
| You leave Sorting mode | The value disappears — you changed modules or left the kiosk |
| You close the tab | The value does not survive; when you return, you start by selecting a basket manually |
| You refresh the page | The value remains; a refresh does not change the operator |
The remembered basket goes with the operator. A sorting terminal may be shared: one person finishes a shift and the next takes the same Zebra. That is why logging out or leaving the mode clears the basket. Otherwise, the new operator’s first scan could put goods into a basket they had never seen, without asking.
Basket capacity is not checked. You decide when to start a new one.
The basket code is looked up within your warehouse. Codes are unique per warehouse, so searching by code alone could find another warehouse’s basket.
What the short flow leaves out
The one-step response does not include the order’s item count or weight. In practice, you lose the weight; the count would always show “1/1” because the short flow applies only to single-item orders.
Batch sorting
Sorting is the only mode where batch placement is off by default; it must be enabled in company settings. Picking, packing, and receiving/shipping have it enabled by default.
In practice, there is nothing to batch here: every production sorting item is created for one unit, and batch placement is limited to what is on a single item.
Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.
Book a demo