RGIS Stocktake Alternative: A System That Counts Itself

RGIS sends counters once a year to fix a number that's been wrong for months. The real alternative isn't a different counting crew. It's a system that keeps stock accurate year-round, so the disruptive full count stops being the only time you trust your figures.

OpsMavix 17 min read
A team of hired counters working through a warehouse at night on one side, a live stock dashboard updating itself on the other

The best RGIS stocktake alternative depends on what you want to change. If you need people to complete a physical count, compare counting services, an internal team and hybrid arrangements. If your records become unreliable between counts, improve the stock movements and checks that maintain them. A new counting provider alone will not resolve an unrecorded return or a transfer that never reaches the system.

A connected inventory system and regular cycle counts can reduce the drift between stocktakes. They do not remove the need to verify physical stock, and they do not automatically replace financial reporting or audit requirements. The useful goal is a record you can explain and check throughout the year, with a counting programme suited to your operation.

RGIS itself offers more than annual stocktakes. Before switching, establish whether the gap is counting capacity, the counting method, inventory software or the workflow around it.

This guide explains the alternatives, how to run reliable cycle counts and how to assess the cost of maintaining accuracy between full counts.

Warehouse shelving and stored goods used to support inventory and fulfilment operations

Physical counts verify the stock you hold. Transaction controls help maintain the record between those checks.

Key Takeaways

  • RGIS offers several counting approaches, including outsourced, hybrid, self-scan and cycle-count services.
  • Changing the counting provider and improving the inventory workflow are separate decisions that can work together.
  • Cycle counting checks selected stock regularly, helping identify discrepancies closer to when they occur.
  • Connected software maintains a transaction record; it does not physically count the shelf or guarantee every movement was captured correctly.
  • Compare staff time, counting services, software, implementation and ongoing support across the same scope.
  • Start with a controlled pilot and agree any changes to year-end counting with the people responsible for financial reporting and audit.

In this guide:

1. Decide What You Need to Replace

An RGIS stocktake alternative might replace a counting crew, counting technology or an operational process. Those are different briefs, with different staffing and system requirements.

RGIS is not limited to annual counts

RGIS’s UK stocktaking solutions page describes multiple approaches to counting. Its inventory services overview lists fully outsourced counts, supervisor-led hybrid counts, U Count self-scan, targeted counts and cycle counts. Availability and delivery arrangements should be confirmed for your sites.

It is therefore inaccurate to frame the choice as “RGIS counts once a year; an alternative counts continuously.” A business can use an external provider for recurring verification while maintaining its own transaction records.

Write the requirement around the missing work

Your requirement What to evaluate
Count a whole site within a short window Provider capacity, preparation, supervision and reconciliation
Run recurring checks without enough internal staff Outsourced or hybrid cycle-count support
Let staff count using suitable technology Self-scan tools, training and count controls
Record stock accurately between checks Inventory software and movement capture
Understand repeated discrepancies Investigation workflow, evidence and corrective action
Support financial reporting Count coverage, cut-off records and the agreed reporting process

You may need more than one of these. Software can schedule a count, but a person still needs to find the location, identify the item, count the units and investigate exceptions.

Start with your existing arrangement

Review what the service currently includes, which tasks remain internal and which results you use afterwards. Ask whether count exports include locations, units, timestamps, recounts and discrepancy reports in a usable format.

If the service produces sound evidence but your team never investigates the recurring differences, the gap may sit after the count rather than inside it.

2. Find Why Stock Drifts Between Counts

A full count can establish a useful baseline. Its reliability afterwards depends on the transactions, physical handling and checks that follow.

The record may drift because events were missed, entered incorrectly, duplicated or posted to the wrong location. Damage, theft and identification mistakes also need controls; they do not disappear because software is connected.

Trace the common gaps

Event Failure to look for Control to test
Receiving A box is entered as one unit instead of its contents Purchasing-to-stock unit conversion
Picking and dispatch Stock is deducted twice or not at all Defined reservation and deduction stages
Returns A unit is restocked without inspection or recording Return receipt and condition status
Transfers The source is reduced but the destination never confirms receipt Separate in-transit and received states
Damage and scrap Stock leaves the shelf without an authorised transaction Reason-coded write-off
Integration A replayed event changes stock again Duplicate-event handling and reconciliation
Adjustments Someone overwrites the balance without evidence Approval, reason and transaction history

Choose a recent discrepancy and follow its movement trail. “The system is wrong” is a starting observation, rather than an explanation.

Distinguish location errors from missing stock

Hypothetical example: the system shows 20 units in bin A and 10 in bin B. The count finds 15 in each. Total recorded stock and total physical stock are both 30 units.

