Built for Cannabis Dispensaries

The CRM dispensaries actually run their shop out of.

A dispensary general manager runs a compliance-first retail business where the regulator can walk through the door on a Tuesday afternoon and ask for a 36-month purchase log. The CRM has to hold the patient card, the recreational loyalty ledger, the age-gate on every outbound text, and the Metrc or BioTrack handoff for every unit of flower that leaves the store. Most CRMs built for retail cannot do half of that out of the box, and most seed-to-sale platforms do not do CRM at all.

Start free trial See pricing
What this audience is actually dealing with

The pains that bring buyers here.

A dispensary operator is running three businesses stapled together. A retail shop with budtenders, foot traffic, and a POS that has to reconcile to the penny. A compliance operation that answers to a state regulator with 300 pages of rules that change twice a year. And a customer loyalty engine that is the only durable moat against the dispensary 400 feet away that opened last quarter. Most retail CRMs assume the loyalty, outreach, and reporting side is the whole picture and ignore the compliance substrate. Most seed-to-sale platforms assume the Metrc handoff is the whole picture and ignore the customer. Strkr for dispensaries is the one workspace where the patient record, the loyalty tier, the age-gated outbound, the Metrc or BioTrack reference, and the regulator-ready audit log all live on the same timeline. The five pains below show up on every discovery call we run with licensed cannabis retailers, from a single-store Michigan shop to a 40-location MSO running Colorado, Arizona, New Mexico, and Illinois. If any of them read like a Tuesday morning in your store, the rest of the page shows how Strkr collapses the stack back into one record of truth for every customer who walks through the door.

Compliance tracking lives in a spreadsheet

The regulator asks for a 36-month purchase log and I open Excel.

State regulators (CRC in New Jersey, DCC in California, OMMA in Oklahoma, MRA in Michigan, MED in Colorado, OCM in New York) can request a purchase history for a given patient card or recreational customer going back the full retention window. In most dispensary stacks that record is scattered across the POS, the Metrc API log, a loyalty vendor dashboard, and the budtender notes. Strkr threads the purchase, the Metrc reference, the budtender who rang the sale, the ID check artifact, and the loyalty redemption on one customer timeline with a 36-month default retention and audit export in under a minute.

State rules change every quarter

A new rule drops and nobody tells the budtender until a fine lands.

State cannabis boards publish rule updates on their own cadence: purchase limits shift, equivalency formulas change, THC caps on edibles get redrawn, delivery radius rules move. In a dispensary with 20 budtenders the signal gets lost between the compliance officer email and the register. Strkr Flows push rule-change bulletins to the budtender dashboard with an acknowledgement step logged to the audit trail, and purchase-limit math updates centrally so a Michigan shop running a 2.5-ounce flower equivalency cap does not accidentally overserve on a concentrate purchase.

Loyalty points, no loyalty insight

I know who earns points. I do not know who my best customers are.

Most dispensary loyalty tools stamp a QR code on a receipt and tally points. That is a ledger, not a CRM. The GM cannot answer "which 100 customers drove 40 percent of my concentrate margin last quarter," cannot segment by product preference, cannot see which patients lapsed after a strain was discontinued. Strkr pairs the loyalty ledger with real customer segmentation: tier membership, product-category spend, visit cadence, lapsed-customer flags, patient-vs-rec split, and preferred-strain history. The GM runs campaigns on segments that matter, not on everyone with a punch card.

Inventory handoff friction

The POS says one thing, Metrc says another, the shelf says a third.

Every unit of cannabis in the store carries a Metrc or BioTrack tag that must reconcile to the POS inventory count, which must reconcile to the physical shelf, which must reconcile to the receipt the customer leaves with. When those three systems drift the dispensary eats either a shrinkage write-off or a regulator finding. Strkr sits beside your POS (Dutchie, Treez, Flowhub, Blaze, Cova, Meadow) with a reconciliation view that surfaces drift on the customer record so a budtender notices before the end-of-day close instead of three days later during the audit.

Outbound messaging in a legal minefield

Every text to a customer could trigger a TCPA complaint or a state cease-and-desist.

