Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Green
Assigned To: Unassigned
Created By: Cory Warden
Created Date/Time: 1/3/2020 1:02 pm
 
Action Status: Paused
Show On The Web: Yes - (public)
Priority: 6
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: 1599
Template/Type: Community Funded Projects
Title/Caption: Tracking of inventory via secondary barcodes
Start Date: 1/3/2020
End Date: Unknown... (open or blank)
Total Time: Unknown... (open or blank)
Target/Due Date: 1/3/2020
Main Status: Active

Sorry, no photos available for this element of time.


Uploaded Media/Content & Other Files (6)
Media Name   File Type Date Description
adilas_bidding_estimate for 710 labs secondary barcode project.xlsx   Doc/Spreadsheet 3/20/2020
custom_process_for_time_id_1599_in_adilas.mp4   Video 3/4/2020 This is a 15 minute video showing some of their existing spreadsheets and logistics and how they setup routes and what not.
flow chart_1.png   Image/PNG 2/27/2020
flow chart_2.png   Image/PNG 2/27/2020
flow chart_3.png   Image/PNG 2/27/2020
710 Labs Flow (1).pdf   Doc/PDF 2/24/2020


Notes:

4/2/20: Did a proposal- never heard back.

2/25/20: Received flow chart from client. Set meeting to review chart for comprehension on 2/27/20.

2/11/20: Moving forward...Physical vs digital inventory discrepancy in adilas. Goal is to create a scanning mechanism to scan a barcode and track inventory from sales rep to partners.


1/21/20: Client is thinking about it and will get back to us


From 710:

1) Sales rep creates transition invoice with items to hold product so no one else can sell. Get order from dispensary. Confirm order. Will click on email but instead of sending to dispensary send to the team (logistics, inventory and fulfillment.) They email the Logistics team once that invoice has been confirmed.

*Activate setting that currently exists to add QR code to the bottom of the invoice.

* It might help to assign SKUs cold or warm in inventory.

 

2) Inventory pulls the order and hands it off to Fulfilment. 

*Would be amazing to have a way to scan check out SKUs from inventory to fulfilment, but this isn’t needed for this exercise. Just an idea we like.

 

3) Fulfilment prints out the invoice to box up the order to get it ready for delivery. 100 items but only two delivery boxes. Fulfilment puts the items in either warm boxes or cold boxes. (freezer vs fridge)

Details: There could be 1 sku in 3 different boxes or 3 skus in 1 box. There can be multiple cold or warm boxes. Depends on the size of the order and the amount of cold vs. warm products on the invoice.

For example, we’ll label an order that takes 5 Boxes (3 warm, 2 cold): 1/5W, 2/5W, 3/5W, 4/5C, 5/5C. Or a two box order (1 warm, 1 cold), 1/2W, 2/2C.

 

4) Fulfillment scans the QR code on the invoice to pull it up. Now the cold box(es) and warm box(es) each need their own barcode assigned to the master invoice.  Need to know 1 of 5 cold boxes (how many of each kind). 

For Example, on Invoice 4125 (QR Code 1) that has 5 Boxes (3 warm, 2 cold)::

  • 4125.1.5W (QR Code 1A)
  • 4125.2.5W (QR Code 1B)
  • 4125.3.5W (QR Code 1C)
  • 4125.4.5C (QR Code 1D)
  • 4125.5.5C (QR Code 1E)

 

5)  Once the barcodes are assigned to the boxes, each time they are scanned it will check them in or out of their next destination.

*It’s crucial that each time they’re checked in or out it only works if all boxes on the invoice are scanned. So it needs to notify whoever is moving the boxes that this invoice is missing a box.  

a) Check-in to invoice

b) Check out of facility ** There would sometimes be a variable where the boxes would skip from stage b to stage e so there would need to be a way to enter or set the course or itinerary for the boxes in step 4.

c) Check in to layover (for the socal orders)May sit for a couple of days here

d) Check out of layover

e) Check in to sales location ***This check in would be the final stage and it would convert transition invoice to customer invoice


Phases that things go through along with communication that goes along with that. Check boxes- where is this advancing along its way. Only way to pull from inventory is using the transitional invoice. 

Sales rep- processor-fulfillment- are all phases. 