That is a location discrepancy. Investigate a possible unrecorded transfer before reducing A by five and increasing B by five as unrelated adjustments. The count has identified something important even though the total quantity agrees.

If an adjustment conceals the missing transfer, the process may repeat the same error next week.

For the wider workflow, see why stock never matches the system. The objective is a traceable record of what happened, rather than repeated resets to unexplained balances.

3. Use Cycle Counts to Check Stock Throughout the Year

Cycle counting means physically checking selected items or locations on a recurring schedule. It spreads verification over time and can make repeated discrepancies easier to investigate.

It requires planned capacity, reliable location coverage and follow-up. A list that gets counted only when someone has spare time is unlikely to stay complete.

Prioritise by operational risk

A useful schedule can consider:

  • Stock value and exposure to loss.
  • Movement frequency and recent discrepancies.
  • Criticality to customer orders or production.
  • Similar-looking items and awkward units of measure.
  • Batch, serial or expiry requirements.
  • Empty bins, unexpected stock and newly created locations.

High-value items are worth attention, but a low-cost spare that stops production may also deserve frequent verification.

Calculate the counting workload

Hypothetical programme: a warehouse has 600 SKU-location records. It plans the following schedule over 48 working weeks:

Group Records Checks per record each year Planned checks
Higher-risk items 100 12 1,200
Medium-risk items 200 4 800
Lower-risk items 300 1 300
Total 600 2,300

That is approximately 48 checks a week, or 10 a working day over a five-day week. At six minutes per check, the initial counting work totals 230 hours a year.

Those figures exclude travel between areas, recounts, investigation, supervision and adjustment approval. Add capacity for those tasks before deciding the programme fits existing staffing.

The frequencies are illustrative. Your stock, risks and reporting needs should determine the actual schedule.

Verify both the records and the shelves

Counting only system-listed locations can miss stock stored in an unexpected place. Include checks that confirm listed stock exists and floor checks that establish physically present stock is recorded.

Record empty locations where relevant. Keep quarantined, customer-owned and consignment stock distinguishable so it is not added to ordinary available inventory by mistake.

A programme needs complete planned coverage as well as frequent attention to troublesome items. Recounting the same easy bins every month does not verify the rest of the warehouse.

4. Control Movements While Counting

Cycle counts can reduce disruption, but they still need control over the area being counted. Without a clear count time and movement procedure, a difference can simply be a timing mismatch.

Business tools connected through a central operations system

The count must reconcile to the inventory record at an agreed time, including receipts and issues around that point.

Choose a controlled method

One option is to pause movements in a small location while it is counted. Another is to record movements precisely and reconcile them to the count timestamp. The right method depends on your operation and system capabilities.

Either approach should identify:

  • The location and items within scope.
  • The balance and timestamp used for comparison.
  • Receipts, issues and transfers around the count.
  • Pending offline or integration transactions.
  • Who can release the area and approve the result.

A count sheet created at the start of a shift is not automatically the right comparison for a shelf counted three hours later.

Reconcile a count-time difference

Hypothetical example: the record shows 100 units at 09:00. A receipt of 20 units is completed at 09:10. Ten units are issued at 09:20. A physical check at 09:30 finds 110 units.

The expected position is:

100 + 20 − 10 = 110 units.

Comparing the count with the 09:00 snapshot would suggest a ten-unit gain. Accounting for the intervening transactions shows there is no quantity variance in this example.

This is why a process can remain wrong even after someone has physically counted every unit correctly.

Reduce bias and identification errors

Where suitable, use a blind first count so the counter is not shown the expected quantity. Scan the location and item to reduce identification mistakes, then enter the actual physical quantity.

Scanning a product label identifies the code; it does not prove the number of units inside a carton. Define how sealed packs, open boxes, weight-based stock and mixed units are counted.

Use a different counter for significant or unexplained variances where practical. The recount should follow the same controlled timing rules rather than repeat an unclear comparison.

5. Investigate Variances Before Adjusting Stock

An adjustment makes the record match an accepted count. It does not by itself explain the difference or prevent recurrence.

Use a repeatable discrepancy workflow

  1. Confirm the item, location and stock unit.
  2. Recount according to the agreed threshold and risk policy.
  3. Check adjacent locations, returns, quarantine and goods in transit.
  4. Review movements around the count time.
  5. Identify a supported cause or record that it remains unresolved.
  6. Obtain adjustment approval where required.
  7. Assign corrective action and verify whether the problem recurs.

Retain the original balance, count, recount, transactions and approval. Corrections should leave a history rather than erase the previous figure.

Separate missing stock from financial loss

Hypothetical example: a count finds a confirmed five-unit shortage on an item carried at £12 per unit. The quantity difference corresponds to £60 of stock value, before any applicable valuation treatment.

