Many stores have two different ID's for their products:
- An item number/SKU (used internally for inventory management, reporting, etc); AND
- A separate barcode lookup id (often called the "PLU", often created by the supplier/manufacturer).
Can we add an extra field to the Item Properties for the PLU?
I like that idea. I also have the same need. I dont want to create my own barcodes. Its costly and cumbersome to print barcodes of my own and they dont necessarily stay stuck to the items. Also untidy and gather dust. Worse still, my SKUs are very long because they contain a lot of metadata so if i dont print barcodes the products are impossible to find because no one can remember all my SKUs. I just want to associate the manufacturers PLU or barcode with my SKU so that when i scan the bar code printed on the product by the manufacturer it automatically recognises the product in my inventory. A flag to make an additional attribute searchable in POS would be perfect, but what would also help me a lot is the ability to capture that field by just scanning the manaufacturer barcode. So basically just go through all my products one by one and for each one just put the cursor on the attribute and scan. The thought of capturing all the manufacturer PLUs manually makes me want to slit my wrist right here and now. Thanks you.
A suggestion - I wonder if this Request is best dealt with by introducing Custom Fields (
More work initially but would handle all future requests of the nature "I need an extra field for <my requirement here>".
Is there a way to search for products in POS by just typing the name of the product or do i have to add them all onto Quick Sell? Coz that would be a good interim solution for me. As i see it it would simply mean the product name/description becomes searchable in POS.
A second box could be added easily, but when i take a look at this request, the first thing that comes to mind is, what if someone want a thrid, then 4th field. I think Jarrons addition to this would make more sense in addition to this... a flag that would make the custom field searchable when a barcode is scanned.
I'll take all of these into consideration when creating my iniital plan. I'll then dump the idea here for review prior to implementation.
I didn't notice from your reply, are you using the group codel/masters sku? if not, you can put the short sku under the group code
It looks like that field is for capturing a manufacturer's Case SKU for Purchase Ordering (and accompanying the ratio of Item-SKUs-per-Case-SKU).
I think that can probably do what I need - thx.
We are not using Cash Footprint for Purchasing or Inventory Management. In this scenario, is it OK to use the Case SKU field and leave "Items per Case" at its default value of zero? Any downstream negative impact you can see on doing this?
Ok, so you use all 3 values right now (item number, group code and case plu)? I will take a peek at adding more alias values.