Dutchie Product Team
Dutchie POS (formerly LeafLogix)

Dutchie POS updates: Business intelligence enhancements, bug fixes

AUTHOR: Dutchie Product Team

New features

You can now view more details about inventory audits in BI tools including:

  • Product name

  • Dimension for adjusted quantity (to quantity - from quantity)

  • Measure for total adjusted quantity (sum of adjusted quantity)

We’ve added a Total THC field to the Batch Lab Results views in the Explore section of BI tools. This value is based on the formula: (THCA x 0.877) + THC-D9.

Manitoba: we’ve added a new Manitoba Monthly Provincial Compliance Report that you can export from Reports > State reporting. The export is formatted according to LGCA’s requirements so you can upload it directly to the LGCA web portal.


We've recently released fixes to address the following issues:

  • When viewing a product’s Package History, the Details column showed no information for Sublots.

  • Under Customers > Configure > Doctors, the list only showed doctors created in the location the user was viewing when it should have shown all doctors created in the LSP.

  • Users received errors that prevented running the Transaction Comparison and Sales in Weight By Transaction And Customer reports.

  • Package gross weight information wasn’t carried over after an internal transfer.

  • Drivers weren’t able to view customer phone numbers in Mobile Checkout once a route had been created for the order.

  • The Restrict to group(s) dropdown on the Options tab of a discount was missing the No group assigned option from LeafLogix. We’ve updated the Dutchie POS interface to include this.

  • Users were unable to set a password for another user despite having the necessary permissions.

  • Discounts with bundle or threshold requirements that were also set as automatic and stackable were not stacking with percent-off discounts.

  • New Jersey: product UIDs were not appearing on reprinted labels for completed transactions.

  • Florida: Users received an error message “Error loading allotment: An invalid request URI was provided. Either the request URI must be absolute URI or BaseAddress must be set.” when completing a transaction.

Powered by LaunchNotes