Lot & status control · FEFO · Genealogy
Inventory where every lot carries its quality status.
See each lot's status and location, pick by expiry and count stock.
Status-Aware Stock, Enforced at the Pick
Every lot carries quarantine, released, rejected or on-hold status.
FEFO with Expiry and Retest Control
Picking defaults to first-expiry-first-out.
Full Forward and Backward Genealogy
From supplier lot to weighed dispense to batch to pallet to customer — traceable in both directions on demand, with mass balance.
What goes wrong today3 common problems
Quarantined material gets used
If status lives in a separate QA spreadsheet, nothing stops an operator picking a lot that was never released.
Expiry and retest dates are managed manually
Retest-due material sits available in the system, and expiry write-offs are discovered at the count rather than prevented.
Genealogy is reconstructed after the fact
When a recall question lands, tracing which finished lots contain a suspect raw lot means digging through records instead of running a query.
Everything V5 does here5 capabilities
Status-Aware Stock, Enforced at the Pick
Every lot carries quarantine, released, rejected or on-hold status. Scanning a non-released lot at the weigh station stops the transaction with the reason shown.
FEFO with Expiry and Retest Control
Picking defaults to first-expiry-first-out. Retest-due lots drop out of available stock automatically and reappear only after a passing result.
Full Forward and Backward Genealogy
From supplier lot to weighed dispense to batch to pallet to customer — traceable in both directions on demand, with mass balance.
Cycle Counting and Reconciliation
Scheduled cycle counts by ABC class with variance investigation, so the count is a control rather than an annual event.
Storage Conditions on the Record
Cold-chain and controlled-storage excursions attach to the affected lots and trigger the impact assessment before the material moves.
Standards Referenced
- 21 CFR 211.80–211.94 — control of components and containers
- 21 CFR 211.137 — expiration dating
- 21 CFR 117.130 — preventive controls, supply-chain program
- FSMA 204 — traceability lot codes and KDEs
- ISO 13485 §7.5.8 — identification and traceability
Common questions5 answers
- Does this replace our ERP inventory?
- It can, or it can sit alongside it. Many customers keep ERP for purchasing and finance and let V5 own lot-level status, genealogy and shop-floor transactions, syncing balances back.
- How does it stop unreleased material being used?
- Status is enforced at the transaction, not on a report. Scanning a quarantined or expired lot at dispense blocks the step and records the attempt.
- Can it handle FSMA 204 traceability lot codes?
- Yes. Traceability lot codes and the critical tracking events with their key data elements are captured as part of normal receiving, transformation and shipping transactions.
- What about serialized or unique-device items?
- Serial, lot and pallet levels are all supported, so a device UDI or a pharma SGTIN carries alongside the lot record through to dispatch.
- How fast is a recall trace?
- Both directions run as a query against one genealogy, so a full trace with mass balance is produced and exported as an evidence pack.