Dispensary POS integrations for email and loyalty
Our platform doesn't start from a blank template. It starts from your POS: your products, your offers, your tickets, your customers. Every integration below exists to feed one machine: campaigns generated from what's actually happening in your store, and revenue measured at the register instead of the click.
Deep integrations, live today
These three connections are built, running, and syncing for live stores right now. They power auto-generated campaigns and campaign-to-POS revenue attribution.
Treez
LiveProducts with images and first-seen dates, METRC batch expiry, restocks, and ticket lines with customer emails. This is the backbone of revenue attribution and purchase segments. Nightly sync in your store's timezone.
Explore
Dispense
LiveLive ecommerce catalog, offers, and product images read at campaign-build time, with menu deep links that land customers one tap from checkout.
ExploreAlpine IQ
LiveKeep your AIQ loyalty program and send email through us: your existing audiences resolved live at send time, points on wallet cards, two-way opt-out sync.
ExploreAlso live via custom onboarding & imports
Running Dutchie, Flowhub, or Cova, or migrating off SpringBig? These connections are available today: we hook up your customer list, catalog, and offers as part of setup through flexible imports and custom feeds we build with you, so the campaign engine has real store data from week one. We're upfront about depth: the deepest automatic sync and register-level attribution ship on our native integrations first.
Dutchie
Catalog, offers, and customer list connected during onboarding. No POS switch required.
Explore
Flowhub
Customer list and catalog feed set up as part of your onboarding.
Explore
Cova
Customer list and catalog feed set up as part of your onboarding.
ExploreSpringBig
Import your SpringBig contacts and loyalty data, run email side by side, and switch in about two hours when the numbers convince you.
ExploreYour system
On something else? Ask us. If your data can be exported, we can connect it. That's the point of custom onboarding.
Every connection at a glance
The honest version of an integrations page: what actually flows, how often, and whether it's live today. No hundred-logo wall.
| Feature | What flows | Cadence | Status |
|---|---|---|---|
| Treez | Products, batch expiry, restocks, ticket lines, customers | Nightly, store timezone | Live today |
| Dispense | Live catalog, offers, images, menu-site banners | Read live at campaign build | Live today |
| Alpine IQ | Audiences, contacts, points, 2-way opt-outs | Audiences resolved at send time; points ~8h | Live today |
| SpringBig | Contacts, consent state, exported balances | One-time import + POS feed | Import path live |
| Dutchie | Customer list, catalog, offers | Onboarding import + configured feed | Live via custom onboarding |
| Flowhub | Customer list, catalog, offers | Onboarding import + configured feed | Live via custom onboarding |
| Cova | Customer list, catalog, offers | Onboarding import + configured feed | Live via custom onboarding |
Moving serious volume? We build the connector.
If you're an operator sending hundreds of thousands to millions of emails a month off a legacy platform, integration work is part of onboarding, not a change order. We build the connector that gets your contacts, suppression lists, and catalog flowing, then move your sending onto dedicated IPs with an automated warm-up at a pace your domain reputation can absorb.
A different theory of integrations than Alpine IQ or SpringBig
Alpine IQ publishes over a hundred integration logos, and that breadth is genuinely useful if you need many channels stitched together. But breadth is not depth: G2 reviewers report data that "takes 24 hours to load," and AIQ audiences rematerialize roughly nightly, so the segment you mail this afternoon can be a day stale. SpringBig is an SMS-first platform; POS data mostly feeds loyalty accrual, and its email toolset is widely reported as the weaker half, which is why operators often pair it with a separate email vendor.
We integrate for one purpose: generating campaigns from live store data and proving revenue at the register. Fewer logos, more mechanics: nightly ticket sync, product images with prices and menu deep links, purchase-rule segments, and per-campaign POS-verified revenue on supported POS integrations (Treez today). See how that plays out on the Alpine IQ comparison page and the SpringBig import & migration page.
Why not just plug a POS into Klaviyo or Mailchimp?
Two reasons. First, policy: Klaviyo tolerates cannabis email but bans cannabis SMS, and Mailchimp's acceptable-use posture leaves dispensaries one automated review away from a frozen account. Generic ESPs weren't built to say yes to this industry. Our sending infrastructure was approved with full cannabis disclosure. Second, plumbing: there is no off-the-shelf Treez-to-Klaviyo connector that carries ticket lines, batch expiry dates, and restock streaks. Without that data, an ESP is a blank canvas and every campaign starts from zero. With it, the platform drafts the campaign for you and then tells you what it earned in register receipts, not click estimates.
Frequently asked questions
See your own store's data light it up
Book a 20-minute demo. We'll connect a sample of your menu and show you the campaigns it generates, all before you commit to anything.