Start With a Stock Policy People Can Actually Use
A stock policy should tell staff exactly what happens from the moment goods arrive to the moment they leave site. Keep it short, practical and written for the people doing the work in warehouses, stores and branches across places like Centurion, Johannesburg and Durban. If the rules are easy to follow, they are easier to enforce.
Set the basics first: who may receive stock, who may adjust quantities, who signs off write-offs and who checks variances. In many SMEs the problem is not the system itself, it is that everyone uses it differently. A simple written policy reduces that risk and makes audits far easier later on.
- Define one item code per product, size or pack where needed
- Set approval levels for purchases, transfers and write-offs
- Agree on cut-off times for daily processing
- Keep physical stock areas labelled the same way as the system
Set Up Item Master Data Before You Count a Single Box
Good stock control starts with clean master data. If item names, units of measure and locations are messy, every count will be off. A bottle can be captured as units, packs or cartons and suddenly nobody can trust the numbers. That is how small errors turn into costly shortages or excess stock.
Check that each item has the right description, supplier code, reorder level and unit of measure. If you trade across the East Rand, West Rand, Cape Town or Gqeberha, make sure branch naming is consistent as well. One site should not be calling the same location by three different names.
- Use one naming standard for products and locations
- Match units of measure to how stock is actually stored and sold
- Remove duplicate items and inactive records
- Review reorder points against actual monthly movement
Use Receiving Rules to Stop Errors at the Gate
Most stock issues start at receiving. If goods are booked in without checking quantities, batch details or damage the system will carry the mistake forward. A proper receiving process should compare the delivery note, purchase order and actual goods before anything is posted. This matters even more when deliveries arrive during power cuts or after-hours handover, because attention drops fast.
Train staff to reject short deliveries, note damaged cartons and record variances immediately. Keep a simple exception log so recurring supplier problems can be traced. In coastal areas such as Durban and Cape Town, storage conditions matter too, especially for items affected by humidity, rust or packaging damage.
- Count and inspect every delivery before posting
- Record shortages, overages and damaged items on the spot
- Separate quarantined stock from saleable stock
- Keep proof of sign-off for disputed deliveries
Count Stock Often Enough to Trust the Numbers
Annual counts are not enough for an SME that wants proper control. Cycle counts work better because they keep attention on high-value or fast-moving items throughout the year. A business in Pretoria or Centurion with multiple branches should count the busiest categories more often, while slower items can be checked less frequently.
Count by location, not by memory. Use one team to count and another to verify where possible. If the same person receives, stores and counts stock, the risk of missed differences goes up. Keep the count sheets simple and force a reason code for every adjustment. That makes it easier to spot patterns such as theft, breakage or poor recording.
- Count fast-moving and high-value items weekly or monthly
- Use blind counts where staff do not see expected quantities
- Investigate variances above a set Rand value
- Lock system edits during the count window
Link Stock, Sales and Purchasing So Work Flows in One Direction
If sales, purchasing and stock are run in separate silos, the same item can be bought twice, sold before it is available or written off too late. Integration helps when the order, receipt, issue and invoice all speak to one another. This is useful for SMEs that handle branches, field teams or project-based work.
Set clear triggers for replenishment, transfers and dispatch. For example, a reorder can be triggered when stock falls below an agreed point, while sales orders should reduce available stock immediately. Good integration also helps when teams work from different towns or during load-shedding because managers can still see what is on hand and what is committed.
For stronger discipline, make sure these rules are followed:
- Sales orders reduce available stock at capture
- Purchases update expected arrivals and supplier lead times
- Transfers show both source and destination locations
- Credit notes and returns are matched to the original transaction
Use Reports That Flag Action, Not Just Numbers
Stock reports should help managers make decisions not fill folders. Focus on ageing, slow movers, negative stock, variance history and gross margin by product group. A monthly report pack should tell you what to buy, what to stop buying and where controls are weak. If a report does not lead to action, it is just noise.
Ask for reports that are easy to read at branch level and at head office. A business in Johannesburg may need one view for warehouse control and another for branch replenishment. Keep the number of reports manageable so managers actually review them every month, not only at year end.
- Slow-moving stock older than 90 days
- Negative stock and backdated adjustments
- Top variance items by value and by count
- Stock ageing by branch or storage site
Build a Simple Response Plan for Problems Before They Grow
Even with good controls, stock problems will happen. The value is in how quickly they are identified and corrected. Create a short response plan for missing stock, supplier disputes, damaged goods, system errors and failed imports. Staff should know who to call, what evidence to keep and when to stop the transaction.
For SMEs in South Africa, practical support matters during month-end, power interruptions and peak trading periods. A written response plan keeps the team focused and reduces guesswork. It also makes it easier to onboard new staff, especially when the business is growing across regions.
Keep the plan simple:
- Log the issue immediately with date, site and item code
- Freeze related adjustments until checked
- Review the root cause and fix the process, not just the number
- Update training if the same problem happens again
