Peptide Inventory Management: Lot Traceability, FEFO, Holds, and Recall Readiness
# Peptide Inventory Management: Lot Traceability, FEFO, Holds, and Recall Readiness
Peptide inventory management should answer two questions without guesswork: Where is every controlled unit now, and which events put it there? The minimum design is a lot-level data model with explicit states, guarded transitions, immutable event history, exception containment, and a bidirectional trace between each lot and every affected order.
FEFO can be one allocation rule inside that system. It is not a universal product requirement, a quality decision, or a substitute for release authority. Never set storage, expiry, retest, release, or disposition rules from a generic article or software default. Use exact item evidence and accountable qualified owners.
This page owns inventory state and traceability. The cold-chain fulfillment checklist covers pick-to-return execution, while the 3PL selection guide covers provider evaluation.
Define the controlled entities
Use one canonical meaning for each term across the storefront, inventory system, 3PL, support, finance, and evidence files.
| Entity | Canonical definition | Identity rule |
|---|---|---|
| SKU | The sellable catalog configuration | Stable SKU; a material product or package change creates a reviewed version or new SKU |
| Lot or batch | The supplier- or process-defined group tied to shared source records | Immutable lot ID; aliases are mapped, never substituted silently |
| Container or unit | The physical handling unit where unit-level control is required | Unique ID linked to SKU and lot |
| Report or COA | A scoped document with methods, results, sample identity, issuer and version | Stable record ID plus content version; link to exact lot only when supported |
| Location | A controlled physical or logical place | Stable location ID with type and access owner |
| Status | The inventory’s current eligibility state | One state at a time under an approved state model |
| Event | A timestamped change or observation affecting inventory | Append-only event ID with actor, reason, source, before-state and after-state |
| Order | The customer or transfer request that consumes inventory | Stable order ID linked to allocation, pick, shipment and lot |
| Exception | A deviation requiring containment, investigation or repair | Stable exception ID linked to all affected objects and evidence |
A lot number typed differently in the warehouse and storefront is not a formatting problem. It is a broken join between evidence and shipment.
Define the inventory states
Keep states mutually understandable. A workable base model is:
- EXPECTED: purchase or transfer record exists; stock has not been received.
- RECEIVED: physical receipt is recorded; eligibility is not yet established.
- QUARANTINED: stock is segregated pending required evidence and decision.
- RELEASED: named authority approved the lot for the defined scope.
- ALLOCATED: eligible quantity is reserved to a specific order or transfer.
- PICKED: identified quantity has been physically selected and reconciled.
- SHIPPED: custody transferred under a recorded shipment event.
- RETURNED: material came back and awaits controlled assessment.
- HOLD: use or movement is blocked for a stated reason.
- REJECTED: named authority determined the material is not eligible for release.
- DISPOSED: final authorized disposition is complete and evidenced.
- CLOSED: the controlled quantity is fully reconciled with no remaining stock.
HOLD should be reachable from every active state. Release from HOLD requires an explicit guard and a new event; it should never happen because a user edited the status field.
Minimum lot and event schema
For each lot, preserve:
- SKU, lot or batch ID, container IDs where required, supplier and source reference;
- quantity received, unit, location, status, and available/allocated/held quantities;
- report or COA references, sample identity, version, observation date, and scope;
- item-specific dates or conditions only when a qualified source and owner authorize them;
- receipt, discrepancy, quarantine, review, release, hold, rejection, allocation, pick, shipment, return, adjustment, and disposition events;
- actor, timestamp, source system, reason code, evidence pointer, approval, before-state and after-state;
- order, fulfillment, shipment, tracking, return, complaint, and exception IDs;
- every alias or cross-system mapping used by a supplier, 3PL, marketplace, or carrier.
Read the COA interpretation guide and batch-specific versus generic lot report guide before designing the report link. A document should not be presented as lot-specific unless the evidence actually connects the tested sample, reported lot, and controlled inventory.
State transitions, guards, and evidence
Every transition needs a before-state, after-state, guard, evidence, and authorized owner.
| # | Transition | Guard | Evidence | Owner | Failure state |
|---|---|---|---|---|---|
| 1 | EXPECTED → RECEIVED | Physical receipt matches a purchase or transfer reference | Receipt timestamp, quantity, condition and discrepancy record | Warehouse owner | QUARANTINED if identity or quantity is unresolved |
| 2 | RECEIVED → QUARANTINED | Receipt completed; eligibility review still pending | Location move and quarantine event | Warehouse owner | HOLD if segregation cannot be proven |
| 3 | QUARANTINED → RELEASED | Required evidence is present, scoped and approved | Release decision tied to exact lot and evidence versions | Quality owner | HOLD or REJECTED if evidence is missing, conflicting or unacceptable |
| 4 | Any active state → HOLD | Approved trigger, exception or precaution exists | Hold reason, affected scope, timestamp and authority | Quality or designated incident owner | Escalate if system cannot block movement |
| 5 | HOLD → prior eligible state | Root cause resolved and named authority approves | Investigation, repair, review and release-from-hold event | Quality owner | Remain HOLD if any criterion is unresolved |
| 6 | RELEASED → ALLOCATED | Quantity is available and lot is eligible for the exact order | Allocation record and rule result | Inventory system owner | HOLD if rule or lot identity is ambiguous |
| 7 | ALLOCATED → PICKED | Picker confirms exact SKU, lot, quantity and location | Pick event and reconciliation | Warehouse owner | Exception; do not silently substitute |
| 8 | PICKED → SHIPPED | Package, order, lot, address and service reconcile | Pack, label, carrier-handoff and shipment events | Fulfillment owner | HOLD shipment and correct discrepancy |
| 9 | SHIPPED → RETURNED | Authorized return is received and identified | Return authorization, receipt, condition and custody evidence | Returns owner | QUARANTINED if identity or condition is uncertain |
| 10 | RETURNED → RELEASED | Item-specific procedure and named authority allow re-release | Assessment, evidence and approval | Quality owner | HOLD, REJECTED or DISPOSED |
| 11 | Any physical state → REJECTED | Named authority rejects within the defined scope | Decision, reason, scope and affected quantity | Quality owner | HOLD until disposition is authorized |
| 12 | REJECTED → DISPOSED | Approved disposition is completed | Quantity reconciliation, method, provider and witness evidence as applicable | Quality plus operations owners | Remain REJECTED/HOLD until complete |
| 13 | RELEASED → CLOSED | All original quantity is shipped, transferred, adjusted or disposed with reconciliation | Lot balance equation and closure review | Inventory plus quality owners | Exception if balance is nonzero or unexplained |
Do not let a system administrator become the quality authority just because they can edit the field. Permission to operate software is not permission to make the underlying decision.
FEFO is a guarded allocation rule
First-expired, first-out selects eligible inventory with the earliest qualified expiration date. A valid FEFO candidate therefore needs:
1. an approved item or process rule that makes expiration-based selection applicable;
2. a qualified date tied to the exact lot;
3. RELEASED status for the order’s scope;
4. available quantity in an eligible location;
5. no customer, study, contract, or order-specific lot requirement that overrides the sort;
6. a deterministic tie rule and a logged override process.
If any input is missing or conflicting, the lot should not win merely because its date field sorts first. The result is HOLD or manual review under named authority.
Official software documentation illustrates the difference between the feature and its prerequisites. Microsoft Business Central defines FEFO as selecting the items with the earliest expiration dates first, but its behavior depends on item tracking, expiration data, and location settings. See Microsoft’s FEFO configuration documentation. That source does not establish your item’s expiry or authorize the rule.
Allocation and pick reconciliation
At allocation, record the rule, eligible candidate set, selected lot, quantity, timestamp, and any override. At pick, verify the physical SKU, lot, quantity, and location against the allocation.
Never silently substitute:
- a different SKU or strength;
- a different lot when a specific lot was required;
- a lot with missing or different evidence;
- a different package or route condition;
- held, quarantined, rejected, returned, or disposed stock.
If the selected stock is unavailable, open an exception and return the order to an approved decision point.
Returns, damage, and adjustments
Every returned or damaged unit should enter a controlled state before any disposition decision. Preserve identity, source order, lot, quantity, custody, condition, reason, images where authorized, and communication history.
An inventory adjustment is not a cleanup tool. Require:
- before quantity, adjustment quantity and after quantity;
- unit of measure and sign;
- reason and affected status/location;
- physical count or source evidence;
- actor, reviewer and timestamp;
- linked exception and corrective action where applicable.
Repeated “found” or “missing” adjustments are signals that receipt, movement, pick, return, or integration events are failing. Repair the missing event path instead of normalizing the variance.
Bidirectional trace test
Run both directions against a frozen export.
Lot to orders
Select a lot without warning the person running the trace. Return every on-hand location, status, container, allocation, order, shipment, return, adjustment, complaint, and disposition tied to it. Reconcile the original quantity:
`received = on hand + allocated + shipped + transferred + disposed + documented adjustments`
Use the units and event definitions approved for the system. A balanced equation does not prove each event was authorized; review both quantity and state.
Order to lot
Select an order. Return the product and content version, allocated and shipped lot, source and report references, fulfillment and shipment events, return or complaint history, and current disposition.
The two results must join. If the order points to a lot that does not include the order in its forward trace, the model has a broken mapping.
Exception and recovery cases
Test at least these flows:
- receipt has no usable lot identifier;
- supplier lot and warehouse lot use different values;
- report is missing, stale, generic, conflicting, or tied to another lot;
- held stock appears in an allocation candidate set;
- picker scans a different lot;
- partial shipment and split lot occur;
- a return has unknown identity or condition;
- stock exists physically but not in the system, or vice versa;
- the 3PL portal is unavailable;
- a data export omits status history or event actors.
Contain first, preserve evidence, name the owner, repair the root cause, reconcile affected history, and rerun the case plus shared-path regressions.
Metrics without invented universal limits
Track observations that reveal control health, but set action thresholds from your approved operating context:
- quantity and age of inventory by state;
- lots with missing or conflicting required fields;
- held inventory and unresolved exception age;
- attempted held-stock allocation or unauthorized override events;
- pick, ship, return and adjustment discrepancies;
- trace completeness and reconciliation result;
- export and restore success;
- time from event detection to containment, review and closure.
Do not publish a universal “good” percentage or duration without evidence for the item, system, risk, and owner decision.
Change control
Reopen the design when the SKU, supplier, lot schema, report format, item evidence, inventory platform, 3PL, facility, route, carrier, location, status, allocation rule, return process, integration, export, retention, or qualified owner changes.
The peptide business compliance operating system explains how to keep those reviews connected to governance. After the inventory model passes, a separately approved mock-recall drill can test the response workflow.
Frequently asked questions
What is the minimum lot-tracking record?
At minimum: SKU, lot ID, quantity, unit, location, status, source and report references, item-specific qualified fields, complete event history, order and shipment links, actors, timestamps, reasons and evidence.
Is FEFO always required for peptide inventory?
No universal rule is established here. FEFO is an allocation method that may be appropriate when a qualified item or process rule, reliable expiration data, release state, and system configuration support it.
Can returned inventory go back to available stock?
Only under an item-specific approved procedure and named authority. The default state on receipt should be controlled, not automatically available.
How do I know traceability works?
Run a blind lot-to-order trace and a separate order-to-lot trace against frozen exports. Reconcile quantities, states, locations, events and joins, not just search results on screen.
Does lot traceability prove product quality?
No. It proves the recorded identity and movement path to the extent the data is accurate. Quality, test scope, release and suitability are separate evidence and decisions.
Sources and scope
Sources were checked on August 8, 2026. Software behavior is version- and configuration-specific; item rules require qualified evidence and ownership.