Skip to main content
SellTreez: Product Updates 16.0.0
T
Written by Treez Admin
Updated over 8 months ago
TZ_Support_ST_L1.png

August 19, 2021

NEW!

Fulfillment

  • An AUTHORIZED filter has been added to the Fulfillment Dashboard.

Authorized_Fulfillment_Dashboard.png

Configuration

  • METRC Licensee names are now present in Config Page > Integrations > METRC API Key & State Tracking Licenses.

SellTreez POS

  • Adding 2 of the same product with 2 different package IDs will now show up as 2 separate ticket lines during checkout.

  • Users can now select whether to capture funds immediately or to continue using the Authorized and Captured workflows.

IMPROVEMENTS

Packaging/User Permissions

  • Moving forward, 'Manager' User Groups in SellTreez will have Packaging permissions enabled when the packaging module is turned on for a Retailer.

image__3_.png

SellTreez Omni Channel Sales

  • With this release, users will be able to update the language on their "Thank You" eCommerce page to fit their needs.

Configuration

  • Under Config Page > Integration > METRC API Key & State Tracking Licenses, the check Licenses button shows Success.

FIXES

Inventory Management

  • The license field in Inventory under package details is now exposed for AZ users. This will allow them to add and edit the license associated with the product and it will ensure the correct license is populated on any delivery manifest.

  • Allows for multiple split/move of batches to happen, as expected.

  • After merging one or more batches, the batches with zero quantity are now removed from the display panel.

Fulfillment

  • Extra units added to in process order is now resolved. The number of items on the order remains the same even if user inadvertently clicks ‘YES’ more than once.

Product API

  • Price Tier name in History Log is displayed.

Customer API

  • An improvement to the stability of the Customer API has been made in Treez. Customer profiles with multiple merged profiles are no longer causing the customer API to return an error and will now result in a successful response.

Did this answer your question?