Toner Allocation Queue
What happens when shared toner stock can't cover every printer that needs it.
Why a queue exists
When a toner mapping points several printers (often at different customers) at the same Inventory Item, auto-fulfillment only fires when stock is comfortably above the item's Min Quantity and covers every currently open request for that item. A request is held as Pending Allocation β instead of being silently handed to whichever printer polled first β when:
- on-hand stock is at or below the item's Min Quantity (the low-stock hold), or
- stock can't cover all the open requests competing for it.
Set Min Quantity on the Inventory Item (Inventory β Items). A Min Quantity of 0 turns the low-stock hold off, leaving only the contention check.
Working the queue
Go to Monitoring β Toner Allocation Queue. Each row shows the requesting printer, its customer, that customer's user count and SLA tier, and how much stock is on hand versus needed.
- Approve consumes the stock and fulfills that printer's request.
- Order Fresh Instead leaves the shared stock alone and raises a new supplier order for this printer, exactly like the fully-automatic path does when no stock is available at all.
A ticket is raised automatically the moment a request enters the queue, and closes itself once you approve or reject it.
Where to go next
Was this article helpful?