Dutchie POS: Sync route updates from Onfleet; expire loyalty points X days after earned; configure SMS sending hours; audit segment changes; fixes

Projected release dates: 8/17/26-8/20/26. Subject to change.

Enhancements

Delivery

Onfleet route sync is coming to Dutchie POS. Dispensaries using Dutchie’s Onfleet integration for delivery management will be able to sync route updates from Onfleet back into Dutchie Register with the new Sync from Onfleet action. After a route is optimized or updated in Onfleet, this option pulls in the latest stop order, assigned driver, and assigned vehicle so you no longer need to manually reconcile route changes across both systems. Learn more in the Help Center.

Loyalty & Marketing

• Expire points X days after date earned. Dutchie loyalty programs currently offer points that never expire or expire a set number of days after a customer’s last purchase. To limit liabilities, create urgency for customers to redeem points, and drive customer engagement and repeat visits, we’re introducing a new option where points expire a set number of days after they are earned. Learn more in the Help Center.

• Point boost workflows to include recipient visibility. This will give retailers more transparency into automated loyalty point boosts by showing which customers were processed for a point boost and whether points were awarded. The Recipients view will include details such as customer, date and time, points granted, and interruption reasons when a boost could not be applied. Point boosts also appear as their own loyalty transaction type and are reflected in point liability reporting, making it easier to audit campaigns, troubleshoot customer questions, and track loyalty liability.

• Configure SMS sending hours. Set specific SMS sending windows for each day of the week to better align marketing messages with local regulations and customer expectations. Messages scheduled outside the configured window are automatically deferred to the next available sending time, helping teams stay compliant while reducing the need to manually time campaign sends. To configure sending hours, go to Marketing > Configure > SMS Sending Hours.

• Audit customer segment changes. Segment details will soon include a History tab that shows when a segment was changed, who made the change, and the previous and new values. This gives teams better visibility into updates to segment definitions and settings, making it easier to troubleshoot audience changes and understand how customer groups have evolved over time.

Inventory

Receive Inventory document uploads now support larger files. The file size limit for documents attached on the Receive Inventory page will increase from 10 MB to 30 MB. This makes it easier for teams to attach larger invoices, manifests, and supporting documents without needing to compress or split files before upload.

Compliance

We’ve updated the behavior of these Metrc integration settings:

• When Use “Use by date” is set to No, use by dates will remain visible in Dutchie POS (for Colorado operators only), but will not be reported to Metrc when creating new packages.

• When Use “Expiration date” is set to No, expiration dates will remain visible in Dutchie POS but will not be reported to Metrc when creating new packages.

Fixes

We’re releasing fixes for the following issues:

• Partial package moves do not preserve case-sensitive barcodes, which means moved inventory can stop scanning correctly at the register. The case-sensitive barcode also is not visible on the inventory list, making it harder for teams to verify and troubleshoot barcode values.

• Some Metrc manifest completions fail with a generic integrated-system error because required driver occupational license information is not sent in a way Metrc accepts. This blocks affected stores from completing transfers and posting manifests to Metrc.

• Loyalty receipt messaging can show the number of points expiring based on the customer’s balance before a redemption, rather than after points are used in the transaction. This can make receipts show more points expiring than the customer actually has remaining, creating confusion for customers and staff.

• In Louisiana, customers with a negative flower allotment can be blocked from purchasing non-flower products even when those products are legally allowed. This prevents valid checkouts because Register treats any negative allotment as a full purchase blocker.

• The Initial Reward for Sign-Ups loyalty setting appears to save successfully but reverts after refreshing or navigating away. This forces staff to manually adjust loyalty rewards for new members because the configured sign-up reward does not reliably persist.

• Prices on compact Star receipt printers can wrap onto two lines, splitting values like “$65.00” into “$65” and “.00.” This makes pick tickets and receipts harder to read and can create confusion during fulfillment or checkout.

• Purchase orders can display oldest-first instead of newest-first, especially after a user has saved table preferences. This forces users to scroll through older records to find the purchase order they are actively working on.

• Certain “Buy N for $X” discounts can apply to only part of a qualifying cart and leave remaining items available for another discount. This causes incorrect discount stacking and inconsistent pricing when the cart contains more qualifying items than the deal’s threshold.

• The Initial Reward for Sign-Ups loyalty setting appears to save successfully but reverts after refreshing or navigating away. This forces staff to manually adjust loyalty rewards for new members because the configured sign-up reward does not reliably persist.

• Moving a cultivation batch between rooms appears to succeed but does not actually update the batch's room assignment. Individual plants within the batch move correctly, but the batch record itself remains in the original room. This fix will make keep both the batch and its plants in sync with the selected destination room.

• When a consumer replies “STOP” to an SMS marketing message, the consumer is added to a block list by Dutchie and the carriers, but they still appear as opted in to SMS messaging in the Backoffice and Register. This fix makes it so the consumer’s opt-in status is correctly reflected in Dutchie.