Start with item and location data
Choose a consistent internal item identifier and map existing supplier or retail barcodes to it. Record the unit each code represents. A carton containing several units needs an explicit mapping, not a picker guessing the pack size.
Label locations using a structure staff can follow. Test whether workers can distinguish neighbouring bins and scan a label from a practical working position. Keep a controlled process for replacing damaged labels and retiring old codes.
Distinguish internal labels from trading identifiers
Internal bin and task labels are different from identifiers required by retailers or supply-chain partners. Confirm external barcode requirements with the relevant trading partner and use GS1 South Africa guidance where GS1 identifiers are needed.
Do not assume that creating a barcode image registers a product identifier. Keep a record of who owns each code range and how item changes are approved. The software and label printer should use the same mapping.
Test the transaction, not just the scanner
A scanner behaving like a keyboard can enter a code without validating whether the action is allowed. Define the required item, location, unit and quantity for the transaction, then decide what the interface does when they do not match.
Test duplicate scans, empty labels, damaged codes and dropped connections. Verify that a retry cannot silently create a second receipt or dispatch. Give staff an exception route that records the issue rather than encouraging an undocumented bypass.
Pilot one bounded workflow
Choose one receiving lane or picking zone and agree acceptance checks before rollout. Train operators on normal tasks and exceptions, then reconcile the physical goods against the recorded movements. Keep unresolved discrepancies visible during the pilot.
Ask the Pika WMS team to review current scanning capabilities with your devices and labels. Device compatibility, offline behaviour and printing should be demonstrated, not inferred from a generic feature name. Expand only after the pilot meets your agreed criteria.
Useful questions
Can I use this checklist to evaluate Pika WMS?
Yes. Use the same requirements and acceptance scenarios for Pika WMS and other shortlisted systems. Confirm available functions, deployment, pricing and support directly with the supplier.
Do you offer warehouse software discussions for Johannesburg, Kempton Park and Cape Town?
Yes. Contact PCube for a remote Pika WMS walkthrough and requirements discussion for these service areas and elsewhere in South Africa. No local office or on-site support entitlement is implied.
Sources and further reading
Reuse and attribution
Reuse the original blank PCube evaluation checklist under CC BY 4.0 with attribution and a note of changes. Third-party documentation, product names and linked provider content are excluded.
Suggested citation: PCube Innovations editorial. “Barcode stock control for South African warehouses: a practical rollout guide”. Updated 17 October 2026. https://pcubesolution.com/blog/warehouse-barcode-stock-control-guide.
