Keep the line moving. Keep the visit personal.

Dispensary checkout brings the visit, customer context, basket, price review and completion record into one staff workflow. Explore the working sample, then confirm the required controls, equipment and payment support for your licensed store.

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

Checkout

See the floor. Know who’s next.

Actual capture from the working sample app. Walk-ins, active sales and pickup orders illustrate queue ownership and next actions; deployment scope is confirmed separately.

BLACKLEAF POINT OF SALEProduct preview
Blackleaf checkout queue in Sales floor mode with waiting, serving, pending fulfillment, preparing, and waiting for pickup columns.
  • Sample queue states
  • Named order ownership
  • Staff next-step actions
Captured from the working demo. All people, stock, audiences, and results shown are sample data.Enlarge image Try this workspace

Give every visit a clear next step.

A walk-in needs help while a pickup customer arrives for an order. The working sample puts both in a shared queue with an owner and next action. Its Sales floor, Curbside, Delivery and all-orders views illustrate different staff work. Queue movement is not evidence that an order is paid, ready or handed over; confirm those states separately.

Queue paths shown in the preview
VisitProgression
Walk-inWaiting in line → Serving.
Online pickupPending fulfillment → Preparing → Waiting for pickup → Waiting in line → Serving.
CurbsidePreparation → Waiting for pickup → arrival at a parking spot → Waiting in car → Serving.
DeliveryPreparation and dispatch work in the delivery workspace.

At the counter

A little context. A better conversation.

The basket, customer context, and suggested next action stay beside the sale.

BLACKLEAF POINT OF SALEProduct preview
Blackleaf sample checkout for James Gude showing his basket, payment choices, and AI Assist beside the sale.
  • Customer context
  • Cart and totals
  • AI Assist
Captured from the working demo. All people, stock, audiences, and results shown are sample data.Enlarge image Try this workspace

Keep the conversation beside the cart.

The sample checkout places customer context, products, discounts and the basket together. Staff verify sellable stock and explain the actual price and terms. Blackleaf’s POS AI agents are in production in California; the captured AI Assist uses sample data. Confirm supported actions and approval controls for your store.

A quick sale can stay anonymous.

The working sample creates a separate anonymous contact for each quick order, rather than inheriting another customer’s points or messaging preferences. Staff can explicitly assign the order to a person when appropriate. An anonymous application record does not remove the store’s required age, identity or purchase-eligibility checks.

  • Review the items, applicable discounts, purchase limits and total through the supported store procedure.
  • Keep customer arrival, order readiness, payment status and final completion distinct.
  • Confirm actual payment methods, refund rules, reporting and recovery procedures before deployment. A payment choice in a sample screen is not provider approval.

Review the sale before recording completion.

Use this as a planning sequence for the required store workflow, not a claim that every check is automatic. Staff, configuration and supported external services each have a role. Agree which person can resolve an exception and what evidence allows the sale to proceed.

Checkout checkpoints to validate with your store
CheckpointStaff decision and evidence
Visit and customerMatch the right person or permitted guest record, store and order. Complete required eligibility checks through the approved procedure.
Basket and stockConfirm product, package/variant, unit, quantity and current sellable stock. Held or damaged stock must not be treated as available.
Price and benefitsReview discount/reward eligibility, stacking, tax treatment and total. Resolve an unexpected difference before payment.
TenderUse the supported method and actual device/provider workflow. An uncertain acknowledgement needs reconciliation before another attempt.
Completion and handoffConfirm the existing sale/payment state and give the correct receipt or pickup handoff. Avoid duplicate sales or tenders.
Reporting and follow-upReconcile stock and required external reporting. Treat messaging eligibility and event readiness as separate decisions.

Make the exception understandable to the team.

A useful checkout workflow shows staff when to hold, what to check and whom to involve. The following are rehearsal prompts, not promises of automatic recovery, offline selling or a universal override. Preserve existing transaction references when the result is uncertain.

