Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Green
Assigned To: Unassigned
Created By: Cory Warden
Created Date/Time: 10/7/2019 8:36 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 10
Finished/Done: No - (open)
Finished/Done By: ...
Budgeted/Estimated Value: 0.00  
Actual/Real Value: 0.00   [donate]
Invoice/Quote Status: Blank (n/a)
General Amount: $0.00
 
Time Id: 1525
Template/Type: Community Funded Projects
Title/Caption: There are several projects here...
Start Date: 10/7/2019
End Date: 10/7/2019
Total Time: 0.00 Minutes
Target/Due Date: 10/7/2019
Main Status: ** Inactive **

click to enlarge - photo by: Brandon Moore - Screenshot from Steve
click to enlarge - photo by: Brandon Moore - More from the original screenshot.
 


Notes:
Per Steve 10/1/19: We are close to having all the testing results flowing in from Metrc. We can expose the attributes so these can be populated at the same time.
On the labels we do have the PO label that can be configured as you desire. Danny builds these custom per client requirements.
Have you also tried the new adilas label builder?
This is now tied into the attributes for parts and soon POs and Invoice labels
It's our new app that you can build labels for all your systems with. Under 'more options' on each item or PO home Invoice home. Click here to get more information and download your free copy of the adilas label builder app.
https://data0.adilas.biz/MyEasySoftware/adilas_label_builder_app.cfm
Print Custom Pdf Labels

Hey Cory, would you please add this to the list? I'm thinking Josh can help with this one? Per client 9/27/19:
Honestly, I think it's fine to just map the products and not scan the RFID.  As for the COGS, I agree and don't think you should use the numbers in METRC b/c they are often wrong.  But here are some improvements that would be helpful.
If you are missing a parent, you don't need to go out of the METRC API, make the parent and start the PO over
If you make a mistake, you can go back and fix it.  What happens now, is that if you say miss the total costs for one of the items and hit submit, it gives  you an error so you have to go back and add it.  However when you go back, it no longer recognizes the field cost/unit as numeric so you have to start over and retype in the Total costs for every line it.
We don't use the Sub-inventory templates because it's too much work to finish the PO then go to every sub you just added and edit it to add the Sub-inventory attributes.  What would be really great is that during the making of the PO in the METRC API, we had the following fields that we could fill in.  These should be optional and can be left empty if the data is not relevant, not available or folks don't want to use it.  Some of them can be pulled from METRC and some need to be manually entered from the physical products
Manifest #
Received date
Vendor name
Vendor license number
Batch number
Type of Product – for ex. For bud, you could put Indica, Sativa or Hybrid.  For others you may want to write Chocolates, gummies, etc.
Expiration Date
Right now, fulfill bud in the back of the store and place it on the sales floor for the budtender to sell throughout the day.  We do not use Adilas for our fulfillment labels.  So when we fill a vial with bud, my staff prints a label from Dymo that we maintain manually outside of Adilas.  This label has the following information on it:
Strain name so the budtener knows what's in the vial.  Also so when we do inventory, the budtender can count it correctly
Type – Indica, Sativa, Hybrid so the customer knows what it is when they have it at home and can't remember about that strain
Grower License # (required by MED)
Batch # (required by MED)
Last 4 of RFID so when we do inventory the budtender knows which package it is
Weight so the budtender knows what's in the vial and for when we do inventory
At the POS, we add a second label that has our license name, license number, quantity, full RFID and date of sale.  The two label system works really well for us but we have to manually create the fulfillment labels b/c we can't do that in Adilas.
For products, we barcode label everything with the name of the product, the barcode label and the quantity.  That we get in Adilas.  It would be helpful to put the expiration date but there's not really room.  So better would be to be able to pull a report in Adilas to see everything expiring soon or just a list of products and expiration dates that can be exported to excel to sort.  We often have to put stuff on sale that's expiring soon.  Another great report would be a list based on received date so we can see products that are old and need to put on sale.
As I mentioned to Josh about the discount engine, I can afford to put some money in to make these improvements to Adilas.  Thanks.
Regards,
Renee