Inventory Control Software for Small Business: Stopping the Count From Drifting
Inventory control software for small business is about accuracy and accountability, not just storing a number. This guide shows how the right-sized system stops your count drifting for firms outgrowing spreadsheets and disconnected tools.
Inventory control software for small business keeps the stock figure on screen true to what is physically on the shelf. It does that by controlling how stock changes: what counts as received, who can adjust a quantity and why, what is already promised to a customer, and how counts and variances are reviewed.
The practical problem is rarely a missing stock list. It is a list that anyone can overwrite, deliveries booked in before they are checked, orders that promise the same item twice and a year-end stocktake that reveals gaps nobody can explain. Good controls make each change deliberate, attributable and reviewable, so a wrong number can be traced back to the event that caused it.

Counting against the system record is one of the main checks that keeps recorded stock true. Illustrative photograph, not an OpsMavix project.
Image credit: Cova Software, Unsplash License. No edits.
Key Takeaways
- Inventory control is about keeping recorded stock true, not just storing a quantity per item.
- Stock should only become available after a receiving check against the order and the delivery.
- Every adjustment needs a reason, a person and, above a set value, a second approver.
- Separate on hand, reserved and unavailable stock so the business never sells the same unit twice.
- Small, frequent counts with a variance review catch errors while the cause is still traceable.
- Software should enforce the controls you can describe; it cannot replace someone reviewing exceptions.
In this guide:
- 1. Understand What Inventory Control Covers
- 2. Find Where Recorded Stock Goes Wrong
- 3. Check Goods In Before Stock Is Available
- 4. Make Every Adjustment Carry a Reason
- 5. Separate Available and Reserved Stock
- 6. Count Little and Often
- 7. Review Variances and the Audit Trail
- 8. Introduce Controls in a Sensible Order
- Frequently Asked Questions
- How OpsMavix Can Help
1. Understand What Inventory Control Covers
Management versus control
Inventory management is mostly about decisions: what to stock, how much to buy and when to reorder. Inventory control is about evidence: whether the quantity you are basing those decisions on is correct, and whether every change to it can be explained.
The two depend on each other. A reorder point is only useful if the stock figure it watches is accurate. A forecast built on records that drift will order the wrong amount with great confidence.
If you are still deciding which kind of system to use, our sibling guide on inventory management systems for small business covers how to size and choose one without overbuying. This guide assumes you have, or will have, a system and focuses on the controls it should enforce.
Why accuracy is worth the effort
Record errors are common, even in organised retailers. In a three-year study with seven European retailers, ECR Retail Loss found that 59.54% of audited SKUs did not match the system record at the time of the stocktake. In the same study, stores that counted and corrected their records saw sales rise by approximately 4% to 8% compared with matched control stores.
That research covered retail stores, so treat it as evidence that record errors are normal rather than as a forecast for your business. The point applies widely: stock the system thinks is missing is not sold, and stock it wrongly thinks is present gets promised to customers.
The legal floor for companies
For UK limited companies that deal in goods, records of stock are also a legal requirement. Section 386 of the Companies Act 2006 requires accounting records to contain statements of stock held at the end of each financial year and the statements of stocktakings from which those figures were prepared. Your accountant can advise on how that applies to your business and how stock should be valued.
2. Find Where Recorded Stock Goes Wrong
The usual causes of drift
Discrepancies often start with everyday process steps, not only theft. Before tightening controls, find out which of these causes appears most in your operation.
| Source of error | What happens | Control that addresses it |
|---|---|---|
| Receiving | Stock booked in from the supplier’s paperwork without a physical check | Receive against the purchase order with counted quantities |
| Picking | Wrong item or quantity sent, so one SKU is overstated and another understated | Scan or confirm item at pick and pack |
| Returns | Returned goods restocked without inspection, or never put back | Hold returns until inspected and graded |
| Damage and waste | Broken or expired items thrown away without a record | Adjustment with a reason code at the point of disposal |
| Unit of measure | A case received as a single unit, or the reverse | Defined pack sizes and conversions on each SKU |
| Overrides | Someone types over the quantity to make it “look right” | Adjustments only through a logged transaction, never a direct edit |
| Theft | Stock leaves without any transaction | Access controls, counts on high-risk lines and variance review |
3. Check Goods In Before Stock Is Available
Receive against the order, not the paperwork
Receiving is where many records go wrong first. If stock is added from the supplier’s delivery note without anyone counting it, any short delivery, substitution or damage becomes a hidden error that surfaces weeks later as a “missing” item.
A controlled receipt compares three things: what was ordered, what the supplier says they sent and what was physically counted. The counted quantity should be what enters stock. The other two explain the difference and support any claim against the supplier.
This connects naturally with purchasing. A purchase order system for small business gives receiving something to check against, and gives finance a receipt to match before paying the invoice.
What software should enforce at goods in
| Control | What it prevents |
|---|---|
| Receipt linked to an open purchase order | Stock appearing with no source document |
| Counted quantity entered, not copied from the order | Short deliveries silently booked in full |
| Partial receipts kept open | A short delivery being treated as complete |
| Damaged or rejected items recorded separately | Damaged goods becoming sellable stock |
| Receipt identifies the person and time | Anonymous receipts that cannot be queried |
| Over-receipt beyond a tolerance flagged | Extra or wrong goods absorbed without review |
4. Make Every Adjustment Carry a Reason
Adjustments are where control is won or lost
An adjustment is any change to stock that is not a normal receipt, sale or transfer: a damaged item written off, a count correction, a found item or a sample given away. They are necessary, and they are also where errors and losses can most easily disappear.
The rule is simple: no quantity changes without a transaction, and no adjustment without a reason, a person and a time. Corrections should be new entries that leave the history intact, not edits that overwrite it.
Reason codes that support analysis
Keep the list short enough that people use it properly, for example:
- Damaged in storage
- Damaged on receipt (if not handled through a supplier claim)
- Expired or out of date
- Count correction, increase
- Count correction, decrease
- Found stock
- Samples or internal use
- Unit of measure correction
Avoid a catch-all such as “Other” unless it requires a written note. If most adjustments end up as “Other”, the reason codes are not telling you anything.
Packaged tools handle this in different ways, so check the detail. Zoho Inventory’s adjustment screen asks the user to select a reason from a list you can maintain, and lets an adjustment be saved as a draft before it is converted and changes stock.
Permissions and approval thresholds
Not everyone who can receive or pick should be able to write stock off. A practical permission model separates three roles:
| Role | Can do | Cannot do |
|---|---|---|
| Warehouse or shop staff | Propose adjustments with a reason and evidence | Post adjustments above the approval threshold |
| Supervisor or manager | Approve or reject adjustments, post within their limit | Approve their own adjustments |
| Owner or finance | Set thresholds, review adjustment reports and trends | Bypass the log |
Approval workflows exist in some packaged tools. Zoho Inventory’s transaction approval documentation, for instance, lists stock adjustments and transfer orders among the transactions that can be routed for approval. If your tool lacks this, a custom workflow or a separate approval step can fill the gap. Our stock adjustment approval workflow guide goes into the evidence and posting checks in more detail.
Hypothetical example: setting an approval threshold
Suppose a business sets a rule that any single adjustment worth more than £100 at cost needs a manager’s approval. A staff member proposes writing off 5 units of an item that costs £65.00 each. The adjustment value is 5 × £65.00 = £325.00, so it goes to a manager. A separate write-off of 2 units at £4.50 is worth £9.00 and can be posted directly, but still records a reason and a name.
The threshold is illustrative; set yours from the size of typical adjustments and the review time you can sustain.
5. Separate Available and Reserved Stock
On hand is not the same as available
Many overselling problems come from treating one number as if it answered every question. A controlled record distinguishes at least these quantities:
| Quantity | Meaning |
|---|---|
| On hand | Everything physically at the location |
| Reserved or committed | Set aside for orders, transfers or quotes that have been confirmed |
| Unavailable | Held back as damaged, in inspection or as safety stock |
| Available | What can still be promised to a new customer |
| Incoming | Ordered from suppliers but not yet received |
Shopify, as one example, documents that On hand equals Committed plus Unavailable plus Available, and that incoming stock is not available to sell until it has been received at the location.
Hypothetical example: what can still be sold
A hypothetical shop holds 40 units of a product. Twelve are reserved for confirmed orders awaiting dispatch and 3 are held as damaged pending a supplier claim.
| Line | Units |
|---|---|
| On hand | 40 |
| Less reserved for orders | 12 |
| Less unavailable (damaged) | 3 |
| Available to promise | 25 |
If the website shows 40 rather than 25, the business can accept up to 15 orders it cannot fulfil from stock. Reservations should be created when an order is confirmed and released when it is dispatched or cancelled, so they do not linger and understate availability.

