Dispensary reporting you can reconcile.
Dispensary POS reporting explains store activity: sales, returns, inventory movement and customer visits. Connect those records to supported texting data to examine campaign response. Keep operational totals, attributed purchases and estimates of incremental impact separate; they answer different questions.
In production in 11 states. Nevada, Ohio, and Colorado are expected in January 2027. See supported states.
Start with the question behind the number.
A sales report helps reconcile what happened in the store. Campaign attribution connects qualifying activity with messaging under a stated rule. Incremental measurement asks what changed because of the campaign. A dashboard can present all three, but a purchase after a text is not proof that the text caused it.
- Use the map below to label the report before acting. It describes measurement types, not a list of automatically enabled Blackleaf reports.
- Blackleaf texting is available separately and can complement supported existing POS systems. You do not need to switch POS to evaluate a texting measurement workflow.
| View | Question it answers | Evidence needed |
|---|---|---|
| Operations | What sold, returned or moved? | Source transactions, states, dates, locations and definitions. |
| Attribution | Which qualifying purchases match the campaign? | Recipient and purchase identities, message event, window and credit rule. |
| Incremental impact | What likely changed because of the campaign? | A suitable comparison design, consistent outcomes, costs and uncertainty. |
Reconcile the store report before ranking performance.
Choose a closed reporting period and record the time zone, order state and date used. An order placed before midnight but completed later can fall into different periods under different definitions. Check the transaction detail behind a summary before treating two totals as comparable.
- Distinguish gross sales, net sales, tax, tender and refunds. The same label can have different inclusions across reports.
- State whether a return is recognized on its processing date or attached to the original order period. Reopened or corrected records can change a later export.
- Keep completed orders, unique buyers and customer profiles separate. A person can place several orders or have duplicate records.
| Measure | What to record |
|---|---|
| Sales | Gross/net basis; discounts, returns, taxes, fees and included order states. |
| Orders | Unique order identifier, completed/void/cancelled treatment and date used. |
| Customers | Stable identity, duplicate handling and anonymous or unmatched purchases. |
| Inventory | Product/package, location, movement type, sellable stock, holds and as-of time. |
| Margin | Actual product cost, returns, vendor reimbursements and included selling costs. |
| Coverage | Locations, channels, historical start, missing records and last complete update. |
Trace a text through to the purchase record.
Before the campaign, agree the eligible audience, matched customer identity, stores, message event and attribution window. Keep submitted, delivered, failed and unknown messaging outcomes distinct. A click, landing-page visit, redemption and completed order are separate events; an SMS delivery state does not prove that a person read the text.
- Join using supported stable identifiers. Record unmatched purchases and duplicate profiles rather than forcing every sale onto a recipient.
- Choose the credit rule for overlapping campaigns and channels before reviewing revenue. Select the window before launch; report it with the result.
- Reconcile message usage, platform allocation and operating costs with net sales and margin. Do not subtract a discount twice if it already reduces net sales.
- For an appropriate randomized marketing holdout, retain the original assignment in the primary comparison, including failed sends. Report delivery diagnostics separately.
Compare locations without counting the same person twice.
Use consistent dates, definitions and channel scope when reviewing stores. Sum comparable additive amounts, such as net sales under one definition. Recalculate rates from the underlying counts; do not average store percentages without their denominators. A portfolio total should allow a manager to explain the location-level records behind it.
- A shopper who visits two stores can be one portfolio customer and a customer at each store. Define the question before counting.
- Keep store of purchase, preferred store and sending location distinct when matching a campaign.
- Account for different opening hours, stock availability and store launch dates. A percentage change alone does not establish staff performance.
- Confirm location permissions, aggregation, export access and any cross-location identity support in the actual rollout.
Keep the report’s refresh time and source with it.
A real-time screen label does not establish that every source or derived metric has finished updating. Record the source event time, last successful sync, report generation time and the period considered complete. Re-run a reconciliation after late transactions, returns or corrections under a documented policy.
- Keep the exported report, filters, definitions, source IDs and known exceptions together. Limit customer detail to the staff who need it.
- Save the closing snapshot with its cutoff. If a later report for the same store, period and filters differs, keep both exports and trace late transactions or corrections by transaction ID before updating the closeout record.
- Confirm supported formats, retention, historical coverage and permissions. A sample download or API logo does not prove every production export is available.
- Blackleaf’s Monthly Billing workbook and successful-payment receipts document usage and payment records. They are separate from POS sales reports and campaign lift analysis.
Bring one reconciliation exercise to every demo.
Ask each provider to walk from a summary to the source records, then to an export using the same scope. Use synthetic or otherwise authorized validation data. Mark each required report as shown, documented, pending or not needed, with its definition, freshness, owner and proposed package.
- Dutchie’s sales documentation distinguishes order-date and transaction-state criteria and defines calculated fields. AIQ’s reporting guide distinguishes attribution settings and reporting periods and describes update delays. Happy Marketers presents attributed sales and winback reporting. These sources are useful prompts for definitions, not independent proof of incremental return.
- Official sources reviewed October 15, 2026. Confirm the proposed account and connector; this page does not rank providers or establish reporting superiority.
| Check | What to demonstrate |
|---|---|
| Source | One completed order, discount, cancellation, partial return and duplicate event. |
| Totals | Explain how source records become gross/net sales, orders, tax and margin. |
| Time | Show the cutoff, time zone, source delay and last complete reporting period. |
| Matching | Show one matched customer and one unmatched or anonymous purchase. |
| Credit | Explain the message event, campaign window and overlapping credit rule. |
| Locations | Reconcile store totals, a cross-store shopper and restricted staff access. |
| Export | Reproduce filters and IDs; confirm supported format, retention and history. |
| Decision | Separate a descriptive result, an attributed purchase and a causal estimate. |
Turn an explained finding into a reviewed action.
Use a reconciled finding to form the next inventory, audience or offer hypothesis. Check fresh stock, current permission, customer relevance and the permitted messaging route before preparing outreach. A successful sales match does not create marketing permission or authorize a restricted route.
- Blackleaf has a working POS in production in 11 states. Confirm the scope of Blackleaf’s production Metrc approval for your licensed facility. Confirm the supported reports and jurisdiction; approval is not all-state coverage or an accounting audit.
- Connected POS AI agents are in production in California. A sample Insights screen or AI suggestion does not establish live cross-system analysis, an executed inventory change or a sent campaign.
- Blackleaf’s available AI texting preparation has its own scope. Review the actual data and generated content before testing or launch; report the evidence behind any recommendation.
Explain the drawer difference before closing.
Download the editable cash closeout worksheet to compare expected and physically counted cash for one drawer, session, cutoff and currency. Its three tabs contain instructions, eight cash-movement inputs and an exception log. Amounts and source references start blank. This is a generic planning workbook, not a released Blackleaf cash report, POS connection or automatic drawer-close feature.
- Expected cash equals opening float plus cash receipts, minus cash refunds, plus other cash paid in, minus payouts, outgoing transfers and earlier drops, plus a documented signed adjustment. Use the same scope throughout and avoid counting the same movement twice.
- Enter evidenced zeros when no movement occurred; leave unknown values blank. The workbook requires movement references and amounts with two decimal places. It provides no discrepancy tolerance, automatic approval or explanation for a variance.
- Review recounts, tips, late transactions, transfers, missing receipts and duplicate movements under the approved store procedure. Keep an exception owner, next action and reviewer; never use an unexplained adjustment simply to make totals match.
- Cash reconciliation is separate from Texting attribution, profit and incremental campaign results. Blackleaf Texting can be evaluated with supported existing POS systems without a POS switch.
| Record | Check before comparing |
|---|---|
| Receipts | Use actual cash retained after customer change, with the report basis and source reference. Revenue, card sales, processor settlement and campaign-attributed sales are different records. |
| Refunds and movements | Record cash refunds, paid-ins, payouts, outgoing transfers and prior drops once each. Do not subtract a refund already netted from receipts or a drop already listed as another withdrawal. |
| Count | Count the cash in this drawer at the agreed cutoff and record it before viewing expected cash if your store uses a blind count. Keep earlier drops separate. If you recount, record the second count alongside the first. |
| Variance | The worksheet subtracts expected cash from counted cash. Positive is over; negative is short. Missing inputs remain unknown, and even a zero difference still requires review. |
| Next-shift float | The optional planning amount is counted cash minus the approved retained float. It excludes earlier drops and does not establish a bank deposit, settlement or authorization to move money. |
Questions worth asking.
Clear answers for planning your store’s next step.
What does a positive or negative cash-drawer variance mean?
In this worksheet, variance is physically counted cash minus expected cash for the same drawer, session, cutoff and currency. A positive amount is over; a negative amount is short. Missing inputs leave the result unknown. Recount and review the source movements through the approved process; zero difference still requires review. The workbook does not close a drawer, authorize an adjustment or set an acceptable discrepancy tolerance.
What should a dispensary POS report include?
Define the report’s purpose, period, time zone, locations and included order states. Useful operational records include sales, discounts, returns, tax, orders, product movement and customer identity where available. Confirm actual fields, calculations, history and exports for the proposed deployment rather than assuming every report is included.
Why can two dispensary sales reports show different totals?
Reports can use different order dates, completion states, time zones, location filters, discounts, returns, taxes, fees or update timing. Compare definitions and source transaction IDs before deciding a total is wrong. Reconcile late returns and corrections using the stated reporting policy.
Is POS sales reporting the same as SMS attribution?
No. POS reporting describes store transactions and operations. SMS attribution matches qualifying activity with a campaign under a defined identity, event, window and credit rule. The match does not prove that the message caused the purchase or that the campaign was profitable.
Does attributed revenue prove incremental sales?
No. Some recipients would have purchased without the campaign. A suitable randomized marketing holdout can help estimate incremental outcomes with consistent definitions and uncertainty reporting. Keep original group assignment in the primary comparison, including failed sends. A prior-period trend does not have the same causal strength.
Can I add each store’s unique customer count?
Not to obtain a unique portfolio count when the same person can shop at several locations. Define stable identity and duplicate handling, then distinguish store-level customers from unique people across stores. Orders, buyers and profiles are different measures; confirm actual cross-location matching support.
Are all Blackleaf POS reports and connections real time?
Do not assume that. Confirm the supported report and connector, source-event timing, sync frequency, correction handling and last complete period for the selected deployment. A live screen or demo does not establish fresh data from every connected source.
Is a Monthly Billing workbook a sales or ROI report?
No. Blackleaf’s released Monthly Billing workbook covers prior-calendar-month workspace usage, with Month, Location, Rate, Phones and Messages columns and calculation notes. Successful-payment receipts are separate payment records. Neither document, on its own, establishes POS sales, profit or incremental campaign return.
What should we confirm about reporting exports?
Review actual available reports, formats, stable IDs, columns, filters, time zone, history, retention and permitted staff access. Reconcile the export to the source and keep definitions and known exceptions with it. A preview, general API description or vendor logo does not confirm every production export.
Can POS AI automatically act on a report today?
Connected Blackleaf POS AI agents are in production in California. Confirm supported actions and approval controls for the deployment; a sample insight does not establish a completed price, stock or campaign change. Available AI texting preparation is separate and still needs verified source facts and the applicable review.
Do we need Blackleaf POS to measure Blackleaf texting?
No. Blackleaf texting is available separately and can complement supported existing POS systems. Confirm the authorized connection or data method, customer matching, purchase and return fields, costs, update timing and the reporting plan. POS adoption is a separate store-operations decision.