One order, from online interest to a familiar welcome.
Explore how Blackleaf connects online order preparation, pickup, curbside arrival, and delivery work with the dispensary queue.
Development preview · Availability and deployment scope confirmed for your store.
Prepare the order before the visit.
The preview separates Pending fulfillment, Preparing, and Waiting for pickup. Staff see the cart and preparation state without confusing a ready order on a shelf with a person waiting for service.
Show each team the work it handles.
Store settings enable the relevant channels. Sales floor includes walk-ins and online pickup preparation; a combined view adds curbside. Delivery has its own workspace, while the back office can review all orders.
| Channel | Handoff |
|---|---|
| Online pickup | Preparation and shelf readiness, then customer arrival in the store. |
| Curbside | Planned QR/app arrival signal with parking spot, then service at the car. |
| Delivery | Preparation, dispatch, and delivery work; live provider connections confirmed separately. |
Keep the online promise connected to the store.
A customer should see the same offer and relevant order information across the visit. The planned connection brings menu availability, order ingestion, notifications, and checkout together. The sample queue demonstrates the staff flow; live customer ordering and parking notifications are future connection work.
- Confirm menu source, stock updates, duplicate-order handling, and canceled orders.
- Agree which notifications are supported and how failed delivery is handled.
- Validate tender, fulfillment, and reporting requirements for the deployment.
Questions worth asking.
Clear answers for planning your store’s next step.
How does POS fit with loyalty and customer history?
The POS direction reuses Blackleaf’s existing customer and rewards foundation. Current development includes customer and rewards context; production earning, redemption, historical migration, and related checkout behavior must be confirmed in the rollout scope. Customer data is not, by itself, marketing consent.
Can our technical team connect other software?
Documented POS interfaces, customer-authorized integrations, and data exports are core roadmap requirements. Review the actual available operations, permissions, event delivery, limits, and fees with Blackleaf before committing to an integration. The existing public Blackleaf messaging API should not be assumed to expose the developing POS functions.
Which payment methods are supported?
Payment methods and providers are confirmed during store onboarding. The development preview is not a promise of live card processing, cashless ATM, ACH, or offline payment support. Ask for the permitted tender types, provider terms, fees, and refund behavior in your deployment scope.