How orders get into a queue

An order gets into a queue in four ways. First, the actual steps for manual addition from the queue screen, then an overview of all four routes. These four are alternatives, not consecutive steps.

Step by step: manually add orders

1. Open the queue list and enter a queue by clicking its number or name.
2. Go to the Orders tab (tab names are in English: Products, Orders, Workers, Settings, Auto Queue).
3. Scroll down to Add Orders to Queue. It contains only orders that are not yet in any queue.
4. Narrow the list with the filters above the table: Search…, Time, Integration, Status, Payment, COD, Max. quantity, and the Label checkbox. The crossed-out funnel icon (Clear filters) clears them all.
5. Select orders using the checkbox in a row or All (n), which selects everything matching the filters.
6. Press the blue button with a + and the number of selected orders. It appears only after you select something.
7. Read the response:
   • “Added {n} orders” — they were added;
   • “No orders to add” — nothing was added and nothing was skipped;
   • “Queue is busy, try again in a moment” — someone else was adding orders at the same time; repeat the action;
   • a warning about orders that require manual warehouse assignment — fix this on the order profile; forcing the addition will not change it.
8. If the Orders not added to queue dialog opens, choose: OK leaves them outside the queue; Add despite shortage adds exactly the orders listed in the dialog.
9. Check Orders in Queue above — it refreshes automatically after adding.

Route 1: manually from the queue screen

This is the basic route and it starts from the queue, not the order. There is no “add to queue” action on the orders list — open a queue and select orders from the list of those that are not yet in any queue.

The system returns a breakdown rather than a simple “added” message:

• added,
• skipped — no stock,
• skipped — requires replenishment,
• skipped — already fulfilled,
• skipped — no warehouse.

For what each means and which can be forced through, see “Why was an order not added to the queue?”

Route 2: automatic top-up

A queue can have its own automatic top-up configuration with rules. A background task regularly checks all such queues and adds orders that match the rules.

Rules narrow orders using filters: Integrations, Order statuses, Delivery method, and Payment method (text patterns matched against the name from the order, such as PayU% or %cash on delivery%, in “only” or “exclude” mode), Paid, Order type, Cash on delivery, Bundles, Personalization, Shipment created, Only 1 item, and ranges for order value, number of lines (distinct EANs), and number of units (the sum of quantities across all lines). The line count ignores quantity: 1 EAN × 100 units is one line. Only Min. / Max. number of units distinguishes it from 100 EANs × 1 unit. The scenario rule in route 3 has the same filters.

Order type = SINGLE means exactly the same as during packing: 1 product × 1 unit and not a bundle. A bundle with one line is MULTI — it matches the MULTI rule, never SINGLE. If it entered a singles queue, sorting would scatter its components across bins, and each bin would stop being a basket run during packing and show one order per scan.

A rule must have at least one filter. A rule with no filter matches every order, and in “all rules” mode the results of rules are combined — one empty rule therefore opens the queue (or the whole scenario) to every integration. That is why Add rule creates only a draft (the “unsaved” badge): until you choose a filter, Save rule is disabled, and the system will reject a blank rule anyway. Conditions, sorting, schedules, and batch size do not count as filters.

The top-up history shows one of these results: added, skipped (thresholds), no orders, error, disabled, outside schedule, closed automatically, paused (fulfilment started).

Remember the last one: if the queue is set to freeze during fulfilment, nothing else is added after the first pick or cart reservation. This is intentional — otherwise an operator picking a queue would never see its end.

Route 3: a scenario that creates queues

A level up: a scenario does not top up an existing queue; it creates new queues according to a schedule. There are two modes:

• regular — creates an empty queue and leaves it for automatic top-up,
• batch — creates a queue immediately with a full batch of orders.

The scenario has a dry run, so you can check what it would do before it starts doing it.

Too few carts of one type: “Waiting for or on a cart”

A batch scenario has a “Waiting for or on a cart” field in the Splitting tab, under Limits. It counts only queues belonging to that scenario that are waiting for a cart or are on a cart (they still have something to pick). When the limit is full, the scenario does not create another queue. Orders wait, and a scenario checked later can take them.

Example: 4 carts with 20 shelves and 9 carts with 15 shelves. The “20” scenario is higher in the scenario list (it is checked first — drag to change the order) and has a limit of 4. The 20-shelf carts always get a full queue, and the remaining orders go to queues for 15-shelf carts. When a 20-shelf cart finishes picking, another queue for it is created on the next run.

This is different from “Active queues at once” — that limit counts all active company queues, including manual ones.

Two schedules, not one

The scenario has its own window — it says when to create a queue. Every rule has a second window — it says when that rule may add orders to a queue that already exists.

The hours can differ and usually do. Creation is a moment: the “Morning” scenario opens for fifteen minutes, just long enough to create one queue for the morning. Filling lasts longer: the same rules continue adding orders until 11.

The days must match. A queue created on a day when no rule runs will stay empty — there is no rule to fill it. That is why, when saving, the system will refuse and say which days are affected, and the run will not create a queue on those days. You can save a disabled scenario regardless; the days are checked when you enable it.

A Custom rules scenario with no enabled rules does not take any orders. To have it take everything, select All waiting orders.

Set both windows on the scenario screen: the upper one is in the Schedule tab (Working hours); the second is in the expanded rule, in the When the rule adds orders block. A rule with no window always runs.

Route 4: changing an order that is already in the queue

You do not start this — it happens automatically:

• quantity on a line changes — only untouched units are added or removed. Anything already picked or being packed is never changed,
• a new line is added to an order — it is added to the queue that already contains the order,
• an order is cancelled — its items disappear from the queue, except for units that already have a packed item; that is not undone,
• the order composition changes — its type is recalculated automatically between SINGLE and MULTI.