Inventory

The inventory view is the working stock enquiry: by product, location, pallet, batch or lottable value, for a storer or across storers. On-hand, allocated and available quantities are shown separately, so a line that looks present but is committed to an order reads as committed.

A bin transfer moves stock between locations as a documented movement with its own number and status — DRAFT, CONFIRMED or CANCELLED — rather than an untracked correction.

Transfers are searchable by transfer number, product, storer, status and by created or confirmed date range. Confirmation writes to the audit trail.

Adjustments are the controlled route for changing quantity or attributes outside normal movement. Each adjustment carries a number, a date, a storer and a status of DRAFT, CONFIRMED or CANCELLED, and stays searchable by number, product, status and date range.

Lottable attributes on existing stock are changed through the adjustment detail screen, so the change is attached to a numbered document and an audit row.

Counts are raised against locations or products, counted, and posted as variances. Counting work logs to the productivity record, and every posted variance writes an audit row of type STOCK_COUNT.

Counted variances do not post themselves. They queue for approval, and the approver sees the counted figure against the system figure before accepting. This is the control that separates the person counting from the person authorising the change.

Replenishment tasks move stock from bulk into pick faces. Tasks are generated on demand, then assigned to users individually or in bulk.

The picking rule for replenishment is set per warehouse and defaults to FEFO; FIFO is the alternative.

Writing stock off is a request, not an action. A scrap request selects the inventory lines, states a reason, names the scrap location the goods move to, and then passes through approval before anything leaves the books.

Reasons available: expired, QC rejected, recalled, damaged, other. Requests are numbered SCRAP-YYMM-NNNNN.