University research labs run on purchasing. Every reagent, every consumable, every piece of equipment starts as a request that has to move through approval, procurement, and eventually lands in someone's hands. When that process is smooth, researchers barely notice it. When it's broken, it consumes time that should go toward science.
This guide covers the practical mechanics of setting up a purchasing workflow that actually works — one that satisfies institutional compliance requirements without turning every supply order into a project.
Why Lab Purchasing Breaks Down
The most common failure mode isn't complexity — it's inconsistency. Labs accumulate purchasing habits over time: some PIs approve via email, others use a shared spreadsheet, some labs have a designated buyer, others let everyone order independently. When those habits collide with grant reporting season or an audit, the gaps become expensive.
The second failure mode is context loss. When a purchase is made in January and reconciled in October, the person doing reconciliation often has no idea why that item was ordered, which project it was for, or whether it was ever received. Without that context, every line item becomes a small investigation.
The Basics: What Your System Needs to Track
For each purchase, you need to capture:
What was ordered — specific item, quantity, unit, and vendor. "Lab supplies from Fisher" is not useful. "500mL HPLC-grade methanol, 4 units, Fisher Scientific" is.
Who ordered it — not just for accountability, but for follow-up. If something arrives damaged or doesn't arrive at all, you need to know who to contact.
Why it was ordered — which project, grant, or budget line covers this purchase. This is the field most labs skip and most labs regret skipping.
When it was ordered and when it arrived — these two dates matter for reconciliation. Ordered-in-December, arrived-in-January affects which fiscal year the charge hits.
How much it cost — the estimated price at order time and the actual price on the invoice. They're often different.
Setting Up Approval Workflows
The right approval structure depends on your lab's size and the nature of what you're buying. A few patterns that work:
Single-approver, threshold-based — anything under $500 can be ordered without approval; anything over requires PI sign-off. Simple, low-overhead, appropriate for smaller labs where the PI is closely involved.
Category-based routing — chemicals go through safety review, equipment goes through facilities, everything else routes to the lab manager. Useful when different purchases carry different compliance requirements.
Role-based delegation — the PI approves new vendors and large purchases; the lab manager approves routine replenishments; anyone can flag urgent needs directly. This works well when PIs are frequently traveling or managing multiple grants.
Whatever structure you choose, write it down. The implicit "we all know how this works" policy breaks the moment someone leaves or joins the lab.
Handling Vendors
Maintain a short list of preferred vendors and the reason each is preferred. "We use VWR for bulk chemicals because our institution has a contract that discounts consumables 12%" is information that gets lost when the person who made that decision moves on.
For new vendors, require that someone verifies they're an approved vendor through your institution before placing the first order. Routing a non-approved vendor through accounts payable for the first time — under deadline pressure — is a reliable way to delay a critical purchase.
The Receiving Step
Receiving is where most lab purchasing systems fall apart. Items arrive, someone puts them on the shelf, and the PO sits open for weeks because no one recorded the receipt. Then finance follows up, the lab manager spends an hour reconstructing what arrived and when, and the vendor gets paid late.
The fix is simple but requires discipline: receiving is a step in the process, not an afterthought. When something arrives, it gets logged — item, quantity, condition, date. If it's a partial shipment, that gets noted. If something is missing or damaged, that gets flagged immediately rather than discovered at reconciliation.
In practice, this means whoever receives packages needs to know they're responsible for closing the loop on open orders. In larger labs, that's a dedicated receiving role. In smaller labs, it's a shared responsibility that needs to be explicitly assigned, not assumed.
Reconciliation Without the Pain
Monthly reconciliation is easier when you have clean data. The goal is to match every line on your credit card statement or purchase order report to a specific order in your system.
Three things make this go smoothly:
Consistent vendor names — "Fisher Scientific" and "Thermo Fisher" and "Fisher" are the same vendor. Pick one name and use it everywhere. The same goes for grant account strings.
Invoice numbers on orders — when you pay an invoice, record the invoice number on the corresponding orders. This creates a two-way link: from the order to the invoice, and from the invoice back to the orders it covers.
Receipt confirmation before payment — don't release payment for items that haven't been confirmed received. This is a standard accounts payable control that many labs skip because it feels slow. It prevents paying for things you didn't get.
Grant Compliance Basics
Every funding agency has rules about what can be charged to a grant. The ones that cause the most trouble:
Unallowable costs — entertainment, alcohol, certain types of equipment, and personal items cannot be charged to federal grants regardless of whether they're lab-related. Know your agency's list.
Prior approval thresholds — many grants require prior approval from the program officer for equipment purchases over a certain dollar amount (often $5,000 for NSF, $25,000 for NIH). These thresholds vary by agency and award.
Period of performance — charges must be incurred during the grant period. An order placed on the last day of the grant is allowable; an invoice paid a week after the grant ends may not be, depending on institutional policy.
Keep a simple reference document with your active grants, their key dates, and any unusual restrictions. Review it before making large purchases or trying to charge something atypical to a grant.
Making It Stick
The biggest challenge with lab purchasing systems isn't design — it's adoption. A well-designed system that half the lab uses produces incomplete data that's worse than no system at all.
A few things that help:
Make the compliant path the easy path. If submitting a purchase request takes five minutes and bypassing the system takes thirty seconds, the system will be bypassed. If the system reduces friction — auto-filling vendor info, surfacing budget balances, sending receipts — people will use it.
Make the consequences of bad data visible. When a researcher sees that their grant is 12% over budget because three unlogged purchases hit an account, that's a better teacher than any policy memo.
Start simple and add complexity only when you need it. A spreadsheet used consistently beats a sophisticated system used sporadically.
Tools
Ixion is designed specifically for university research labs — it handles purchasing requests, approval routing, receiving, and invoice reconciliation in one place. Every purchase is tied to a grant account, and the system generates the documentation you need for audits automatically.
If you're evaluating lab management tools, the key questions to ask are: how does it handle partial receipts, can it support multiple grant accounts per order, and what does the audit trail look like? Those three capabilities separate tools built for lab environments from generic procurement software.