Aliquora Team

Lab Reagent Tracking: Stop Treating It as an Afterthought

Poor lab inventory and reagent tracking silently corrupts your QC data. Here's how to build a system that prevents failures before they reach the COA.

Lab inventory and reagent tracking is one of the most under-engineered parts of a QC operation — and it's responsible for more OOS investigations and failed audits than most lab directors want to admit. This post argues that reagent management deserves the same rigor you give your analytical methods, and shows you what a defensible system actually looks like.

Reagent Tracking Is a Data Integrity Problem, Not a Logistics Problem

Most labs treat inventory as a purchasing problem. They count bottles, set reorder points, and call it done. That framing is wrong, and it costs labs credibility when things go sideways.

The real issue is traceability. When an OOS result surfaces, your first question shouldn't be "did we run the method correctly?" It should be "can we prove every input to this analysis was within specification at the time of testing?" If you can't link a result to a specific reagent lot, with a verified expiry and a documented receipt check, you don't have an investigation — you have a guess.

That distinction matters enormously under ISO 17025, FDA 21 CFR Part 211, and any cannabis or food safety regulatory scheme. Auditors don't want to see that you have reagents. They want to see that you know exactly which reagent lot touched which sample, when, and who authorized its use.

The Three Points Where Reagent Tracking Actually Fails

Labs don't usually collapse from one catastrophic failure. They erode through three recurring gaps:

1. Receipt without verification. A shipment arrives, someone signs for it, and the bottles go on the shelf. No one checks the Certificate of Analysis from the supplier. No one confirms the lot number matches the purchase order. Three months later, an analyst uses a reagent that was already outside its retest date when it arrived.

2. In-use tracking that stops at the label. Opening a reagent and writing a date on the label is not tracking. It tells you when that analyst opened that bottle, but it doesn't tell you which samples were prepared with it, whether the storage conditions were maintained, or when it should have been retired.

3. Expiry management by memory. Someone knows that the HPLC mobile phase modifier expires next Tuesday because they remember ordering it. When that person is out sick, no one else knows. The expired reagent gets used. The samples get reported. The audit finds it six months later.

Each of these failures is preventable. None of them require expensive instrumentation. They require a structured process and a place to record it.

What a Defensible Reagent Inventory System Actually Contains

Let's be specific. A QC-grade reagent tracking system needs to capture and link the following for every reagent in the lab:

  • Supplier, lot number, and CAS number logged at receipt
  • Supplier COA reviewed and filed — not assumed to be acceptable
  • In-house receipt inspection result (appearance, concentration check if applicable, acceptance or rejection)
  • Storage location (with temperature zone if relevant)
  • Date opened and prepared-by identity
  • Expiry date and in-use expiry (which is often shorter than the manufacturer's shelf life)
  • Linked sample batches that used the reagent during its active period

That last point is the one most labs skip. Without sample linkage, you can prove a reagent was good when you opened it, but you can't prove which results depend on it. That matters when you need to scope a recall, a re-test, or an investigation.

Consider a concrete example. Greenfield Analytical, a mid-size environmental testing lab running EPA Method 200.8 for metals, had an ICP-MS calibration standard go out of spec on a quarterly QC check. The standard had been in use for 11 weeks. Without lot-to-sample linkage, they faced the prospect of reviewing every metals result from the past quarter — roughly 2,300 samples. With a linked inventory log, they narrowed the affected window to 19 days and 340 samples. The difference between a manageable corrective action and a potential crisis came down to a field in their tracking system.

Why Spreadsheets Are a Liability, Not a Solution

The counterargument here is predictable: "We've been running on spreadsheets for years and we've never had a problem." That's worth taking seriously, because many labs do manage reasonable inventory control with well-designed spreadsheets.

But there are three structural weaknesses that spreadsheets can't solve:

Audit trail integrity. A spreadsheet can be edited without a trace. Date fields can be backdated. Lot numbers can be corrected after the fact. Whether or not anyone in your lab would ever do that intentionally, the system permits it — and auditors know it. The moment an inspector asks "how do I know this wasn't changed after the fact," you have no answer.

Real-time expiry alerts. A spreadsheet shows you expiry dates. It doesn't tell you that three reagents expire in the next 72 hours unless you're actively looking. In a busy lab, that's a significant assumption.

Cross-referencing under pressure. When an OOS result hits and you need to reconstruct the reagent chain for a batch within hours, manually cross-referencing a reagent log with a sample log with a batch record is slow and error-prone. Linked data returns the answer in seconds.

A LIMS with built-in reagent tracking — like Aliquora, which connects inventory directly to sample records and flags expiries automatically — solves all three without requiring analysts to learn a new workflow from scratch.

Building the Process Before You Build the System

Here's an opinion that might be unpopular: your tracking system will fail if the process isn't defined first. Software doesn't fix a lab where analysts aren't sure who is responsible for logging a new reagent or what counts as an acceptable receipt inspection.

Before you implement any tool, answer these questions in writing:

  1. Who is responsible for logging reagent receipt — the person who signs for the shipment, or the QA designee?
  2. What is your in-house retest interval for reagents where the manufacturer provides only a shelf life?
  3. What triggers a reagent to be quarantined versus immediately rejected?
  4. When a reagent expires mid-batch, what is the protocol — complete the batch, stop, or complete with documented deviation?
  5. Who has authority to approve the use of a reagent past its labeled expiry in an emergency?

If you don't have written answers to these, implement those answers first. Then build or configure the system around them. Technology applied to an undefined process just automates confusion.

Frequently Asked Questions

What information should be on a reagent label in a QC lab?

At minimum: reagent name, lot number, date received, date opened, expiry date (or in-use expiry if shorter), storage conditions, and the preparer's initials. Many labs also add a unique internal ID that links to the master inventory record for easy cross-referencing.

How long should reagent inventory records be retained?

This depends on your regulatory framework. ISO 17025 requires records to be retained for a minimum defined period that supports the validity of reported results — typically at least the life of the test report plus any applicable client or regulatory hold period. FDA-regulated labs often apply a two-year minimum for GMP-relevant records, but check your specific 21 CFR part.

What is an in-use expiry for a reagent, and how do I set one?

An in-use expiry is a lab-defined time limit that begins when a reagent is opened or prepared, separate from the manufacturer's shelf life. For example, a phosphate buffer might carry a 12-month shelf life unopened but a 30-day in-use limit once prepared. You set it based on stability data, historical performance, or published method requirements — and it should be documented in your reagent SOP.

Can expired reagents ever be used in a QC lab?

In rare, documented circumstances, yes — but only with written authorization, a retest demonstrating the reagent still meets specification, and a formal deviation record. The authorization should name who approved the exception and why. This should be the exception, not a workaround for poor inventory management.

How do I link reagent lots to specific sample results?

The most reliable method is to record the reagent lot number(s) used in the batch record or sample preparation log at the time of analysis — not retroactively. In a LIMS environment, this can be structured so the analyst selects the active reagent from a dropdown tied to the inventory record, creating an automatic link between the reagent lot and every sample in that run.