Stock Outs Module
The Stock Outs module is the governed outbound workflow for Vendventory. It still handles manual sales, loss, damage, expiry, internal usage, sample issues, and other outbound events, but it now does so with stronger batch awareness and FEFO review for expiry-sensitive stock.
Current stock-out header fields
- Stock Out Date: shared datepicker field with quick shortcuts.
- Reference No: generated outbound document reference.
- Reason: shared custom select for manual sale, damaged, internal usage, lost, expired, sample, or other.
- Status: draft, completed, or cancelled through the shared segmented control.
- Notes: document-level explanation for the outbound event.
Batch-aware item lines
The most important modernization inside stock outs is at the item level. Outbound rows are no longer documented as only product and quantity. For governed items the operator can work against released batches and explain FEFO exceptions directly in the form.
- Product: selected inventory item for the outbound line.
- Released Batch: batch selector where released batches are available for that product.
- FEFO Override Reason: explanation field used when the operator does not follow the suggested earliest-expiry batch logic.
- Qty: outbound quantity.
- Unit Cost: cost basis for the line.
- Sale Unit Price: commercial value used when the reason is manual sale.
- Line Total: calculated outbound value.
- Notes: line-level notes for additional context.
Reason and commercial meaning
- Manual Sale: sale-oriented outbound event with commercial meaning.
- Damaged, Lost, Expired: loss-oriented outbound events.
- Internal Usage: internal consumption rather than customer-facing sale.
- Sample: controlled sample or promotional outflow.
- Other: outbound case that does not fit the standard list.
Status and inventory impact
- Draft: editable and safe for preparation.
- Completed: writes the outbound impact into inventory movements and affects reporting.
- Cancelled: preserved for audit visibility but no longer editable.
Dynamic form behavior in the live UI
- Product rows update available stock hints when selection changes.
- Batch-aware products can repeat across rows when they are issued from different released batches.
- FEFO guidance is presented through released-batch context and override fields.
- Line totals and summary values update live as quantities and pricing change.
- The form uses the same shared select, date, segmented-control, and feedback patterns as the other modernized transaction pages.
Why stock outs matter more in the governance build
Outbound stock is where many governance failures become visible. If the wrong batch is issued, expiry-sensitive logic is ignored, or manual loss is recorded unclearly, the reporting story becomes unreliable. That is why the stock-out form now documents batch choice and FEFO reasoning directly.
- Improves batch-level auditability of outbound movements.
- Supports FEFO review instead of leaving batch choice opaque.
- Feeds loss, movement, and rescue analytics with better outbound data.
- Strengthens the credibility of recall and batch-dossier review later.
What changed in the stock-out documentation
- The page now documents released-batch selection and FEFO override reasoning as part of the live form.
- The outbound workflow is now described as a governed issue workflow, not only a general stock reduction form.
- The relationship between outbound lines and downstream analytics is now explicit.
Screen-by-Screen Stock-Out Breakdown
- Stock-out index: browse outgoing documents by reason, destination, status, and movement context.
- Create stock out: define the outbound reason, destination type, dispatch reference, warehouse/bin context, and issue lines.
- Edit stock out: refine the document before it is finalized when the outbound decision is still in progress.
- Batch-aware line area: choose the correct released batch, review FEFO guidance, and explain overrides when the chosen lot is not the natural FEFO candidate.
- Why it matters: stock outs are where governed inventory leaves a location, so this page has direct impact on traceability, loss reporting, and recall credibility.