Start the next chapter with a clear plan.
A dispensary POS rollout needs verified records, trained staff, supported connections and a clear go-or-hold decision. Plan each stage around your licensed store, with evidence and an owner for every required check.
In production in 11 states. Nevada, Ohio, and Colorado are expected in January 2027. See supported states.
Agree the scope before the date.
Dispensary POS implementation is the production transition from the current store workflow to a verified new setup: source records, equipment, staff, connections and launch responsibility. Blackleaf POS is in production in 11 states. Confirm supported operations for your licensed facility under Blackleaf’s production Metrc approval. Confirm the licensed location, jurisdiction and supported operations before committing to a launch.
- Name the store decision-maker, migration owner, inventory lead, staff-training lead and support contacts. One person may hold several roles; responsibility should still be explicit.
- Record locations, service channels, stations, required connections, retained equipment and the workflows needed on day one.
- Agree the POS AI actions and approval controls your store will use at launch. Blackleaf POS AI agents are in production in California; optional connections still need their own confirmed scope.
| Stage | Evidence to review | Proceed when |
|---|---|---|
| Scope | Agreed location, workflows, responsibilities, quote and dependencies. | The required setup is supported and the owners accept the plan. |
| Prepare | Source exports, field mapping, equipment readiness and training plan. | Missing or conflicting records are explained; required equipment is available. |
| Rehearse | Representative workflows and expected-versus-observed outcomes. | Critical scenarios pass or have an explicitly approved supported resolution. |
| Cut over | Final changes reconciled, active-system decision and support coverage. | Named owners approve the go/no-go review; unresolved blockers hold the launch. |
| Stabilize | First-shift reconciliation, issue log and handover. | Open issues have owners and the store can operate the agreed scope. |
Reconcile the records you actually have.
Begin with an authorized representative export and a mapping review. Preserve the original source, record the export time and agree how final changes will be captured. A successful import is not proof that balances, identity and historical coverage agree. Keep unsupported history readable through an agreed archive or export rather than promising every record will migrate.
- Compare counts and control totals, then inspect representative records and exceptions. Define acceptable differences and their resolution before cutover.
- Confirm source-system access, export terms and retention needs before terminating the old service.
- Use the approved data-sharing process; do not put customer exports or confidential access details into public worksheets.
| Record | Check before accepting the migration |
|---|---|
| Customers | Stable source IDs, duplicates, store scope and usable contact fields. Do not merge profiles solely because names match. |
| Loyalty | Opening balances, redemption rules, expiry and liabilities. A balance total alone does not establish that checkout can honor the same benefit. |
| Messaging permission | Actual opt-in evidence, scope, current opt-outs and suppression ownership. Unknown values are not permission; an import must not silently resubscribe anyone. |
| Products and packages | Product identity, SKU/variant mapping, package references, units, sellable versus held quantities, cost and agreed prices. |
| Orders and financial records | Open orders, tender states, returns, deposits where relevant, totals, time zones and retained history. Record what is excluded. |
Rehearse the shift, including the exceptions.
Train the people who perform the work: front desk, budtender, inventory staff and manager. Use the supported training environment and approved validation procedure. A sample-store demo helps explain a workflow but does not prove the licensed deployment, payment provider, equipment or external connection is ready.
- Walk through check-in, a sale, discount or reward, void or return, open order, pickup and cash close as applicable.
- Test the intended scanner, receipt/label printer, customer display and payment device by model and actual job. Kiosk order entry and customer-display pairing are different functions.
- Rehearse missing stock, interrupted payment, late order update and a connection becoming unavailable. Staff should know when to stop and whom to contact.
- Record each person’s demonstrated workflow and remaining training, rather than treating attendance as operational readiness.
Verify traceability and the supported connections.
Production Metrc approval does not establish all-state coverage, every operation or a regulatory endorsement. Confirm the jurisdiction, licensed facility and required actions. For the actual deployment, review how a POS record becomes an accepted external record and who owns pending, rejected or mismatched results. Metrc’s validation explanation distinguishes specified functions from endorsement of a provider’s product.
- Reconcile the supported package and inventory state before opening the new workflow. A displayed count and an accepted traceability submission are different evidence.
- Validate the required sale, return, receiving or correction scenarios only through the approved procedure for the store and connection. Do not submit fictitious production transactions as a training shortcut.
- For each connection, record source, destination, field mapping, direction, update timing, error visibility and responsible organization.
- Confirm a supported recovery and reconciliation path. A timeout is not proof that an action failed, and retrying must not duplicate a sale or stock movement.
Keep texting continuity in its own plan.
Blackleaf texting is available separately from Blackleaf POS. If messaging is the immediate priority, confirm a supported connection or authorized data method for the POS you already use. A POS replacement and a texting improvement are separate decisions. When a POS changes, revalidate the messaging inputs rather than assuming customer history, rewards and permission arrive unchanged.
- Carry current opt-outs and permission evidence through the agreed source of truth. A customer or loyalty import alone does not establish marketing eligibility.
- Recheck store mapping, completed purchases, returns, order events, reward fields and the latest successful refresh. Missing history is unknown, not evidence that every imported customer is lapsed.
- Coordinate affected campaigns and automations during stale or uncertain feeds. Reconcile recent purchases and messages before resuming a workflow so old events do not create duplicate outreach.
- Confirm sender, links, audience, exclusions, tests and approvals for the actual supported texting setup. A working data connection does not establish that every business, use case or route is permitted.
Use an acceptance record everyone can read.
Copy these prompts into the store’s own project record. This is a blank planning worksheet, not a completed Blackleaf deployment or a guarantee that every scenario is supported. For each required check, record the named owner, environment and version, source timestamp, expected result, observed evidence, status, issue reference, reviewer and review date. Keep sensitive records in the approved private system.
- Use clear statuses such as not checked, passed, blocked or not applicable—with a reason and reviewer. A blank cell is not a pass.
- Do not average away a critical blocker because several easier checks passed. Resolve the required scenario or revise the supported launch scope.
- Use the same evidence record for re-tests after a configuration or data change; an old sign-off may no longer apply.
| Required check | Evidence to retain | Decision to record |
|---|---|---|
| Opening data | Mapped source and destination counts, totals, sample records and explained differences. | Owner: ___ / Result: ___ / Reviewer and date: ___ |
| Checkout and equipment | Approved rehearsals on intended devices; receipt, stock and tender results agree. | Owner: ___ / Result: ___ / Blocker or issue: ___ |
| Traceability and integrations | Supported-action list, reporting status and reconciled exceptions for the licensed scope. | Owner: ___ / Result: ___ / Reviewer and date: ___ |
| Customers, loyalty and texting | Identity, balances, current permission/suppression and the intended event timing checked separately. | Owner: ___ / Result: ___ / Missing fields: ___ |
| Cutover and continuity | Final changes reconciled; active system, pause criteria, supported fallback and escalation agreed. | Decision-maker: ___ / Go or hold: ___ / Date: ___ |
| First-shift handover | Cash/tender/order/stock reconciliation, open issues and support ownership. | Owner: ___ / Outstanding actions: ___ / Next review: ___ |
Make cutover a go-or-hold decision.
Agree the final export or change-capture point, reconciliation steps, cutover window and who may approve launch. Define which system is authoritative for each record and when that changes. Avoid uncontrolled parallel entry that creates competing sales, payment or stock records. The date follows readiness; no fixed launch duration or zero-downtime promise is made here.
- Record the final export time and the time the new POS takes over, using the same time zone. If trading or receiving continues between those points, have the migration owner match each sale, return and stock movement by its source ID to the destination or the agreed exception log. Check a sample on both sides of the handoff to catch activity that was missed or counted twice.
- Name the conditions that hold the launch: unresolved inventory or tender differences, missing required reporting, unready equipment or staff, and unsupported critical workflows.
- Document who can pause affected operations, which approved continuity procedure applies, and who coordinates providers and the store.
- A fallback is a deployment-specific procedure, not a promise of an instant rollback button or offline selling. Restoring an older snapshot can lose subsequent activity unless it is reconciled.
- If reverting is necessary, preserve completed sales, tenders, inventory movements and external acknowledgements; reconcile them before resuming through the supported plan.
Plan the first shift and the handover.
Agree support contacts, coverage hours, escalation, provider dependencies and who owns each unresolved issue. During stabilization, reconcile the first shift’s orders, cash or tender totals, stock and required external reporting. Confirm the handover criteria and training needs before treating the implementation as complete. These are planning requirements, not a published Blackleaf support SLA.
- Keep an issue log with impact, owner, evidence, next action and next review time. Separate a blocked sale or reporting problem from a later enhancement.
- Include migration/export work, hardware, training, integrations, payment onboarding, messaging and any overlap with the old contract in the quote. Unknown cost is not zero.
- Request the actual proposed scope, fees, responsibilities, supported geography and launch conditions in writing. No universal migration coverage or included training package is implied.
Download the POS migration acceptance workbook.
Use the free editable XLSX workbook to carry reconciliation, workflow acceptance and cutover review in one store-owned record. Its five sheets include instructions, 12 reconciliation rows, eight workflow checks, an issue log and six cutover gates. Numeric differences stay separate from reviewer acceptance, and missing evidence keeps the default state at Hold for review.
- Record the source and target cutoffs, units or identity mapping, observed values, evidence and reviewer. Repeat rows for each store, package or balance type; matching aggregate totals can hide mismatched records.
- Keep customer identity, loyalty balances, permission evidence and current suppression separate. A successful customer import does not establish marketing permission or complete Texting continuity.
- Name an owner for each finding. Blocking issues stay visible until their resolution and review evidence are recorded. Review excluded requirements and nonblocking follow-ups explicitly.
- The workbook can indicate Ready for human review; the authorized store decision-maker records the actual go-or-hold decision and date. Keep the completed workbook and sensitive evidence in the store’s approved private systems.
Questions worth asking.
Clear answers for planning your store’s next step.
What should a dispensary POS migration acceptance workbook contain?
Record source and target cutoffs, units and identity mapping, control totals, observed workflow results, evidence, reviewers, unresolved issues and cutover responsibility. Keep customer identity, loyalty and Texting permission separate. The free workbook on this page supplies blank records and completeness checks; the authorized store decision-maker approves the actual supported deployment.
How long does it take to implement a dispensary POS?
There is no fixed Blackleaf launch duration promised here. Timing depends on supported location and workflows, data quality, required equipment and connections, training and reconciliation. Agree the milestones and owners first, then approve a date when the required acceptance checks are satisfied.
Can any dispensary start a Blackleaf POS rollout now?
Blackleaf has a working POS and production Metrc approval. Confirm the licensed location, jurisdiction, required operations and deployment readiness directly. Approval does not establish all-state availability or every feature.
Will all our historical POS data migrate?
Do not assume every field or historical period is supported. Review a representative authorized export, map the records, reconcile counts and totals, and document excluded history. Agree how retained reports remain accessible before ending the old service.
Does moving customer or loyalty data preserve texting permission?
Customer identity, loyalty membership, balances and marketing permission are separate records. Preserve actual consent evidence and current opt-outs through the agreed source of truth. An import must not silently turn unknown permission into eligibility or resubscribe a suppressed person.
What should we check when implementing a dispensary kiosk POS integration?
Confirm the intended kiosk or display model, software version, order or basket handoff, supported payment role and staff exception workflow. Test current product and price data on the actual devices. A paired customer display is not automatically a self-service ordering or payment kiosk.
Does Metrc production approval finish the implementation checks?
No. Confirm the jurisdiction, licensed facility, supported actions and reporting readiness for the deployment. Reconcile required records and acceptance states, and assign responsibility for rejected or pending submissions. Production approval is not a guarantee of regulatory compliance.
Does a successful public demo prove our store is ready?
No. The public demo uses sample data. It helps explore workflows but does not establish migrated records, trained staff, actual equipment, payment-provider support or licensed external reporting. Validate the actual supported deployment separately.
Can we simply switch back if something goes wrong?
A fallback must be agreed and rehearsed for the deployment. It is not an instant rollback guarantee. Preserve and reconcile any sales, tenders, stock movements and external acknowledgements created after cutover before resuming through the supported plan. Do not assume an old snapshot contains later activity.
Do we need a POS migration to use Blackleaf texting?
No. Blackleaf texting is available separately from Blackleaf POS. Confirm the supported existing-POS connector or authorized data method, actual fields, customer match and update timing. Evaluate a POS replacement separately from improving customer messaging.
What should an implementation quote include?
Ask for migration and export work, retained or supplied hardware, training, integrations, payment onboarding, support scope, recurring services, messaging and any overlap or exit cost from the old provider. Specify owners and launch conditions. This page does not establish a fixed fee or support SLA.