A Montana dispensary counter where market evidence is reviewed before pricing and buying decisions

Montana market evidence

See the public menu evidence behind the market read.

Scannabis turns public Montana menu data into pricing, assortment, brand, and report evidence so store owners, brands, and market-entry buyers can decide what to review next.

Evidence flow

Public menu to buyer decision

01

Collect

Public menus, product rows, brands, prices, and source timestamps.

02

Normalize

Comparable categories, pre-tax price reads, store context, and brand naming.

03

Review

Anomaly checks keep obvious display noise out of customer-facing decisions.

04

Route

The same evidence becomes a store action list, brand call sheet, or market report.

What the read is built from

Evidence first, recommendation second.

A useful market read should show the row-level reason behind the advice. These are the evidence layers Scannabis uses before it tells a store, brand, or report buyer what deserves attention.

Coverage

Which menus are usable right now?

Store coverage, source quality, freshness, and product-level depth are kept visible so buyers know what the read can support.

Check data trust

Price movement

Where did the shelf actually move?

Public price indexes show the broad market; paid workflows separate meaningful moves from tax, promo, and menu-display noise.

View price index

Assortment gaps

What should a store review before buying?

Scannabis compares public menus across nearby operators to surface category gaps, brand gaps, and menu-sync issues worth checking.

For retailers

Brand presence

Which accounts fit a brand's next sales move?

Brand reads connect shelf presence, competitor overlap, discount risk, and account fit so reps bring evidence into the buyer conversation.

For brands

Choose the buyer path

Same market data, different job to be done.

A local store, a Montana brand, and an out-of-state diligence buyer need different outputs. The evidence stays consistent; the workflow changes around the decision.

Dispensary owner

What should I price, buy, or check this week?

Use the retailer workflow for local price position, assortment gaps, competitor moves, and public-menu drift.

See retailer workflow

Brand owner

Which stores are worth calling, and where is pricing at risk?

Use the brand workflow for target accounts, shelf presence, price-integrity checks, and sales follow-up.

See brand workflow

Market-entry or diligence buyer

What does the Montana category look like before I commit?

Use focused reports for category economics, city conditions, price ladders, brand density, and expansion questions.

View report samples

Custom scope

Bigger questions get scoped before access is opened.

Chain, portfolio, API, and out-of-state research buyers should not have to guess which subscription button fits. Scannabis reviews the use case first, then routes it to a report, subscription, annual agreement, or custom feed.

Multi-location chains

Roll store reads up across locations without losing the local competitor context each door needs.

Brand portfolios

Scope multiple labels, categories, target-account lists, price-integrity checks, and Product Finder setup before billing.

API and data feed

Custom, annual-only access after review. No cheap self-serve feed that exposes the engine or creates copycat risk.

Out-of-state research

Use a report-first diligence path for market entry, category sizing, acquisition review, or expansion planning.

How to trust it

Built to support review, not automatic overreaction.

Menu data is messy. Scannabis makes that visible instead of hiding it: stale reads are labeled, suspicious moves are checked, and recommendations are framed as decisions to review.

Read data trust notes

Evidence rules

What Scannabis does before a buyer sees the signal

1

Start with public menu data.

2

Normalize prices before comparing.

3

Label stale or weaker sources.

4

Treat signals as review prompts.

Ready for the account-level read?

Use the market evidence against your own store, brand, or diligence question.