Barcode Printing
I am setting up Barcodes for some inventory tracking in our company, and am wondering if we need to buy a barcode printer that is compatible with a certain software? Is it as simple as using a Bluetoo...
Forum Discussion
Yes that is the plan for our team as well, we will be linking all QR codes to an inventory item so when they scan the QR code using their phone, it will pull up that item for them and they can make inventory adjustments as needed.
I think we got that part good to go, and are ready to order the label printer. However, I am wondering if we need to order one that supports a specific software. It looks like they need to be CSV compatible but has your team run into any other issues with the system you are using?
------------------------------
Darian Vigil
------------------------------
I think we got that part good to go, and are ready to order the label printer. However, I am wondering if we need to order one that supports a specific software. It looks like they need to be CSV compatible but has your team run into any other issues with the system you are using?
------------------------------
Darian Vigil
------------------------------
The inventory we track are actually large items outdoors, so we have our QR codes printed by a company that offers the printing on weather proof stickers, and metal tags, etc. So unfortunately I do not have any experience or advice on printing yourself.
However, regarding the URL itself, there are two ways to go about it, that you should consider.
1. URL references the record ID. This is nice and simple, but comes with some drawbacks. Your 'ID' or 'Barcode Number' for each inventory item will essentially be the Record ID. For us, this was not good because when you scan the URL, anyone can put any random record ID in the URL to see other inventory items. I did not want people to be able to 'guess' other URLs. Also, using a record ID, if anything happens to that record (maybe you accidentely delete it), you have to change out any stickers in reference to the item (when you recreate it, it will have a new record id). For us, another reason Record ID didn't work is our tags can fail over time in the elements and we have to put a new one on. That requires us ordering the same tag from the company (if you are printing your own, you avoid this).
2. Alternatively you can make a key field. That is what I did - I have a random 6 digit alphanumeric code. My URL uses the key field instead. Solves all the problems above, but does have one very large drawback. Our inventory items have children (photos, inspection reports, etc). When I change out a QR tag to a new number, I go into my database and we can type in the new Alpha Numeric number there. Seems great, except that immediately orphans the children. I combat this with automations, but indeed it is a chunk of extra work.
------------------------------
Mike Tamoush
------------------------------
However, regarding the URL itself, there are two ways to go about it, that you should consider.
1. URL references the record ID. This is nice and simple, but comes with some drawbacks. Your 'ID' or 'Barcode Number' for each inventory item will essentially be the Record ID. For us, this was not good because when you scan the URL, anyone can put any random record ID in the URL to see other inventory items. I did not want people to be able to 'guess' other URLs. Also, using a record ID, if anything happens to that record (maybe you accidentely delete it), you have to change out any stickers in reference to the item (when you recreate it, it will have a new record id). For us, another reason Record ID didn't work is our tags can fail over time in the elements and we have to put a new one on. That requires us ordering the same tag from the company (if you are printing your own, you avoid this).
2. Alternatively you can make a key field. That is what I did - I have a random 6 digit alphanumeric code. My URL uses the key field instead. Solves all the problems above, but does have one very large drawback. Our inventory items have children (photos, inspection reports, etc). When I change out a QR tag to a new number, I go into my database and we can type in the new Alpha Numeric number there. Seems great, except that immediately orphans the children. I combat this with automations, but indeed it is a chunk of extra work.
------------------------------
Mike Tamoush
------------------------------
- Hi Mike, I am trying to start an inventory also with large equipment and fixed GPS items on the equipment. As you said the elements can take affect and stickers can be damaged or lost. My work around was to be able to stick any random alpha-numeric numbered barcode on the GPS or tool item when its lost and just reassign that tool with the new number. At that point everyone said there would be orphans....How did you deal with orphans using an API to reassign them? Is it as easy as a search command for the old tag number to be replaced by the new tag number application wide?
Thanks for your input. I have been working with this a while and I am ready to implement it. Hoping to be able to use random numbers to eliminate the need for printing in the field.
Thanks
------------------------------
Michael Hall
------------------------------- Good morning,
Why not just re-print the same code for the same piece of equipment?
I don't think that you should necessarily use the Record ID for the key field. However, you shouldn't think that your data is secure because you use a random number. Depending on their role and the permissions, people can still access all of the particular records using the Record ID. You're much better off using Role Permissions to ensure the Data Security.
Thank you,
John
------------------------------
John Crosland
Software Developer
Inglett & Stubbs
Mableton GA
------------------------------- Thanks for the reply John, I was actually attempting to make labeling and relabeling in the field an easier process by being able to use any number tag and then simply applying the number to the unit in a specific identifying field that is related to the serial number. In the event the tag needed replacing I wanted to be able to apply the next numbered tag and change the records field to the new number. I realized this would cause orphan records which I would need to deal with in some way.
Security was not an issue. Simplicity for field personnel not adept to using QB or printing new identical tags was more the issue.
------------------------------
Michael Hall
------------------------------
