Know what’s available. Trace what was used.

1Plan from the containers, not just the total.

The fictional RM-062 example has 28 L of buffer concentrate on hand. A new job needs 9 L. But C02 is reserved for B-042 and C03 is held for a storage assessment. Only C01's 8 L remain unreserved and not held, and its point-of-use checks still need to be satisfied.

The records in Figure 1 connect those commitments to the physical containers. They also retain the three original receipts and the 2 L already consumed by B-041. Planning, warehouse, laboratory and production work can use the same evidence without maintaining separate versions of the balance.

1.1Keep the different quantities explicit.

Purchasing knows what was ordered, the warehouse what was received and moved, quality what was released or held, and the laboratory and production what was sampled, dispensed or consumed. Each source can be accurate for its own job while the combined picture is already stale. Seal keeps the distinctions explicit:

• On hand means the material is physically recorded at a location.
• Released means an authorised quality decision permits a defined scope of use.
• Available-to-plan accounts for reservations, holds and other configured restrictions without double-counting overlapping populations.
• Eligible means a specific container satisfies the rules for a specific use at a specific time.

Production planning, laboratory scheduling and point-of-use selection consume different views of the same controlled population, not separately maintained totals.

1.2Why teams choose Seal for inventory

A supplier notice asks where every container of a lot went. When an ERP or warehouse system knows totals while the laboratory and production keep their own trackers for what was actually used, the answer is a hand reconciliation. Seal keeps the container as a record on the same platform as the batch record and the test, so eligibility is checked at the step and consumption is written into the genealogy as the work runs. Revised storage rules or status logic apply to transactions from their approval onwards; earlier transactions keep the rules under which they were made.

2The container is the unit of control.

A material definition says what an item is. A lot preserves its manufacturing and supply identity. A container is the physical object that can be received, labelled, moved, opened, sampled, partially consumed, damaged, quarantined or destroyed.

In this example, C01 is a 10 L container from supplier lot SUP-884, with 8 L remaining after a 2 L use. Its current location is the preparation room. C02 and C03 share the material identity but have different commitments, locations and restrictions.

Pallets, drums, bottles, vials, kits and aliquots can form parent-child handling units. A split creates new physical identities without losing source genealogy. A relabel changes the label, not the history. Current quantity and state are derived from what actually happened to each object.

2.1Receipt creates governed inventory, not just stock.

The effective material definition controls approved manufacturers and sites, grade, specification, storage, shelf life or retest, sampling, release and use restrictions, and its version changes apply from a defined date without rewriting historical receipts. Receiving preserves shipment references, manufacturer and supplier lots, quantities, condition, certificates and initial location. Labels are generated from the governed record. The incoming population normally begins in a state that prevents unapproved use while sampling, testing, document review and disposition remain open.¹

Supplier datasheets, specifications and certificates can be extracted into a source-linked change set. neil proposes values; a qualified person reviews, corrects and approves them, and the source stays attached.

2.2Status changes what the system allows.

Quarantine, under test, released, restricted, held, rejected, expired and consumed are operating states that change what users can select and what workflows can execute. Every state change retains its scope, reason, effective time, evidence and approver. A lot-level hold can propagate to every child container. A damaged-container restriction can remain limited to one physical item. Release can permit R&D use while still blocking GMP manufacturing.

Expiry, retest, open life, preparation life and use-by rules can update eligibility automatically. If governance permits an exception, it follows a separate authorised path with defined scope, rationale, controls, duration and approval. There is no generic “continue anyway” action that silently turns a failed check into an accepted use.

3Eligibility is evaluated at the moment of use.

A planning balance does not stand in for point-of-use controls. Configure the batch step, laboratory method or preparation to evaluate the material and grade, supplier, quality status, dates, storage and excursion state, reservation, available quantity, restrictions and user authorisation for that use.

The decision returns eligible, conditional or blocked with the rule and evidence that produced the result. Selection lists can exclude ineligible stock; a barcode scan confirms the physical container at the point of use. An accepted dispense records the exact lot, container, quantity, operator, time and execution context while updating the remaining balance.

The execution record therefore preserves both what was used and why it was considered suitable at that moment.

3.1Every movement and quantity change leaves a balanced transaction.

