Queue priority — where it comes from and how it affects cart assignment
The same five-level scale as for orders. A queue can have a fixed priority from its template or inherit it from its orders.
In the queue list and selection fields, a star die shows the level — the number of stars is the priority. The column in the list is narrow and has no heading; hover to see the level name.
A WMS queue uses the same scale as an order: from 1 (Very low) to 5 (Very high), with 3 (Normal) as the default.
The old 0–10 number field no longer exists — it was replaced with a list of five levels. Old queues that had zero are now set to Normal.
What it is used for
- A picker scans an empty cart → the system gives them an available queue with the highest priority. If priorities are equal, the older queue wins (A cart reserves a queue — one cart, one queue).
- The queue list has a Priority column. Click the heading to sort.
Where to set it manually
- When creating a queue, in the New queue drawer, use the Queue priority field.
- In the queue details, use the same field in the settings section.
Automatic queues: two modes
In the automatic queue creation scenario (Settings → WMS → Automatic queue creation, Picking tab), the Picker priority field has a mode switch — a lock or arrow — and an adjacent level from 1 to 5:
| Mode | How it works |
|---|---|
| Fixed (lock) | Every queue from this scenario gets the selected level. Its orders do not affect it. |
| From orders (arrow) | The queue takes the highest priority among its orders. The selected level is only the starting value for an empty queue. |
In From orders mode, priority is dynamic: it rises when a more urgent order is added and can also fall when someone changes an order’s priority or the order leaves the queue. This is not a fault — it is how this mode works.
Example: a B2B scenario creates queues containing one order each in From orders mode. An order with Very high priority gives the queue Very high; an order with Low priority gives the queue Low. The picker gets the first one before the second.
Splitting and queue names
A scenario can also split orders into separate queues by priority (Splitting tab, the Each priority separately option) and include the level in the queue name. Without this option, orders with different priorities can end up in the same queue.
Trap: a strict batch with no release time
Automation always takes higher-priority orders first, then older ones. In a scenario with Wait for full queue enabled and or after … min left empty, a low-priority order can wait a very long time if more urgent orders keep arriving. Previously, request order decided this, so this situation did not occur.
Set a batch release time to avoid this.
Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.
Book a demo