Identify the package.
Capture source, package, manifest, quantity and product measurements. Review discrepancies before the stock becomes eligible for sale.
THE CANNABIS SOFTWARE SUITEBuilt around the detail
Built around the detail
that cannabis demands.
A dispensary workflow needs more than a retail item and a quantity. Our software is designed around the customer, the license, the package and the records behind each transaction.
Discuss your operating requirements ↗FROM RECEIVING TO RECONCILIATION
Follow the product.
Preserve the context.
A connected workflow brings receiving, inventory control, checkout and reconciliation into one operating model, with the package and customer context carried through each step.
Know what can move.
Separate selling stock, backstock, holds and quarantine. Preserve the source and destination of each movement.
Apply the context.
Evaluate the customer, license, product quantities, taxes and configured transaction checks before completion.
Explain the result.
Connect sales, returns and adjustments to the package trail. Make pending reporting and unresolved exceptions visible.
PACKAGE INVENTORY
A SKU describes the item.
A package tells its story.
The product model separates merchandise identity from regulated inventory identity. Staff can understand the product a shopper wants while retaining the package and quantity behind the sale.
- Multiple packages associated with one retail product
- Weight, potency, serving and testing information
- Package-aware sales, returns and adjustments
- Quarantine, waste and documented disposition
- Count sessions and reviewed variance resolution
ILLUSTRATIVE DATA RELATIONSHIP
01
Retail product
Name, brand, type, description and selling presentation.
02
Package or batch
Source identity, measurements, status and remaining quantity.
03
Inventory event
Receiving, transfer, sale, return, hold or disposition.
04
Reviewable record
Who acted, what changed, why and what remains unresolved.
CUSTOMERS, RULES & REPORTING
Clear checkpoints.
Before the handoff.
Medical and adult-use requirements differ. Configure those differences explicitly in the operating rules and validate them for each installation.
Arrival & eligibility
Scan-assisted check-in, expired-document handling, patient and caregiver relationships, and a service queue that carries useful context into the sale.
Explore check-in →Transaction guardrails
License-aware limits, equivalency calculations, product and customer tax treatment, and consistent checks across supported ordering channels.
Explore rules & taxes →Labels & accountability
Package-aware product and exit labels, printer configuration, reprint history, and a retained explanation of inventory and transaction events.
Explore labels →Reporting & exceptions
A reporting workflow with submission history, pending states, acknowledgments, retries and staff review of discrepancies. External connections require separate authorization and verification.
Explore integration scope →PAYBOTX does not claim an active connection to a state tracking system, regulatory certification or approval. No software description on this site guarantees legal compliance or permission to operate in a particular market.
COMMON QUESTIONS
Know what you’re evaluating.
What is included in the cannabis software suite?
The product overview covers check-in, patient and caregiver workflows, package inventory, purchase rules, taxes, labels, customer engagement, online ordering and reporting. Your walkthrough confirms feature availability, selected modules and rollout scope for your installation.
Does this site claim a regulatory integration?
No active state-system connection, certification or regulatory approval is claimed. External connections are separately authorized and verified for each deployment.
Can the software be configured for medical and adult-use retail?
The product suite addresses medical and adult-use operating models. Patient, caregiver, license, inventory and transaction requirements are configured and validated for the actual deployment.
Are cannabis payments live in the demonstrations?
No. Reference environments use simulated payment flows. Live acceptance depends on an approved provider, the merchant’s business and products, a completed integration and verified settlement behavior.
Can we discuss our state and license requirements?
Yes. Include your market, store type and operating priorities in a demo request. Do not upload customer identity documents, medical records or sensitive credentials.
LET’S TALK ABOUT YOUR STORE
A better next step
starts with your workflow.
Bring your product mix, operating requirements and growth plans. We’ll build the walkthrough around you.