POS integrations with a clear scope.

A dispensary POS integration connects specific records and actions across store systems. Start with what must move, who owns it, and how you’ll verify the result. Blackleaf confirms connection scope for each deployment.

In production in 11 states. Nevada, Ohio, and Colorado are expected in January 2027. See supported states.

Know what is available today.

Blackleaf has a working POS system and production Metrc approval. Production POS is available in 11 states. That status is different from a promise that every connector, jurisdiction, device or public API operation is available. Use the table to identify what needs confirmation for your store.

Blackleaf integration availability · Reviewed October 16, 2026
AreaCurrent positionConfirm before rollout
Store POSProduction system available in 11 states.Required checkout, inventory and customer workflows for your location.
MetrcProduction approval.Jurisdiction, licensed facility, supported operations and reporting readiness.
Internet loss and Metrc outage recoveryProduction offline recovery; validate the store setup before activation.Separate failure modes, durable event storage, permitted checkout, automatic catch-up and reconciliation.
Blackleaf textingAvailable separately from adopting Blackleaf POS.Supported existing-POS connector, fields, update timing and messaging eligibility.
Payments and equipmentDeployment-specific scope.Provider or device model, supported actions, terms and operating responsibilities.
Public POS interfaces and POS AI agentsIn production in California; confirm connection and action scope.Actual endpoints, event coverage, permissions, approved actions and release readiness.

Read Metrc approval within its scope.

Production approval is a meaningful milestone. It should not be read as all-state coverage, support for every Metrc operation, or a guarantee of regulatory compliance. Metrc’s own validation explanation distinguishes specified functions from an endorsement of a provider’s product. Confirm the jurisdiction, facility and operations that apply to the deployment. In Metrc’s directory, select BlackLeaf Marketing Solutions in the Integrator filter to find the California listing.

Metrc questions to resolve for the licensed store
Scope questionWhy it mattersEvidence to review
Which jurisdiction and facility?Reporting requirements and authorized access belong to a specific licensed operation.Confirmed jurisdiction, license mapping and deployment scope.
Which actions are supported?Sales, returns, adjustments, receiving and corrections are distinct workflows.A supported-operation list and representative records for the actions your store needs.
When is an action reported?A completed POS action and an accepted external submission are different states.Reporting timing, acceptance status and handling of pending or rejected submissions.
How are exceptions resolved?Missing acknowledgements, rejected records and mismatched quantities need an owner.A reconciliation procedure, responsible staff and a supported recovery path.

Review the whole Metrc workflow.

A connected status only answers whether a service can be reached at that moment. Evaluate what happens to packages, sales and corrections across a complete store day. Use these requirements to confirm the supported deployment; they do not establish that every listed function is already released in Blackleaf.

Metrc integration checklist · Request observed results
PrincipleDemonstration to requestEvidence to keep
Sync direction and frequencyTrace package data into the POS and supported sales or corrections into Metrc. Show scheduled updates, a manual refresh and a delayed update.Source, destination, normal interval, event time, last successful sync and visible stale-data status.
Receiving and package reconciliationReceive a short shipment, a mismatched package tag and an incorrect unit. Identify discrepancies at intake and hold affected stock until the approved resolution.Manifest and package references, expected versus received quantity, facility, unit, restriction and correction owner.
Voids, returns and correctionsTrace a cancellation before submission and a permitted return or correction after acceptance. Test a correction waiting behind its original sale.Linked original and correcting records, supported Metrc operation, resulting quantity and disposition, reason, approver and acceptance result. A refund does not automatically make returned stock sellable.
Category, unit and tax mappingReview how a package maps to the product category and unit, then to the store’s configured tax rules. Test an unmapped or conflicting value.Reviewed mapping, conversion and tax configuration with change history. A Metrc tag alone does not establish the correct tax treatment.
Audit history staff can retrieveFollow a package receipt, sale, sync attempt and authorized adjustment without relying on a support ticket to explain the record.Staff identity, timestamps, original reference, reason, before/after values, submission response, correction history and confirmed export/retention scope.
Rate limits and fair recoveryThrottle one facility while another has pending work. Show bounded batches, retry delays and how an invalid event is isolated.Facility-scoped queues, oldest pending age, attempt history, API-limit handling and ownership of reporting deadlines. One failed facility should not silently stall another.
Transfers between licensed locationsMatch the sending and receiving facility, manifest, package and quantity on both ends, including a short receipt.Separate dispatch, in-transit, receipt and accepted states. A portfolio inventory view does not complete a regulated transfer.
Nightly package reconciliationCompare POS movement, Metrc balances and physical counts at a common cutoff. Explain pending submissions, holds, transfers and corrections.Package-level differences, event timing, investigation owner and authorized resolution. Do not overwrite balances merely to make two screens agree.

