Keep the rest of your operation connected.
Understand Blackleaf Point of Sale integration plans, the separate messaging platform, and the scope to confirm before deployment.
Development preview · Availability and deployment scope confirmed for your store.
Know what connects—and what moves.
The useful question is what a connection does for your team. Customer identity, transactions, inventory, consent, and payments have different owners and update needs. Define those records and actions before selecting an integration.
| Connection | Purpose | Availability |
|---|---|---|
| Blackleaf messaging | Customer audiences, outreach, and messaging activity. | Separate existing product; current-POS compatibility depends on the connector and data access. |
| POS customers and orders | Carry customer and transaction context across store workflows. | Demonstrated with sample records; production interfaces are in development. |
| Metrc | Store-specific reporting, corrections, and reconciliation. | Planned; jurisdiction and live reporting must be validated. |
| Payment providers | Tender authorization, refunds, and settlement records. | Providers, supported actions, and terms confirmed per rollout. |
| Workforce and devices | Hours, cash counts, scanning, and printing. | Source systems, supported models, and connection scope confirmed per store. |
Keep one transaction from becoming two.
An interrupted connection should leave an understandable status. Before launch, test which system owns the record, how updates arrive, and how staff see failures or delayed updates. A retry must not create a second sale or a duplicate inventory movement.
- Agree the matching IDs, supported fields, and update direction.
- Demonstrate retries, exceptions, and reconciliation with representative records.
- Name the person who handles an unresolved connection error.
Give your technical team a defined starting point.
Documented POS interfaces and event delivery are roadmap work. The existing public messaging API does not establish access to POS operations. Review the available operations, permissions, exports, usage limits, and support before committing to an integration.
- The interactive preview uses sample data and browser storage, not a live vendor connection.
- Approved production access and developer package pricing are separate from a store subscription.
Questions worth asking.
Clear answers for planning your store’s next step.
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.
Do I have to switch POS systems to use Blackleaf texting?
No. Blackleaf’s dispensary messaging platform is available separately and can work alongside an existing POS, subject to the integration and data access available for that system. Adopting Blackleaf Dispensary POS is a separate store-operations decision.
Can our technical team connect other software?
Documented POS interfaces, customer-authorized integrations, and data exports are core roadmap requirements. Review the actual available operations, permissions, event delivery, limits, and fees with Blackleaf before committing to an integration. The existing public Blackleaf messaging API should not be assumed to expose the developing POS functions.