Cannabis Dispensary Software: When Dutchie and Flowhub Are Enough and When They Stop
The threshold is five locations or a second state, and it moves earlier if you weigh flower by hand at volume.
On this page
The threshold is five locations or a second state, and it moves earlier if you weigh flower by hand at volume. One to three stores in one state selling packaged product and prepackaged eighths, no delivery, under roughly six million dollars in revenue: buy Dutchie, Flowhub, Treez or Cova and stop reading. The honest test above that is arithmetic rather than store count. If reconciliation, oversells and limit violations cost you more than $150,000 a year, a build pays back inside two years.
When is off the shelf genuinely the right call here?
Buy, and here is which one. Dutchie, Flowhub, Treez and Cova are real products built by people who understand this industry. At one to three stores in a single state, selling packaged product and prepackaged eighths with no delivery, the per store subscription is genuinely cheaper than an engineer and any of them will hold. Anyone telling you to build at three stores is selling you something.
Buy if your pain is presentation or messaging rather than inventory truth. Jane and Weedmaps are established at menus and ordering, Alpine IQ and springbig are established at loyalty and text messaging, and a custom version of either returns very little. Keep them whatever else you decide, because integrating is much cheaper than rebuilding.
Keep LeafLink or Distru on the wholesale side and your accounting package at the end of the month. None of those is where the losses sit.
There is a fourth case worth naming, and it is a stop rather than a buy. Nothing you build replaces the state track and trace system. You report to it, and any scope that suggests otherwise should be caught before it reaches a quote.
When does a custom build actually pay off?
Build when you are paying people to compensate for software every week. Five triggers, and three together makes the case.
The first is silent reporting failure. Packaged systems post sales receipts to the state in a background job, and when the state application programming interface is slow or rejects a receipt because a package was finished minutes earlier at another register, most of them log it and move on. You discover it three weeks later, when the fix requires a package adjustment with a reason code and a story nobody remembers.
The second is the Sunday night spreadsheet. Joining a state Active Packages export against a point of sale (POS) on hand report in Excel is a permanent labour line that does not shrink as you add stores.
The third is limits across locations. The limits are per person per day in equivalency, and packaged platforms enforce the cart in front of them. A customer who buys at your first store at noon and your second at six has been checked twice and constrained once.
The fourth is deli style weighing at volume, where tare drift, rounding in the customer's favour and jars that arrived light are invisible until the jar closes out.
The fifth is roadmap. You asked your vendor for cross store limit enforcement or a real exception queue and it has been on the roadmap for four quarters. At that point you are paying a subscription to wait.
How do they compare on the things that matter in this industry?
Failure handling. This is the difference that matters most and it is invisible in a demonstration. A packaged platform's reporting queue is shared across thousands of licensees and its support tier will not reprocess your specific Friday. A build treats the state system as an unreliable downstream on purpose: a durable outbox with idempotency keys per receipt, backoff, and a human facing exception queue carrying the original cart, the budtender, the register and the timestamp. On top of that, a nightly job diffs quantity by tag against your ledger and ranks the variance by dollar value before anyone opens a spreadsheet.
Identity and limits. A build resolves identity at the door, stores a hashed key rather than the raw document, and writes every sale to one rolling daily equivalency ledger all locations read from. The budtender sees remaining headroom before the item enters the cart, and every check is logged, so when the state asks how you enforce, you show the ledger instead of a policy document.
Inventory as a balance. Menus on Jane, Weedmaps and Leafly pull availability on a schedule, so between synchronisations the last two carts sell in store and three online orders arrive for them. On hand minus reserved equals available, with reservations created at cart and released on abandonment, is boring and it works.
Weigh events and tax ordering. Generic inventory has no concept of a weigh event, and generic tax engines are a handful of toggles rather than a rules table with jurisdiction, effective date, base, ordering and rounding.
What does total cost of ownership look like at your scale?
Three lines describe your current position and only the first is a subscription.
Line one is what you pay now: point of sale per store, ecommerce, loyalty and reporting. It is the smaller half. Line two is labour, meaning the hours per week your inventory manager spends reconciling, multiplied by loaded cost, per state, treated as permanent because it does not decline as you add stores. Line three is what the gaps cost: write offs from jar variance nobody could attribute, oversells that produce refunds and reviews, and limit exposure from a customer who cleared a limit twice in a day across two of your stores.
On the build side, a focused first release covering point of sale, state integration with a durable outbox and nightly reconciliation, cross location purchase limits and inventory as a single source of truth runs $60,000 to $130,000 over 12 to 16 weeks in Digital Heroes delivery experience. A full platform adding ecommerce and channel availability, delivery manifests and a driver application, purchasing and receiving, payments, loyalty integration and reporting runs $150,000 to $400,000 phased over 6 to 12 months.
An eight store single state operator with deli weighing lands at about $126,000 for the first release and roughly $328,000 across both phases. Offline register mode is about $34,000 of that and it is the item teams most often assume is trivial. History migration with tags preserved is about $20,000 and a two to three week workstream.
Afterwards budget 18 to 25 percent of build cost a year, so $59,000 to $82,000, because state rules, tax rates and traceability interfaces all move on someone else's schedule. Add hardware replacement and the internal time of whoever works the exception queue daily. That role changes from reconciling to reviewing, which is the point, but it is not zero.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. In retail cannabis the hybrid is usually about which parts of the stack you keep rather than which vendor you replace.
The split most operators land on keeps Jane or Weedmaps for menu presence, Alpine IQ or springbig for loyalty and messaging, LeafLink for wholesale, and your accounting package for the ledger. You build the inventory service, the state outbox and reconciliation, the cross location limit ledger and the register itself, because those four are where truth and liability sit and none of them is a differentiator anyone will sell you.
Inside that there is a sequencing hybrid that saves real money. Take one state in phase one even if you already operate in two, and prove the outbox, the reconciliation and the limit ledger against a single traceability system before doubling the surface area. Defer delivery, which is a whole operation rather than a feature and can continue on a spreadsheet and a phone for another two quarters.
Defer offline register mode too, if your connectivity is reliable and you can add a wired fallback. Buy a second internet connection before you buy conflict resolution engineering, because the second connection is dramatically cheaper and it solves the same problem for most operators.
And migrate a shorter history. Bring across enough for audit resolution and reporting continuity, keep the old system readable for the remainder of its retention period, and put the saving into the pilot instead.
Which should you choose, by operator size and stage?
One to three stores, one state, packaged product only. Buy Dutchie, Flowhub, Treez or Cova and put the money into product and staff. The subscription is cheaper than an engineer and the products are good.
Four stores, one state, starting to feel the reconciliation load. Stay bought, and measure. Count the hours per week spent joining a state export against an on hand report, count your unattributed jar variance for a quarter, and ask your vendor in writing for cross store limit enforcement. Those three numbers make the decision for you within a quarter.
Five or more stores, one state, deli weighing at volume. This is the crossover. Build the focused first release at $60,000 to $130,000, pilot at one store for two to four weeks running parallel on read only reconciliation, then convert store by store. A bad cutover during a weekend rush is a revenue event.
Two or more states, delivery, or vertical integration. Build the full platform and expect the upper end, because every additional traceability system is a new integration rather than a configuration flag and vertical seams are where inventory dies. Sequence offline mode late, once online reconciliation is proven and boring.
The question that separates the two routes is not which point of sale is best. It is which parts of your operation nobody else's software can ever know about. Those parts are your build, and everything else you should keep renting.
When the shortlist is down to two and you need a tiebreaker, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Global retail loses an estimated $1.73 trillion annually to inventory distortion (out-of-stocks and overstocks), equal to about 6.5% of global retail sales, despite $172 billion spent on improvements in the past year. Source: IHL Group (2025) →
- U.S. retailers lost an average of 1.6% of sales to shrink in FY2022 (up from 1.4% the prior year), equating to $112.1 billion in inventory losses - the benchmark case for POS-integrated loss prevention and inventory accuracy. Source: National Retail Federation (NRF) (2023) →
- Per the Standish Group CHAOS 2020 report (reviewed at this URL), across tens of thousands of software projects roughly 31% end successfully, about 50% are 'challenged', and roughly 19% fail outright; small projects succeed far more often than large ones, and Agile approaches succeed at markedly higher rates than Waterfall. Source: The Standish Group (2020) →
- In an October 2025 survey of 530 small-business employers (conducted by TechnoMetrica, October 3-9, 2025), 88% reported using AI tools and 73% said those tools had been important to their competitiveness and growth over the past year, with 60% citing efficiency and productivity as the primary motivation for adoption (42% cited improving customer service). Source: Small Business & Entrepreneurship Council (SBE Council) (2025) →
Frequently asked questions
What does it cost to switch off Dutchie or Flowhub?
Around $20,000 for the migration workstream itself, typically two to three weeks, covering sales history, package tags, customer records and loyalty balances with the traceability tag preserved as the join key so historical audits still resolve against state records.
The riskiest data is not sales history. It is open packages and partially depleted deli jars, which need a physical count at the moment of switch, so budget staff hours per store rather than assuming it fits inside a shift.
What happens if our point of sale vendor raises prices or changes its terms?
Per store pricing means your own expansion raises the bill, so model the figure at your planned store count rather than your current one before signing.
The more useful protection is structural. If you keep Jane, Alpine IQ and your accounting package as integrations rather than dependencies, and the inventory and reporting truth sits in something you own, a vendor change becomes a negotiation about one component. That is where the bargaining power actually comes from.
How long does a dispensary software build and rollout take?
Twelve to sixteen weeks for a first release, and rollout is a separate calendar. Pilot at one store for two to four weeks running parallel on read only reconciliation, then convert store by store rather than all at once.
Full conversion for an eight to ten location operator typically spans another six to ten weeks of staged cutovers, evenings and weekends, with staff support at each one and a physical count of open jars at every switch.
Is Treez enough for a six store operator?
For the counter, the menu and day to day retail operations, it is competent and many six store operators run on it happily. Where packaged platforms stop is failure handling and cross location identity.
Their reporting queue is shared across thousands of licensees, so a rejected receipt on a busy Friday becomes your problem three weeks later, and they enforce the cart in front of them rather than a rolling daily equivalency ledger across your stores. If those two are what is costing you, the answer is a build rather than a different subscription.
What does offline register mode actually cost?
Around $34,000 in our worked example, and it is the item teams most often assume is a checkbox. The cost is not caching a menu, it is conflict resolution: deciding what happens when two disconnected registers each sold the last of a package and the state ledger has to be told a coherent story afterwards.
If your stores have reliable connectivity, buy a second internet connection first. It is dramatically cheaper than the engineering and it solves the same problem for most operators.
Why does cross store purchase limit enforcement need a custom build?
Because the limits are per person per day in equivalency rather than per transaction, and packaged platforms are built for single store licensees where checking the cart is sufficient. Most vendors will not add a cross location identity ledger because it creates liability for them.
Building it is about $18,000 in our worked example: hash the identity from the identification scan, never store the raw document, and write every sale to one rolling ledger every location reads before the item enters the cart.
Does deli style weighing justify a build on its own?
For some operators, yes. Generic inventory has no concept of the weigh event, so tare drift, rounding in the customer's favour and jars that arrived light stay invisible until the jar closes out.
At about $16,000 in the worked example, scale integration writing gross, tare and net per transaction against the register, the budtender and the jar's tag pays back quickly at volume. The visible result is variance per jar per shift, which surfaces a consistent overpour pattern in week one rather than in the third quarter.
What is the cheapest credible version of this system?
Around $60,000 for a five store single state operator taking the inventory service, the state outbox and reconciliation, and the limit ledger, with the register kept on the incumbent product for a first phase and delivery, offline mode and migration deferred.
Be sceptical of a cheaper quote from anyone who conflates a state package with a stock keeping unit when asked to draw the data model. That single mistake costs a rebuild, and it is the fastest way to tell whether a developer has shipped in this category.
What does it cost to maintain a custom POS after it launches?
Budget 15 to 20 percent of the original build cost per year, so a $100,000 system runs $15,000 to $20,000 annually for hosting, OS and payment SDK updates, security patches, and small feature changes. Digital Heroes structures this as a monthly retainer for most POS clients, commonly $1,000 to $3,000 depending on location count. For multi-location operators that figure usually still undercuts the per-terminal subscription fees they were paying before.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
How do I vet a development agency for a POS project specifically?
Ask to see a live POS or payments product they built, then ask exactly how they handled offline mode, receipt printing, and PCI scope, because those three areas expose anyone who has only built ordinary web apps. A competent agency will name the payment SDKs they used, such as Stripe Terminal or Adyen, and describe their terminal certification process without checking notes. If the portfolio is all marketing sites and dashboards, keep looking.
How do I calculate the payback period on a custom POS?
Add up what you pay per year today: subscription fees per terminal, add-on modules, and the gap between your effective processing rate and an interchange-plus rate, then divide the build cost by that total. A retail group paying $60,000 a year in fees and processing markup against a $150,000 build pays back in 2.5 years, before counting labor saved by workflows designed for your operation. Digital Heroes models 2 to 4 year payback for most multi-location operators and advises against building when the model shows longer.
We run multiple restaurant locations on Toast. Would switching to a custom POS actually save money?
Usually only at 8 or more locations, where per-terminal software fees, add-on modules like online ordering and loyalty, and processing markup commonly total $8,000 to $20,000 per location per year in the statements Digital Heroes reviews for restaurant groups. A custom system converts that into a one-time build of $100,000 to $250,000 plus maintenance, which models out to 18 to 30 month payback for most groups. Under five locations, stay on Toast and put the money into operations.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
Who can build a custom POS software system?
Digital Heroes builds custom POS software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other POS software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Zoe.
Senior Brand Designer · New-york · 8 posts on the site
Published · Last updated .