Checkout exception rehearsal
SituationHold and check before proceeding
Payment result is unclearCheck the existing sale and provider result through the supported process. Do not create a second charge just because the screen timed out.
Price or reward differsConfirm the current terms, customer eligibility and staff authority. Re-test the corrected total before payment.
Stock is damaged or heldRemove the unsupported item from the sale, record the issue and review an available alternative with the shopper.
Pickup order changed or was canceledRecheck current order state and customer/store match. Arrival alone is not authorization to complete the old order.
A required connection is unavailableFollow the agreed hold/escalation procedure. Do not assume offline checkout, live tender approval or external reporting continues.

Let the next message follow the right event.

Checkout can supply useful customer or purchase context for a supported texting workflow, but a receipt, completed sale or loyalty record is not marketing permission. Blackleaf texting is available separately from Blackleaf POS and can complement supported existing systems. A POS replacement is not required to improve texting.

  • For an order update, confirm the actual readiness event, current order state, store, recipient and permitted messaging route. A queue label or payment record alone is insufficient.
  • For a return-visit campaign, confirm available completed-purchase history, returns, current permission, recent purchases and contact exclusions.
  • Review copy, offer facts, destination, sender and timing before launch. AI preparation does not establish current stock, customer intent or permission.
  • Keep delivery, replies, opt-outs and matched purchases separate. Attribution does not prove an additional sale caused by texting.

Rehearse your actual counter setup.

The public sample and captured images help your team understand queue and basket behavior. They do not establish migrated customer records, payment-provider support, production device behavior, jurisdiction coverage or checkout speed for your store. 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 and supported operations. Production Metrc approval does not establish all-state coverage, every reporting action or a regulatory endorsement.
  • Use the approved validation environment to test a walk-in, pickup, guest order, reward, changed price, return and unclear tender result as applicable.
  • Test the actual scanner, receipt printer, customer display and payment device. A customer display is not automatically a self-service ordering or payment kiosk.
  • Name the manager and support contacts, agreed coverage and escalation. Record expected versus observed results before accepting the deployment.

Questions worth asking.

Clear answers for planning your store’s next step.

Is Blackleaf checkout available to every dispensary?

Blackleaf POS is in production in 11 states. Confirm the scope of Blackleaf’s production Metrc approval for your licensed facility. Confirm your licensed location, required operations, equipment, payment provider and onboarding.

Does waiting for pickup mean an order is paid and complete?

No. Queue position, preparation, arrival, payment and completion are different states. Staff should verify the current order and supported payment or handoff procedure before recording completion.

Can an order use an anonymous customer record?

The working sample creates a separate anonymous contact for a quick order and does not inherit another customer’s rewards or messaging preferences. That application record does not remove required age, identity or purchase-eligibility checks. Confirm guest-sale scope for the deployment.

Which payment methods are supported at checkout?

Confirm the actual method, provider, geography, device, onboarding and reconciliation procedure for the proposed deployment. A payment choice in the sample is not proof of live approval or support for every tender. Review the payments page and deployment scope.

What should staff do when a payment result is unclear?

Hold the uncertain action and check the existing sale and provider result through the supported procedure before retrying. Preserve transaction references and escalate when needed. Do not create another charge solely because an acknowledgement is missing.

Can checkout continue when the connection fails?

Do not assume universal offline checkout, payment approval or traceability reporting. Confirm supported interruption and reconciliation behavior for the actual setup and train staff on when to hold and whom to contact.

Does the AI Assist capture show a released autonomous POS agent?

No. The capture uses sample data. Blackleaf POS AI agents are in production in California, but the image is not a live transaction or customer result. Confirm supported actions and approval requirements for your store.

Does a purchase give permission for marketing texts?

No. Purchase history and loyalty membership are separate from marketing permission. Keep actual opt-in evidence and current suppression, and confirm the message and provider route are permitted. Blackleaf texting can complement supported existing POS systems without adopting Blackleaf POS.

Does the demo establish checkout speed or deployment readiness?

No. Sample data and captured screens help explore the workflow. Validate staff, migrated records, actual equipment, payment support, required reporting and exception handling for the licensed store. No checkout-time or zero-error guarantee is made here.