Dutchie POS 1.122: Discount stacking update; Manifest template enhancements; fixes

Projected release dates: 11/18/24-11/21/24. We plan to pause non-essential Dutchie POS product updates from 11/18/24 to 12/1/24. Subject to change.

Discount stacking update

Correction, edited as of November 14: Rather than rolling back the Discount Stacking update for all customers as communicated on November 13, we will instead give customers the optionality to revert back to the prior configuration. While we believe these changes add value, we recognize that you may prefer to retain the previous setup for continuity over the holidays.

Adjusting Your Discount Stacking Settings:

• If you’re satisfied with the current Discount Stacking functionality launched in October, no action is needed.

• To revert to the previous version, please reach out to our Support team at possupport@dutchie.com.

We apologize for any confusion - we will only be making adjustments to the current functionality upon your request.

Manifest template enhancements

We’re making the following updates to manifest templates. Some of these are optional and require configuration by Dutchie Support:

• Base Manifest and the Retail Manifest will be updated to display a fourth row of item properties and use a single text block per column to support auto text sizing.

• Item Description columns within the Base Manifest and Retail Manifest will stay aligned to avoid text overflow.

• The system will fetch and display brand names on the manifest items detail page in the Backoffice.

• Option to set Item Column 1, Row 4 and Item Column 2, Row 4 to display the configured item property at the respective location (contact Dutchie Support to enable).

• Option to display Tested Date on the Base and Retail manifest (contact Dutchie Support to enable).

• Option to protect driver information by hiding the driver’s date of birth and driver’s license number on the printed manifest (contact Dutchie Support to enable).

Fixes

This release includes fixes to address the following issues:

• The Harvest Wgt Report incorrectly calculates post-trim weight.

• When the Closing report includes an adjustment amount, the report viewed in the Backoffice differs from data fetched from the API

• Ohio: A “customer’s allotment has been exceeded” error intermittently appears when the customer’s allotment has not actually been exceeded.

This release also includes fixes for the following issues, which apply only to Florida BioTrack operators:

• BioTrack Traceability Log time stamps reflect the date and time that a user requested the log rather than the date and time of the actual traceability events.

• Users report being unable to adjust quantities of non-cannabis items, including delivery devices.

• Delivery vehicles appear in multiple locations when they should only appear in the location where they were created.

• This release will eliminate the need for extra steps or workarounds when receiving delivery devices. As long as delivery devices are set up correctly in your catalog, you can receive them the same way as other non-cannabis inventory and/or on the same manifest as cannabis inventory, and they will automatically be reported to BioTrack.