Dutchie E-Commerce: Pay by Bank enhancements, fixes

Here’s what’s new and coming soon in Dutchie E-Commerce

Enhancements

• Customers who complete an order without using Pay by Bank now get a Pay by Bank button in order status emails, and an SMS “nudge” to check that email when their order is Ready for Pickup or Out for Delivery, giving them a way to attach Pay by Bank after checkout but before the order is finalized at the register. Requires Order Status Emails & SMS to be enabled in E-Commerce Admin.

• Mobile app customers with a pending Pay by Bank payment now see a Pay Now button on their iPhone lock screen (Live Activity widget) or in their Android notification shade, which deep-links straight to the Pay by Bank payment screen for that order. No dispensary setup is required; it's controlled by the location's existing Pay by Bank configuration.

Fixes

We’re releasing fixes for the following issues

• Receipts could show the wrong store address, such as a different city than the dispensary that fulfilled the order.

• "Mobile Only" discounts could still appear and apply on the storefront until the page was refreshed.

• Fixed recurring Plus API addItem failures and checkout price inconsistencies that were affecting multiple retailers integrated through the Plus API.

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

• Discounts could display on product cards across the menu but disappear once the item was added to the cart.

• Custom menu sort order wasn't reflected on printed menus.

• 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.

• For dispensaries using the Cova integration, a normal "customer not found" response was being misclassified as an internal error.

• Checking order status could crash for dispensaries using the Cova POS integration.

• Changes to brand sort order in admin weren't reflected on the live storefront.

• Checkout could fail with an error for dispensaries using the Greenline POS integration with Moneris payments, when the payment response was missing an expected field.

• A curbside arrival notification could remain active after the associated order was cancelled.

• A data cleanup operation could unintentionally affect all users instead of just the intended dispensary's users, for dispensaries not part of a retail chain.

• Category sort overrides configured in admin weren't reflected in the Dutchie Plus API's menu settings response.

• The Dutchie Plus API could return an error when it received an invalid combination of menu filter parameters.

• When a POS integration was removed, some of its specials could remain active instead of being fully cleaned up.

• Simultaneous edits to menu order settings by different admin users could silently overwrite each other's changes.

• Updating a customer's address or medical card information could unexpectedly clear other profile fields, or fail with a server error.

• Updating an admin user's email address didn't check for duplicates the way creating a new admin account does.

• A kiosk could occasionally be identified as a different kiosk when duplicate claim codes existed.

• Updating a coupon could still fail with an error for certain optional fields left blank, a follow-up to an earlier fix for this same issue.

• Cache purges after a storefront content update could silently fail, so shoppers would sometimes see outdated content longer than expected.

• A temporary Cloudflare service issue during checkout could be mistaken for a failed security check, incorrectly blocking a customer from completing checkout.

• Clicking a product on the menu or embed page could cause the page to scroll to the bottom unexpectedly.

• Collections restricted to specific channels (Web, Kiosk, Mobile) could still appear on a channel it wasn't configured for.

• Sorting the admin Menu Score list in ascending or descending order didn't work correctly.

• Delivery and pickup reservation slots didn't account for a dispensary's configured special hours.

• The storefront header and logo could shift position right after the page loaded, contributing to layout instability.

• Custom storefront pages could briefly flash a "page not found" error before loading correctly.

• Kiosk phone-based login could occasionally sign a customer into a different customer's account when multiple accounts shared the same phone number.

• The cart preview could show a misleading "cannabis tax included" label on the subtotal; the final checkout total was always correct.

• Printed order tickets could show the wrong promotional price for a line item, even though the order total and receipt were correct.

• Pay By Bank could still appear as a payment option for delivery orders after switching from pickup to delivery within the same session, even when disabled for delivery.

• Retrying a menu wipe or integration removal that had partially failed could crash with a server error instead of completing or failing gracefully.

• Kiosk checkout could replace a specific, actionable error message with a generic "please fill out the missing information" banner, and could carry over stale errors from a previous attempt.

• Sorting by price (low to high) was only applied within each page of results, so a lower-priced item could appear after a higher-priced one across a page boundary.

• For dispensaries using the Cova integration, a cart-level discount could be spread across every item on an order, including cannabis products, instead of applying only to the qualifying item.

• Visiting the dispensary directory with a city filter in the URL could return a server error instead of the page.

• Connecticut's THC-potency-based cannabis tax has been removed from checkout calculations, following the state's tax law change effective October 1. Connecticut retailers need to configure their new tax in E-Commerce admin, or their online orders won't charge cannabis tax.