Why Integrate Blackbird with Adilas?
If you use Adilas as your point of sale software in the dispensary, and Blackbird for CRM tools or an online menu, you may benefit from setting up an integration between the two software platforms.
An integration allows for sharing of relevant data between the two platforms which can save time and money by eliminating double entry of data and reducing the need to manage info manually. Creating an integration for use with CRM and online menu features increases efficiencies and automates processes that would have to be handled manually.
You can use an integration with Adilas to facilitate points per dollar loyalty. By pulling order information into Blackbird from Adilas, points can be automatically awarded to customers based on the value of their order. This removes the need to manually add points to customer profiles for orders completed in the point of sale and incentivizes customers to spend more money.
If you are using an online menu through Blackbird, you may find value in using the integration with Adilas to pull inventory into Blackbird for sales online. This removes the need to duplicate the inventory in Blackbird manually and try to keep the two systems in sync with each other. It allows inventory information online such as price and available quantity to match Adilas at all times.
Additionally, orders placed online can be sent directly to the client’s Adilas account with all the order information so there is no need to recreate orders (or customer profiles) that come in from the menu into Adilas.
Information is shared between Adilas and Blackbird in two ways: Blackbird either requests information from Adilas and syncs it in Blackbird, or Blackbird pushes new information into Adilas. Blackbird syncs customer, product and order information from Adilas, and has the ability to push online order information into Adilas. You will have the ability to determine what functionality is useful for your business application, and only enable relevant sync or push functionality. Below, each of the syncs and information pushes are described in more detail.
The customer sync requests customer information from Adilas and stores it in Blackbird for use with a Blackbird loyalty program. In order to assign points to customers in Blackbird based on their orders in Adilas, we have to know who the customers are in Adilas. By syncing this info, we can ensure Blackbird and Adilas are sharing customer information to allow accurate assigning of points per dollar spent.
The following fields are pulled from the customer profile in Adilas:
Customer syncs are set to run every 3 hours. On the first sync, all customers are pulled into Blackbird and on the subsequent syncs Blackbird pulls in any new customers and updated customer information every 3 hours.
Please Note: Adilas does not allow you to distinguish different types of customers (ex. - medical vs. recreational). As a result, you may have two different Adilas ‘locations' or accounts that separate medical customers + orders from recreational customers + orders. If this is the case, two MyBlackbird locations need to be set up along with two integrations. You may be required to pay for two software platforms as a result.
The order sync requests order information from Adilas and stores it in Blackbird for use with the loyalty program. The order information is used to assign points to customers per dollar spent in the order. Orders are pulled for all statuses, but only completed orders are used to award loyalty points.
The following fields are pulled from orders in Adilas:
Order syncs are set to run every 3 hours. On the first sync, all orders are pulled into Blackbird and on the subsequent syncs Blackbird pulls in any new orders from the previous 3 hours.
This functionality sends online order information to Adilas automatically when a customer places an order on a Blackbird menu. This will be helpful to those using an online menu and for those that do not want to manually recreate orders into Adilas. Order information is pushed to Adilas in real time - as soon as an order is submitted on the menu, the info will be sent to Adilas automatically. A customer record will be created along with the order, if the customer does not exist in Adilas already.
To determine if the customer exists in Adilas, the integration checks for one of the following things:
Customer Last Name
If there are no customers with a phone number or email in Adilas that match the customer information from the order, a new customer record will be created in Adilas. The new customer profile will include the information from the customer’s BlackbirdGo profile.
This functionality pushes a list of all customers from our platform. Customer Push automatically generates all customer profiles attached to online orders in your POS. Blackbird pushes customer data to POS.
Impacted Feature - Online Ordering
Benefits of Use - Allows for online orders to be sent to POS with associated customer details (with Order Push). Updates POS with customers from online orders that are not yet in the POS.
Syncing in products from Adilas will be beneficial to those using an online menu through Blackbird. This functionality will allow inventory information already stored and maintained in Adilas to be utilized on the menu. This removes the need for manual entry and upkeep of product information in two systems. Any changes made to inventory information like price or product attributes will be updated in Blackbird automatically. Additionally, stock quantity is tracked through the integration, so inventory items cannot be oversold and do not require manual removal from the menu when you run out.
The following fields from inventory are pulled into Blackbird:
The product sync runs every 5 minutes. On the initial sync, all products are pulled in. On subsequent syncs only new products and updated products are synced (including price and quantity updates).
Please Note Regarding Adilas’s Product Structure
In Adilas, you create ‘parent’ products that have general attributes and information, and sub-products. In this way, you can create different inventory batches as sub-products that inherit the parent products attributes, but can have distinct characteristics themselves. Adilas’s API only returns parent products, meaning that individual batches of inventory do not get returned for use on the online menu. This requires you to manually keep track of stock quantity on the parent product instead of relying on the automatic calculation of the sub-products. This means manually adding a quantity to the parent product and ensuring that when there are no more units of sub-products available, you set the quantity on the parent to 0. You should also be aware of implications on products with different size variations, like flower and cartridges. Pricing information is pulled from the parent product as well.
Please Note Regarding Product Test Results
The Adilas API does not return test results for parent products. As such, test results will not be pulled and displayed on an online menu unless you enter that information in MyBlackbird directly.
Was this article helpful? Let us know below! We’re always trying to improve and would love to see your feedback.