Online orders. Clear pickup updates.

Dispensary online ordering connects a basket with store stock, preparation, payment and pickup or delivery. Blackleaf POS is in production in 11 states. The sample queue illustrates staff work; confirm customer ordering, menu synchronization and arrival integrations for your setup.

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

Start with the supported ordering and texting scope.

A working staff queue, a customer-facing storefront and an order-notification connection are different parts of the system. Confirm which part is demonstrated, which is supported for your store and which is in production in California before setting a launch date.

  • Blackleaf texting can complement supported existing POS and ecommerce systems without adopting Blackleaf POS.
  • The preview uses sample orders and customer data. It is not a live storefront or proof of customer purchases, working provider connections or automatically sent notifications.
What is available and what needs confirmation
AreaScope
TextingAvailable separately. Confirm the supported order source, actual event, recipient, plan and permitted sending setup.
POSProduction POS is available in 11 states. Confirm reporting, licensed-store setup and connections.
OrderingThe sample queue demonstrates staff flow. Confirm customer ordering, menu synchronization and arrival connections for your store’s production setup.

Make the menu promise match sellable stock.

Before accepting an order, establish the source for product identity, price, eligible offers and sellable quantity at the selected store. On-hand quantity, available-to-promise stock, reserved units and stock on hold can mean different things. Use the fields and reservation rules actually supported by the ordering connection.

  • Confirm when stock is reserved: basket entry, order submission, acceptance, picking or another supported event. Do not infer a reservation from a visible menu quantity.
  • Define the response to simultaneous orders, stock corrections, a held package or an item that cannot be fulfilled. A recent sync is not a guarantee the last unit remains available.
  • Keep product substitutions and changed prices in a reviewed customer-service process. An AI suggestion does not authorize changing the customer’s order.
  • Test discounts, expiry, stacking, taxes, fees and pickup location in the actual checkout. A text link or offer preview does not establish redemption or tender behavior.

Give every state a clear meaning and owner.

Agree the order lifecycle between the storefront, POS, staff queue and messaging system. The map below is an acceptance-planning exercise, not a claim that every connector exposes these events or uses these names. A source’s accepted order and a prepared pickup are separate milestones.

  • The Blackleaf sample queue separates Pending fulfillment, Preparing and Waiting for pickup, with customer arrival handled in the staff flow. Confirm actual source-state mapping for the deployment.
  • Keep source event time, version and the latest state with the order. A delayed ready event must not override a later cancellation or collection.
Order lifecycle → evidence before a customer update
StageWhat the handoff must establish
ReceivedA stable order ID, customer and store. Receipt of a request does not establish acceptance, payment or stock reservation.
AcceptedThe store or authoritative system accepted the current order. State separately whether payment, stock and eligibility checks are complete.
PreparingStaff have actually started the required fulfillment work. A timer or printed receipt does not establish preparation.
ReadyThe store’s required preparation is complete and pickup can be offered. Recheck location, hours and current order state.
ArrivedThe customer has checked in through a supported process. Arrival is distinct from shelf readiness, payment and collection.
ClosedCollection or cancellation is recorded under the actual source definitions. Stop stale reminders and reconcile holds, payment and history.

Keep pickup, curbside and delivery handoffs distinct.

Each fulfillment method needs its own customer instructions, operating owner and supported signal. A pickup-ready state does not establish a curbside arrival or a delivery-driver location. Confirm local availability and the specific store process rather than enabling every channel by assumption.

  • Pickup: distinguish a prepared order waiting on the shelf from a person waiting in the physical queue. Confirm store, hours, payment and required identification instructions.
  • Curbside: confirm a supported QR/app arrival source, parking details, staff notification and backup contact process for your store. A pickup status alone does not establish a live arrival connection.
  • Delivery: confirm the supported provider, dispatch event, service area and permitted updates. This page does not establish live driver tracking or a reliable arrival estimate.

Send the update that the order evidence supports.

Choose one owner for each confirmation, readiness and change notice. Your ecommerce platform may already send a notification when it accepts an order. Adding a second automation without checking ownership can duplicate the message or describe a different state.

  • Before a ready alert, verify the active order, actual readiness event, recipient, store, current permission/suppression, usable message and permitted business and route. Missing or conflicting facts mean hold for review.
  • Use minimal order references and a suitable details destination. Avoid exposing unnecessary order contents or private information on a lock screen.
  • A submitted message, successful API response and delivered status are different records. None proves a person read the text, arrived or collected the order.
  • Keep a service update focused on the existing order. Adding a deal or product recommendation changes the purpose and needs a separate eligibility review. A transaction label, neutral wording or age gate does not override a provider restriction.

Test the exceptions before opening the connection.

Use synthetic or otherwise authorized validation records and permitted test recipients. Rehearse one store and one event first. The checklist describes expected acceptance questions, not a certification that all actions are live or a requirement to send a test to an unsupported route.

