Custom software for licensed multi-location dispensaries and vertically integrated operators that need their POS, inventory, delivery, and state reporting workflows to agree. We start with the operational break causing the most duplicate entry or reconciliation work, then build a controlled integration around the systems you already use.
One event ledger showing what happened, what was submitted, what failed, and what needs review
POS and inventory integrations built around vendor API access and the exact events your license requires
Exception queues, retry controls, audit history, and role-based approvals for sensitive corrections
A first module scoped around one high-risk workflow before you expand across licenses or states
The problem
Sound familiar?
Does your operations team compare POS totals, physical inventory, and state records by hand after every close?
Do failed or delayed submissions surface hours later, without a clear owner or safe way to replay them?
Does each location handle returns, adjustments, transfers, and delivery inventory differently?
Short answer
Cannabis software development connects a licensed operator's sales, inventory, delivery, and compliance workflows. RaftLabs builds focused first modules in 10 to 14 weeks, with reconciliation and exception handling designed around each location's license rules. The first phase usually connects existing tools instead of replacing required state systems.
What is cannabis software development?
Cannabis software development is the design and build of operational software for licensed cannabis businesses. Sales, inventory, delivery, production, and regulatory records must stay aligned. For a multi-location operator, the most valuable custom layer is often an integration and control layer. It records each business event, validates it against approved rules, submits it to the right system, and makes failures visible to the person who can resolve them.
01 Diagnosis
Where cannabis operations software usually breaks
01
Problem
End-of-day totals require a spreadsheet investigation
Solution
The POS records completed sales, the inventory tool records stock movement, and the state system records regulated events. When those totals disagree, your system shows 50 units and Metrc shows 48, and an operations analyst exports three files to work backwards from the variance. One-way syncs make it worse: data flows to the state system but changes made there never come back, so the team chases mismatches forever. Small discrepancies flag audits with fines from $2,500 to $10,000. We build a shared event ledger that shows which system accepted each transaction and where the chain stopped. The result is reconciliation in minutes instead of a spreadsheet investigation after every close.
02
Problem
The register cannot go down on 4/20
Solution
Peak days expose every reliability gap. Leading dispensary platforms have crashed on 4/20 multiple years running, and when the register goes down, the line stops moving and the day's revenue walks out the door. You need a POS integration you never have to second guess. We design the integration layer for peak load from the start: bounded retries, graceful degradation when a vendor API stumbles, and offline capture that syncs when the connection returns. The result is a register that holds on the busiest day of the year.
03
Problem
Each location follows a different correction workflow
Solution
Multi-location operators often have the same policy on paper and different habits in practice. One manager records a return first in the POS. Another adjusts inventory first. A third sends the issue to compliance at close. Those differences create inconsistent records even when the underlying software works as designed. We make the approved sequence explicit: role-based steps, required reason codes, attachment capture, and approval thresholds turn corrections into a repeatable control, with a jurisdiction matrix keeping local rules separate. The result is one correction workflow across every location.
04
Problem
Payment workarounds disappear overnight
Solution
Cannabis operators are used to payment solutions that vanish after one compliance review: loosely coded merchant accounts pulled without warning, funds frozen while payroll hangs in the balance. What once passed as innovation is now a liability with a ticking clock. We build payment flows around methods that survive scrutiny: cash reconciliation workflows, cashless ATM integrations, and bank transfer where your banking relationship supports it, every one reconciled against the event ledger. The result is money movement you don't have to rethink every quarter.
02 What we ship
Focused cannabis operations modules
01
POS and inventory reconciliation
Connect the existing POS and inventory sources to a canonical transaction ledger. Match sales, returns, adjustments, discounts, taxes, and product identifiers across systems. Show differences by location, register, package, SKU, and business date, with a reviewer workflow for each exception. This is the right first module when close takes hours, unresolved variances roll into the next day, or the compliance team cannot trace a discrepancy to its originating transaction. The outcome is close without the spreadsheet.
02
Track-and-trace integration control
Translate approved operational events into the interface supported for the operator's program. Preserve source payloads, validation results, request history, destination responses, and replay decisions. Surface credentials, rate limits, API changes, and rejected records as operational work rather than silent logs. This is the right first module when staff enter the same event twice or learn about failed submissions only during a manual review. The outcome is submissions you can prove, not submissions you hope went through.
03
Inventory adjustment and transfer controls
Give every adjustment, waste event, transfer, and receiving exception an approved reason, supporting evidence, role, and status. Require review above operator-defined thresholds and keep the before-and-after values in the audit history. This is the right first module when location managers use inconsistent correction steps or the central team cannot see unresolved stock movements across the estate. The outcome is inventory the auditor can't argue with.
04
Ordering and delivery inventory workflow
Connect menu availability to reservations, pickup, dispatch, fulfillment, cancellation, and return states. Apply the operator's approved eligibility and limit rules at the relevant checkpoint, and retain evidence for staff decisions and overrides. This is the right first module when online orders reserve unavailable stock, delivery inventory is tracked separately, or store and delivery teams cannot agree on who owns an exception. The outcome is one inventory ledger for store and delivery.
03 Buy, build, or wait
The cannabis question is not whether you need software. It's what to keep, what to connect, and what to build around your license mix.
Keep or configure
The state track-and-trace system
Where the regulator requires it, you keep it. Custom software complements it; it never replaces it.
Your POS and inventory tools
If they support your jurisdictions and reconcile without manual work, keep them.
Off-the-shelf delivery tools
If the bolt-on covers your workflow, configure it.
Build custom
The integration layer
When the handoffs fail: duplicate entry, mismatched identifiers, spreadsheet reconciliation.
The exception workflow
Rejection handling, idempotent retry, and audit trails designed around your license rules.
The first control loop
One costly workflow, fully controlled, before expanding across licenses or states.
Bottom line
Keep the required systems. Build the layer that makes them agree.
04 How we work
How we scope and ship the first control loop
01
Verify access and map ownership
We confirm the relevant state program, license types, POS and inventory vendors, API permissions, environments, rate limits, and supported event operations. Then we create a field-level ownership matrix: which system originates each identifier, quantity, status, timestamp, and correction. The risk this retires: discovering mid-build that a required write operation was never available.
02
Define the event and exception model
We trace one workflow from the operator's first step through every connected record. The specification covers valid states, prohibited transitions, idempotency rules, retry classes, approval thresholds, reconciliation keys, and who owns each exception. Your compliance owner and legal counsel validate the regulatory interpretation. The risk this retires: building on an interpretation the regulator rejects.
03
Build against representative data
The first working increment proves the connector and event ledger before the broader interface is built. Tests cover normal events, duplicates, out-of-order updates, timeouts, invalid references, expired credentials, partial outages, and corrected records. The risk this retires: a ledger that works in demo and breaks on real data.
04
Run in parallel and reconcile
Before cutover, the new workflow runs beside the existing process for an agreed sample of locations or records. The team compares totals, inspects exceptions, rehearses credential failure and replay, and records sign-off against the acceptance criteria. Expansion happens only after the first license or location stays reconciled. The risk this retires: the cutover that corrupts the compliance record.
Trusted by
05 Planning bands
A credible starting scope
01
Complete operational workflow in the first release
1
02
Weeks for a standard first module
10-14
03
Recommended starting boundary before expansion
1 license
Relevant work you can inspect
Cannabis is a newer vertical for RaftLabs, so we do not present adjacent retail delivery as cannabis client proof. The relevant evidence is our ability to integrate an established POS estate, preserve offline operations, and reconcile multi-location data.
For a US fuel retailer, RaftLabs built a management platform that connected existing POS systems across 40+ locations without replacing them. A lightweight local utility stores data when a connection drops and synchronizes it later; the central system processed more than 20,000 transactions in a day during real-world testing. The project shipped in 16 weeks. Read the multi-location POS and inventory integration case study for the architecture, rollout, and measured results.
The overlap is specific: connecting location systems, handling unreliable connectivity, centralizing inventory and sales events, and giving operators one view of data quality. Cannabis license rules, state interfaces, and acceptance criteria would still require a separate discovery and validation process.
08 Why us
Why choose us?
01
We've seen your problem before
Across dozens of industries, we recognise your situation fast, then frame the fix around your margin and your operations, not a generic template.
02
We own the number, not the ticket
We measure success the way you do: hours saved, revenue earned, margin recovered. We stay through launch and growth, so the result is ours to own.
03
Serious businesses trust us
Vodafone, T-Mobile, Cisco, Energia, Aldi, Nike. Building since 2015. Serious businesses keep coming back because we stay accountable long after launch.
09 Questions
Common questions
No. Where a regulator requires a state track-and-trace system, custom software should complement it rather than claim to replace it. The custom layer can connect your POS, inventory, delivery, or ERP workflow to the approved interface, keep an event history, surface failed submissions, and reconcile your operational records with the state record. Your compliance owner remains responsible for validating the workflow against the rules for each license and jurisdiction.
Often, but feasibility depends on the POS vendor, the state program, available API permissions, and which transactions the interface supports. Discovery starts with an access check and an event map. We identify the system of record for each field, document supported reads and writes, and test one complete workflow in a sandbox or approved test environment before committing to a wider rollout.
Start with one workflow whose failures are costly and measurable, such as end-of-day sales reconciliation, inventory adjustment review, or delivery inventory control. A useful first version normally includes the source-system connector, an event ledger, validation rules, an exception queue, safe retry or replay controls, an audit history, and an operations dashboard. Customer loyalty and advanced analytics can wait until the core records agree.
Each business event receives a stable identifier and a recorded state, such as received, validated, submitted, accepted, rejected, or needs review. Idempotency rules prevent the same event from being applied twice. Bounded retries handle temporary failures, while permanent validation errors move to a human-owned exception queue. A scheduled reconciliation then compares operational totals with the destination record.
A standard first module with one core workflow and a few integrations typically takes 10 to 14 weeks. A broader platform with multiple modules, licenses, locations, and integration paths can take 20 to 28 weeks. We scope every project before pricing. Fixed cost, agreed before work starts. API access, migration volume, validation rules, and rollout constraints determine the actual scope.
Your licensed operator, compliance lead, and legal counsel own the interpretation and final acceptance of regulatory requirements. RaftLabs turns approved requirements into workflows, permissions, validations, logs, and test cases, then records acceptance evidence for each release. We do not treat a software integration as legal advice or assume that one state's workflow can be copied into another.
We integrate the payment methods your operation actually relies on: cash reconciliation workflows, cashless ATM integrations, and compliant bank-transfer options where your banking relationship supports them. We don't promise card processing workarounds that disappear after one compliance review. Every payment flow reconciles against the event ledger, so the books agree whether the money moved digitally or in cash.
Start with the workflow creating the most reconciliation work
Bring the systems involved, the jurisdiction and license types, and one month of representative exception examples. We will map the first shippable control loop and its acceptance criteria.
Scope and cost agreed before work starts. No surprises. No obligation.
Working prototype within 3 weeks of kickoff.
Pay by milestone. You see progress before each invoice.
60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
