LoopBudz
Integrations · Dispense

Your Dispense menu, turned into email

Dispense already holds your best-looking asset: a live menu with real photos, real prices, and real offers. This integration treats that menu as the source file for your marketing, so every email is assembled from what customers can actually buy right now, not from last week's export.

Live integration, reading production menus today

Exactly what syncs, and when

The Dispense connection is deliberately fresher than a nightly batch: campaign content is composed against the live feed at build time.

Your Store · Settings / Integrations / Dispense
Your Store · Settings / Integrations / Dispense
Data streamWhat flowsCadencePowers
Live catalogNames, brands, categories, prices, stock, and product images: the menu as it stands, not a stale nightly copy.Read live when campaigns are builtProduct grids that reflect what’s actually buyable
Offers feedCurrent discounts and bundles with discount depth, remaining stock, image coverage, and dollars already redeemed per offer.Read live at build timeDeals digests, deep-discount roundups, scarcity plays
Image pipelineProduct shots resized for email with the price baked into the card and a deep link to that exact product on your menu.Rendered at insert timeDesigner-free product cards, 1/2/3-up grids
Menu-site bannersThe promotional carousels you already maintain on your menu site, lifted with their true click-through destinations.Scanned during suggestion runsBanner-blast emails with per-banner tracked links

Read-only. Product images are resized, price-stamped, and served from your own mail domain, never a third-party CDN. One honest caveat: prices freeze at insert time in already-sent emails, the same as every email platform.

The campaigns it unlocks

The Dispense feed drives the offer-led half of our auto-generated campaign roster. Every suggestion arrives designed. You edit if you want, then press send.

  • Deals digest & deep discounts

    Offer-led campaigns scored on discount depth × stock on hand × image coverage × redeemed dollars. The engine leads with the offer most likely to move, and shows you the score math.

  • Bundle deals & brand spotlights

    Bundles get their own framed sections; brand spotlights pull up to three product photos per brand with fuzzy brand matching, so “House Extracts week” assembles itself.

  • Banner blast

    One live store's menu site carried 20 distinct promo banners with real click-through links. Someone already designed that carousel. The banner blast turns it into a tracked email in one click.

  • Offer picture grids

    Your offer photos laid out two-up, each linking to the offer on your menu. Zero design time; the assets already exist in Dispense.

  • Menu deep links on every card

    A generic ESP links to your homepage and hopes. Every product card here uses our own signed, tracked redirects to land the customer on the exact product page, one tap from add-to-cart.

  • Scarcity, honestly

    Because stock is read at build time, “only a few left” claims come from the live count, and a product that sold out this morning doesn't headline this afternoon's email.

Click tracking is ours end to end: signed redirects, reported as totals, honestly counted. And if you also run Treez, POS revenue attribution closes the loop from the click to a completed ticket at the register.

Setup: under an hour

This is the fastest connection we run: an API hookup against a menu that already exists.

  1. 0:00

    Connect your Dispense API key

    A read-only API hookup, not a data migration. We never modify your Dispense store.

  2. 0:45

    Catalog and offers are flowing

    The Dispense connection itself typically takes under an hour. Product images route through the resize pipeline and land in your media library.

  3. same day

    Suggestions built from your menu

    Deals digests, brand spotlights, and banner blasts appear in the feed, composed from the live catalog, each with its “why this email” reason attached.

How the incumbents treat Dispense stores

Alpine IQ's integration catalog is broad and includes ecommerce players. Credit where it's due: if you need SMS, push, and a dozen channels in one contract, that's their pitch. But the ecommerce data mostly feeds audiences and templates, with G2 reviewers reporting day-stale syncs; nobody is lifting your menu banners or composing product grids with prices baked into the images. SpringBig is SMS-first and its email product is the reported weak half. A Dispense menu feeding a text blast cannot show a product photo at all. Our approach is narrower and deeper: the menu is the campaign, rendered beautifully in the inbox. See the Alpine IQ comparison for the full side-by-side.

Versus wiring Dispense into a generic ESP

There's no Dispense-to-Klaviyo product feed that resizes images, bakes in prices, and deep-links to your menu. You'd rebuild that pipeline yourself, then still face cannabis policy risk (Klaviyo tolerates email but bans cannabis SMS; Mailchimp enforcement is unpredictable) and shared-IP reputation you don't control. We ship the pipeline built, on dedicated IPs with cannabis-disclosed, approved sending, with your images hosted on your own mail domain, never a third-party CDN.

Frequently asked questions

Watch your menu become a campaign

Book a demo and we'll point the engine at your live Dispense menu. You'll see the emails it drafts from your own products and offers.