Cannabis dispensaries operate under a federal illegal substrate, state-level marketing restrictions (no appeals to minors, no health claims, no public-way advertising in some states, mandatory opt-in language), and the TCPA on every outbound SMS. Strkr Messaging ships with age-gate enforcement on the contact record, state-specific marketing language rules at the template level, double opt-in capture with timestamp, and a cease-and-desist suppression list so an "unsubscribe" never gets re-messaged by a different campaign. Compliance teams review the sent log on the audit timeline, not a vendor dashboard with export limits.

Patient vs recreational data split

My medical patients and my rec customers are the same person half the time.

A dispensary serving both patient and recreational customers (dual-license states like Michigan, Illinois, New York, Massachusetts, Maine) has to track medical card status, expiration, caregiver linkage, and tax treatment separately from the recreational purchase record even when the human is the same. Most CRMs force a split profile that breaks the loyalty ledger. Strkr holds one person record with patient status and expiration tracked as structured fields, tax treatment auto-selecting at purchase, caregiver linkage captured, and a single lifetime value number across both channels.

How Strkr fits the dispensary day

The primitives a dispensary GM actually uses.

Strkr for Cannabis Dispensaries is not a different product than Strkr for retail or Strkr for healthcare. It is the same CRM configured for a licensed cannabis retail workflow with the compliance substrate turned on, the age-gate enforced on every outbound surface, the Metrc or BioTrack reference carried on every purchase, and the loyalty ledger wired into the person record. Everything below ships on every paid tier with no premium compliance module or add-on gate. The primitives are shaped around what a dispensary team repeats every shift: ringing a sale with the right compliance checks, servicing a returning customer with the right loyalty tier, following up with a lapsed patient without crossing a marketing rule, and producing an audit log on demand when the state inspector walks in.

Customer record

One profile for the patient and the rec shopper.

The customer record pulls in patient card number, card expiration, caregiver linkage, recreational status, age verification method and timestamp, loyalty tier, lifetime value, product-category spend, preferred strains, delivery address (where legal), and a full purchase history with Metrc or BioTrack references on every line. The budtender opens the record at the register and sees the compliance checks pass or fail in real time.

Compliance timeline

Every regulated event on one audit log.

Age-check at the door, ID scan artifact, patient card verification, Metrc reference captured on the sale, purchase-limit math pass or fail, loyalty redemption, cease-and-desist flag, outbound message consent. Every event lands on the customer timeline with a timestamp, the budtender or system actor, and the exact rule applied. The state inspector gets a filtered export of the regulated events in a single click.

Loyalty tier

Points, tiers, and real segmentation on one surface.

Loyalty is not a bolt-on. The ledger lives on the customer record with configurable earn rules (dollars, visits, product category), tiered benefits (Bronze, Silver, Gold or custom), expiration windows, redemption history, and tier-change triggers. The GM runs a Gold-tier flower-only campaign in two clicks without exporting to Mailchimp. Patient and rec tiers can share one ledger or stay separate per tenant policy.

POS sync

Dutchie, Treez, Flowhub, Blaze, Cova, Meadow handoff.

Strkr sits beside your dispensary POS with a real-time webhook on each sale. The transaction, line items, Metrc or BioTrack tag references, budtender ID, discount applied, and loyalty redemption flow into the customer timeline the moment the receipt prints. Reconciliation views flag any drift between the POS totals and the customer ledger so the end-of-day close never finds a surprise.

Age-gated messaging

Strkr Messaging with cannabis guardrails on.

Every outbound SMS and email runs through an age-gate check against the stored verification artifact, a state-marketing rule check against the template, a double opt-in verification against the consent timestamp, and a cease-and-desist suppression check against the global list. A template that violates a state rule (health claim, youth appeal, inventory-specific pricing where restricted) does not send. The compliance officer reviews the sent log on the audit timeline.

Patient card expiration

Expiring cards surface before the sale blocks.

The Flow runs daily against every active patient and surfaces cards expiring in the next 30, 14, 7, and 1 day on a dedicated view. The budtender sees the warning on the customer record at the register. An outbound SMS fires at 14 days with the renewal link where state rules allow. Patients never show up at the counter surprised that their card lapsed and the dispensary never has to downgrade a sale mid-transaction.

Mobile for the floor

The GM runs the shift from a tablet.

