For Dispensaries
Built for the teamsbehind the listing.
Weedyy’s public site is not a generic directory homepage with an owner link tucked into the header. It is an operator acquisition system built around listing quality, menus, promotions, portal motion, and a truthful retailer-site embedded storefront story.
The live repo posture is approved-host embedded storefront, cart, checkout, confirmation, order-status, support, and recovery truth without shopper handoff links. Live-driver ownership claims stay restrained until governance and downstream proof are complete.
What Weedyy replaces
A stitched-together owner story
The old pattern scattered value across feature pages, download copy, and a live-directory preview. The new system keeps operator intent in one place.
One route spine for owner intent
One conversion language for claim versus portal access
One visual system across homepage, feature, pricing, and auth entry
System
What operators actually get
The public site should present the operating system in the same order teams feel it in practice.
Listing quality control
Stronger profile completeness, verification cues, and a cleaner public footprint.
Menu and merchandising control
Public-facing menus that explain the visit instead of just dumping raw inventory.
Promotion publishing
Launch promotional surfaces that are compliant, current, and easier to understand.
Portal-first workflows
Portal entry that feels like the natural next step after the story, not a context break.
Approved-host embedded checkout
Launch retailer-site menu, cart, checkout, confirmation, order status, support, and recovery only on approved hosts, with no broad driver-ownership claims.
Embedded storefront truth
Retailer-site embeds can now carry live approved-host checkout.
Weedyy can now support an embedded shopping flow on approved dispensary-owned hosts: menu, cart, checkout, confirmation, and order status. The GTM story still stays narrower than broad white-label commerce because support remains a canonical Weedyy handoff and delivery claims stay limited to configured-delivery gates.
Embedded storefront, cart, checkout, confirmation, and order status are live only for approved merchant hosts.
Configured delivery can appear only when Weedyy delivery, listing configuration, address, zone, verification, quote, inventory, and purchase-limit checks pass.
Support, help, single-order status, and recovery stay embedded in the retailer-site storefront when the required flags and host approval are ready.
Operator motion
How the conversion path should work
Every public route should push users toward one of two actions: claim the dispensary or open the portal.
Learn the system
Use the homepage, solutions, features, and stories to understand what Weedyy improves.
Choose the path
New operators claim the dispensary. Existing teams go directly into portal access.
Enter the product
Login, auth-entry, reset, and signup stay visually aligned so the handoff feels continuous.
Embedded commerce FAQ
What the embedded storefront story does and does not mean
This page should help operators understand the current approved-host embedded checkout truth without drifting into broader platform promises.
No. The live slice today is approved-host embedded menu, cart, checkout, confirmation, order status, support, and recovery. Broad delivery ownership claims stay restrained until governance and downstream proof catch up.
Approved hosts can run the embedded storefront shopping flow with Weedyy sign-in, cart, checkout, confirmation, order status, and canonical support/history/tracking links. Operators should not market it as invisible white-label commerce or Weedyy-owned delivery tracking.
No. Weedyy still keeps market controls in place. Delivery is limited to configured-delivery gates, and public GTM should not imply unavailable-market readiness or downstream driver/location ownership that has not been proven.
Start with the operator surface, not the consumer detour.
This rebuild removes the retired live-directory proof path from the funnel and keeps the story focused on operator outcomes, approved-host embedded shopping, and in-frame order recovery continuity.