Dispensary menus and order privacy
Where does your online dispensary order actually go?
A menu on your WordPress site can store products locally or load them from a vendor. This sample compares those menu paths. Paid ordering add-ons are described, but where they store customer orders has not been verified. Check your checkout provider, who can access order history, and what your backups contain.
Based on plugin documentation, not tests of your site. Which fields you collect, who can open order screens, connector settings, and backup inclusion decide who can see purchase history. This is not legal advice or a compliance rating.
Scan your site for third-party requestsThis scan checks requests made by a visitor's browser on a menu page, age gate, checkout embed, or payment page, including scripts when they load. It does not inspect order databases, medical-card fields, customer accounts, or vendor checkout rows stored only on the server, test staff permissions, or assess whether backups include those tables.
Site-hosted menus vs marketplace embeds
Menu and order records on your WordPress site
Check which product and customer fields you keep, which roles can open order screens, and whether exports or backups expose them. Review retention of completed and abandoned orders. A remote menu iframe without site-hosted checkout is a different surface.
Leafly, Where’s Weed, and similar menu embeds
These plugins load a menu from a vendor host. The cited code does not establish checkout behavior or order storage. Check any separate ordering, age-check, payment, or analytics tools you enable. A browser scan cannot inspect vendor order databases or stored medical-card details.
Dispensary menu and ordering setups
No paid placement. Site-hosted menu tools appear first, followed by any vendor-connector group, then unreviewed rows. Site-hosted tools may still use paid eCommerce add-ons when enabled. Names are alphabetical within each group.
This is a small documentation sample of early-stage WordPress dispensary menu plugins and menu embeds, not a survey of Dutchie, Jane, or the whole cannabis eCommerce market.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| WP Dispensary Last public WP Dispensary package 4.5.0 (WordPress.org directory listing closed 2025-01-29 for a security issue; SVN tag remains public). Free core registers a public `products` custom post type for the online menu (title, editor, excerpt, thumbnail, comments, revisions) and documents menu shortcodes on the site. Paid eCommerce add-ons that let patients place orders through the site, plus customer/patient settings, are described in the readme but were not reviewed here — order history storage is not established from free core alone. Retention of orders or customer records is not documented in the free package. Browser hosts have not been verified for the free menu path. | Menu products stored as WordPress posts; paid eCommerce order path not reviewed | Browser hosts not verified | Not assessed | Not tested |
| |
| Leafly Menu for WordPress Documented shortcode `[leafly_menu]` (plugin version 0.1) that outputs an iframe whose `src` is `http://www.leafly.com/embed/menu/{slug}` (host www.leafly.com). The WordPress install only embeds that remote menu; product browsing and any Leafly-side account or order flow happen on Leafly’s host. Retention of order history on Leafly is not documented in the WordPress plugin. No site-hosted order archive is described. | Menu iframe loads Leafly embed; WordPress does not store the menu catalog | www.leafly.com | Not assessed | Not tested |
| |
| Where's Weed Menu Documented shortcode `[ww_menu]` (plugin version 0.1) that reads a business URL from WordPress options and outputs an iframe to `https://wheresweed.com{path}/widget_menu?v=2&menu_indication=0`, plus a local iframe-resizer script. Menu browsing continues on wheresweed.com. The plugin does not document storing visitor orders or medical-card fields in WordPress. Retention of any Where’s Weed–side order history is not documented in the listing. | Menu iframe loads Where’s Weed widget; site stores only the business URL option | wheresweed.com | Not assessed | Not tested |
|
What this table does and does not prove
This table describes documented dispensary menu and embed workflows, not tests of your site. Consent timing, whether access controls work, and exact retention of order history have not been assessed. Dutchie and Jane ordering iframes are common in the industry but are outside this sample because no citable WordPress.org plugin source was available. Check which customer fields you collect, who can open order tools, embeds, exports, connectors, and whether backups include those tables when records are site-hosted.
Documentation snapshot: Oct 9, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-dispensary-plugin-privacy