POS controls you can verify.
Dispensary POS security and compliance depend on who can act, what records are kept, which reporting workflows are supported and how the store handles exceptions. Blackleaf has a working POS and production Metrc approval.
In production in 11 states. Nevada, Ohio, and Colorado are expected in January 2027. See supported states.
Confirm the scope before rollout.
Start with your licensed location, operating model and required workflows. Production Metrc approval is an important integration milestone; it does not establish every state, transaction type or security control. Review the actual deployment and the evidence behind each requirement before deciding it is ready for your store.
| Area | Evidence and scope to confirm |
|---|---|
| Blackleaf POS | Working system in production in 11 states. The version, enabled functions, location, training, support and go-live criteria. |
| Metrc | Production approval. Jurisdiction, licensed operation, supported submissions, corrections, credentials and reconciliation. |
| Security | Evaluate the implemented controls and applicable evidence. The system and period covered by any assessment or attestation; hosting-provider assurance alone does not establish application assurance. |
| POS AI agents | In production in California. Confirm enabled actions, data access, approval requirements and activity records. |
Give each role a defined job.
Review staff permissions using the work people actually do. A cashier, inventory buyer and manager need different access. Ask to demonstrate the deployed version with a permitted role and a restricted role, including location boundaries. These are evaluation requirements, not a promise that every control below is already available in every deployment.
- Separate viewing a record from editing it, exporting it or approving a change.
- Test discounts, refunds, inventory corrections and customer exports with the intended role.
- For a manual discount your store restricts, use the same eligible sample basket with both roles. Check that the cashier cannot apply the discount alone and the total stays the same. Then have an authorized manager approve it and check the updated total and any available approval record before payment.
- Review account creation, sign-in protections, session handling and removal of access when a staff member leaves.
- Confirm who may change roles or grant integration access, and how that decision is recorded.
Follow the sale through reporting.
A completed POS sale and an accepted traceability submission are separate events. For the supported workflow, ask to trace the transaction, package or product reference, submission, response and any correction. The store needs a way to recognize an unresolved exception and a named person responsible for reconciling it.
- Confirm the applicable jurisdiction and current reporting instructions rather than copying another state’s setup.
- Demonstrate an accepted submission and a rejected or interrupted submission in an authorized test setting.
- Review status, timestamps, error details and the procedure for correcting or retrying without duplicate reporting.
- Reconcile POS records with the reporting system, including returns, voids and adjustments that the deployment supports.
Ask for evidence behind the security claim.
Request information about the actual application and deployment, not just an infrastructure provider’s logo. An assessment, technical control and operating procedure answer different questions. Record what was shown, what remains pending and who owns the follow-up. The table is a buyer’s evidence request, not a list of Blackleaf certifications.
| Area | Evidence and scope to confirm |
|---|---|
| Identity and access | Role/location permissions, sign-in options, account removal and a restricted-action test. Which controls are enabled in your version and who administers them. |
| Activity records | A supported change with actor, timestamp, reason and outcome; available export and retention details. Which events are recorded, how records are protected and what the store can retrieve. |
| Customer data | Data flow, access, storage, retention, export and deletion procedures. What the POS, store, integration and other processors each hold; applicable retention duties. |
| Audit scope | Any applicable report or attestation, its scope, review period, exceptions and remediation status. Which entity, service and controls were actually assessed; do not infer a POS certification from Metrc approval. |
| Recovery | Backup scope, restoration procedure, a recent test summary and agreed recovery objectives. What is restored, the expected data gap, who acts and which dependencies must return first. |
| Payment data | Provider responsibilities, supported tender, authorized data flows and exception handling. Which system handles sensitive payment information and which assurance applies to that system. |
Keep customer data and texting permission separate.
A customer record, purchase or age check does not establish marketing-text permission. Before customer information moves to a messaging tool, define the permitted purpose, fields, access and current suppression source. Avoid exporting identity documents or other sensitive records merely because the POS holds them; transfer only the information the authorized workflow needs.
- Keep documented opt-in source, timestamp, disclosure and scope separate from purchase history or loyalty enrollment.
- Test an opt-out and an older import so stale data does not silently reactivate an ineligible contact.
- Confirm who may export customer data, which location the records belong to and how access is removed.
- Check the actual business, content and sending-route eligibility; consent, registration and an age gate do not override provider restrictions.
Rehearse interruptions before activation.
Blackleaf’s production offline recovery handles store internet loss and Metrc downtime separately. Validate each store setup: a disconnected register needs prepared local data and durable records, while an online POS can keep permitted checkout moving with reporting pending. Payments, stock availability and required customer checks retain their own dependencies.
- Document which actions may continue, which must pause and who decides, using the applicable operating requirements. An outage does not itself change a reporting deadline.
- Validate storage through reload or restart, cached-data age, staff authority, shared-stock limits and a stop condition when a sale cannot be durably saved or a required check cannot be completed.
- Demonstrate automatic recovery of eligible events, uncertain-result checks before retry, dependent void/return handling and reconciliation. Keep pending, accepted, rejected and uncertain reporting results visible with an owner.
- Agree recovery objectives, escalation contacts, support hours and the store’s fallback procedure.
- Review what happens to dependent customer messages when an order state or inventory feed is stale.
Review AI authority as its own permission.
Blackleaf’s POS AI agents are in production in California. The review process separates reading store information, preparing a recommendation, approving it and executing a change. A draft or simulated task is not a completed inventory adjustment, price change, regulatory submission or customer message. Confirm the actual supported action before enabling it.
- Identify the information the action can access and when it was last updated.
- Review which person or role approves the current version and what happens after a change or rejection.
- Confirm the action’s scope, activity record and response to missing data or interrupted execution.
Finish with named operating owners.
Turn the review into a short deployment record: requirement, current evidence, pending item, responsible person and activation decision. Blackleaf and the store should agree the supported setup and handoffs; the licensee remains responsible for accurate information and its operating obligations. Metrc’s published validation disclaimer describes specified integration functions rather than a product-quality endorsement.
- Name the owners for staff access, inventory corrections, reporting exceptions, customer-data exports and messaging suppression.
- Record the support path for an incident, failed submission or recovery test.
- Document any unmet requirement and whether it blocks activation or is explicitly outside scope.
- Keep the record current when the deployment, staff responsibilities or connected systems change.
Questions worth asking.
Clear answers for planning your store’s next step.
Is Blackleaf POS a working system?
Blackleaf POS is in production in 11 states. Confirm the scope of Blackleaf’s production Metrc approval for your licensed facility. Confirm version, enabled operations, training and onboarding for your licensed location.
Does production Metrc approval mean Blackleaf supports every state?
No. Production approval does not establish every jurisdiction, license type or transaction workflow. Confirm the specific supported submissions, corrections, credentials and reconciliation for your licensed location. Metrc validation is not a guarantee of regulatory compliance or an endorsement of product quality.
Does Metrc approval establish a POS security certification?
No. Integration approval and security assurance address different questions. Request the implemented controls and any applicable assessment or attestation, including the entity, system, period, scope and exceptions covered. This page does not claim a Blackleaf SOC 2, PCI or other security certification.
Which staff-permission controls should we test?
Test the actual deployed version with the intended cashier, inventory and manager roles. Review location access, viewing, editing, refunds, discounts, corrections, exports and approval authority. Also confirm sign-in options, account removal and who can change permissions. Do not assume every listed control is enabled in every deployment.
What should happen if a Metrc submission fails?
The supported workflow should make an unresolved submission identifiable, preserve the relevant status and error details, and route it to a named person for correction and reconciliation. Confirm the current procedure, retry handling and duplicate prevention for your deployment. A receipt alone does not prove the reporting system accepted a sale.
Can Blackleaf POS continue operating during an outage?
Internet-loss checkout and Metrc outage recovery are production features in California. Test each independently: prepared local data and durable storage for internet loss; queued reporting and automatic catch-up for Metrc downtime. Confirm permitted actions, payment limits, duplicate prevention and reconciliation. Neither mode guarantees offline electronic payment authorization or settlement.
Does a POS customer record give permission to send marketing texts?
No. A customer record, purchase or age verification does not establish marketing permission. Keep the actual opt-in evidence and current suppression status, and confirm applicable law and provider support for the business and use case. Blackleaf texting is available separately from adopting Blackleaf POS.
Can POS AI execute changes without review?
Blackleaf POS AI agents are in production in California. Confirm the specific enabled actions, data access, approval controls and activity records before activation. Preparing or approving a draft is separate from executing it. Available AI texting tools have their own scope and permissions.