Most warehouse refusals in xMatix are the sequence protecting itself: the actions enforce allocate → pick → confirm → deliver and start → finish → release, and each refusal names the pending quantity or state it found missing. This page lists the messages the warehouse documents actually produce and what each one means, so the fix is a step, not a search.
A fulfilment action refuses to run
| Message | Meaning and fix |
|---|---|
| No pending allocated quantities found in fulfillment order lines to create allocation. | Every line is already fully allocated — nothing left to allocate. |
| No pending picking quantities found in fulfillment allocation lines to create picking. | Nothing is allocated, or all allocation is already picked. Allocate first. |
| No picking lines available to confirm. | Nothing has been picked yet, or every picking line is already confirmed. |
| Cannot create delivery for Picking Lines that are not confirmed. | Run Confirm Picking before Picked Delivery. |
| Perform Picked Delivery as Picking lines are present. | The allocation has moved into picking, so Allocation Delivery no longer applies — deliver through Picked Delivery. |
| No pending delivery quantities found in fulfillment picking lines to create delivery. | Everything picked is already delivered (the allocation-delivery variant of the message means the same for allocated lines). |
| No picked quantities found in fulfillment picking lines to cancel. / No allocated quantities found in fulfillment allocation lines to cancel. | There is nothing for the cancel to undo. |
| Cannot cancel picking for lines that are not confirmed. | Cancel Picking operates on confirmed picks — confirm the lines, then cancel. |
The step-by-step context for each action is in Fulfilment picking.
A delivery order action fails
- "At least one Delivery Order Line with quantity greater than zero is required to create Shipment." The document has no releasable lines — check line quantities.
- "No branch found for account … to create shipment." Release Shipment serves receiving parties that receive in xMatix, so it needs the customer account linked to a branch. For an ordinary customer delivery, skip the shipment — the delivery order is the complete dispatch record.
- "No pending invoice quantities found in delivery order lines to create invoice." Every line is fully invoiced; there is nothing left for Create Invoice.
- "No Delivery Order Lines found for Inventory Posting." The posting action found no eligible lines on the document.
- Populate Checklist creates nothing. Not an error — the action returns quietly when no checklist template of the Delivery type exists. An administrator needs to define one; see the configuration reference.
A cycle count is stuck
- "Cyclecount lines are required to start counting." The scope filters matched no stock: the item may not track inventory, the branch or location may hold nothing matching, or no filter was set. Adjust the filters and save — lines regenerate while the count is in Draft.
- "Counting has already started." / "Counting must be started before finishing." / "Counting has already been finished." The start → finish order, enforced once each. Check the document's stage before re-running.
- "No Discrepancy found. Cycle Count Lines are required to release adjustment." The count has no lines to release an adjustment from.
- "Adjustment is already released for this Cycle Count." One count, one adjustment. Further corrections need a new count or a manual adjustment.
- The scope fields won't change. Item, item group, ABC/FSN class, storage location and maximum items lock once counting starts, because the lines were generated from them. Branch and company are fixed from creation.
- Other users report "Item is locked for transaction!" A count started with Lock Inventory holds those stock positions and lots. The lock releases when the count is finished — finishing it (or asking the counter to) unblocks the transactions.
Stock looks wrong after warehouse work
The warehouse actions post everything they do to the inventory ledger, so the ledger is where the answer is. Three warehouse-specific patterns before the general method: allocated or picked stock is still in hand but not available, so totals and available figures legitimately differ mid-fulfilment; a released-but-unreceived transfer parks its quantity in transit, in neither branch's bins; and a finished cycle count changes nothing until its released adjustment posts. For the general read-the-ledger method, see Troubleshooting inventory.
Common questions
Why is an action I need missing from the document entirely?
Missing (rather than failing) actions are almost always permissions: custom actions like Perform Picking, Release Shipment or Start Counting each need an explicit grant on a security profile, separate from the entity's read/write grants. Ask your administrator to check the action grants for your profile.
Why does the same action work on one document but refuse on another?
Read the message — these refusals are about the document's state, not about you. The pending quantities on the lines decide what each action can still do, and two documents mid-flow rarely have the same pending state. The tables above map each message to the state it indicates.
Who should fix a refused warehouse action — the user or an administrator?
Sequence refusals (everything in the tables above) are user-level: run the missing earlier step, or accept there is nothing left to do. Administrator territory is the configuration behind quiet misbehavior — missing checklist templates, missing action grants, un-declared van capacities — and the platform-managed posting rules, which neither of you can edit.