Ordering and notification acceptance checks
CaseEvidence to review
RepeatThe same source event arrives twice. Show one intended order/action and the actual deduplication responsibility.
LateAn old ready event arrives after collection or cancellation. Show the latest-state check and held reminder.
StockThe final unit changes after menu display. Show reservation, exception handling and reviewed customer contact.
ChangedA partial order, price or return changes. Show the accepted customer record and reconciled payment/stock treatment.
PersonA shared number, changed number, opt-out or wrong-store match. Show exclusion or staff review.
UncertainA connection or send times out. Reconcile recorded activity before retrying an action that may have succeeded.
FailedA notification fails or a customer cannot use the arrival link. Identify a staffed, approved fallback and responsible owner.
ReconciledCompare source orders, fulfillment states, message records and collected/canceled outcomes with matching IDs and periods.

Evaluate conversational ordering by its actual channel.

A conversation that recommends a product, a confirmed ecommerce order and a customer notification are different actions. Ask any AI ordering provider which channel it uses, which stock and price source it reads, how the customer confirms, and what record reaches the store.

  • Flowhub’s Text-to-Order product page describes iMessage/RCS conversations, live Flowhub data and a Flowhub Ecommerce requirement. Do not treat that as ordinary SMS support or transfer its capabilities to Blackleaf.
  • AIQ’s Order Settings guide distinguishes Pending, Confirmed and Ready for Pickup, with notification and integration behavior tied to particular states. Its separate transactional API guide describes approved templates and opt-out handling. These are AIQ-specific rules.
  • Leafbuyer describes online ordering, menu/POS connections and order updates. Reconfirm exact fields, state mapping and timing for the proposed account; marketing language does not establish every connector behavior.
  • Blackleaf’s connected POS AI agents are in production in California. Available AI texting preparation has its own scope; a generated draft does not accept an order, reserve stock, verify customer eligibility or send a campaign automatically.

Measure the order journey and improve the next handoff.

Review elapsed time from the actual source event to staff action and notification outcome. Keep unmatched, failed and unknown records visible. A delivered alert is not a completed pickup, and a change after launch does not alone establish that texting caused it.

  • Define collected, canceled and uncollected orders using one observation period, location scope and source-state mapping.
  • Review duplicate alerts, status questions, reply handling and message costs alongside order volume and staffing changes.
  • Keep operational order updates separate from optional marketing attribution. Use the primary texting measurement guide when evaluating incremental campaign outcomes.
  • Confirm the final rollout scope, acceptance owner and pause/recovery process before expanding. Production Metrc approval does not establish all-state ordering, every connection or universal compliance.

Questions worth asking.

Clear answers for planning your store’s next step.

Is Blackleaf online ordering publicly available today?

Blackleaf POS is in production in 11 states. Confirm the scope of Blackleaf’s production Metrc approval for your licensed facility. The sample queue demonstrates staff work. Confirm customer ordering, menu synchronization and arrival integrations for your licensed store.

Do I need Blackleaf POS to send order updates?

No. Blackleaf texting is available separately and can complement supported existing POS or ecommerce systems. Confirm that the actual source supplies the required order event, identity, location and timing, and review the permitted messaging setup. Customer or completed-purchase synchronization alone does not establish a pickup-ready event.

Is an accepted order ready for pickup?

Not necessarily. Acceptance means the source or store accepted the order under its process. Ready means the required fulfillment preparation is complete. Keep payment, stock reservation, eligibility, readiness, arrival and collection separately defined, and send only an update supported by the actual state.

Does a live menu guarantee the product is available?

No. Stock can change through concurrent orders, sales, holds or corrections. Confirm the supported sellable quantity, update delay, reservation point and exception process at the selected store. Recheck the actual order before promising fulfillment or substituting a product.

How can we avoid duplicate order notifications?

Give each notice one responsible system and map the authoritative event. Test repeat source events, overlapping ecommerce and messaging automations, and uncertain retries. Keep stable order/event identifiers and recorded outcomes. Confirm the actual deduplication behavior; do not assume every connector or send endpoint prevents duplicates.

What happens when an order is canceled before an alert?

Recheck the latest authoritative state before a queued reminder or retry. A stale ready event should not trigger travel instructions after cancellation or collection. Reconcile stock, payment and history under the supported source process, and route any necessary correction to the responsible staff workflow.

Does Blackleaf currently notify staff of a curbside parking spot?

Confirm QR/app arrival, parking handoff, staff notification and the fallback process for your production store setup. A sample queue or pickup-ready state is not a live curbside or driver-tracking connection.

Is text-to-order the same as ordinary SMS?

No. Verify the actual channel and product. For example, Flowhub’s Text-to-Order documentation describes iMessage/RCS and requires Flowhub Ecommerce. That does not establish ordinary SMS capability or Blackleaf support for the same ordering actions. Channel, provider, business and use-case requirements need separate review.

Can Blackleaf POS AI accept an order or reserve stock?

Connected Blackleaf POS AI agents are in production in California. Confirm supported actions and approval for the deployment. Available AI texting preparation is separate; a generated product suggestion or message draft is not order acceptance, a stock reservation, customer eligibility verification or campaign launch.

Does a delivered order text prove a completed pickup?

No. A delivery state describes message handling. Read, customer arrival, collection and completed sale are separate events that need their own source evidence. Reconcile the order ID, store, state and time period before reporting a pickup outcome or causal improvement.