Inventory management software for accurate stock records
Stock by location with every movement on record, a cycle-count program that finds the cause of errors, and reorder points a buyer can check by hand.
Scope a project
Most operations already have an inventory number. The trouble is that nobody trusts it, so the real stock lives in a spreadsheet, on a whiteboard or in a supervisor’s head. We build the inventory layer that keeps stock by location, records every movement and measures whether the record matches the shelf. It runs alongside the ERP or WMS you already have.
Stock by location, not just by item
An ERP often holds a quantity per item per warehouse. The floor needs more: item, location, lot and status. We model your locations as they are used, from site and zone down to aisle, bay, level and bin, plus the places stock hides: staging lanes, the returns cage, the QC hold area, a trailer parked at the door. Each balance carries a status (available, on hold, damaged, in inspection) so that “on hand” and “available to ship” are never confused.
Units of measure are set per item, with conversions for each, case and pallet, because a count in cases posted as eaches is one of the quickest ways to wreck a record.
Every movement on record
Each transaction is a scan or a screen entry with a reference document:
- Receipt against a PO or ship notice, by pallet SSCC where the supplier labels them.
- Put-away from the dock to a bin, confirmed by scanning the location.
- Move from bin to bin, including replenishment of pick faces.
- Adjustment with a required reason code. Adjustments above a quantity or value threshold wait for a supervisor’s approval.
- Pick, issue and ship, so stock leaves the record when it leaves the shelf.
The audit trail records who did it, when, on which device, from and to which location, the quantity before and after, the reason and the document. When a balance looks wrong, an inventory controller can read its history line by line instead of guessing.
Cycle counting programs
ASCM’s dictionary defines cycle counting as “An inventory accuracy audit technique in which inventory is counted on a cyclic schedule rather than once a year.” It says the key purpose is “to identify items in error, thus triggering research, identification, and elimination of the cause of the errors.” We build the program around that purpose, not just the count:
- Classes and frequencies, for example A items monthly, B quarterly and C once a year. Size the workload with the cycle count planner.
- Blind counts, where the counter does not see the expected quantity.
- A recount rule when a variance exceeds tolerance, before anything posts.
- Counts triggered by events: a pick from an empty bin, a negative balance, a location that should be empty but is not.
- A root-cause code on every approved variance, reviewed weekly.
Lot, serial and expiry
Lot and expiry dates are captured at receipt, from the supplier’s barcode where it carries them or keyed where it does not. Allocation can follow first-expired, first-out. Holds and quarantines block a lot everywhere at once. A recall lookup answers two questions from the record: where did this lot come from, and where did it go. Serial numbers are tracked for items where one unit matters.
For food on FDA’s Food Traceability List, these lot-level records feed the work described on our food traceability page. FDA will not enforce the Food Traceability Rule before July 20, 2028, under a congressional directive.
Replenishment you can explain
ASCM describes the reorder point as “normally calculated as forecasted usage during the replenishment lead time plus safety stock”, and safety stock as “a quantity of stock planned to be in inventory to protect against fluctuations in demand or supply.” The textbook formula sets safety stock as a safety factor (k) times the standard deviation of demand over the lead time. The safety factor comes from the service level you choose, about 1.65 for 95 percent.
We show the inputs next to every suggested order, so a buyer can check the number instead of overriding it.
Example (fictional). Item EX-20118 sells an average of 120 units a day, with a daily standard deviation of 35 units. The supplier’s lead time is 9 days. Demand over the lead time is 1,080 units. Its standard deviation is 35 times the square root of 9, or 105 units. At a 95 percent cycle service level, safety stock is 1.65 times 105, about 173 units, so the reorder point is 1,253. The buyer sees all four numbers on the screen. You can run your own items through the safety stock calculator and the reorder point calculator.
Inventory accuracy you can measure
ASCM defines inventory accuracy as the state “when the on-hand quantity is within an allowed tolerance of the recorded balance”, usually measured as the percent of items within tolerance, and adds: “Target values usually are 95 percent to 99 percent, depending on the value of the item.” We build that measure into the system: tolerances per item class, accuracy by zone and class, and adjustments by reason and by person. You can see where you stand today with the inventory accuracy calculator.
Alongside your ERP or WMS, not instead of it
Your ERP stays the system of record for the item master, cost and valuation. If you run a WMS, it keeps directing warehouse tasks. Our layer covers what they do not: the locations the ERP does not track, a counting program the WMS does not support, a satellite site or maintenance crib with no WMS at all. Receipts and adjustments post back to the ERP through interfaces we build and document under ERP and WMS integration, with a written rule for which system wins when the two disagree.
What you receive
- Location model, transaction set and audit trail, configured to your process.
- Cycle count program with tolerances, recount rules and root-cause codes.
- Replenishment logic with visible inputs, and an accuracy report.
- Interfaces to your ERP or WMS, with a reconciliation report.
- Source code and configuration, delivered at handover. Ownership and licensing terms are set out in each statement of work.
Scope your project.
Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.