Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted October 11, 20195 yr I was looking and saw that the SKU number wasn't available for Commerce. The posts were older and I didn't see anything else about it. Is the SKU number option available for Commerce yet? If so, where can I find it? I couldn't find it anywhere. If it isn't available natively, is there a good work-around for it? Thank you.
October 14, 20195 yr Custom Fields wouldn't do the trick here. The SKU field is something to identify the product, not information about the purchase. Basically, its something thats along the lines of the Title, Description, Price, Stock Level, etc. of the product. In database terms, we'd need something like p_sku in the nexus_packages table. I imagine a developer could add this, though it would be nice if it were default functionality since SKU is a pretty ubiquitous field among ecommerce offerings.
October 15, 20195 yr What is the end goal? Do you simply want to prevent duplicates using the SKU or do you need to perform other functionality using it?
October 15, 20195 yr In general, it’s just standard practice to clearly and easily identify a product without relying on the name. Imagine you are selling hundreds of technical parts, furniture parts or something like that. Or hundreds of t-shirts all with size and color options. It’s just easier to get the right product in the warehouse when the packaging slip says “AB022” and you go to the AB shelf and pick one of the 022 boxes. Of course it’s also easier to use that code as product identifier in other software the vendor might be using instead of trying to match the name manually.
October 15, 20195 yr In our case we have a connection with one of our suppliers via API. If we had a SKU field, we could match our SKUs to theirs. Analytics programs also have available tracking by SKU (we can use product ID for those, but a SKU being alphanumeric would allow better description)
Archived
This topic is now archived and is closed to further replies.