Troubleshoot insufficient stock
Follow this guide to review available quantity, backorder control, location and concurrent reservations. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goEnterprise POS → Inventory
What you’ll accomplish
Review available quantity, backorder control, location and concurrent reservations. This section covers the live stock list, availability calculation, manual adjustments and append-only movement evidence.
Follow these steps
- Go to Enterprise POS → Inventory and open the workflow that matches “Troubleshoot insufficient stock”. Confirm the page or record context before making a change.
- Select a location and optionally search inventory.
- Check on-hand, reserved and reorder indicators.
- Select a tracked product.
- Enter a non-zero delta, an approved reason code and a mandatory note.
- Post the adjustment.
- Check the balance and new immutable movement row.
Fields and options to review
- Guide focus: Review available quantity, backorder control, location and concurrent reservations.
- On hand
- Reserved
- In transit
- Quarantined
- Damaged
- Reorder level
- Available quantity
- Adjustment delta
- Reason code
- Mandatory note
- Source type and source identifier
Rules the system enforces
- Available equals on_hand minus reserved minus quarantined minus damaged.
- In_transit is stored but is not included in the available formula.
- Manual UI adjustments change on_hand only.
- Tracked active products and tenant locations are required.
- Negative stock is blocked unless the product allows backorder.
- Movements are appended rather than edited.
How to confirm it worked
- The specific outcome described by this guide is visible and remains tenant-scoped.
- Stock balance and movement agree after a committed transaction.
- Sales, returns, purchases and adjustments leave correlated evidence.
- Public availability uses the configured default location.
Safety checks and troubleshooting
- Use reason-specific, meaningful notes.
- Do not edit or delete movement history.
- Investigate reserved/quarantined/damaged values through supported workflows; the supplied inventory screen does not directly edit them.
Stay within the supported module flow
Use the supplied UI, host module lifecycle and documented endpoints. Do not bypass tenant filters, permissions, CSRF, idempotency, rate limits, audit evidence or transaction checks. A stored table or field does not imply that version 1.0.0 exposes a management screen for it.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.