Why an order was not added to the queue

An order can be skipped for several reasons. Two — no stock and replenishment required — can be forced through with one button; the others cannot.

Step by step: force an order into the queue

1. Add orders normally — open the Orders tab, go to Add Orders to Queue, select orders, and press the button showing the number selected.
2. If any were skipped because of stock, the Orders not added to queue dialog opens. It has two sections: Skipped orders — stock shortages and Items outside the picking path — “WMS Replenishment” status.
3. Review the tables: each row shows the EAN, product name, Required quantity, and Available quantity. These are the facts to base your decision on.
4. Press Add despite shortage — exactly the orders in both sections of the dialog are added to the queue. OK closes the dialog and leaves them outside the queue.
5. Forcing does not apply to the other reasons: already fulfilled, cancelled, or no warehouse. Fix those on the order profile and try adding them again.

Skips you can force through

No stock. There is not enough of the item. The order receives the WMS Out of stock status. Forcing adds it to the queue anyway.

Replenishment required. The item is in stock, but not on the picking path — it is somewhere the operator cannot pick it from. The order receives the WMS Replenishment status and a replenishment signal is sent. Forcing works.

The automation sets both statuses — and returns the order to “Ready to fulfil” when the item is back on the picking path. In the order history, the user appears as Automatic Action, the same account used to sign workflow actions and the replenishment planner. Queues created by a scenario also show Automatic Action in the “created by” field. A person’s name in the history means someone clicked manually — automation never signs under the scenario author’s name.

The stock check does not run at all if the WMS setting to block orders without stock is disabled. In that case neither of these situations will occur.

Skips you cannot force through

Already fulfilled. The latest warehouse status is PACKED or DELIVERED. Forcing will not change this — correctly, because that would mean picking again something that has already left.

No warehouse. Warehouse assignment is enabled for the integration, but the line has no fulfilment warehouse assigned. The system will not guess which warehouse to pick from. The message includes the EAN and product name so you can fix it immediately.

Cancelled. It is silently left out.

No items for this warehouse. All lines belong to another warehouse, are already in another queue, are in a virtual or external warehouse, or have quantity 0 (for example, a unit cancelled by the marketplace — there is nothing to pick). A zero-quantity line also does not enter the queue alongside live lines or affect order type: one live unit and one cancelled unit still make a SINGLE order.

Restrictions on auto-sorting queues

An auto-sorting queue has two hard limits that block an addition without any message to the operator — they appear only in the log:

• SINGLE and MULTI orders cannot be mixed in one such queue,
• there cannot be more than one MULTI order.

“I can’t see the order in the list to add”

This is a different problem from a skipped order — the order does not even reach the selection list. Possible reasons:

1. The WMS settings have an empty list of allowed statuses. Empty means block everything, not “allow everything.” This is the most common reason for an empty list just after go-live.
2. The order status is not in the group of statuses allowed for queueing.
3. Its lines are already in an active queue.
4. Its lines are in a virtual or external warehouse.

“Queue is busy, try again in a moment”

Two people are adding orders to the same queue at the same time. Nothing is broken — repeat the action.