Stock on a shelf may already be promised to a customer, so on hand and available need to be kept apart. Illustrative photograph, not an OpsMavix project.
Image credit: Ashley, Unsplash License. No edits.
6. Count Little and Often
Cycle counts versus a single stocktake
A once-a-year stocktake finds errors long after they happened, when nobody can remember the delivery or order that caused them. Cycle counting spreads the work across the year: a small set of items or locations is counted on a schedule, and errors are investigated while they are still recent.
Many businesses count higher-value and faster-moving lines more often than slow, low-value ones. Our guide to inventory management best practices covers ABC classification and count frequency in more depth.
Some packaged tools support scheduling directly. Odoo’s cycle count documentation, for example, describes setting an inventory frequency in days for each storage location and an annual inventory date for full counts, which requires the Storage Locations setting to be enabled.
Counting controls that keep the result honest
- Blind counts. Counters record what they find without seeing the expected quantity, so they are not tempted to match it.
- Movement freeze or cut-off. Either pause movements for the items being counted or record the count time so later sales and receipts are handled correctly.
- Recount before adjusting. Large differences get a second count, ideally by someone else, before any adjustment is posted.
- Count results as evidence. The count sheet or scan record is kept with the resulting adjustment.
- No quiet fixes. Count corrections go through the same reason codes and approval rules as any other adjustment.
7. Review Variances and the Audit Trail
Why net variance hides problems
When a count finishes, the tempting summary is the net difference in value. Net figures let gains on one line hide losses on another. Review absolute variance as well, and look at the lines behind it.
Hypothetical worked example: one cycle count
A hypothetical business counts eight SKUs. Its rule is to investigate any line where the variance is worth more than £25 at cost or exceeds 5% of the recorded quantity.
| SKU | Recorded | Counted | Difference | Unit cost | Variance value |
|---|---|---|---|---|---|
| A | 120 | 118 | -2 | £4.50 | -£9.00 |
| B | 40 | 40 | 0 | £22.00 | £0.00 |
| C | 250 | 262 | +12 | £0.80 | +£9.60 |
| D | 16 | 11 | -5 | £65.00 | -£325.00 |
| E | 75 | 75 | 0 | £3.20 | £0.00 |
| F | 30 | 29 | -1 | £12.00 | -£12.00 |
| G | 500 | 500 | 0 | £0.35 | £0.00 |
| H | 8 | 8 | 0 | £140.00 | £0.00 |
The results:
- Net variance: -£9.00 + £9.60 - £325.00 - £12.00 = -£336.40.
- Absolute variance: £9.00 + £9.60 + £325.00 + £12.00 = £355.60.
- Line accuracy: 4 of 8 lines matched exactly, which is 50%.
- Lines inside both limits: A (1.67%, £9.00), C (4.8%, £9.60) and F (3.33%, £12.00). These are corrected with a reason code but need no investigation.
- Lines to investigate: D, which is worth £325.00 and is 31.25% of the recorded quantity.
Only SKU D breaches the rule, and it accounts for £325.00 of the £355.60 absolute variance. That is where review time should go: check recent receipts, dispatches, returns and adjustments for D before approving any correction.
What a usable audit trail shows
For any SKU, someone should be able to see each movement with:
- Date and time
- Movement type (receipt, sale, transfer, adjustment, count)
- Quantity change and resulting balance
- The person, app or channel that made it
- Reason code and note, for adjustments
- The source document, such as the purchase order, sales order or count
Check how long the history is kept and how easily it can be searched. Shopify’s adjustment history, for example, shows date, activity, the staff member, app or channel responsible and the quantity change per inventory state. It displays the last 180 days on the product screen and points to a report for older changes that can be filtered by SKU, location, staff member, app and reason.
Turn the log into a regular review
A short monthly review is often enough for a small business:
- Total adjustments by reason code, compared with the previous month.
- Adjustments by person or location, looking for unusual concentrations.
- SKUs with repeated variances across counts.
- Approvals given above threshold, with evidence attached.
- Open receipts, unreleased reservations and items stuck in inspection.
The aim is not to blame individuals. Repeated variances usually point to a process that needs fixing, such as a confusing pack size, a location that is hard to count or a returns step that gets skipped.
8. Introduce Controls in a Sensible Order
Start where errors begin
Introducing every control at once is hard for a small team. A workable order is to stop direct edits first, then control receiving, then show available rather than on hand stock to sales channels. Start cycle counts on the highest-value lines, add approval thresholds once you know the size of typical adjustments, and let the monthly variance review guide count frequency.
Where the controls can live
| Approach | When it fits | What to check |
|---|---|---|
| Configure your existing tool | The control already exists but is switched off or unused | Permissions, reason codes, approval settings and reports |
| Add an integration or add-on | Your tools work individually but stock changes do not flow between them | Which system owns the stock figure, sync timing and failure alerts |
| Packaged inventory software | Its standard workflows match how you receive, reserve and count | Edition limits, history retention and whether approvals are included |
| Focused custom application | A specific control, such as adjustment approval or receiving, is missing | Data ownership, support, and connections to sales and accounting |
| Full ERP, packaged or custom | Stock control is one of many joined-up processes needing change | Finance fit, migration effort and delivery capacity |
This is not a ranking. Configuring tools you already pay for can deliver much of the benefit. The sibling guide on choosing inventory management systems for small business covers sizing and selection in detail.
A control checklist to test any system
Ask a user to carry out each of these on screen, using your own products:
- Receive a short delivery and show the remaining quantity still open on the order.
- Record damaged items on receipt without making them available.
- Propose an adjustment over the threshold and show it waiting for approval.
- Show that the person who proposed an adjustment cannot approve it.
- Confirm an order and show available stock fall while on hand stays the same.
- Run a blind count and post the variance with a reason.
- Open the history for that SKU and explain the current balance.
- Export the adjustment report for a month, grouped by reason.
Frequently Asked Questions
What does inventory control software actually do?
It keeps the recorded stock figure accurate by controlling how it changes. That includes receiving against orders, adjustments with reasons and permissions, reservations for confirmed orders, counting tools and an audit trail of every movement.
Is inventory control different from inventory management?
Yes, although they overlap. Management covers decisions such as what and when to buy. Control covers whether the stock records behind those decisions are correct and whether every change can be explained.
Do small businesses really need approval rules for adjustments?
Not for every adjustment. A value threshold keeps routine low-value corrections quick while making larger write-offs visible to a second person. Even below the threshold, each adjustment should record a reason and who made it.
How often should a small business count stock?
There is no single rule. Many businesses count high-value or high-risk lines weekly or monthly and slower lines quarterly, with a full count at year-end. Limited companies dealing in goods must keep year-end stock statements and the stocktaking records behind them.
Why does available stock differ from on hand stock?
On hand is everything physically present. Available excludes stock already reserved for confirmed orders and stock held back as damaged or awaiting inspection. Selling from on hand rather than available is a common cause of overselling.
What should we look at first if our counts keep drifting?
Look at receiving and adjustments first. Check whether deliveries are counted before stock is added and whether quantities are ever edited directly. Then review which SKUs vary repeatedly and what they have in common.
Can OpsMavix build inventory control software?
Yes. OpsMavix can build focused applications, such as receiving or adjustment approval workflows, or a full custom ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.
How OpsMavix Can Help
OpsMavix can map how stock enters, moves and leaves your business, identify where the recorded figure drifts from physical stock and define the controls needed to keep it true.
That may involve configuring the tools you already use, building an inventory automation system with receiving checks, reasoned adjustments and approval thresholds, connecting online channels through ecommerce inventory automation, or reserving stock against trade orders with a wholesale order management system.
Contact OpsMavix with your last stocktake or cycle count results, a month of stock adjustments and the SKUs that vary most often. We can use that evidence to define requirements and a practical pilot.
Getting value from OpsMavix? Add us as a preferred source on Google — you'll see more of our operations content in your AI Overviews, AI Mode and Search.