Strkr mobile is first-class with offline queue, barcode and ID scan from the device camera, customer lookup, loyalty redemption, and compliance log entry. The GM walks the sales floor with a tablet, pulls up a returning customer in two taps, confirms their patient card, redeems a loyalty reward, and the audit trail writes itself. Nothing dies when the Wi-Fi hiccups because the queue syncs on reconnect.

The compliance substrate

Regulator-ready records, not a dashboard screenshot.

Every state cannabis regulator can request specific records on specific retention windows. California DCC: 7-year retention on commercial records. Michigan MRA: 5 years on sales history. New York OCM: 5 years with 36-month customer purchase lookback on patient records. Colorado MED: 3 years on commercial, 5 on video. Oklahoma OMMA: 7 years on patient records. The retention policy per tenant surface in Strkr lets the compliance officer set the window once and have every automation, export, and purge flow respect it. The compliance primitives below are the ones a dispensary needs on day one, not six months in after the first audit finding.

Retention policy

Per-record-type retention windows per tenant.

Compliance officer sets the retention per record type (sales, patient records, video, employee logs, delivery manifests) at the tenant level. Purge flows respect the policy and surface a review step before any destructive action. The regulator's retention requirement is the floor, not the ceiling, so dispensaries can hold longer where business needs it.

ID scan capture

Age verification artifact on the record.

Every age-check at the door or at the register captures an ID scan artifact (where state rules permit storage) or a verification confirmation code (where storage is restricted) with timestamp, method, and verifier. The customer record carries the latest verification and the full history. A regulator asking 'how did you verify this customer was 21?' gets an answer in two clicks.

Metrc + BioTrack reference

Every sale line carries the state-system tag.

Each purchased unit lands on the customer timeline with its Metrc tag (CO, CA, MI, MA, MO, OR, NV, OH, MD, MT, SD, LA, AK, NM, MN, VT, DC) or BioTrack tag (WA, NM for some licenses, HI, DE, ND, NJ) captured from the POS webhook. A regulator subpoena for 'all sales of this batch to this customer' is a saved view, not a data engineering project.

Purchase-limit math

Equivalency formulas enforced at the register prompt.

State-by-state purchase limits (ounces of flower, grams of concentrate, mg of THC in edibles, mg per package, per-day vs per-transaction) run as centrally-maintained equivalency formulas. When the budtender rings a mixed cart the math runs live and the register surfaces a block or a warning. A rule change on the state side pushes to every store without a POS reconfig.

Loyalty redemption rules

Discount caps per state, enforced on redemption.

Several states cap loyalty discounts (percentage, dollar amount, categories excluded from discounting like excise-taxed items in CA). Strkr enforces the cap at redemption so a Gold-tier customer in California does not accidentally redeem a reward on a product where the discount is prohibited. The audit log carries the attempted redemption and the applied rule.

Audit export

One click to a regulator-ready file.

The compliance officer picks the record type, the date range, the customer scope, and the state format (CRC JSON, DCC CSV, OMMA XML, MRA export spec, MED template). Strkr renders the export, logs the export action to the audit trail, and the file is ready to drop in the regulator portal. Preparing for an inspection is a saved view, not a weekend.

Rule-change bulletin

State rule updates pushed to the budtender dashboard.

When a state rule changes (purchase-limit update, equivalency change, marketing restriction tweak, licensing deadline) the compliance officer publishes a bulletin on the Strkr admin surface. Every budtender dashboard shows the bulletin on next sign-in with a required acknowledgement step logged to the audit trail.

Loyalty and segmentation

The customer insight most dispensaries never get.

A dispensary has a thin menu moat and a loud neighbor-shop problem. The only durable advantage is a loyalty program that actually understands the customer. Strkr turns the loyalty ledger from a punch-card into a segmentation engine with product-category spend, visit cadence, strain preference, patient-vs-rec channel split, and lapsed-customer flags. The six primitives below are what a dispensary GM uses in week two to run their first segmented campaign that actually moves repeat visits.

Tier membership

Bronze, Silver, Gold, custom tiers with threshold rules.

Tiers are configurable per tenant with dollar-earned, visits-per-period, or product-category thresholds. Tier upgrades and downgrades fire Flows so a customer hitting Gold gets a welcome text (where consented) and a tier-exclusive campaign surface. Patient and rec tier structures can share rules or diverge per tenant policy.