Receipt, transfer, split, sampling, dispense, consumption, return, spill, adjustment, destruction and shipment each debit and credit identified stock, so the current balance is the sum of transactions rather than an overwritten cell. Quantities, units, measurement basis, discrepancies and approvals stay with the event, and container history shows who moved or changed it, when, from where to where and for which activity. Location can resolve down to shelf, rack, box and position, and the movement history supplies the evidence for custody, counting and environmental impact.

Fictional transaction in the actual Seal interface. The consumed quantity, physical container and preparation stay linked. View full size

4Storage events resolve the actual exposed population.

A freezer alarm should not create a guess based on where inventory sits now. Seal combines the location hierarchy, container movement intervals, sensor coverage, event start and end, mapping, conditions and alarm evidence to determine which containers were present during the affected period.

A container moved into the unit halfway through the excursion has a different exposure from one stored there throughout. Assessment, supporting stability or shipping evidence, status actions and final disposition remain connected to the exact population. The same trace can identify work that already consumed an affected container.

4.1Reservations make future availability visible.

On-hand inventory does not show what tomorrow’s work has already claimed. Reservations connect production orders, laboratory plans, campaigns, kits and shipments, with their priority, quantity and due time, to eligible stock.

Planners can distinguish released inventory from available-to-promise inventory and see shortages before execution begins. FEFO rules can propose the appropriate containers without taking material reserved for higher-priority or earlier work. Substitution and reallocation remain explicit decisions with impact and approval.

5Actual use establishes the genealogy.

Laboratory and manufacturing workflows record material at the point of sampling, preparation, dispensing or consumption. The inventory transaction and the execution record refer to the same physical container and quantity, so reconciliation does not depend on someone posting a second summary later.

From a supplier lot or container, Seal can traverse samples, tests, preparations, experiments, batches, intermediates, finished products, shipments, retained samples, remaining stock, returns and destruction.² From a batch or result, it can trace backward to the exact containers, approvals, locations, excursions and movements that supported the work.

When a supplier notification arrives, the trace separates stock still on hand, material already consumed, affected work in progress, released outputs and ruled-out populations, with the evidence for each conclusion.

5.1Reconciliation tests the record against reality.

Cycle counts and full inventories freeze a defined population while accounting for transactions in progress, and the system routes recounts, discrepancies, adjustments and approvals. An adjustment does not erase the difference: expected quantity, observed quantity, cause, decision and resulting transaction remain visible, and repeated variance by location, material or transaction type becomes an investigation signal.

6Ask neil to investigate, plan and configure.

Start from a supplier notice, a shortage or a material procedure. neil can read the supplied sources and the records the requester is permitted to see, follow their relationships and create the linked work needed to act on the findings.

For a supplier notice, neil can assemble the lot population, separate stock on hand from actual consumption and follow consumption into the recorded batches, drafting an assessment with source links, missing evidence and candidate follow-up tasks. Missing transactions remain a completeness issue rather than proof that no further material was used.

For the 9 L shortage in the example, it can compare competing demand, replenishment and alternatives, and explain what another lot, a replenishment or a reviewed reallocation would each need. Staged reservations are not confirmed stock or permission to use held material.

For a new workflow, give neil the procedure and supplier documentation. It can author linked templates, capture fields, reference relationships, review states and configured checks. Ask for verification cases covering expired and held stock, insufficient quantity, duplicate posting and an unauthorised state change. Your team inspects and tests the configuration before approving and publishing it.

neil works within the operator’s permissions. Required technical review, material disposition, verification and approval remain with authorised people.

6.1Keep each system’s job clear.

Seal does not need to replace the ERP that buys the material or the WMS that moves it through a warehouse. It supplies the operational answer they usually cannot provide alone: whether this particular container is suitable for this particular use right now.

When a laboratory or manufacturing step requests material, Seal evaluates the live inventory state and records the actual consumption. When a storage monitor reports an excursion, Seal resolves the affected containers and downstream uses. Each system remains authoritative for its own record; the handoffs no longer leave eligibility or genealogy to inference.

7Start with the material that causes the most difficulty.

Choose one material class with costly shortages, frequent expiry, difficult storage or weak traceability. Govern its suppliers and storage rules, label new receipts at container level and connect one real laboratory or manufacturing use. That is enough to test whether the digital record matches physical practice.

Before expanding, put the flow under pressure. Hold a supplier lot. Trigger a storage excursion. Create a count discrepancy. Trace one source lot forward and one batch backward. If the system can explain what exists, where it is, whether it may be used, what consumed it and why the balance changed, the pattern is ready to scale.