Dutchie POS 1.126: QR code support for TSP100 printers; inventory performance reporting and inventory audit enhancements; fixes

Projected release dates: 1/13/25-1/17/25. Subject to change.

Enhancements

Receipt printing

We’re expanding support for QR codes and barcodes on printed receipts to include TSP100 printers (which currently can only print logos). This update also includes receipt formatting adjustments to reduce paper usage and avoid cutting off characters, as well as resized barcodes/QR codes, indents, and the omission of unused/null fields for a better overall appearance.

Reports

In Reports > Inventory, clicking the Days of inventory remaining tile will show more details for individual products, brands, categories, or tags, including:

• Quantity on hand

• Quantity sold

• Quantity sold per day

• Days of inventory remaining

Additionally, clicking the Inventory expiring tile will show more detail about inventory expiring over different time frames by master category, product, or brand.

Inventory audits

To assist with inventory auditing in markets that do not use package IDs, we’re adding the option to add Batch ID, Brand, and Strain columns on the inventory audit detail page. Click the cog wheel to open the column configuration window and add these columns to your view.

User event log

Because user event logs show data across multiple locations, we’re adding a Location column to event log tables so you can identify the location at which a change or update was made.

Fixes

This release will address the following issues:

• Receipts printed from Mobile Checkout via PrintNode show jumbled code.

• Removing items from a cart may cause a customer’s Dutchie POS loyalty points to change to a negative value and cause an incorrect order total.

• Managers with the necessary permissions at one location can void a transaction from another location where they don’t have the necessary permissions as long as they enter a valid manager PIN.

• An “Object reference not set to an instance of an object” error may prevent users from processing preorders.

• A package’s Last Audited Date may reflect the last time its associated product was audited, not necessarily that specific package. We’re releasing a fix to ensure this reflects the last audited date of the specific package instead of the product.