Clear authority. Accountable records.
Review Blackleaf Point of Sale security and compliance planning, including staff permissions, customer consent, reporting, and deployment readiness.
Development preview · Availability and deployment scope confirmed for your store.
Put authority where the work belongs.
The intended permission model separates locations, roles, and actions. A budtender may need an order; a buyer may need inventory; a manager may need to approve a change. The deployment review should cover viewing, editing, exports, and approval authority.
- Review the same workflow using each staff role.
- Keep customer reassignment, discounts, inventory corrections, and exports accountable.
- Distinguish proposed, approved, and executed agent actions.
Keep evidence behind important changes.
A completed sale and an accepted reporting submission are separate events. The planned reporting workflow needs visible submission status, correction handling, and reconciliation for the specific jurisdiction. Initial rollout is planned around California; live coverage is individually confirmed.
| Area | Evidence to request |
|---|---|
| Regulatory reporting | Jurisdiction, supported submissions, rejection handling, and reconciliation. |
| Customer data | Access, retention, export, deletion handling, and consent records. |
| Recovery | Backup and restore process, outage scope, and tested recovery procedures. |
| Payments | Provider responsibilities, supported tender, and transaction exception handling. |
Agree the operating responsibilities before launch.
Review incident contacts, support coverage, data access, and recovery responsibilities with the store. The preview does not establish live Metrc coverage, production offline settlement, a security certification, or guaranteed regulatory compliance. Those require specific implementation and evidence.
Questions worth asking.
Clear answers for planning your store’s next step.
Will AI change prices, place orders, or contact customers without approval?
The intended model gives each store control over authority. Agents prepare the work against store-defined budgets, margins, audiences, and permissions. Purchases, price changes, outreach, and publishing require the appropriate approval before execution. Supported automation rules and approval controls must be confirmed for the deployment; a draft is not an executed action.
Does Blackleaf Dispensary POS integrate with Metrc?
Metrc reporting is part of the planned POS workflow. The current preview does not establish a live production Metrc integration. State-specific reporting, credentials, submissions, corrections, and reconciliation must be implemented and validated before activation. Confirm current coverage with Blackleaf Dispensary POS for your licensed location.
Which states will Blackleaf Dispensary POS support?
The initial rollout is planned around California. Additional state coverage has not been announced here. A store’s jurisdiction, license type, reporting requirements, payment setup, and launch readiness need individual confirmation.
Will Blackleaf Dispensary POS work offline?
Offline operation is on the roadmap. Offline settlement is not currently represented as production-ready. Your deployment review should specify what can continue without internet, which actions are restricted, and how payments, inventory, permissions, and reporting reconcile after reconnecting.