Dutchie E-Commerce: Enhanced collection channel visibility; Contextual AI Concierge entry points; fixes, and more

Here’s what’s new and coming soon to Dutchie E-Commerce. Subject to change.

Enhancements

Show the right collections on the right shopping channels

Retailers can now customize channel availability—Web, Kiosk, and Mobile App—for each Standard and Exclusive Collection, rather than publishing them across every channel by default.

What’s new:

• Channel-Specific Targeting: When creating or editing a collection, choose any combination of Web, Kiosk, and Mobile (available for retailers with a configured branded mobile app) to display your curated items where they make the most impact.

• Storefront Enforcement: Storefront menus, collection carousels, and direct links honor your settings—collections are hidden or marked unavailable on excluded channels.

• Visibility at a Glance: The admin Collections list now displays channel badges on each row so you can quickly see where collections are active without opening each one.

• No Disruption to Existing Menus: All existing collections retain their current multi-channel visibility until you choose to update them.

Contextual AI Concierge entry points

AI Concierge entry points are now integrated directly into browsing workflows across Dutchie E-Commerce, guiding shoppers to relevant products without requiring them to use global search.

What’s new:

• Search & Category Results: Shoppers see a dynamic Concierge card on the first page of results (for lists with >6 items), tailored to active filters and keywords.

• "Recommended for You" Carousel: For signed-in shoppers with browsing history, Concierge leads the carousel with personalized recommendations.

• Product Detail Pages (PDP): In-stock items now include quick-action shortcuts:

  • Find Similar Products: Recommends alternatives based on effect, category, and flavor profile.

  • Teach Me About This Product: Provides instant education on effects, dosage, and usage.

Good to now

• Availability: Rolling out across Dutchie Storefront and embedded menus (not supported on Kiosk).

• Inventory-Aware: Product detail page shortcuts only display on in-stock, purchasable items.

• No Disruption: Does not impact menu pricing, product ranking, inventory logic, or checkout flows.

Automatically route delivery shoppers to the correct store

If a customer enters a delivery address outside their current store's delivery zone, Dutchie checks for another location in the same chain that services that address and prompts the customer to switch menus.

Treez integration update - JWT Organization ID required

We’re adding a Treez JWT Organization ID field to the Treez integration card in admin dispensary settings. Action required: dispensaries on the Treez integration need this field configured before November 1, 2026 as part of Treez's authentication migration.

Fixes

We're deploying fixes for the following issues:

• A non-stacking loyalty reward could still apply alongside a non-stacking automatic discount at checkout, even though both were individually configured not to stack.

• A collection could include a product that didn't actually match the collection's configured criteria.

• Incorrect delivery dates could show across multiple zones, persisting for specific accounts even after a cache clear.

• Lab results (terpenes) on the storefront didn't update when a customer switched between product weights.

• Some storefronts experienced slow page loads and console errors caused by a version mismatch between the storefront host and a customer theme, along with layout-shift issues during page load.

• Orders could be placed outside of a dispensary's scheduled ordering hours, and adjustments to those hours didn't always apply in the UI.

• A product disabled on one menu (medical or recreational) could still appear on that menu under Sponsored Products if it was sponsored, bypassing the menu-level disable.

• A product tagged for two promotions could show under only one of them online until the page was manually refreshed.

• A menu page for a nonexistent product returned a normal (200) response instead of a not-found (404) response, affecting SEO treatment of removed products.

• For Dutchie POS integrations with customer-type-based menu categorization enabled, a product's medical/recreational/both categorization wasn't applied correctly to non-split menus when dual pricing was off.

• The storefront's effects filter had a discrepancy, and terpene-based collections had scope limitations preventing some products from being included correctly.

• An ASAP delivery order could be accepted after a dispensary's configured ordering cutoff time.

• Clicking "All Flower" to clear category filters didn't actually clear them when Sort by Relevance was enabled.

• Creating a BOGO discount at the chain level could fail with a GraphQL error.

• A scheduled pickup slot could be booked before the dispensary's store hours actually opened.

• Publishing changes to the E-Commerce homepage could fail to go live.

• Uploading an image to the home screen in admin could fail with a generic "Something went wrong" error.

• A discount scoped to one product weight could show other weight variants of that product under the special on the online menu, and in some cases show the product under the special with no discounted weight visible at all.

• Product pages could return a server error for archived or unbranded products instead of loading.

• A single discount configured in Backoffice could render as two identical tiles on the customer-facing specials page, across every location in the chain, even though the admin specials list showed only one entry.

• On Kiosk Pro, touch targets for buttons like Cancel and Go to Cart could be misaligned, registering a tap on the product underneath the button instead and adding items customers didn't intend to order. Kiosk Pro also had a noticeable delay when tapping Start Shopping.

• On product detail pages, browsers that support the Web Share API could trigger a full client-side re-render of the page after initial load (visible as a brief flicker and console errors), losing the performance benefit of server-side rendering.

• Delivery addresses that were clearly inside a dispensary's delivery zone could still be rejected as out of range when ordering through an embedded menu with Dynamic Delivery enabled.