Skip to content
← BlogPlatform

Cannabis POS platforms aren't built for South Africa

3 min read
Share

Search "cannabis POS software" and the same names come up regardless of where you are: Dutchie, Flowhub, Cova, Treez, BLAZE. They are real, well-funded platforms running thousands of stores. They are also, without exception, built for the United States and Canada - and that isn't a small detail a South African store can work around.

What these systems are actually built for

Seed-to-sale tracking is the core of nearly every major cannabis POS, and it exists because US states and Canadian provinces legally require it - reporting every plant and product to a state system like METRC or BioTrack from cultivation through to the till. That compliance engine is the product. Everything else - the till, the reporting, the loyalty program - is built around feeding that system correctly.

South Africa has no METRC. It has no BioTrack. A platform built to report to a system that doesn't apply here isn't offering a lighter version of compliance - it's offering compliance machinery aimed at the wrong regulator, for rules that were never the ones a South African store actually has to follow.

Why that gap actually bites

  • POPIA governs how customer and ID data gets handled here - a US-built platform's compliance features are aimed at state cannabis boards, not South Africa's data protection law
  • Sequential, SARS-compliant invoice numbering is a local requirement a system built around US sales tax reporting has no reason to have thought about
  • Weight-based flower pricing alongside unit-based products is standard here, and doesn't map cleanly onto systems built primarily around unit-tracked inventory for state reporting
  • Vendor consignment, common in South African cannabis retail, isn't a workflow US dispensary POS platforms are generally built around at all - most licensed US operators buy stock outright rather than running it on consignment

None of that means these platforms are badly built. It means they were built to solve a specific country's legal problem, and a South African store adopting one inherits software aimed at a regulator it doesn't answer to - while still having to handle POPIA, SARS invoicing, and consignment manually, on the side, because the platform was never going to do it for them.

Patterns that show up even inside their own market

Independent of the South Africa question, comparison sites and review platforms surface the same recurring complaints about the big names. Dutchie has had documented outages on 4/20 - the single busiest day in the industry - in both 2023 and 2024. Reviewers on G2 cite Flowhub's manual reporting workflows and slower support response times, and Treez users report the platform feeling heavy and complex to configure for smaller operations. These are the kind of patterns that show up when a platform is built to serve very large, high-volume operators first.

What a store actually needs instead

Not a smaller version of a US platform - a system built around the rules a South African store actually operates under from the start. POPIA-aligned data handling, sequential SARS-compliant invoicing, weight and unit pricing in the same catalogue, and consignment tracking as a first-class workflow rather than an afterthought nobody bothered to build, because the market it was built for never needed it.

That's the actual argument for switching away from a system built for someone else's regulator - not a longer feature list, but one built to answer to the right one from day one.

Related reading

See how Budstack handles this

Fifteen minutes, a walkthrough of the platform, and a number scoped to the stores you actually run.