Everything you need before you sign in

How FIFO auto-consumption works

Every reagent batch in Vitrio carries its own received date. When a technician logs a test result, the consumption engine looks up that test type's recipe, then deducts the required quantity from the oldest available batch first, not whichever batch happens to be listed first. That's what keeps reagents from expiring unused on a shelf while a newer batch gets used up front. Every deduction writes a chain-of-custody entry naming the exact batch, so if a result is ever questioned, you can trace precisely which lot of reagent was involved.

Reading your Lab Health Score

The Health Score on your dashboard isn't a black box. It's a deterministic blend of a few real signals: how many items are below reorder point, how many are approaching expiry, open maintenance tickets on your equipment, and open supplier complaints. Fix any one of those (reorder low stock, resolve a ticket) and the score recomputes the next time you load the dashboard. There's no hidden weighting you can't reason about.

Setting up your first budget

A budget in Vitrio tracks three numbers against its total: committed (purchase requests awaiting approval), pending estimate (approved but not yet invoiced), and spent (invoiced and paid). Attach purchase requests to a budget as you create them, and all three figures update automatically, with no separate spreadsheet reconciliation at month-end.

Running your first RFQ

Pick the item you need, select which suppliers to ask, and send the request-for-quotation in one action. Suppliers with a portal login respond directly; you'll see every reply lined up for comparison by price and lead time. Convert the one you want straight into a purchase request. It stays linked back to the original RFQ and that supplier's record.

Physical counts vs. system counts

Vitrio's system quantity updates automatically as tests are logged and stock is received, but nothing replaces occasionally counting the shelf by hand. A stock count records what you physically counted against what the system expected at that moment, flags the variance, and feeds your lab's real stock-accuracy percentage. Lab Admins, System Admins, Managers, and Technicians can all log a count.

Understanding role-based access

A Technician can log test consumption and view inventory, but can't add staff or change lab settings. A Procurement Officer manages purchase requests and suppliers, but doesn't touch test logging. A Viewer sees everything read-only, by omission: they're simply excluded from every action that changes data. The full breakdown lives in the role table above and the in-app Roles & Permissions page once you're signed in.

How Test Continuity spots trouble before it happens

Most systems only tell you a test can't run once a sample is already sitting blocked. Vitrio's continuity engine reads the same reagent-capacity math that already drives Stock Intelligence and projects it forward per test type, so a test can read "At Risk" while stock is still technically positive — because it's genuinely projected to run out before any replenishment lands. Staff with the right role see exactly which reagent is the real constraint and why, and can raise a purchase request pre-filled with a sensible quantity in one click, straight from the same screen. Nothing here is a second, separately-maintained score: it's the same evidence Stock Intelligence already computes, just read one step ahead.