Product-category spend

Flower, concentrate, edible, pre-roll, topical splits.

Every purchase line hits a category totaliser on the customer record. The GM sees that a customer is 80 percent concentrates in six months and runs a dab-rig accessory campaign to that segment. Category-level LTV surfaces in reporting so the merchandising team knows which categories drive the stickiest customers.

Visit cadence

Weekly, biweekly, monthly, lapsing customers flagged.

The customer record carries their average visit interval, their last visit date, and a lapsed flag if the gap exceeds the normal cadence by a configurable multiplier (default 1.5x). A biweekly regular who has not shown up in six weeks surfaces on the GM 'at-risk' saved view with a one-click win-back campaign enroll.

Strain preference

Indica, sativa, hybrid, cultivar-level history.

Strain and cultivar from the Metrc or BioTrack reference land on the customer purchase history. The record shows the top three strains or cultivars by frequency so a budtender making a recommendation on the floor knows what the customer has bought before and what adjacent products might land. A discontinued-strain alert flags customers who regularly bought a cultivar the inventory team is retiring.

Patient vs rec channel

Dual-license dispensaries with one person record.

In a dual-license state (MI, IL, MA, ME, NV, NY, NJ, MD, VT, CA for the few integrated storefronts) the same human is often both a medical patient and a recreational customer. Strkr holds one person record with both channels tracked, tax treatment auto-selecting at the register based on the active status, and the loyalty ledger consolidated across channels with per-channel reporting.

Caregiver linkage

Patient caregivers tracked and purchase-limit-aware.

In medical states where a registered caregiver can purchase on behalf of a patient (OK, MI, ME, NM, AZ, several others) the caregiver is linked to the patient on the record with each caregiver carrying a separate purchase limit math. The register knows which patient the caregiver is buying for, the state purchase-limit calculation runs correctly, and the audit log carries both identities on the sale.

Flows for the dispensary motion

Automations that cover the full retail cannabis shift.

The best dispensary teams do not run their shift on budtender memory. They run it on a dozen Flows that handle the quiet operational drag so the budtender spends their energy on the customer interaction. Strkr Flows cover the dispensary automations every store needs out of the box, each shipping as a native trigger with no webhook plumbing. The pattern below is what shows up in week two of every dispensary deployment, and compounds into cleaner compliance, higher loyalty engagement, and faster end-of-day close.

Age-check capture

Every door entry captures a verification artifact.

A greeter scans an ID at the door and the Flow creates or updates the customer record with the verification method, the artifact (stored or hashed per state rule), the timestamp, and the greeter actor. The budtender at the register sees the age-check passed indicator on the record and the compliance log is already written.

Patient card verification

Card expiration checked against the state registry.

The Flow verifies patient card status against the state registry API where available (OMMA, MRA, OCM, DCC caregiver lookup) or against the stored card image artifact where API access is not available. Expired or invalid cards surface a block on the register and route the customer to the recreational workflow where legal.

Purchase-limit enforcement

Mixed cart math runs live before total.

At cart total, the Flow runs the state purchase-limit math across all cart lines (flower weight, concentrate grams, edible THC mg, pre-roll count) and surfaces a block or warning on the register. A regulator finding on an over-limit sale is prevented at the system boundary, not caught three months later.

Loyalty earn + redeem

Points earned and redemptions logged on the sale.

Every POS webhook fires a Flow that calculates earned points per the tenant rules, applies any in-flight redemption, respects state loyalty discount caps, and writes both events to the customer ledger. The budtender sees the updated tier status on the next sale without a manual sync.

Lapsed-customer win-back

Dormant customers get a compliant outbound.

Daily Flow finds customers whose visit cadence has slipped past the lapsed threshold with active SMS consent. Pushes a win-back SMS using a state-compliant template (no health claims, no youth-appeal content, no public-way advertising promises) with a loyalty-tier-appropriate incentive. The GM sees the campaign results on the saved win-back dashboard.

Patient card renewal

Expiring cards get a renewal nudge.

