Multi-location dispensary POS, with clear boundaries.
Multi-location dispensary POS needs a shared operating view and clear boundaries for each store’s inventory, orders, staff access and customer records. Decide what can be shared, who can act and how each location’s records reconcile. Blackleaf POS is in production in 11 states; confirm the actual multi-location scope before committing.
In production in 11 states. Nevada, Ohio, and Colorado are expected in January 2027. See supported states.
Map what belongs to the group and what belongs to the store.
Start with the organization, legal entities, licensed facilities and locations you actually operate. One brand name or dashboard does not make those boundaries interchangeable. The map below is a planning architecture, not a statement that every sharing feature is enabled in Blackleaf. Confirm the supported record and action at each boundary.
- Give every required capability a status: demonstrated, documented, pending or not needed, with an evidence date and responsible person. Pending is not supported by assumption.
- Confirm jurisdiction, license type, facility and required actions for every proposed location. Production Metrc approval does not establish all-state coverage or every reporting function.
| Layer | Boundary to confirm |
|---|---|
| Group | Common product definitions and approved procedures may span stores. Agree which entity owns each record and who can publish a shared change. |
| Store | Keep orders, tenders, sellable stock, holds, package references and required reporting attached to the actual location and licensed facility. |
| Person | Define customer identity, purchase-history scope and rewards rules separately. A familiar phone number does not prove one shared customer account. |
| Sharing | Document fields, direction, locations, source owner and update timing. Shared visibility does not automatically grant editing or export access. |
| Outreach | Check the matched contact, message scope, current exclusions, participating stores and overlapping campaigns before a supported send. |
| Movement | A stock proposal or combined total is not a completed transfer. Verify the authorized movement, receiving and required external records separately. |
Separate location access from permission to act.
A manager may need to read several stores while changing records at only one. Define location scope and permitted actions independently, including exports, refunds, discounts, stock corrections and staff administration. Demonstrate both an allowed action and an action the role must be unable to perform.
- Keep individual staff accounts, the approved location/action record and an accountable reviewer. Recheck access when someone changes stores or leaves.
- Test the current session after a role or location change through the approved process. A hidden menu alone does not prove the restricted action is blocked. Confirm actual implementation and access history for the rollout.
| Role | Acceptance question |
|---|---|
| Store team | Can this role complete its approved local work while other stores’ restricted customer records, cash and actions remain unavailable? |
| Area lead | Can this role read the agreed stores and perform only the specifically approved actions? Check editing and exporting separately from viewing. |
| Group owner | Can this role review the required portfolio records without unintentionally granting broad access to every employee? Who can change roles and locations? |
Keep shared catalogs separate from sellable stock.
A common product definition can help stores use consistent names and categories. Quantities, packages, holds, prices and eligibility can still differ by location. Confirm which fields are shared, which may be overridden and how a bulk change is reviewed before it affects another store. A matching SKU does not make stock interchangeable.
- Check the selected store, package, unit, sellable quantity, reservations, holds and last update before relying on availability. Do not present one location’s stock as another location’s pickup inventory.
- For a required store-to-store movement, confirm the supported workflow, sending and receiving facilities, responsible roles and applicable external requirements. An internal planning record does not authorize physical movement.
- Reconcile sent, in-transit, received, rejected or corrected states under the approved process. Keep a discrepancy with an owner; do not count the same units as available at both stores.
- A kiosk or online menu also needs the correct location, stock and order destination. Confirm that connection separately rather than treating a portfolio view as an ordering integration.
Recognize a customer without spreading every record everywhere.
Decide whether customers are identified within one store, one entity or a permitted group of locations. Confirm stable identifiers, duplicate handling, history coverage and who can view or export each field. A shared phone, similar name or imported profile can produce a false match. A purchase record and marketing permission remain different facts.
- Confirm how a profile merge treats purchases, returns, contact changes, rewards and permission evidence. Preserve current opt-outs and applicable exclusions when records are imported or reconciled.
- Check the actual earning, redemption, expiry and return rules before promising that a reward works at another store. A shared customer view does not establish shared balances or cross-store redemption.
- Keep sensitive identity and purchase details limited to the approved purpose and staff. Confirm lawful sharing and retention with the responsible adviser; this planning map is not a privacy authorization.
- For messaging, resolve duplicate recipients across participating stores and coordinate contact frequency. A local list must not revive someone suppressed for the proposed program. Unknown permission stays unknown.
Make the portfolio total traceable to each store.
Use the same reporting period, time zone policy, order states and definitions for sales, discounts, returns and taxes. Reconcile location records before comparing stores. A late or missing feed should be visible as a coverage exception rather than silently reported as zero. Confirm the actual aggregation, drill-down and export scope for Blackleaf’s selected deployment.
- Add comparable additive amounts under one definition. Recalculate portfolio rates from their underlying counts rather than averaging store percentages without denominators.
- A person who buys at two stores can appear in both local customer counts. A unique portfolio count needs verified identity and duplicate handling; adding the local counts does not provide it.
- Keep store operations, matched campaign purchases and causal marketing effects separate. An attributed sale or a cross-store visit does not prove that a campaign caused an added purchase.
- Record the source IDs, locations, filters, history coverage and last complete update with the export. A portfolio report needs enough detail to explain a correction.
Confirm the next location before copying the first.
A successful first-store setup is useful evidence for that store. The next location still needs its own supported jurisdiction, licensed scope, devices, connections, staff roles and acceptance results. Use this blank checklist alongside the implementation plan; it is not a completed rollout or a promised onboarding duration.
- Add a status and needed-by date to each required gate. Recheck affected evidence after a device, configuration, service channel or location changes.
- Use the current Multi pricing tab to review Software pricing for the first five stores and each additional store. Confirm the complete quote, stations, equipment, setup, payments, messaging usage, taxes and other applicable charges; unknown costs are not zero.
- All three plans support multiple stores. Confirm equipment and operating scope for each licensed location.
| Gate | Record before approval |
|---|---|
| Scope | Location and licensed facility: ___ / Required operations: ___ / Confirmed support and review date: ___ |
| Access | Role and allowed locations/actions: ___ / Allowed and denied scenario results: ___ / Reviewer: ___ |
| Records | Products, stock, customer/rewards sharing and source timing: ___ / Reconciled evidence: ___ / Owner: ___ |
| Handoffs | Equipment, tender, ordering, required reporting and texting dependencies: ___ / Observed result and date: ___ |
| Decision | Unresolved blockers: ___ / Approved scope and go-or-hold decision: ___ / Responsible person and date: ___ |
Ask every provider to show the same boundaries.
Use identical store, role and record scenarios when reviewing providers. Dutchie documents location assignments and location-specific permissions. Flowhub’s official role guide separates action permissions and identifies same-environment requirements for internal transfers. Cova describes location-based roles, a master catalog, local pricing and consolidated reporting. These are useful review prompts, not evidence that Blackleaf implements the same controls or that a vendor guarantees an outcome.
- Ask for the actual proposed account, market, package, connector and record scope. Public documentation may not settle every deployment detail.
- Request an allowed action, a denied action, a corrected stock record and an explainable portfolio total. Keep missing evidence and follow-up ownership in the review. Official sources reviewed October 15, 2026.
Keep customer texting independent of the POS decision.
Blackleaf texting is the primary customer-communication product and can complement supported existing POS systems. A multi-store operator can evaluate one supported texting workflow without replacing every register. Confirm the actual connection or authorized data method, location mapping, customer match, update timing, current eligibility and team approval.
- A group-wide offer still needs participating stores, accurate terms and stock that each intended location can honor. Coordinate overlapping outreach and assign responsibility for replies.
- Blackleaf POS is in production in 11 states. Confirm reporting, cross-store actions, POS AI and approval controls for your locations. A preview or prepared suggestion is not a live stock movement, sent campaign or completed regulated action.
Give every shared change a named owner.
Download the editable multi-location responsibility matrix to assign thirteen catalog, stock, access, reporting, customer and Texting decisions. Its three tabs contain instructions, responsibility records and a change/exception log. Record the policy owner, local operator, approver, result reviewer and escalation contact for each actual store scope. Names, implementation limits and evidence start blank; capability status starts Unknown.
- Duplicate a row when facilities, versions, permitted actions or owners differ. Treat Documented and Demonstrated as different evidence states; Unsupported and Not required need an explicit limit or reason. A selected status without evidence is not verification.
- The change log separates a proposal from observed execution. Retain the original reference, intended locations, approval, resulting state, unresolved issue and review date. A completed spreadsheet does not grant system access, move inventory or submit required records.
- Use this matrix with every provider, including Blackleaf. It is a blank planning aid, not evidence of every multi-location function. Blackleaf POS is in production in 11 states; confirm sharing, supported operations and location permissions for your stores.
- Blackleaf Texting can complement supported existing POS systems without a POS switch. Keep the customer-communication owners and evidence in the same planning record while treating POS adoption as a separate decision. Store completed records and sensitive evidence in approved private systems.
| Area | Ownership to agree |
|---|---|
| Catalog and pricing | Who owns the common definition, who requests a local exception, who approves the affected stores and who checks the published result. |
| Stock and movement | Who owns local package/quantity records, holds and corrections; who separately approves sending, verifies receiving and resolves required external outcomes. |
| Permissions | Who authorizes location and action scope, who applies the change and who verifies allowed and denied behavior in the supported environment. |
| Reports | Who owns definitions and cutoff, who reconciles each store and who approves a portfolio view with missing-feed and duplicate-identity exceptions visible. |
| Customers and Texting | Who resolves identity, who checks actual permission and current exclusions, who approves participating-store offers and who owns replies. A shared profile is not send authorization. |
Questions worth asking.
Clear answers for planning your store’s next step.
Who should own changes in a multi-location dispensary POS?
Assign the shared policy owner, local operator, change approver, result reviewer and escalation contact for the actual facility and action. One person may fill more than one role where authorized, but a shared dashboard does not grant permission. Keep catalog definitions separate from local stock, and report definitions separate from reconciled results. Record supported scope, evidence and unresolved limits. The downloadable matrix is a blank planning record, not proof that a Blackleaf feature is released or that a change has executed.
What should multi-location dispensary POS keep separate?
Keep each store’s orders, tender, sellable inventory, packages, holds and required reporting tied to the actual location and licensed facility. Define shared catalogs, customer records, rewards and portfolio reporting separately. Confirm the supported fields, actions, ownership and update timing before treating a shared view as a shared operating capability.
Does Blackleaf support every multi-location setup today?
Blackleaf POS is in production in 11 states. Confirm supported operations for your licensed facility under Blackleaf’s production Metrc approval. Confirm the actual locations, jurisdictions, license types, sharing, roles, reports, devices and required operations for your deployment. This page does not establish all-state coverage or immediate self-service access.
Is access to a location the same as permission to change its records?
No. Define the allowed locations and the permitted viewing, editing, exporting and administrative actions separately. Ask for both an allowed and a denied scenario using the proposed role. Confirm the implemented controls and how current sessions reflect access changes for the actual rollout.
Does a combined inventory view make stock sellable at every store?
No. Products may share catalog definitions while packages, quantities, holds, prices and eligible selling locations differ. Check the actual store and source time. A proposed stock movement is separate from an authorized transfer, physical receiving and any required external records.
Will customers and rewards automatically work across all stores?
Do not assume that. Confirm identity scope, duplicate resolution, permitted sharing, history and staff access. Review earning, redemption, expiry and return rules at each participating location. A shared customer view does not establish shared rewards or marketing permission.
Can we add store customer counts into a portfolio total?
Not to obtain unique people when the same customer can shop at several locations. Confirm stable identity and duplicate handling, then distinguish local customer counts from unique portfolio customers. Reconcile additive sales under consistent definitions and recalculate rates from their underlying counts.
What should be checked before adding another location?
Confirm its licensed scope, supported operations, devices, connections, staff access, opening records and required reporting. Retain observed acceptance results, evidence dates, owners and unresolved blockers. A first-store launch or published additional-location price does not establish that the next store is ready.
Do all our stores need Blackleaf POS to use Blackleaf texting?
No. Blackleaf texting is available separately and can complement supported existing POS systems. Confirm the authorized data method, location and customer matching, fields, update timing, current permission and exclusions. Coordinate overlapping store campaigns; POS adoption remains a separate operations decision.
Can Blackleaf POS AI automatically move stock or send across stores?
Connected Blackleaf POS AI agents are in production in California. A sample workspace or suggestion does not establish an executed inventory movement, accepted external action or sent campaign. Confirm actual supported actions, review and availability separately from the POS and Texting products.