Many different products, always changing. Small batch with lots of variety. 

Some accounts are getting 2 orders a week. Some less active. Send out a menu twice a week.

Another phase at some time: Items shouldn't be active until they are ready to ship

Are 10 packs ever broken up- NO.

Might be individual products and samples available as needed.



How could they use internal builds to package up to the next level. 


Add invoice grouping as a possible solution


Is there a way to print out two QR codes associated with invoice. Tells us what is in the boxes and also track the movement of the boxes- check in check out?

There is some labeling where certain phases need to generate a label. Almost a sub phase. 


Use flex grid to tie to an element of time to the invoice. 


Flow chart: Zack will create one. 


Additional Comments/Notes - Subs (2)
Title/Caption Date Time Done By Comment/Note
Questions from initial flow chart review 2/27/2020 12:01 pm Cory Warden
Brandon and I went through the flow chart and have some questions. We would like to schedule a meeting next week to go over everything with you. I will write down our questions here so you can have an idea of what we are needing. I am also attaching a few screen shots that show how we numbered everything, and the questions connect to the numbers written on the screen:

1)How is product transferred to Distributor- how does it come in- on a PO? 
Do you need a phase here (element of time) saying "we got it?" Does it sit in a queue? Do you receive it into inventory?

Amelia St (manufacturer to distributer) to ASV-EQ1 with a normal invoice. From one corp to another.

2) Does product get invoiced out to be tested at lab? Yes. ASV-EQ1 will create an invoice for the lab. Not testing every item or every gram. Between 8-13 items. Amount can vary based on the amount of the master batch. Different for each project.

Or a piece of the product, and the rest sits in inventory? see above
Then, once tested, what needs to be recorded? Once results come back, we are adding all required lab result data.
How do we know something is out for testing (or is it only a sample)? Is this another phase to track? No
How do we know something needs to be tested? All product is tested. Individual batches get passed testing date in sub attributes. 
How long is it in testing? 2-5 days. Are all products in testing for same length of time (ie are there multiple answers)? Is this already built into sub attributes?

Potentially a custom inventory list- only shows items that have passed testing. Other items stay hidden. Preset filter based off of sub attributes. Maybe once the items are a 10pk then they make the list.

Between #2) and #3)= Does it have to pass testing to get a UID and barcode? Yes. What is the process? Already packaged in individual grams. Manufacturer is packaging. Distributor sends items to the lab. Add barcode and UID once it passes. It gets one big sticker- uid, strain, batch number, lab results, date packaged, manufactured date, expiration date, license number (manufacturer).  What happens if it doesn't pass testing (ie does it go to a completely different process)? Do we need to add a sub process to clean it up or send it elsewhere? Never happens!! Go Scott!


Question- are 1-3 being tracked? Yes they are. Is each number a phase? Yes it is. If not, which ones are phases? Sub locations- putting items where they can't be sold. Out for testing, being stickered= not available. Once stickered- yes, can be sold. A sales location.

3) Do we need to print a label for the barcode here? (UID supplied by Franwell/metrc) No, will already have UID on the package. Only need barcodes for 10pks and delivery boxes (not needed on individual items)

4) This is a build process. Raw item turned into 10 pack. (use internal build, recipe or production) Will create sub inventory (10pk)
Brief discussion about mini conversions. Stick with normal build process for now.

5) Need more info- what is double confirm= is it a sign off? Is it a visual or physical quality control. Yes.This will be an Element of Time that needs to be recorded. Not necessary to confirm in adilas.

6) This is inventory now, sitting on the shelf.

Question- Are #4) and #6) the same step? Or is there a difference and if so what is it? Not really. See #4. 

7) Use shopping cart. This is when it would be great to have the filtered inventory list so sales rep can see what is truly available.

8)Confirm through email? Or how? Confirm with retailer, make changes per interaction with retailer. Then once its built, transition invoice is sent by sales rep via email to group email- fulfillment and logistics
9) Sending email or how? See above.
Using transitional invoices to claim inventory. Hold it for one retailer until confirm yes or no.

10)-11)= Are they scanning all items onto invoice? Typing in items - getting long list. Need to filter!!
How are you dealing with back orders? No back orders. Only full orders on transitional invoice. Small batch- inventory is always changing- Recommendation is if you only have 3 of 4 items, to put 3 on one invoice, remove the 4th from that invoice and create another invoice with the 4th. Can flex grid the two invoices together. 

