Storage & inventory
Available vs on-hand inventory: what the numbers mean
A piece can be on the shelf and still be spoken for. On-hand inventory records the stock you have. Available inventory accounts for commitments that prevent you from using or selling some of it.
01 · name each quantity
Keep physical stock and commitments separate.
These terms describe different questions. On hand asks what the physical record says is present. Available asks what remains after the commitments you have chosen to honor. Write down each subtraction so you do not hide a decision inside one total.
| Term | Question it answers | Example boundary |
|---|---|---|
| On hand | What stock is recorded at the location? | Physical count or lot quantity |
| Order reservation | What stock is committed to an accepted order? | Held for fulfillment |
| Build hold | What stock is set aside for a build? | Committed to a list or project |
| Safety reserve | What stock do you choose not to use? | Operational cushion |
02 · work through one bin
Use a non-overlapping example.
Here is a deliberately synthetic model for learning the arithmetic: 40 pieces on hand, 2 reserved for an order, 4 held for a build, and 2 in safety reserve. If those commitments are separate, the teaching calculation is 40 − 2 − 4 − 2 = 32 available.
This is an illustrative model, not a statement of Brick Pulse's released availability formula. Some systems include holds inside a broader commitment number. Check the application's exact semantics before labeling this arithmetic a Brick Pulse calculation.
03 · follow what changes next
Track the event, not just the new total.
A useful record explains why a number moved. The following transitions are a synthetic teaching sequence; actual controls and state names belong to the released product.
| Event | What changes | What to check |
|---|---|---|
| New order | Reservation increases | Confirm the committed quantity and source lot |
| Cancellation | Reservation can be released | Do not assume a physical restock occurred |
| Hold release | Build commitment decreases | Check whether the piece returned to the same location |
| Count discrepancy | Physical count and record differ | Review the cause before correcting the number |
04 · money is not a physical return
A refund does not tell you where the piece went.
A refund is a money event. A physical return is a separate event that needs receipt, inspection, and a decision about condition and location. Do not increase on-hand merely because money moved back; update stock after the physical pieces are actually checked.
05 · check before editing
Review differences in a fixed order.
- Confirm the location, part, color, and condition you counted.
- Compare the physical count with the lot record, not only an aggregate.
- Review active reservations, build holds, and safety reserve separately.
- Look for a move, receipt, build, pick, return, or previous correction.
- Write the cause, then correct the number and recheck the location.
06 · read the labels carefully
Similar words can hide different boundaries.
Software may use “committed,” “reserved,” “held,” or “available” differently. A label is not a universal accounting rule. Read the field description, inspect one concrete lot, and verify whether a hold is already included before comparing numbers across screens or systems.
07 · common questions
Use the smallest clear example.
- Is every on-hand piece available?
- No. Reservations, holds, or a safety reserve can make part of on-hand stock unavailable for the next use.
- Does a cancellation automatically restock a returned piece?
- Cancellation and physical return are different events. Inspect a returned piece before putting it back into a lot.
- Can I compare “available” across tools?
- Only after checking what each tool includes in its calculation. Similar labels can represent different commitments.
08 · next step
Make the number traceable to the shelf.
Brick Pulse's inventory feature covers physical lots, locations, and reviewable stock boundaries. Sellers can follow the broader seller workflow. This private preview does not promise overselling prevention, sync latency, marketplace writes, or public availability.