Inventory management · ERPNext · Warehouse operations
Stock Is Available—But Can We Actually Sell It?
Sales sees 200 units in stock and promises 100 for tomorrow. The warehouse checks the shelves: some units belong to another order, some are damaged, and another batch is waiting for inspection. The stock figure was correct. The delivery promise was not.
By Craft Interactive · Published 3 November 2026
What makes stock sellable?
Sellable stock is inventory that meets the conditions for the intended sale: it is in acceptable condition, released from any required hold, suitable for the customer and available for the promised delivery. When accepting a new order, we must also check whether that stock is already committed elsewhere.
These checks answer different questions. A reserved item may be perfectly suitable for its existing customer but unavailable to a new buyer. An unreserved item may still be damaged or expired. A batch that is usable today may not meet a customer’s remaining shelf-life requirement at delivery.
The useful question: How much eligible, uncommitted stock can we supply to this customer from the right location by the agreed date?
200 units on hand. Only 80 available for a new order.
Consider Harbour Industrial Supplies, a fictional UAE distributor selling batches of industrial sealant. Its physical stock and recorded on-hand balance both show 200 units.
Before confirming a new order, the team checks the condition, allocation and release status of those units.
| Stock group | Units | Available for this new order? |
|---|---|---|
| Released, suitable and uncommitted | 80 | Yes, subject to location and delivery checks. |
| Reserved for an existing customer | 60 | No, unless an authorised reallocation is agreed. |
| Damaged and isolated | 20 | No, pending an authorised disposition. |
| Expired batch | 15 | No, under this business’s sale policy. |
| Awaiting quality release | 25 | No, until the required checks and release are complete. |
| Total on hand | 200 | 80 units available for the new order. |
200 units
Physically present and recorded on hand.
120 units
Committed or currently ineligible for this new order.
80 units
Eligible and uncommitted before final delivery checks.
The new customer wants 100 units. The team can discuss supplying 80 now and sourcing the remaining 20, or agreeing a later delivery. It should not promise the full quantity based on the total alone.
This is an illustrative operating scenario, not a client case study. The five groups are mutually exclusive, and all quantities use the same stock unit. In a live system, restrictions can overlap; the same unit must not be deducted twice.
SCENARIO 01
The goods are here, but we have already promised them
A contractor has ordered 60 units for a scheduled site visit. The goods are still on the shelf when another customer calls with an urgent requirement.
If the second salesperson checks only physical stock, both customers may receive the same promise. The problem is allocation, not a missing item.
We need to know which order holds the reservation, the quantity, the warehouse and who may release it. If the original order is cancelled or changed, its reservation should be reviewed promptly. Otherwise, suitable stock can remain unnecessarily unavailable.
ERPNext supports stock reservation against Sales Orders and Pick Lists when the relevant feature is enabled. We confirm how that setup behaves in the deployed version and test competing orders, partial fulfilment and unreservation.
What we test: Reserve 60 units, create another order and check what sales and warehouse users can promise and pick. Then release part of the original reservation and verify the updated position.
SCENARIO 02
The delivery arrived, but part of it cannot be supplied
A supplier delivers cartons with crushed corners and leaking containers. The receiving team counts the full quantity but identifies 20 damaged units.
Those units still exist physically. Recording every unit as usable stock creates a misleading availability figure. Leaving them beside dispatch-ready cartons also creates a picking risk.
We separate the goods physically and record their location and condition. A named person then decides the next action: supplier return, inspection, approved rework or disposal. Any subsequent release must be supported by that decision.
ERPNext Purchase Receipts can record accepted and rejected quantities in their respective warehouses. Rejected goods remain traceable rather than disappearing from the stock record.
However, naming a warehouse “Damaged Stock” does not by itself prove that sales or dispatch from it is blocked. We test access, warehouse selection, picking and submission controls.
SCENARIO 03
The batch is present, but its usable life has run out
Fifteen units remain from an older sealant batch. They were counted correctly, but their expiry date has passed. In this business, they must be excluded from sale and reviewed for the appropriate disposition.
We keep the batch identity, expiry information and physical location connected. Moving the cartons or changing their shelf label must not erase the reason they were restricted.
ERPNext batch records can hold expiry dates. Its documented batch selection considers the item, warehouse, expiry relative to the transaction posting date and available quantity. We verify the actual transaction routes used by the team.
“Not expired” may still be unsuitable for the customer
A contractor requires at least 90 days of remaining shelf life on delivery. A batch with 30 days remaining may be unexpired today and still fail that requirement.
This needs an order-specific check against the expected delivery date. A basic expiry filter should not be assumed to enforce every customer’s shelf-life policy. The additional validation, warning or approval must be included in the implementation scope.
SCENARIO 04
The goods look fine, but nobody has released them
Another 25 units arrive with a certificate still to be checked. There is no visible damage, but the agreed receiving process requires inspection before release.
“Awaiting inspection” is different from “accepted”. The team needs a clear hold location or controlled status, an inspection owner and evidence of release. Sales should be able to see why the quantity is unavailable without treating a possible release date as a guaranteed promise.
ERPNext supports Quality Inspections for incoming and outgoing items, with inspection requirements configured on the item.
An inspection record alone should not be treated as a universal quarantine mechanism. We test the complete hold-and-release process, including whether users can select held stock through another warehouse, transfer or sales transaction.
What we test: Attempt to pick or dispatch the held quantity before release. Complete the authorised release process, then verify that only the approved quantity becomes eligible.
Why one subtraction formula is not enough
Our example divides stock into separate groups. Real inventory is less tidy. A reserved batch may also become damaged. A quality-held batch may expire while the team waits for a decision.
Subtracting every restriction independently can understate availability by counting the same units more than once. We assess eligibility at the relevant item, warehouse, batch or serial-number level, then apply allocation rules.
Incoming purchases need separate treatment too. A confirmed supplier order may support a future delivery plan, but it is not stock already received and released. We distinguish what can be supplied now from what depends on a future receipt, transfer or inspection.
How we design a useful availability view in ERPNext
When we discuss ERPNext inventory management for businesses in Dubai and across the UAE, we start by defining what “available” means for the people using the figure.
Sales needs a reliable promise. Warehouse staff need eligible stock to pick. Procurement needs the uncovered requirement. Finance needs accurate quantities, values and approved adjustments.
| Question | Information we need | Control to verify |
|---|---|---|
| Is it already committed? | Reservation quantity and source order. | Allocation, release and reallocation permissions. |
| Is it in acceptable condition? | Inspection evidence and stock location. | Isolation and authorised disposition. |
| Is the batch suitable? | Expiry and customer shelf-life requirements. | Selection and dispatch checks. |
| Has it been released? | Hold reason, owner and release evidence. | Restrictions before release and permitted release actions. |
| Can it reach the customer on time? | Warehouse, transfer needs and delivery date. | A delivery commitment based on the actual fulfilment route. |
Standard reservations, batches, receipts and inspection records provide useful building blocks. A combined sellable-stock view, customer-specific shelf-life rules or additional quarantine restrictions may require configuration or development. We identify those requirements before promising the finished result.
Keep the stock position useful after go-live
Even a well-designed system becomes unreliable when physical events are recorded late. Damage discovered during picking, expired reservations and inspection results need timely updates.
- Review old reservations: confirm that the customer order still needs the quantity.
- Review ageing holds: give each unresolved inspection or damage case an owner and next action.
- Check approaching expiry: consider delivery dates and customer requirements before allocating batches.
- Count restricted stock as well: damaged and held goods still need physical traceability.
- Review availability failures: investigate orders promised from stock that could not actually be dispatched.
These reviews help us find the underlying issue: an outdated reservation, a missing movement, an unclear release decision or a report that combines quantities with different meanings.
Frequently asked questions
Is stock on hand the same as sellable stock?
No. Stock on hand can include quantities that are reserved, damaged, expired or awaiting release. Suitability also depends on the customer, warehouse and promised delivery date.
Can reserved stock still be sold?
Reserved stock is normally intended for an existing commitment. Supplying it to another order requires an authorised reallocation and a review of the original customer promise.
Does a rejected warehouse automatically prevent dispatch?
Do not assume so. A separate warehouse helps identify and isolate stock, but permissions, document selection and dispatch controls must be configured and tested.
Can ERPNext track batch expiry?
Yes. Batch records can include expiry dates, and documented batch selection considers expiry against the transaction posting date. Additional customer shelf-life rules need their own implementation review.
How do we avoid counting a restriction twice?
Evaluate the affected units at the appropriate warehouse, batch or serial-number level. If the same quantity is both reserved and held, do not deduct it twice from the same on-hand balance.
Let’s check what your stock figure really means
Bring us an item that appears available but regularly creates problems at dispatch. We can review the reservations, warehouse movements and release rules, then discuss how ERPNext can give your teams a clearer answer.
Discuss your inventory workflow
Product references
The operating scenarios are illustrative. Product capabilities are referenced from the official ERPNext documentation: Stock Reservation, Batch, Purchase Receipt and Quality Inspection.
