Lab Inventory Management Software

Laboratory inventory looks like ordinary stock control until you notice that almost nothing in a lab is fungible. Two bottles of the same reagent from different lots are not interchangeable if a result has to be defended, and the one at the back of the freezer expired in March.

We sell source code you clone and run yourself, so there is nothing hosted here. For most academic and small commercial labs, an existing product covers this well, and Quartzy is the one that appears most in this search for good reason: it is built for the ordering and stock side of lab life and has a free tier that fits a single group.

What a lab record has to carry

Ordering is usually the reason it gets adopted

The stock half of lab inventory is rarely what drives a purchase. The ordering half is: a researcher requests a reagent, somebody with budget authority approves it, a purchase order goes to a supplier, and the item arrives and needs receiving into stock.

That request-to-receipt loop is where labs lose time, and it is why the successful products in this space are as much procurement tools as inventory tools. When comparing options, follow one order end to end rather than evaluating the stock screens.

Where this sits relative to a LIMS

A laboratory information management system is a different and much larger purchase. A LIMS manages samples, tests, results, instruments, and often the regulatory workflow around them. Lab inventory manages the consumables the work consumes.

They overlap at one point: a result should be traceable to the materials that produced it. If that traceability is a regulatory requirement for you, check whether the inventory tool can be referenced from wherever results live, because a lot number recorded in a system nothing else can see does not provide traceability.

For most academic labs a LIMS is more than the work requires, and inventory plus a good notebook practice is enough.

When building happens

Individual labs should not build this. The case that recurs is an institution or a platform: a core facility charging other groups for materials and instrument time, a multi-site organisation that needs consolidated visibility with per-group isolation, or a supplier building a customer portal into their own catalogue.

All three are multi-tenant applications where the inventory is one component and the charging model is the part no off-the-shelf product handles.

What you would start from here

There is nothing lab-specific in this stack. No reagents, no lots, no freezer locations, no expiry tracking, no ordering workflow, and no grant coding.

What the Vault template gives the institutional case is the application around it: organizations as the boundary each group or facility lives in, roles and invitations so a principal investigator sees their own group's stock and budget, a Hono backend with Prisma and Kysely on Postgres, an admin app, and Stripe billing if you are charging groups or external users.

You would write the item, container, and lot models, the location hierarchy down to rack position, the expiry and open date logic, and the request and approval flow that turns a researcher's need into a purchase order. Model the container as the primary record rather than the product, because that decision is what makes lot traceability possible later and is painful to reverse.

If you run one lab group, look at the free tiers first. The packs below are for the facility or platform case.