Choosing site inventory software: IP accountability, storage links, and whether your team will actually use it daily

In short: Choose site inventory software the way an inspector will judge it, not the way a price sheet presents it. The right system records every unit of investigational product (IP), links it to the storage conditions it experienced, keeps studies and sponsors cleanly separated, and is fast enough that coordinators use it for every transaction — because software the team avoids does not eliminate the spreadsheet, it just drives it underground.

Price is the easiest criterion, and the least useful one

Two products can look similar in a demonstration and behave very differently on a busy clinic day. The real cost is not the subscription. It is the hour spent reconciling a count that does not match, the monitor query that takes three days to answer, and the inspection finding that starts with a question nobody could answer from the records: where is this unit, who received it, where was it stored, and what happened to it next?

I lead Amavita Research Services, a Miami cardiovascular trial site with more than 18,000 active cardiology patients and zero Food and Drug Administration (FDA) Form 483 findings, and bioaccess, a first-in-human contract research organization (CRO). Accountability systems earn their keep on the worst day, not the average day. Evaluate for the worst day.

First criterion: accountability that survives an inspection

Investigational product accountability is the chain of evidence for a physical object. For each unit, the record should show receipt, storage, dispensing, return, and destruction or return to the sponsor — with dates, quantities, lot numbers, expiration dates, and who performed and verified each step.

Ask whether that chain survives when something goes wrong, because something always goes wrong: a damaged carton, a dose prepared and then not administered, a recalled lot. If correcting an entry erases the original, you no longer have accountability. You have a current opinion about accountability.

A sound system needs three properties. An audit trail that cannot be quietly edited: corrections add a new, dated entry with a reason, rather than overwriting history. Controlled permissions, limited by role and ending when a staff member leaves. And reconciliation visible at any moment — received minus dispensed, returned, and destroyed should equal what is on the shelf, for each lot, without a hand-built report.

Test this before you buy: ask the vendor to show, live, one unit's complete history from receipt to final disposition, including a corrected entry. If that takes more than a minute, imagine fifty units under inspection pressure.

Second criterion: inventory events must link to storage

A temperature excursion is where inventory software stops being a stock list and becomes a safety and compliance record. When a refrigerator or freezer drifts outside its permitted range, the question is never only how far or how long. It is: exactly which product, from which lots, for which studies, sat in that unit during that window?

If inventory and storage records live in separate places, answering becomes reconstruction, and the answer arrives late and with doubt attached. Exposed product may need to be quarantined, assessed by the sponsor, and in some cases replaced or destroyed. Product never in the unit should not be pulled from service because nobody could prove where it was.

Look for a direct link between each unit and a specific storage location over time, not just a current location field. Product moves: receiving, quarantine, active storage, dispensing, sometimes a backup unit during maintenance. Each location and interval should be recorded, so an excursion report lists the affected lots precisely.

Your standard operating procedure (SOP) should define what happens next, and the software should support it: a quarantine status that blocks dispensing, a documented assessment, and release only after sponsor or principal investigator (PI) authorization is recorded. Staff quietly moving product out of quarantine is not a convenience. It is a gap.

Third criterion: many studies, many sponsors, no cross-contamination

Most sites run several studies at once, for different sponsors, sometimes with similar-looking product, blinded supplies, and different rules for return and destruction. Software built for a single study fails quietly here: searches surface the wrong study, reports mix sponsors, and a busy coordinator posts against the wrong protocol.

Separation should be structural, not cosmetic. Each study needs its own ledger, permissions, and reporting, so a sponsor or monitor sees only their study. For blinded product, the system must also protect the blind, limiting who sees identifying details while tracking every unit.

Ask how it handles ordinary collisions: two shipments the same morning for two studies, one coordinator receiving for both, a shared refrigerator holding product for three protocols, a sponsor asking for a report on their study alone. If any of those requires a workaround, the workaround becomes your process — and workarounds are where cross-contamination begins.

Fourth criterion: your team has to use it daily

This criterion decides whether the other three exist in practice. A system can be capable in every respect and still fail, because receiving takes eleven screens, the scanner does not read the labels your shipments carry, or dispensing requires the coordinator to leave the participant and find a desktop computer.

When the official system is slower than memory, staff build a shadow system: a notebook at the refrigerator, a spreadsheet on a shared drive, entries posted at week's end from both. Now you have two sources of truth, and neither is complete. The problem is not discipline. It is design.

Judge usability by timing real tasks, not by watching a demonstration. Receiving one shipment — barcode scanning, lot and expiration capture, quantity verification, storage assignment — should take about two minutes once the shipment is open and checked. Dispensing should be scannable at the point of work. If a task cannot be done where the product is, coordinators will batch it, and batching is where errors enter.

Involve the coordinators who will use it daily, and weight their judgment heavily. Rejecting a clumsy workflow is not resistance to change. It is an accurate forecast of a late afternoon with participants waiting.

Questions to ask every vendor

Put these in writing, and require answers in the system, not in a slide deck:

• Can you show one unit's complete, unedited history — receipt to final disposition — in under a minute?
• How are corrections made, and is the original entry always preserved, with a reason?
• Which lots were in a specific refrigerator during a specific date and time range — can the system list them?
• When product is quarantined, can it be dispensed by mistake? Who can release it?
• Are studies and sponsors fully separated in permissions, searches, and exports? How is the blind protected?
• How long does receiving take, timed, with our labels and scanner?
• How are expiring lots flagged, and how far in advance?
• Which reports can we produce ourselves, without vendor help?
• If we leave, how do we export our complete records, including audit trails?

That last question matters. Your records must outlive any vendor relationship.

The trial-period test: run one real shipment through it

Do not evaluate on sample data. During the trial period, run one real shipment end to end, alongside your existing records. Receive it and time the workflow. Assign it to storage. Simulate an excursion on that unit and produce the affected-lot list. Dispense a unit to a test participant record, then return it unused. Correct one deliberate error and confirm the audit trail shows both. Produce the report for that study alone. Finally, ask a coordinator who skipped the training to count using only the system and the shelf.

If the team finishes asking to keep using it, you have a candidate. If they ask for their spreadsheet back, believe them — whatever the price was.

What good looks like

Good inventory software is unglamorous. It makes the correct action the fast action, keeps each study in its own clean ledger, ties every unit to the conditions it experienced, and answers an inspector's simplest questions immediately.

Buy for that standard. A cheap system your team avoids is the most expensive one you will ever own: you pay twice — once for the software, and again for the records it never created.