Question- between 7 and 11= what are you scanning during 11, since items are already on invoice from step 7? Are you removing items originally placed on invoice? Items are on the invoice. 10/11= when invoice in its digital form is sent to inventory. Inventory pulls the actual items and fulfillment assigns it to a delivery box.
Pull the items and put in a clear bin and send it off to fulfillment.

10) This is another Element of time dealing with logistics, routes. How are you currently doing this (ie with spreadsheets, badger?) Do you want to automate this? We can tie it in. (see video attached for details)

12) Ok metrc manifest stays as is.

11) and 13) seem similar- what is the difference?

14) Figure out how to assign boxes to invoices. Is there labeling after 13? Could add flex grid to invoice for each box and each box would have a barcode flex gridded in. Once we have transitional invoice, we have all of the pieces. Create a small interface that says "pull inventory" and you can check it off the list. 

13-15) Seems like one giant step (process). Pack it and label it. Not sure if joined or separate. When it's time to pack it- another interface: Decide what to pull together into a box. Check them off. 

16) Double confirm- is it a new sign off, physical or visual? What are you doing here? Yes, someone who hasn't packed them does an intake to make sure what's inside matches the invoice.

17) Something with elements of time. Once we have box counts done, link pieces together: driver, vehicle, boxes in order. 
How detailed do you need to be? GPS coordinates for destinations or are addresses ok? Addresses are good. Are also linked to licenses so that is important for compliance.

18) Report needs to be created based off 14 and 17 to give to the driver. Correct.

19) Driver scans barcodes. This currently doesn't exist. Custom interface that will be automated. Driver fills in their info- name, vehicle, then scans first barcode- we can stamp it with date and time- any other info needed? Box description ie warm/cold? Then they scan next barcode, same outcome, and next and so on. Yes

20) Another scan time when delivered. Can have an interface that acts just like the last one: driver, vehicle, time/date stamp when scanned in. This will alleviate having to go back to the invoice itself and look up the box and do that action there. Yes absolutely

21) and 22) Another interface- need to know what you want to track. date/time/notes. Any way to link this in to adilas would be helpful but it isn't necessary.
Flow Chart 2/11/2020 4:11 pm Cory Warden

Phase one: Sales rep build invoice. Interaction between buyer and sales rep. Pulling inventory from adilas using transition invoice. Using checkout on account. Lock it. Stays in this phase so that sales rep can delete and add. Hold on to this until order is confirmed. Once confirmed...

Phase two: Inventory and fulfillment processing the order. Physically pulling the inventory and putting it into the delivery boxes. Might need to break this into more pieces. May not be instantaneous. Sometimes we can't actually fulfill the order. Can we fulfill? If yes, goes into the delivery boxes. If there are 10 10pks, how are we breaking these down- it is based on the item. Set of items need cold box, another set needs a warm box. What if you have 9 of 10 items? Do you pull the one unavailable item onto its own invoice because it can't advance? They can make changes to invoice based on this scenario- change out the item for a new item. Sales reps aren't allowed to make these changes- only fulfillment and inventory team. Locking and permissions at certain phases- for these settings- can't be touched by certain people. At the end of phase two- need a box count/list. Invoice X has two boxes- one is warm, second is cold. Want to be able to assign QR code to boxes and also know QR codes for items that are in the boxes. One QR code has a sub list underneath it.

Phase three: Logistics team takes over. Route creation. Delivery boxes are sealed and ready to be delivered. Need to pick what day they will leave and where they are going. Would want to create a schedule of the 5 invoices. QR codes are linked to a delivery schedule as well. Need some upper level views to estimate the routing. Almost happens at the same time as phase two.Once you know what needs to go where, you can start planning out the route. (grouping)

Phase four: Route, box list. Five stops on the route. Driver needs to have all 10 boxes and then they can check out. Can't if they don't. Will scan the QR codes on the boxes. Make sure they have all invoices and all boxes for that day. 

Phase five: Handing off to a dispensary or checking in and then out of a layover, and then handing off to a dispensary. Must scan out of van and into dispensary or layover (in/out first) and then dispensary.