Do not also call the full retail selling price a realised loss unless the evidence supports that conclusion. A shortage may cause an order cancellation, but avoided fulfilment costs, replacement stock and later sales affect the actual commercial impact.

For operations reporting, record observable consequences separately: expedited freight, overtime, customer credits or production downtime. Avoid counting the same consequence twice.

Measure first-count accuracy and corrective action

A useful set of measures includes:

  • Planned counts completed on time.
  • First-count agreement, before corrections.
  • Absolute quantity and value variances.
  • Repeated discrepancies by item or location.
  • Investigation time and unresolved cases.
  • Completion of corrective actions.

Hypothetical metric: if 46 of 50 counted records agree exactly before adjustment, exact-match accuracy is 92%. Define the denominator and whether any tolerance applies before comparing periods.

Net variance alone can hide problems. A five-unit shortage in one location and five-unit surplus elsewhere net to zero, while still revealing an issue that can affect picking.

6. Compare Services, Software and Total Cost

The useful comparison is between complete operating approaches. Counting services supply capacity and expertise. Inventory software supplies records and controls. A business may benefit from both.

Compare the practical options

Approach Where it can fit Responsibilities to include
Fully outsourced physical count Large scope, short window or specialist counting needs Preparation, provider delivery, cut-off and internal reconciliation
Outsourced or hybrid cycle counting Recurring verification without enough internal capacity Coverage, scheduling, investigations and handover
Internal counts with packaged software Standard requirements and trained staff Counting labour, configuration, support and approval controls
Internal counts with custom software Specific workflow gaps standard tools cannot handle economically Development, count labour, maintenance, integration and handover

Standard software can support movement history and cycle-count tasks. Custom development should be justified by a demonstrated gap, rather than the assumption that only bespoke software can provide those controls.

Model the cost over several years

Hypothetical three-year comparison: administration and counting labour are valued at £25 an hour over 48 working weeks. The recurring allowance includes the defined counting service or software/support costs. These figures are examples, not RGIS prices or OpsMavix quotations.

Cost component Current outsourced-count arrangement Internal programme with packaged software Internal programme with custom software
Setup or implementation £0 £6,000 £18,000
Annual service/software/support allowance £5,000 £2,400 £3,600
Internal counting and administration per week 6 hours 5 hours 4 hours
Internal labour over three years £21,600 £18,000 £14,400
Recurring allowance over three years £15,000 £7,200 £10,800
Total modelled cost £36,600 £31,200 £43,200

In this example, packaged software is the least expensive route if it meets the requirements and the team has capacity. Custom costs more and needs additional, evidenced benefits to justify it.

Before applying the model, ensure each route delivers the same necessary coverage and evidence. Include any full count that remains required, extra supervision, disruption and implementation effort. If a provider performs work not represented in the other options, add that work to those options.

Released staff capacity is not automatically a cash saving. State whether it reduces overtime, replaces external spend or allows more productive work.

Include maintenance and access

A custom system still needs hosting, backups, security updates and support. Confirm source-code rights, documentation, data exports and access for another maintainer in the agreement.

With a counting provider or packaged platform, confirm export formats, service expectations and exit arrangements. Reliable records need to remain usable beyond the next count.

7. Keep Full Counts Where They Serve a Purpose

A full physical count is not evidence that a business has failed. It may provide a starting baseline, independent verification, wider coverage or evidence needed for reporting.

Full counts can remain useful

Consider them when:

  • Opening balances are unreliable.
  • A site moves or inventory changes ownership.
  • A substantial part of the stock was outside existing controls.
  • Coverage gaps or recurring discrepancies undermine the cycle-count programme.
  • Financial reporting, audit, lender or insurance arrangements call for particular evidence.

The scope and timing should follow the actual requirement. Do not cancel a planned stocktake simply because a new system is installed.

Agree changes to reporting counts

The FRC’s ISA (UK) 501 sets requirements for audit evidence when inventory is material, including attendance at physical counting unless impracticable. It also addresses counts performed at a different date and evidence over intervening movements.

A perpetual inventory record does not automatically exempt a business from physical verification. The appropriate evidence and counting approach depend on circumstances and the auditor’s assessment.

Discuss proposed changes with finance and, where applicable, the auditor before changing the programme. Keep the records needed to support the agreed approach.

Carry the baseline forward carefully

After a full count, reconcile approved adjustments, pending movements and opening balances. A clean result can be undermined if an old import overwrites it or delayed transactions are posted twice.

Use a documented physical stocktaking procedure for preparation, coverage, movement control and sign-off. Then use recurring checks to assess whether the records remain reliable.

8. Pilot a Counting Programme You Can Maintain