Daily Flow finds patient cards expiring in the next 30, 14, 7, 1 day. Sends a renewal nudge where state rules allow (OK and MI permit renewal reminders, some states restrict). The budtender dashboard shows the expiring-cards saved view so a renewing patient is handled at the counter without a surprise block.

End-of-day reconciliation

POS totals cross-checked against the customer ledger.

At shift close, the Flow pulls the POS end-of-day report and reconciles it against the sum of customer-ledger events for the day. Drift surfaces on a reconciliation view with the specific sales lines flagged. The GM resolves drift that night, not three days later when the regulator-ready export fails validation.

What the compliance officer sees

Views that make the Tuesday inspector visit a non-event.

A good compliance officer does not want surprises when the inspector walks in. Strkr surfaces the records a regulator would request on a saved view that is always current. The views below ship as defaults for the compliance role on every tenant and can be duplicated and personalised without an admin ticket. If the state format requires a particular export shape, the audit export surface lets the officer pick the format at run time and the file is ready in under a minute.

Daily sales audit

Every sale, every Metrc tag, every budtender.

The daily sales audit shows every sale with the Metrc or BioTrack tag, the budtender actor, the age-check artifact, the patient-vs-rec channel, the purchase-limit math result, and any loyalty redemption. Drill into any row for the full timeline. The inspector asks for the Tuesday sales log and the officer renders a 90-second export.

36-month customer lookup

Full purchase history for any customer on request.

Pull a customer by card number, last name, phone, or email and surface their 36-month purchase history with Metrc references, loyalty events, consent timestamps, and compliance-event history. The inspector asks for a specific patient and the officer surfaces the record while the inspector is still typing.

Age-check failures

Every under-21 attempt logged for review.

Under-21 or expired-card attempts land on an age-check-failure view with the greeter, the method, the artifact (where legal), the timestamp, and the next action taken. A regulator asking how the store handles underage attempts gets a documented pattern of refusals with full timeline.

Over-limit blocks

Carts that would have exceeded purchase limits.

A view of every cart that triggered an over-limit block, with the budtender, the mixed-cart composition, the math result, and the resolution (reduced sale, refused sale, split transaction). Patterns of near-limit activity flag customers worth a compliance review and show the regulator a defensive posture.

Consent and suppression

Who opted in, who opted out, who is suppressed.

Every SMS and email consent event lives on the customer record and rolls up to a consent view. Opt-outs, cease-and-desist flags, and suppression entries carry a timestamp and reason. TCPA complaints become a resolved audit event, not a legal threat, because the opt-out trail is on the record.

Rule-change acknowledgement

Which budtenders have read the latest bulletin.

Rule-change bulletins from the compliance officer require an acknowledgement step from every budtender. The acknowledgement view shows who has read what, who is overdue, and which store has the most friction on compliance updates. The regulator asking 'how do you push rule changes to the floor' sees the trail.

Head-to-head

Strkr for Dispensaries vs the typical cannabis retail stack.

A typical dispensary stack runs a seed-to-sale platform (Metrc or BioTrack) for the regulator interface, a cannabis POS (Dutchie, Treez, Flowhub, Blaze, Cova, Meadow) for the register, a loyalty vendor (springbig, Alpine IQ, Fyllo, Sprout) for the ledger, a separate marketing suite for SMS and email, and a compliance log that lives in a shared drive. Strkr collapses the loyalty, marketing, customer, and audit layers into one workspace that sits beside your POS and Metrc, with one bill, one admin surface, and one record of truth per customer.

Feature Strkr Typical dispensary stack
Number of tools the GM opens daily 1 (Strkr) plus your POS 4 to 6
Metrc / BioTrack reference capture Native, carried on every customer purchase line POS only, not linked to customer record
Age-gated outbound messaging Strkr Messaging with age-check, state-rule, and consent enforcement Separate SMS vendor, manual compliance review
Loyalty ledger Native with tier rules, product-category spend, segmentation Separate loyalty vendor, exported for marketing
Patient card expiration tracking Native Flow with 30/14/7/1-day nudges and register block Manual review, often caught at the counter
Purchase-limit math Centrally maintained, enforced at register prompt POS-configured per store, drift between locations
Caregiver linkage Native with per-patient purchase-limit math Spreadsheet or paper file
Audit export One-click, state-specific format, logged action Manual CSV pull from 3+ systems
Rule-change bulletin Native budtender dashboard with ack logged Compliance officer email, no ack trail
Dual-license patient + rec profile One person record, both channels, consolidated LTV Split profiles, broken loyalty ledger
Mobile for the floor First-class with offline queue, barcode and ID scan POS mobile wrapper, limited customer surface
Admin changes Self-serve for compliance officer and GM Multiple vendor tickets, cross-system coordination
How teams use Strkr

