An order that won't allocate is one of the most common — and most quietly frustrating — issues in Manhattan WMS. The order sits there, inventory looks like it's on hand, but nothing releases. This is the path a senior consultant walks to find out why, working from the most likely cause to the least.
1. Confirm inventory is actually available to allocate
"On hand" and "available to allocate" are not the same thing. Check that the inventory is in an allocatable status (not held, damaged, quality-blocked, or in a non-pickable location), that it sits in a location type allocation draws from, and that it isn't already reserved or committed to another order. Inventory that's physically present but logically unavailable is the single most frequent cause.
2. Check allocation mode and whether it's even running
Is allocation set to run automatically on order release, or does it depend on a scheduled job or manual trigger? If a batch allocation job has failed, stalled, or been switched off, orders accumulate unallocated with no error on the order itself. Confirm the job ran and completed.
3. Review the allocation rules and search sequence
This is where allocation fails silently. Walk the logic that matches supply to demand:
- Allocation search sequence: does it resolve to a location and inventory that actually exist for this item? If the sequence only looks in zones with no eligible stock, nothing allocates.
- Unit of measure and rounding: a mismatch between the order UOM and available inventory UOM, or a rounding rule that can't be satisfied, can block allocation entirely.
- Lot, expiry, or attribute constraints: if the order demands a specific lot, FEFO date, or attribute the available stock doesn't meet, allocation correctly refuses.
4. Look for holds on the order, item, or customer
Credit holds, order holds, item holds, and customer-level blocks all prevent allocation. Check the full chain — an order will not allocate while any active hold applies, and the hold is often set upstream in the order management or host system rather than in the WMS.
5. Confirm the order is in an allocatable state
An order has to reach the right status before allocation will consider it. Verify it's released (not draft, on hold, or in an exception state) and that any required upstream steps — payment, verification, wave assignment — have completed.
6. Read the logs for the real reason
If steps 1–5 look clean, the allocation logs usually state exactly why demand couldn't be satisfied — commonly a "no available inventory" or rule-evaluation message that names the constraint. That message is the fastest route to the root cause.
The faster way
Allocation failures are exactly the kind of cross-configuration puzzle SupplyChain Assist is built for — describe the symptom and the system walks the likely causes with the specific checks for your setup, instead of you working the chain alone or waiting on a support queue.