Discussions

Ask a Question
ANSWERED

Merged Customers and Related behavior with the Customer API and Webhooks

Treez has updated the way merged customers are displayed through our API, enabling Partners and operators to better track merged profiles. When using GET/ Customer endpoints, the resulting post-merge account will be the primary and have a value called MERGED_CUSTOMER_IDS associated with it. This field will display all profile IDs that have been merged into the resulting account and will have a STATUS listed as 'MERGED'. On top of that, a note will be added into the NOTES field that details the time and date of when the merge occurred. When using the GET/ Customer endpoints with merged and deactivated profiles you'll see similar behavior as with an active profile. The STATUS for a merged and deactivated account will be listed as 'DEACTIVATED' and associated with a new field called MERGED_INTO_CUSTOMER_ID which will display the member ID that profile was merged into The changes to our APIs for Merged profiles also carries over to our Update Customer API. When you attempt to use the Update Customer API with an account that has been merged and deactivated the request will fail and Treez will return an error message that will include the Member ID for MERGED_INTO_CUSTOMER_ID (i.e. the resulting customer profile). There is also a new event that will trigger our customer webhooks. Whenever two accounts have been merged in Treez you'll receive separate payloads for both the surviving profile and the merged/deactivated profile. The payloads will include the values MERGED_INTO_CUSTOMER_ID and MERGED_CUSTOMER_IDS.
ANSWERED

Filter patients by spending habits

How could I filter to see who my top 3, 5, or 10 spending patients are? Could I see that over 30, 60, 90 days or the entirety of our site's operations? I've tried utilizing the Sales tab and can source some info but not exactly this. Could you help me?
ANSWERED

How to I view Products in Specific Inventory Location?

If you would like to view only products that reside in a specific inventory location with Treez, you can use the sellable_quantity_in_location filter. https://api.treez.io/v2.0/dispensary/DISPENSARYNAME/product/product_list?sellable_quantity_in_location=CABINET 1&page=1&pagesize=50 The above example URI would provide first 50 (page=1 and pagesize =50) sellable products in a location called "CABINET 1". The location name is case sensitive and must be entered EXACTLY as it appears in the Treez instance. "cabinet 1" would not produce the desired response because the location name is in all lowercase letters while the location name in the Treez instance is capitalized. *Please note that DISPENSARYNAME should be replaced with the first part of the dispensaries Treez URL. Example: If the retailers Treez URL is edmundsdispensary.treez.io then you should replace DISPENSARYNAME with edmundsdispensary
ANSWERED

DAILY PURCHASE

HOW TO INCREASE DAILY PURCHSE LIMIT FOR A CUSTOMER WITH MEDICAL ID
ANSWERED

What is the Sellable_Quantity Cap?

ANSWERED
ANSWERED
ANSWERED
ANSWERED

How Do I Prevent Adding Duplicate Profiles in Treez?

When adding new customer profiles into Treez, it’s important that partners perform checks to prevent adding any duplicate profiles. Creating multiple profiles for the same customer in Treez clutters the store's data and provides a less than ideal experience for our mutual clients and their customers. For example, duplicate profiles can cause the customer not to receive the discounts that they should. That’s why Treez has provided multiple endpoints for partners to utilize when looking for existing customer profiles. See below for all of the available endpoints: GET/ Customer by Driver License: https://api.treez.io/v2.0/dispensary/dispensary_name/customer/driverlicense/license GET/ Customer by Phone: https://api.treez.io/v2.0/dispensary/dispensary_name/customer/phone/phone GET/ Customer by Email: https://api.treez.io/v2.0/dispensary/dispensary_name/customer/email/email GET/ Customer by First and Last Name: https://api.treez.io/v2.0/dispensary/dispensary_name/customer/firstname/first_name/lastname/last_name Treez provides endpoints based on the common information that our partners obtain through their app during sign-up. Suppose a partner is unable to locate a customer based on their first request. In that case, we suggest an iterative approach to search for the profile by other data fields (and their respective endpoints) that have been obtained from the customer. If partners are still unable to locate a matching customer, they should create a new account for the customer.