How dispensary teams run Strkr.

The patterns below show up across dispensary operators from a single-store Michigan shop to a 40-location multi-state operator running CA, CO, NM, IL, MI. The common thread: collapse the compliance, loyalty, outreach, and customer records into one surface so the budtender spends their shift on the customer and the compliance officer stops living in spreadsheets. Each playbook is a motion a Strkr dispensary runs today, not a hypothetical from a demo.

Single-store Michigan dispensary

Dual-license shop with patient and rec loyalty on one ledger.

A single-store Michigan MRA licensee running both medical and adult-use (common in MI) moved off a loyalty vendor plus a separate SMS tool plus a shared-drive compliance log. The customer record now holds patient card status, expiration, caregiver linkage, rec purchase history, and loyalty tier on one profile. End-of-day reconciliation catches drift between the POS and the Metrc counts the same night. The compliance officer runs the state audit export in under five minutes. Monthly loyalty engagement doubled in the first quarter after the segmentation views went live.

5-store Colorado operator

MED compliance plus loyalty tier campaigns across the fleet.

A 5-store Colorado MED licensee rolled out Strkr across the fleet with a shared loyalty program and store-level marketing campaigns. The compliance officer owns the retention policy at the tenant level with MED's 3-year commercial and 5-year video rules enforced centrally. Rule-change bulletins push to every budtender dashboard with ack logs. Tier campaigns run per-store with central reporting rolling up fleet-wide spend by product category. The GM at each location runs their own saved views without a central ticket queue.

12-store California MSO

DCC audit readiness plus Dutchie and Treez POS parallel.

A 12-store California DCC licensee operating across two POS platforms (Dutchie in SF Bay stores, Treez in SoCal stores) uses Strkr as the one customer record that spans both. The compliance officer runs a single audit view across the fleet with DCC-formatted exports ready for inspection. Loyalty discount caps enforce DCC excise-tax rules at redemption. The 7-year retention policy drives purge Flows that respect the floor without manual review every quarter.

3-store New York adult-use

OCM-ready records plus caregiver linkage plus age-gate enforcement.

A 3-store New York OCM adult-use operator uses Strkr for the customer record and age-gated outreach. Every door scan captures an ID artifact per OCM retention rule. Loyalty tiers respect OCM marketing restrictions on template content. The compliance officer runs the OCM 5-year audit view with 36-month customer lookback on patient records before the quarterly licensing review. SMS campaigns respect NY TCPA and OCM marketing rules with every send logged to the audit trail.

40-location MSO across 5 states

Multi-state compliance substrate with per-state rule configuration.

A 40-location MSO running CA, CO, NM, IL, MI uses Strkr as the shared customer and compliance surface across all five states, with state-specific purchase-limit math, retention policies, loyalty discount caps, and audit export formats configured per state. The compliance team runs one dashboard that surfaces state-level findings and store-level drift. Rule-change bulletins publish per-state and target the right budtender dashboards. Fleet-wide loyalty insights roll up without cross-state data confusion because the state substrate stays separate where it matters and consolidated where it does not.

See the CRM dispensaries actually run their shop out of.

Start free with the full dispensary stack enabled: patient and rec customer records, Metrc and BioTrack reference capture, state purchase-limit enforcement, loyalty ledger with tier segmentation, age-gated Strkr Messaging, retention policy per record type, and one-click audit exports in your state's regulator format. One workspace that sits beside your POS, one record of truth per customer, one compliance surface that holds up on inspection day. The features page lays out the loyalty and messaging surfaces in detail if that is where you want to start, and the integrations page shows the POS and seed-to-sale platforms Strkr connects to today.

Start free Explore the features
Common questions

What buyers in this bucket ask most.

Can Strkr integrate with my dispensary POS (Dutchie, Treez, Flowhub, Blaze, Cova, Meadow)?

