Why stocktakes go wrong when systems are not aligned
Many South African SMEs still treat stocktaking as a once-off stock room event, then wonder why the numbers do not match the ledger. The issue is often not the count itself, but the way items are created, moved and adjusted during the rest of the month. If product codes are duplicated, units of measure are unclear, or goods are issued without a proper transaction trail, a count will only expose the mess.
We often see this in wholesalers, parts distributors and light manufacturers that operate from Centurion, the East Rand or Durban. A pallet is received, split into cases, then into singles, but the system still shows one stock code in three different ways. By the time the team starts counting, nobody is sure whether the physical count, the bin card or the ERP should be trusted.
The fix starts long before stocktake day. Stock records need one owner, clean naming rules, correct units and a process for every movement from receiving to dispatch. If those basics are in place, the count becomes a check on reality rather than a guessing game.
Build stocktake rules into the ERP before count day
Good stocktakes are planned in the system, not added at the end. That means setting clear cut-off times, defining which locations are included, and making sure all open transactions are either completed or flagged before the count begins. Without that discipline, the warehouse team counts one reality while finance closes another.
For SMEs in Johannesburg or Pretoria, this matters even more when multiple branches share inventory. One branch may hold emergency stock, another may handle repairs and a third may dispatch to customers. If transfers are not captured properly, the same item can appear in two places at once. That causes delays, extra write-offs and avoidable questions from management.
- Freeze movements at a set time and communicate it clearly to receiving, dispatch and sales teams.
- Use location codes for each store, cage, yard or satellite depot.
- Mark damaged, reserved and quarantined stock separately.
- Match counting sheets or mobile count screens to the exact item master in the ERP.
- Set approval rules for adjustments above a defined Rand value.
Make the warehouse count faster, even during load-shedding
Counting slows down when the team is tired, screens go dark during load-shedding, or labels are hard to read under warehouse lighting. In practice, a good stocktake process has to work with the realities of South African operations. That means offline-friendly devices where possible, printed backup count sheets and a clear escalation path when power or network access drops out.
In a Cape Town cold store or a Gqeberha parts warehouse, humidity and salt air can also affect labels, scanners and handheld devices. If barcodes fade or labels peel, the count becomes slower and less accurate. Choose durable labelling, keep spare batteries on charge and test the count process before the actual weekend or month-end.
It also helps to split the stocktake into zones. One team counts, another checks, and a supervisor resolves differences on the spot. That is far better than doing a full count first and trying to fix every issue later in a back office with no context.
Clean master data makes the biggest difference
Stocktake accuracy depends on the quality of the item master. If one product has three codes, or if one box is counted in metres on one report and units on another, the system will never give a reliable answer. This is where item descriptions, units of measure and pack sizes need proper attention.
A practical stock master should make it easy for staff to recognise the item, count it correctly and post the result without confusion. That does not require complicated software. It requires disciplined setup and a review of how the business actually buys, stores and sells goods.
- Standardise descriptions so the same item is called the same thing in every branch.
- Remove duplicate codes and obsolete products from active lists.
- Confirm pack sizes, conversions and minimum stock levels.
- Separate stock items from non-stock items such as consumables and spares.
- Check that stock valuation rules match how the business operates.
Once the master data is tidy, cycle counts become more useful too. Small monthly checks then catch errors early, instead of leaving a major correction for year-end.
A local example from a multi-branch SME
Consider a Centurion-based distributor supplying sites in Pretoria, the East Rand and Durban. Before tightening its process, each branch counted stock differently. One team used handwritten sheets, another used spreadsheets and a third made adjustments at the end of the month with limited checks. The finance team spent days reconciling variances and customers sometimes waited while stock was being “found”.
After aligning ERP setup, transfer rules and count procedures, the business changed three things. First, every branch used the same item codes and units. Second, all inter-branch transfers were processed before stocktake time. Third, managers received a variance report showing only the items that needed review. The result was not perfect magic, just a lot less noise. They finished counts faster and had fewer surprises when reporting stock values.
That kind of improvement is realistic for many SMEs. It does not require a full system replacement. It needs better process mapping, proper integration between the warehouse and finance functions, and support from people who understand how local operations actually run.
What to review after the count is done
The stocktake is not complete when the last item is counted. The real value comes from reviewing the exceptions and fixing the root cause. If the same line item keeps showing a shortage, the issue may be theft, mis-picks, receiving errors or incorrect unit setup. If multiple branches show the same type of variance, the problem is probably process related rather than isolated.
Post-count review should be structured and practical. Do not just approve adjustments and move on. Look for patterns that can be removed before the next cycle.
- Compare variance by location, category and counter.
- Check whether high-value items were counted twice or missed.
- Review goods received notes, dispatch records and transfer documents.
- Measure how long the count took and where delays happened.
- Log corrective actions so the same issue does not return next quarter.
When that follow-up becomes routine, stocktake stops being a painful event and becomes a useful management tool. That is where ERP, reporting and training work together.
How Bizmatics supports stocktake readiness
Bizmatics helps SMEs prepare stock processes that fit their operations, from the first process map through to training and go-live support. The work can include ERP implementation, data migration, system integration, custom reporting and workflow automation. For businesses with teams in Johannesburg, Pretoria, Durban, Cape Town, Gqeberha or across the West Rand and East Rand, the goal is the same: make sure the system reflects what is happening on the floor.
We also support upgrade planning, system audits and support retainers for businesses that want ongoing help after the first project. That is especially useful for companies with seasonal counts, multiple branches or frequent stock movement between sites. If the process is clear and the data is clean, stocktake becomes easier to manage and easier to trust.
In practice, that means fewer corrections, better decision-making and less time spent arguing over numbers. And for a busy SME, that is worth a lot more than a pretty report.
