Plan your dispensary’s first day.
Choose a new dispensary POS around the licensed store you plan to operate: its service channels, opening inventory, equipment, staff and required reporting. Confirm those dependencies before committing to an opening date. Blackleaf POS is in production in 11 states. Texting can be evaluated separately with supported existing POS systems.
In production in 11 states. Nevada, Ohio, and Colorado are expected in January 2027. See supported states.
Start with the decisions that can hold the opening.
Write down the jurisdiction, licensed facility, license type and intended channels before choosing the setup. A first storefront, pickup service and delivery operation can have different requirements. Confirm applicable state and local conditions with the responsible authorities and advisers; software selection does not grant permission to open.
- This is a blank planning worksheet, not a completed Blackleaf deployment. Add a status to each gate: not checked, passed, blocked or not applicable with a reason. Keep sensitive evidence in your approved private system.
- Give each dependency a needed-by date and an accountable person. A promised delivery date, demo or account invitation is not proof that the dependency is ready.
- Blackleaf POS is in production in 11 states. Confirm your licensed location and required workflow scope before scheduling store launch. Production Metrc approval does not imply all-state coverage.
| Gate | Owner and verification |
|---|---|
| License | Owner: ___ / Required permissions and opening conditions: ___ / Evidence and review date: ___ |
| POS scope | Owner: ___ / Supported jurisdiction, facility and required operations confirmed in writing: ___ / Reviewer and date: ___ |
| Stock | Owner: ___ / First delivery, package records, physical counts and sellable stock reconciled: ___ / Evidence and date: ___ |
| Setup | Owner: ___ / Actual equipment, network, tender and required connections tested: ___ / Evidence and date: ___ |
| People | Owner: ___ / Staff roles, approved procedures and first-shift support rehearsed: ___ / Evidence and date: ___ |
| Launch | Decision-maker: ___ / Unresolved blockers: ___ / Go or hold, approved scope and date: ___ |
Map the customer journey before ordering equipment.
Walk the production floor from check-in through shopping, payment and handoff. Count the work at each station, who owns it and which device it needs. Check sightlines, power, connectivity and accessible staff movement before approving a hardware order. A customer-facing display is a different job from a register or self-service kiosk.
- Record exact device models, connection types, operating system, drivers, consumables and ownership. Reusing a computer or seeing a familiar brand does not establish compatibility.
- Confirm supplied quantities, substitutions, installation, warranty and return terms in the quote. Leave time for actual acceptance rather than treating delivery as completion.
| Area | Decision to verify |
|---|---|
| Check-in | Who completes required eligibility checks, finds the right customer and hands off the visit? Confirm supported identification workflow and privacy. |
| Counter | How many staff can sell at once? Test the intended scanner, receipt printer, approved tender method and customer display at each station. |
| Stockroom | Who receives, labels, holds and counts products? Verify package identity, label output and the actual receiving station. |
| Office | Who manages access, cash close, reports and exceptions? Confirm management equipment and escalation contacts. |
Prepare opening stock as well as the menu.
A menu is a planning record; opening inventory needs verified products, packages, quantities and the store’s required receiving records. New stores may have no historical sales, but they still need an accurate starting point. Assign a person to reconcile the physical delivery, POS records and applicable external records before treating stock as sellable.
- Prepare product names, categories, units, SKUs, prices and verified descriptions. Keep package identifiers and product variants distinct so a scan finds the intended item.
- Review tax, discount and receipt configuration with the responsible adviser. Test the actual transaction rules for the location rather than copying another store’s setup.
- Use the approved validation process to check receiving, held or damaged stock, a count discrepancy and a correction. Record expected and observed results. Do not create fictitious production sales for practice.
- Keep any imported customer identity, balances and permission evidence separate. No purchase history is unknown history, not proof that an imported contact is a lapsed customer.
Rehearse a shift, including the uncomfortable moments.
Use the intended devices, staff roles and approved validation environment. Practice what happens when the expected result does not arrive, then agree who can hold the action and resolve it. A successful public sample helps explain a workflow; it does not prove your equipment, payment provider, reporting or team is ready.
| Scenario | Evidence to keep |
|---|---|
| First sale | Correct customer or permitted guest, eligible basket, stock, reviewed totals, tender, receipt and completed sale. Record the staff role and result. |
| Changed basket | Unavailable item, corrected price or reward difference handled with the right authority; final stock and totals agree. |
| Unclear tender | Existing sale and provider result reconciled before retrying. A timeout must not cause a second charge or duplicate sale. |
| Reporting | Required external status and store record reconciled. Name who resolves a pending or rejected submission. |
| Interruption | Device or connection failure follows the agreed hold and escalation procedure. Do not assume universal offline sales or automatic recovery. |
| First close | Cash or tender, orders, stock and required reporting reconciled; discrepancies have an owner, evidence and next review. |
Plan the first customer message as carefully as the first sale.
Blackleaf texting is the primary customer-communication product and can complement supported existing POS systems. A new store can evaluate its messaging setup separately from its POS choice. Confirm the actual supported data method, sender, permitted use case and approval requirements before scheduling launch outreach. A contact form, loyalty account or purchase is not marketing permission by itself.
- Collect the permission evidence required for the intended program and preserve current opt-outs. Confirm store and customer matching, source fields, update timing and exclusions for the supported setup.
- Review opening hours, offer dates, prices, stock and destination links before sending. Recheck if the opening moves; an old scheduled message must not announce an unready store.
- Assign one owner for each order notice. Confirm the actual ready, changed or canceled event and current order state; payment or arrival alone does not prove readiness.
- Keep available AI texting preparation separate from POS AI agents, which are in production in California. A prepared draft does not establish permission, current stock or a completed campaign.
Compare plans for your new store.
Choose Software if you have compatible equipment, Complete for supplied hardware, or Managed for agreed operating help. Confirm the equipment, integrations, and reporting workflows you need before launch.
- Review Software, Complete or Managed against the actual live deployment, equipment and operating-help scope. Published packages do not establish immediate availability or a confirmed launch date.
- Budget the POS subscription, stations, equipment and installation, training or setup, payments, messaging usage, taxes and third-party charges as applicable. Keep unknown fees visible rather than treating them as zero.
- Confirm the current package, capacity, ownership, service coverage and contract terms in writing.
Ask providers to explain who owns each handoff.
Use the same opening plan when reviewing providers. Ask who activates each account, configures the store, checks the first records, trains staff and remains available through the first reconciled close. Separate the store’s responsibilities from POS, hardware, payment and messaging providers. A generic onboarding duration does not establish when your dependencies will be ready.
- Request a supported jurisdiction and workflow list, an equipment decision, actual connection scope, dated quote and accountable support contacts. Keep required work separate from later enhancements.
- Useful official references include Cova’s role-based SOP guidance, Flowhub’s opening guide covering layout and technology, and Dutchie’s cash-management guide for opening and reconciliation. These are vendor resources, not evidence that every provider or Blackleaf supports every described operation.
- Ask for a demonstration of your required exception, not just a successful standard sale. Record missing evidence and the person responsible for resolving it.
Agree the opening decision and first-shift support.
Let readiness determine the supported launch scope and date. The decision-maker should review the required evidence, unresolved blockers, staff rehearsal and available support before giving a go decision. Do not average away a critical reporting, inventory, tender or eligibility blocker because other checks passed.
- Agree who can pause an affected workflow, what approved continuity procedure applies and how the team reaches the responsible contact. This is a store-specific plan, not a published support SLA.
- If a configuration, device, opening date or service channel changes, recheck the affected evidence. A prior sign-off may no longer apply.
- After the first shift, reconcile the required records, review open issues and confirm the next responsible owner and review time. Keep customer outreach aligned with what the store can actually deliver.
Give every first-day check a named owner.
Use the printable staff checklist for the shift briefing and its editable CSV for your team’s record. Both contain twelve checks spanning opening, the first sale, exceptions, Texting, close and handover, with space for an assigned person, status and review time. Fill them from actual rehearsals on the intended setup; the blank template does not establish readiness.
- Mark each check Not checked, Ready, Blocked or N/A with a reason. Keep the evidence and reviewer in the approved private record; a blank owner or status is not a pass.
- Escalate unresolved critical items to the duty manager before relying on that workflow. Keep the actual opening decision and supported scope separate from a staff checklist. Texting can be evaluated separately with supported existing POS systems.
| Assign | Record before the shift |
|---|---|
| Duty manager | Name, backup, support contact and who can hold an affected workflow or authorize an exception. |
| Station owner | Staff member, role, intended device, required rehearsal, observed result and review time. |
| Message owner | Person approving current message facts and eligibility, sender, scheduled work and reply coverage. |
| Closing owner | Person reconciling the agreed shift records, logging differences and handing open issues to the next owner. |
Questions worth asking.
Clear answers for planning your store’s next step.
Who should own the first-day dispensary POS checklist?
Name a duty manager to coordinate the shift, then assign actual people to check-in, checkout, inventory, customer messaging and close. Record the required check, status, evidence, reviewer and time. Staff should know who can hold a workflow and resolve an exception. The checklist supports the store’s opening review; it does not replace the authorized go-or-hold decision.
What should a new dispensary prepare before choosing its POS?
Prepare the jurisdiction, licensed facility and license type, service channels, opening-stock plan, station count, equipment, required reporting, staff roles and customer-communication needs. Use a readiness record with an owner, evidence, review date and status for each dependency. Confirm supported scope before committing to the opening date.
Can a new dispensary open on Blackleaf POS today?
Blackleaf POS is in production in 11 states. Confirm supported operations for your licensed facility under Blackleaf’s production Metrc approval. Confirm your jurisdiction, licensed facility, required operations, equipment, payment support and opening readiness directly. This page does not establish immediate self-service access or all-state coverage.
Can I try the POS before opening?
Use Free trial on the pricing page to ask about trial access and setup. Confirm live checkout and reporting for your licensed location separately.
Should we buy POS equipment before selecting the software?
Map the workstations first, then confirm the supported software and complete device setup before ordering. Record exact models, connections, operating system, drivers, consumables, quantities and service terms. Existing equipment or a familiar brand does not establish compatibility; a customer display is not automatically a register or kiosk.
What records does a new store need without sales history?
Prepare verified products, units, prices, package references, opening inventory and the required receiving records. Reconcile physical stock, POS records and applicable external records. Review tax and receipt setup separately. Imported customer identity, balances and marketing permission need their own evidence; missing purchase history is unknown.
Does production Metrc approval finish the opening checks?
No. Confirm jurisdiction, facility, supported actions and reporting readiness for the actual deployment. Metrc validation covers specified functions and does not endorse a provider’s product. A completed checkout does not establish an accepted external submission; assign an owner to pending, rejected or mismatched records.
What should staff rehearse before opening?
Practice the required first sale, changed basket, unclear tender result, reporting exception, interruption and first close on the intended setup through an approved validation process. Retain expected and observed results and responsible roles. Do not create fictitious production sales for training or assume offline selling and automatic recovery.
How long does a new-dispensary POS launch take?
Timing depends on licensed scope, supported operations, opening records, equipment, provider activation, staff training and accepted evidence. Name each dependency’s owner and needed-by date, then agree the launch date after readiness review. No fixed onboarding duration or zero-downtime promise is established here.
Do we need Blackleaf POS to start Blackleaf texting?
No. Blackleaf texting is available separately and can complement supported existing POS systems. Confirm the actual connection or authorized data method, fields, matching, timing and permitted messaging setup. A purchase, imported contact or loyalty membership alone does not establish marketing permission.
What should we bring to an opening-plan review?
Bring the licensed location and license type, service channels, floor and station plan, equipment list, opening inventory, required connections, staff responsibilities and target timing. Include the customer-texting plan. Ask for written scope, a complete quote, acceptance evidence and named support responsibilities.