Who should decide which backorders receive scarce stock?
Format: Article.
Name a person who can decide which backorders get scarce stock. Give that person clear rules and the promises already made to customers. Do not let a software sort order make the choice by default. Sales can explain customer needs. Warehouse staff can check usable stock. Neither fact alone sets the rule for who gets it.
This choice is called allocation: deciding which requests get stock when there is not enough for all. Counting stock is a separate task. Shopify, for example, lists available stock apart from committed and unavailable stock. [S02] Those states help staff check the pool. They do not decide which customer should come first.
Define the decision before sorting the queue
Write down who sets the rule and who may approve a change to it. State which requests belong in this stock pool. Does the rule use earlier promises, due dates, or account terms? May staff send part of an order? Your business must choose those rules. This guide does not tell you to favor one type of customer.
Do not let sales value, account size, or a pushy message become a rule no one approved. If the business gives some accounts priority, write down who set that rule and when it applies. If no rule settles the conflict, ask the person in charge. Do not make up a score.
Use an allocation decision worksheet
| Field | Purpose |
|---|---|
| Item, location, and unit | Ensure all demands concern the same usable stock pool |
| Available pool and check time | Establish the quantity supported by current evidence |
| Existing reservations | Identify stock already committed and whether it is excluded |
| Demand reference and quantity | Link each request to its actual open requirement |
| Commitment evidence | Show the accepted promise or documented requirement |
| Partial-fill permission | Record whether a partial shipment is allowed and useful |
| Approved priority rule | Name the rule and its version, not just a ranking number |
| Proposed assignment | Show the quantity proposed for each request |
| Override | Record who changed the proposal, why, and which requests are affected |
| Release review | Confirm current stock and authorized release separately |
Keep requests that got no stock on the sheet. Show who is still waiting and what staff need to do next. Removing those rows makes the work look done. Sales would still have customers to answer, but no clear list to work from.
Hypothetical example: three demands for pump kits
A fictional distributor has 24 usable pump kits in the reviewed pool. One open commitment needs 10 kits, another needs eight, and a third needs 12. The last customer does not accept a partial shipment under the recorded terms.
For this exercise, the rule is to fill earlier agreed delivery promises first. The first two requests have those earlier dates. The sheet gives them 10 and eight kits. Six remain. But the third customer will not take part of an order. Keep those six unassigned while the account owner asks what to do. Do not treat the unused stock as an error.
A salesperson asks to give the newest request its full 12 kits first because the account is important. That would leave only 12 for the earlier requests, which need 18. Send the request to the person who can approve an exception. Show who would lose stock. Keep the first proposal beside any approved change so staff can trace the decision.
This example demonstrates a policy, not the correct policy for every distributor. It also does not authorize a shipment. Warehouse release still needs its own current checks.
Prevent two people from allocating the same stock
Save the stock count and time used for the proposal. Before release, check whether another team has used or reserved some of it. If so, the old proposal is stale. Review it again. Do not take units from a different customer's share just to keep the old total.
Keep a proposed share separate from stock actually held for an order. A draft sheet does not reserve goods. If staff use an approved process to hold stock, they must check the result in the warehouse system. This guide does not reserve stock or write to that system.
Review outcomes without inventing a success story
After a practice run, ask a second reviewer to explain who got what and why. Check the counts still waiting, the reasons for rule changes, and who will follow up. These questions test whether the record is clear. They do not prove better service or more sales.
Core Agentic can plan custom AI software to fit your order and warehouse tools. A proposed view could build this worksheet and flag conflicts. Your people still approve the rules, exceptions, and release. Test data access, stock update times, and who can take each action before use. This is a proposed design, not a connected stock service.
Bring a scarce-stock conflict to discuss a design that makes the decision visible. Book a Demo.
Sources
These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.