[Barcode scanner] Disallow barcode on parent variable products, when in Products tab

[iamgabrielma]

From a different fix: #12576

When navigating to Products, and select a variable parent product, we can edit some details like adding an SKU for inventory management. In this case, SKU should be disallowed/hidden as the parent product is just a base for its variations, but is not selectable by itself (only the variations are).

Edit:

When navigating to Products, and select a variable parent product, we can edit some details like adding a barcode tied to the SKU, for inventory management. It's unclear if the use case requires a parent product to have a barcode, since these cannot be added to the order directly, but only their variations are. However, since this is tied directly to the SKU, there could be a case for it.

Keeping this open for discoverability if we happen to work another barcode/scanning milestone.

[dangermattic]

Thanks for reporting! 👍

[rachelmcr]

My understanding from the variable product documentation is that you should be able to manage SKU and inventory at either the parent product level or the variation level (or both).

[iamgabrielma]

My understanding from the variable product documentation is that you should be able to manage SKU and inventory at either the parent product level or the variation level (or both).

Thanks for the link. In this case, seems that the only thing that we should disable is the capacity of adding a barcode to the parent, but not an SKU, is that right? 🤔 Since we use the barcode to add the product directly to an order via scanning, and this shouldn't be possible.

[rachelmcr]

I haven't worked with the barcodes feature, but that sounds right. The only thing I'm not sure about is whether it's expected to be able to get to a variable parent product details by scanning a barcode for it on the Products tab. (In that case, I think I'd expect the option to add a barcode to the parent, but have the scanning feature in Orders ignore any parent product results?)

[iamgabrielma]

I see what you mean. I've edited the issue to narrow down the "problem" (not even sure is a problem, or just unintended miss-use). Keeping this open for the moment for discoverability, in case we happen to work on another barcode/scanning milestone, so we can evaluate it.