Written by Chris Mitchem, founder of ShelfSpace and a former cannabis operator. Provider policies checked 11/06/2026.
Every cannabis company hits the same wall. The POS runs the store, Metrc runs compliance, QuickBooks or Xero runs the books, and the bank runs the money. Nothing connects them, so a person does: re-typing invoices, chasing receipts, building the same spreadsheet every Monday.
At some point someone says, “we should just build something.” Sometimes that’s right. Often it isn’t. This guide is for the owner, CFO or controller deciding which.
When off-the-shelf software is the right answer
Buy when a tool already does the job for cannabis and your process is close to everyone else’s. Point of sale, seed-to-sale tracking and standard accounting all have mature options. Building your own POS is almost never worth it.
A good test: if the vendor has cannabis customers who run the way you run, buy it and change your process to fit. Custom software you have to maintain forever is a real cost.
Four signs you need custom software
- The tool won’t move money for you. Expense apps, bill pay and spend tools often capture the data fine and then stop at the payment, because their banking partners screen out cannabis. Expensify’s help center lists marijuana-related businesses among those it can’t process direct payments for, and BILL’s acceptable use policy bars plant-touching businesses.
- You run several companies. Licenses usually mean separate legal entities with separate books. Most tools make you log in and out of each one. You want one screen, filtered by company, with each person seeing only the companies they work for.
- Your systems don’t talk. If a person copies data from Metrc or your POS into your books every week, that’s an integration waiting to be built.
- Your process is your edge. A consignment program, a credit policy or a rep commission plan that no product supports is worth building around, because it’s how you compete.
What makes cannabis software different
A developer who hasn’t built for cannabis will learn these on your project. Ask about each one up front.
- Metrc. Many states track every cannabis package in Metrc. A tool that reads transfers, sales or inventory needs Metrc access set up the way the state requires, and has to keep working when Metrc changes its API.
- Payments. Paying vendors, employees or yourself from a cannabis company’s account needs a bank and payment provider that accept the industry. Get that answered in writing before any code is written.
- Separate books for each license. Every expense, bill and payment has to land in the right entity’s books, with the right account and tracking category.
- 280E. Under section 280E, how you code costs affects your tax bill. Software should let your CPA set the accounts, not guess them.
- Access control. Cannabis companies have owners, managers, budtenders, sales reps and outside bookkeepers. Every one should see only what their job needs, with a second factor on anything that moves money.
Build from scratch, or extend a platform
There are three ways to get custom software, and they differ mostly in how much plumbing you pay for.
- Build from scratch with a general developer. You own every decision, and you pay for logins, permissions, hosting, the Metrc connection, the accounting sync and the payment rail before the first feature that’s actually yours.
- Hire a freelancer to glue tools together. Cheap to start, but the person who understands the glue often leaves, and the tools it connects change without warning.
- Extend a cannabis platform. Start from software that already handles payments, Metrc, Xero or QuickBooks, permissions and hosting, and build only what’s unique to you. You pay for less, and you get it sooner.
What to ask a developer before you sign
- Have you connected to Metrc, and in which states?
- How will this tool pay people, and which bank or payment provider has agreed to handle cannabis money?
- How does it handle several companies with separate books?
- Who hosts it, who fixes it at night, and who updates it when Metrc or our accounting software changes?
- Can we use a working piece before the whole thing is done?
An example: expense management across several companies
A multi-state operator we work with runs several companies, each on its own Xero. Mainstream expense apps either wouldn’t pay their employees back or made them switch between companies all day. Here’s what we’re building with them:
- Employees snap receipts from a phone and pick the company each expense belongs to.
- One approver per employee, then a final check on coding by finance.
- Approved reports post to the right company’s Xero as a bill, with the receipts attached.
- Employees are paid back by bank transfer from the company’s own account, and the payment is recorded on the bill.
- Every feature switches on per company and per person, so the AR team sees collections and not expenses.
The payment rail, the Xero connection and the permissions already existed. The project paid for the expense workflow itself. You can see the result on our expense reports page.
How we build custom software for cannabis companies
ShelfSpace started as a back office for cannabis money: accounts payable, collections and payments. Every custom project builds on that.
- Payments built in. E-checks, mailed checks and bank transfers from your own account, with approvals before anything is sent.
- Integrations built in. We’re a certified Metrc third-party vendor and connect to Xero, QuickBooks Online, Outlook and Gmail. See all integrations.
- Built in pieces. We agree a plain-English scope, then ship one working piece at a time so your team uses it while it’s still easy to change.
- Run by us. Hosting, security, two-factor sign-in, updates and support stay with us.