Yes. Strkr sits beside your POS with a webhook integration on each sale. The transaction, line items, Metrc or BioTrack tag references, budtender ID, discounts, and loyalty redemption flow into the customer timeline the moment the receipt prints. We do not replace the POS, we complement it. Dutchie, Treez, Flowhub, Blaze, Cova, and Meadow all expose webhooks or APIs that Strkr consumes natively. For POS platforms without a stable webhook, Strkr can run a scheduled sync against the sales export file.

How does Strkr handle Metrc and BioTrack references?

Every purchased unit lands on the customer timeline with its Metrc or BioTrack tag captured from the POS webhook. Strkr does not replace Metrc or BioTrack as the state system of record; those remain the authoritative seed-to-sale platforms for the regulator. Strkr makes the state-system reference searchable at the customer level so a regulator subpoena for 'all sales of this batch to this customer' is a saved view instead of a data engineering project. In states that use BioTrack (WA, HI, DE, ND, some NJ licenses) the integration swaps in without changing the customer-facing surface.

Can Strkr enforce state purchase limits at the register?

Yes. State purchase-limit math (flower weight, concentrate grams, edible THC mg per package, pre-roll count, per-day vs per-transaction rules, patient vs rec limits, caregiver purchase math) runs as a centrally-maintained equivalency formula per state. When a budtender rings a mixed cart, the Flow runs the math live and surfaces a block or warning on the register. State rule changes update centrally so a Michigan equivalency change pushes to every store without a POS reconfig. The over-limit saved view shows every near-miss for compliance review.

How does age-gated messaging work in Strkr Messaging?

Every outbound SMS and email runs through four gates before send: age-check against the stored verification artifact, state-marketing-rule check against the template content, double opt-in verification against the consent timestamp, and cease-and-desist suppression check against the global list. A template with a health claim, youth appeal, inventory-specific pricing where restricted, or public-way advertising language that violates the state rule does not send. The compliance officer reviews the sent log on the audit timeline with every blocked send recorded. TCPA complaints become a resolved audit event because the full opt-in and opt-out trail lives on the customer record.

What state regulators does Strkr support audit exports for?

The audit export surface supports the common state-regulator formats: California DCC, Colorado MED, Michigan MRA, New York OCM, New Jersey CRC, Oklahoma OMMA, Illinois IDFPR, Massachusetts CCC, Arizona DHS, New Mexico CCD, Maryland MMCC, Missouri DHSS, Nevada CCB, Montana DOR, Oregon OLCC, Washington LCB, Maine OCP, Vermont CCB, and a handful of other state formats. The compliance officer picks the record type, date range, customer scope, and state format at run time. If your state format is not listed, Strkr can configure the export spec from the published regulator template without a code change.

How does Strkr handle dual-license patient and recreational customers?

In dual-license states (MI, IL, MA, ME, NY, NJ, NV, MD, VT, and the few integrated-licensee storefronts in CA) the same human is often both a medical patient and a recreational customer. Strkr holds one person record with both channels tracked as structured fields: patient card number, card expiration, caregiver linkage, patient status flag, recreational status flag. Tax treatment auto-selects at the register based on the active channel for the sale. The loyalty ledger consolidates across channels with per-channel reporting so the GM sees the full LTV picture without a split profile that breaks the lookup. For states that mandate separate patient and rec records at the regulator level, Strkr maintains the dual records with the shared person profile layered on top.

Can the compliance officer and the GM make admin changes without a vendor ticket?

Yes, within the permission matrix. Loyalty tier rules, campaign templates, state-rule bulletin publishing, saved views, dashboard widgets, Flow configuration, and retention policy are self-serve for the role the admin has granted the permission to. Most dispensary tenants give the compliance officer full self-serve on bulletins, retention, and audit exports; the GM gets self-serve on saved views, campaign enroll, and store-level Flows; tenant-wide changes (new state onboarding, cross-store automation, data model migrations) route through the admin role. The change ships the hour it is needed with an audit trail on who changed what, so there is no three-week vendor queue in the middle of a licensing-deadline sprint.

Also built for

Related audiences.

For Small Business For Ecommerce For Healthcare For Mid-Market For Founders For Marketing Managers

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing