Item
Define item code, name, stock category, standard unit, owner, approved suppliers, and any category-specific fields that remain stable across lots.
Implementation guide
Build a lab inventory process people can keep accurate
Define the records, movements, stock states, ownership, exception rules, and daily views before importing a list or configuring software.
Opens the populated Jodoo example after sign-in. Start with the Free plan for up to five users; no credit card required.
This guide focuses on operational inventory control. Chemical safety, regulatory retention, purchasing, accounting, and validation requirements need qualified review for your environment.
- Decide what an item, lot, location, balance, and transaction mean before migration
- Separate available stock from low, expiring, held, expired, and consumed material
- Design the daily receiving, issuing, review, and replenishment work around named owners
5 stepsfrom scope to controlled rolloutLot-firstrecord and movement designOpen recordsbehind every risk count
Agree the identity and control fields before importing data
A clean item list is not enough. Laboratory users often select a usable supplier lot, not an abstract catalog item. Write down which fields belong to the item, the lot, the storage location, and each transaction.
Lot
Define supplier lot, local record number, received quantity, current quantity, opened date, expiry, certificate, restriction, availability state, and evidence.
Location
Define the rooms, cabinets, refrigerators, freezers, shelves, and controlled zones people will actually select and maintain.
Transaction
Define receipt, issue, adjustment, return, and disposal. Each transaction needs quantity, time, person, lot, reason, and related work when relevant.
Make each state answer a practical question
Avoid vague values such as active and inactive. A user needs to know whether the lot can be used, why it cannot be used, who owns the next action, and what event changes the state.
Available
The lot is present, within the permitted date and storage conditions, and not subject to an unresolved restriction.
Low stock
The quantity is at or below the local replenishment point. Keep the item, lot, quantity, owner, and planned response visible.
Expiring soon
The expiry or approved-use window is inside the planning period. The owner decides whether to schedule use, replace, return, or dispose.
On hold
A certificate, condition, discrepancy, investigation, or other restriction prevents normal use until a documented decision.
Expired or consumed
The lot is not available for new work. Retain the record and movement history rather than deleting it from the system.
Keep the common path short and the exception path explicit
Inventory accuracy depends on when people record changes. Make the receipt and issue paths easy enough to use at the point of work, then add clear handling for discrepancies, holds, and corrections.
Receive
Confirm the item, supplier lot, quantity, unit, storage, expiry, evidence, and initial availability before shelving the material.
Store and open
Record the location and storage condition. Add the opened date or changed stability window when it affects usability.
Issue
Record the quantity used, lot, time, person, and sample or assignment context. Choose FEFO when expiry should drive selection, FIFO when receipt order is appropriate, or a documented manual choice when restrictions override both.
Reconcile
Investigate a difference, record the reason, obtain the required review, and use an adjustment transaction instead of silently changing the balance.
Replenish or dispose
Use low-stock, expiry, hold, and upcoming-work views to create an owned response before the material interrupts work.
Build the screen each role opens at the start of work
A dashboard should not replace the register, and a register should not force every role to scan every field. Pair summary signals with detailed lists that open the underlying records.
What can be used now?
Show available lots by item, location, quantity, expiry, opened date, and restriction.
What could interrupt work?
Show low stock, expiring material, held lots, unresolved discrepancies, and the scheduled samples or assignments affected.
Why did the balance change?
Show receipts, issues, adjustments, returns, and disposal by lot, date, person, reason, and related work.
What needs an owner?
Show replenishment, restriction review, expiry action, discrepancy investigation, location correction, and overdue follow-up.
Do not import every spreadsheet problem into the new application
Inventory migration is a business review as well as a file import. The team should agree which records are active, which units are valid, which lots are usable, and who owns unresolved differences.
Normalize identifiers
Choose one item code, one supplier-lot format, and one local lot record per usable lot. Keep legacy references in a separate field when they still help users.
Confirm quantities and units
Count or reconcile the opening balance, remove mixed units from numeric cells, and document any conversion rule outside the imported quantity.
Verify dates and availability
Check expiry, opened date, received date, hold reason, and availability rather than assuming every row in the old file is usable.
Load a pilot set first
Import a controlled set of high-risk or frequently used items, run the daily processes, correct the model, and then expand.
Use ownership, reviews, and measures to prevent slow data decay
The application stays useful when staff know who owns item setup, lot receipt, movements, discrepancy review, replenishment, and field or workflow changes.
Assign data ownership
Name the people who create item records, receive lots, change availability, approve corrections, and retire values that should no longer be selected.
Review exceptions regularly
Use a recurring queue for negative or unexplained balances, held material, past-due actions, upcoming expiry, and lots without a valid location.
Change the app carefully
Let a trained administrator add categories, fields, rules, alerts, and views, then retest affected forms and automations before staff rely on them.
Measure operating health
Track stockouts affecting work, lots below reorder point, expiring or discarded quantity, held-lot age, adjustment frequency, transaction delay, and avoidable expiry waste.
Schedule cycle counts
Count high-risk, high-use, or discrepancy-prone locations more often. Record the observed balance, variance, reason, corrective transaction, reviewer, and next count date.
Connect the purchasing handoff
When stock reaches its reorder point or safety stock, send the item, usable balance, open demand, supplier, lead time, requested quantity, and owner to purchasing instead of copying an alert into email.
A practical design guide
Use this guide before importing inventory or choosing fields
It helps a laboratory define item and lot identities, transaction rules, issue order, replenishment thresholds, physical reconciliation, and ownership before software configuration begins.
Start with the operating decision: Decide what can be issued, what must be held, when replenishment begins, and which record explains every balance change.
Use the App as a worked example: Open the item catalog, lot register, transaction form, risk dashboard, and exception queue while adapting the method to your own controls.
Bring qualified owners into scope: Chemical safety, cold-chain monitoring, regulated retention, purchasing, accounting, and validation need input from the people responsible for those controls.
Sources used for this guide
Reviewed September 21, 2026. These references inform the operating questions in the guide; they do not make the example application compliant with any specific standard.
Reference for laboratory inventory, purchasing, receipt, storage, and quality-system responsibilities.
Reference for stock management, expiry control, storage, and laboratory quality review; apply only the requirements relevant to your setting.
Practical questions about lab inventory management
Should we track items or lots?+
Track both when supplier lot, expiry, opened date, certificate, storage, restriction, or usage history can differ. The item provides the stable catalog identity; the lot is the usable operational stock record.
How often should laboratory inventory be reviewed?+
Review frequency should match usage, expiry risk, storage risk, replenishment lead time, and the cost of interrupted work. Many teams combine transaction-time updates with weekly risk review and periodic physical reconciliation.
What should we clean before importing a spreadsheet?+
Clean duplicate item codes, inconsistent units, missing lot numbers, invalid dates, obsolete locations, unclear availability, unexplained balances, and owner names. Preserve legacy identifiers only when users still need them.
Can one Jodoo app manage inventory and samples?+
Yes. Related forms can connect lots and transactions to samples or assignments. Keep the records separate enough that inventory owners and laboratory staff can maintain their parts without overwriting each other.
When should we move beyond a spreadsheet?+
Move when several people update the file, lots need separate histories, reminders or permissions matter, transactions must link to work, exceptions require review, or managers need reliable current views without manual consolidation.
Explore the populated laboratory workspace
Explore the lab inventory exampleUse the working inventory example to test your design choices
Compare the guide with populated lot, movement, sample, and risk views. Keep what fits, remove what does not, and pilot the model with real owners and exceptions.