Test internet loss and Metrc downtime independently.

Blackleaf’s production outage recovery separates a disconnected register from an online POS waiting on Metrc. It preserves permitted sales and reporting events durably, then resumes eligible submissions when the required connections recover. Confirm the operating limits, applicable outage instructions and setup for your store.

  • For store internet loss, rehearse on a prepared register with a dated local snapshot and durable event storage. Verify a reload or restart, local quantity deductions, authorized staff access and explicit limits for stock shared with other registers or online orders. Stop when safe persistence or required verification is unavailable.
  • For Metrc downtime with internet working, keep checkout and reporting status separate. Show what is pending, the last successful sync, the oldest unreported sale, attempts and the person responsible for unresolved records. Payment providers retain their own availability and approval requirements.
  • For recovery, synchronize local records to the POS service before their dependent Metrc work. Preserve stable sale and event references, original transaction times and facility identity. A timeout is an uncertain result: check whether Metrc accepted the original before creating another submission.
  • Resume eligible work in dependency order with bounded requests and backoff. Honor Retry-After when provided; isolate validation errors, route credential failures to an owner and keep unaffected eligible work moving. Do not blindly retry every error.
  • Trace a sale followed by a void or return through recovery. An accepted original needs the supported correction path, not deletion of its local evidence or a second unrelated sale. Reconcile quantity, disposition, tender and reporting independently.
  • Close the incident only after queued, uncertain and rejected events are accounted for and package discrepancies have owners. Retain the outage interval, attempts, acceptance references, corrections and reconciliation result.

Define the records, direction and timing.

An integration name or logo does not describe the complete connection. Write down the source of each record, the fields shared, whether the connection reads or writes, and how quickly a change becomes available. The examples below are a requirements checklist, not a claim that every Blackleaf connector supports every field.

  • Distinguish a manual import, scheduled synchronization and event delivery.
  • Identify how stale or missing data becomes visible to staff.
  • Agree who owns corrections and how the corrected record reaches the other system.
Connection requirements to confirm
Record or actionUseful detailImportant boundary
Customer and order recordsMatching IDs, location, current order state and duplicate handling.A customer import is not necessarily an order-event feed.
Inventory and product dataProduct or package identity, location, sellable quantity, holds and last update.A catalog listing is not proof of stock available to sell.
Sales, returns and reconciliationTransaction identity, adjustments, acceptance status and ownership.A retry must not create a second sale or duplicate inventory movement.
Messaging permissionOpt-in evidence, scope, current opt-outs and the source of truth.Purchase history or loyalty membership alone does not establish marketing permission.
Payments and settlementAuthorization, cancellation, refund and reconciliation responsibilities.A provider connection does not establish support for every tender or action.

Check kiosks and devices by the job they do.

A paired customer display, a self-service kiosk and a payment terminal have different jobs. Seeing a basket on another screen does not establish that the device can create an order, accept a tender or complete every checkout action. Confirm the specific model, software version, pairing and handoff required for your store.

  • Test basket and price updates on the intended customer-facing screen.
  • Confirm how a kiosk order reaches staff and how exceptions are handled.
  • Validate supported scanning, receipt and label-printing workflows on the actual equipment.
  • Identify what staff can do when a paired device or connection is unavailable.

Make an interrupted update understandable.

Before activation, rehearse a delayed response, duplicate event, canceled order and rejected update. Staff should be able to distinguish a pending action from a confirmed failure and an accepted result. The appropriate recovery depends on the supported connection and the store’s approved operating procedure.

  • Use the same record identity when checking a disputed or delayed result.
  • Confirm the supported way to retry without duplicating a sale or stock movement.
  • Assign an owner for rejected or unresolved records and retain the outcome.