Start with one stock area where discrepancies matter and the workload is manageable. It might contain fast movers, frequently mis-picked lines or critical production parts.

Barcode-enabled warehouse management illustration

Pilot the physical count, transaction reconciliation and investigation workflow together.

Establish the starting point

Confirm item codes, locations, stock units and unavailable inventory. Count the opening position under controlled conditions and reconcile it before the pilot starts.

Map the movements that affect the area: receipts, picks, dispatch, transfers, returns and adjustments. Identify events that are still recorded elsewhere or arrive late.

A connected inventory system can bring those transactions into an agreed record. Check existing software capabilities before deciding new development is necessary.

Use acceptance criteria tied to evidence

The pilot should demonstrate that:

  • Count tasks cover the agreed records and locations.
  • Counters identify stock and enter physical quantities correctly.
  • Movements around the count time reconcile to the result.
  • Significant variances receive an appropriate recount and investigation.
  • Approved adjustments retain their evidence and history.
  • Duplicate messages and delayed updates do not silently corrupt balances.
  • Unexpected stock found on the floor can be recorded and investigated.
  • Missed counts and overdue investigations remain visible.
  • Another trained person can operate the process.

Test a return, a partially received transfer, an open carton and a transaction pending during a count. These cases reveal more than a demonstration using perfectly prepared stock.

Review results before expanding

Measure first-count agreement, investigation effort, repeat discrepancies and staff time across several count cycles. Expand after correcting the process gaps the pilot reveals.

Keep required full counts in place while the evidence develops. A successful pilot should justify the next step, rather than promise that the whole warehouse will never need another stocktake.

Frequently Asked Questions

What is the best RGIS stocktake alternative?

It depends on the requirement. Another provider, an internal team or a hybrid arrangement can deliver physical counts. If the problem is unreliable records between counts, improve movement capture and recurring verification. The best solution may combine a counting service with inventory software.

Does RGIS only provide annual stocktakes?

No. RGIS advertises several approaches, including outsourced, hybrid, self-scan, targeted and cycle counts. Confirm the available service and scope for your location before comparing providers or changing the arrangement.

Do cycle counts replace an annual stocktake?

Not automatically. They can support ongoing verification and may allow a different counting approach where accepted. Coverage, control reliability and reporting or audit requirements determine what remains necessary. Agree changes before cancelling the full count.

Can an inventory system count stock by itself?

It calculates balances from recorded transactions. It does not prove what physically exists or capture every loss, damage event or handling mistake automatically. Physical checks and investigation remain part of maintaining reliable inventory.

Are cycle counts always cheaper than an external crew?

No. Count frequency, staffing, supervision, investigation and software costs affect the answer. External capacity can be valuable for large or complex counts. Compare complete approaches over the same scope and period.

Can we keep RGIS and improve our inventory system?

Yes. A counting provider can perform independent or recurring checks while your system maintains the movement history. Agree how results are imported, reconciled and approved so differences are investigated and balances are not overwritten incorrectly.

Should counts happen while the warehouse is working?

They can, where movements are controlled and reconciled. Some areas may need a temporary pause; others may use timestamped transactions. Counting during activity without those controls can create apparent discrepancies that are only timing differences.

Do we need custom software to run cycle counts?

Not necessarily. Existing inventory or warehouse software may provide suitable tasks, locations, history and approval functions. Configure and test those capabilities first. Consider custom development for a specific gap standard options do not address economically.

What should we bring to an initial review?

Bring a recent count report, examples of repeated variances, movement history, current count instructions and the costs of preparation and reconciliation. Include the reporting requirements the programme must support. Those records help identify whether the gap is labour, process or software.

How OpsMavix Can Help

OpsMavix builds custom inventory systems for businesses whose stock movements, count checks and investigations no longer fit their current tools.

We map where the record loses touch with the shelf, then assess whether configuration, integration or a focused custom build can close the gap. Physical counting can remain with your team or an external provider.

OpsMavix can help you:

  • Connect receipts, picks, dispatch, transfers and returns to agreed stock records.
  • Structure item codes, locations and stock units consistently.
  • Schedule count tasks and track coverage.
  • Reconcile counts to movements at an agreed time.
  • Record recounts, reason codes and adjustment approvals.
  • Make repeated variances and overdue investigations visible through operations reporting.
  • Pilot the process and document operation, access and handover.

If the same discrepancies return after each stocktake, book an Operations Leak Audit. Bring the last count report and one recurring stock problem. We will map where the record drifts, what the follow-up costs and which change should be tested first.

#Inventory Management#Stock Control#Stocktaking#Cycle Counting#Warehouse#Inventory Accuracy#Custom Systems

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.