Has anyone come up with a solution to allow multiple scannable barcodes in the POS?
Hey @Chris_Hildreth, can you share a little more context on the specific roadblock you’re running in to here?
I’m assuming you mean that you are looking for a way to have multiple barcodes on a single product? If so, have you tested if product metafields will work for storing this data?
Yes, multiple scannable barcodes on a single variant product. I have tried the Metafields which allows for the data to be stored and works in a search but those are not scannable values at the Point of Sale to add an item to the transaction. There are numerous reasons why we might end up with different barcoded values on the same product such as 1 set of items was sourced from US inventory and has UPC’s on it vs a different shipment might come from an EU source and have EAN’s on them. Also we are buying other similar businesses to our and many of those have their own barcoding and labeling (lots unfortunately covering up the manufacturers UPC label) that they have been using from their old POS. I really don’t want to have to relabel 10’s of thousands of inventory items when we could just use their old barcode labels in our system if at all possible.
Definitely not possible (this is the first system I’ve ever used which can’t cope with scanning a SKU as well as barcode).
I’d tackle this by adding another variant for each barcode - they’ll still tie to the same parent product; and there may be benefits in tracking different cost prices for each ‘source’ etc too.
only for POS?
this should work:
- Create new product with Extra Barcode and SKU/Price/ETC
- Use mutation CreateBundleComponents to link the original product as a component within the new product.
- Turn off all except for POS
This will then when scanned display and let checkout on the new product, but will split into the component (the original product)