Use texting alongside the POS you have.

If customer outreach is the immediate priority, evaluate Blackleaf’s existing texting product with your current POS. Campaigns, replies and reviewed messaging workflows are separate from adopting a new point of sale. Available purchase or order context depends on the supported connector and data access; no POS switch is required for every texting customer.

  • Start with one useful message and confirm the inputs it needs.
  • Keep current permission and suppression checks separate from the purchase record.
  • Confirm the business, message purpose and route are permitted; a working connection does not establish messaging approval.
  • Keep released AI texting preparation separate from POS AI agents that are in production in California.

Give the technical team a defined agreement.

Confirm POS interfaces and event delivery for your deployment. Production POS availability does not mean every public API operation is exposed. The messaging API is a separate interface; review POS operations, permissions, exports, limits and commercial terms before connecting another tool.

  • Record the connection’s scope, responsible organizations and support path.
  • Confirm setup work, vendor dependencies, recurring fees and any usage charges.
  • Agree acceptance checks, exception handling and the information staff can export.
  • Treat the interactive sample environment as a way to explore the workflow, not evidence of a live vendor connection.

Questions worth asking.

Clear answers for planning your store’s next step.

Can a POS keep selling if Metrc is down?

That depends on the implemented POS workflow and the store’s applicable outage procedure. Metrc downtime can leave the POS and payment services online while reporting is pending. Blackleaf’s production feature keeps permitted checkout independent of a delayed Metrc response, with durable queued events and automatic catch-up. Validate the actual supported version, restricted actions and reconciliation before activation.

Is Metrc downtime the same as losing store internet?

No. Store internet loss can disconnect the register from POS services, Metrc and payment providers. It requires prepared local data, durable sales storage and limits on stock, staff authority and required checks. Metrc downtime can leave checkout online. Blackleaf has production recovery for both in California; test each separately. Electronic payment authorization is a separate dependency.

What should nightly Metrc reconciliation compare?

Compare package-level POS activity, Metrc records and physical counts using the same licensed facility, package, unit and cutoff. Explain unreported sales, accepted corrections, holds, returns and transfers before deciding a quantity is wrong. Preserve differences, investigation ownership and authorized correction history; a discrepancy alone does not prove shrink.

Does Blackleaf POS have production Metrc approval?

Yes. Blackleaf has a working POS system and production Metrc approval. Confirm the jurisdiction, licensed facility, supported operations and reporting readiness for your deployment.

Does production Metrc approval mean every state and operation is supported?

No. Read approval within the relevant jurisdiction and function scope. It does not establish all-state coverage, every Metrc operation or a guarantee of regulatory compliance. Ask for the supported actions and validation appropriate to your licensed location.

Do I need to switch POS systems to use Blackleaf texting?

No. Blackleaf texting is a separate available product that can work alongside supported existing POS systems. Confirm the connector, fields, timing, plan requirements and messaging eligibility for your setup. Adopting Blackleaf POS is a separate store-operations decision.

Does the public Blackleaf messaging API include POS inventory and purchasing?

No. The public messaging API documents messaging workflows. Legacy product, order and inventory entries do not provide a supported way to manage POS inventory, prices or purchasing. Confirm the available POS operations and permissions for your deployment before building.

Can I connect a kiosk, customer display or other hardware?

Confirm the specific device model, software version and supported job for the deployment. A customer display, order-entry kiosk, scanner, printer and payment terminal have different requirements. Validate pairing, data updates, handoff and exception handling on the intended equipment.

Are all POS integrations real time?

No. A manual import, scheduled sync and event feed have different timing. Confirm the update frequency for the specific record or action, how freshness is shown, and what staff should do when data is late or unavailable.

What should happen when an integration update fails or times out?

Identify the existing record and whether the action is pending, accepted or rejected before using a supported recovery path. Reconcile the systems and assign responsibility for unresolved exceptions. Do not assume a missing acknowledgement means it is safe to create a second sale or stock movement.

Does the public demo prove a live third-party connection?

No. The interactive preview uses sample data and illustrates store workflows. It does not establish live vendor access, approved reporting scope or production readiness for a particular connection. Review those separately for the actual deployment.