Replies: 2 comments
-
My initial thought was, this does indeed seem like extension territory ... but if there is sufficient demand and adding this generally reduces friction, it could be a nice win. I'm also curious about how it would work on the frontend—would there be a corresponding setting to specify what the field actually is (ie, a setting to designate it as the ISBN field rather than a EAN field)? Fwiw, reminder here that we actually already support custom product fields (or, inherit them from WordPress) which can be configured on a post-by-post basis, and perhaps this could be complimented by new functionality that allows them to be defined globally—could that be the better/more flexible solution? |
Beta Was this translation helpful? Give feedback.
-
Expanding on Nathan's points, we're evaluating adding this as a Core option because it holds significant potential benefits for a large number of merchants. These include:
|
Beta Was this translation helpful? Give feedback.
-
We've been studying adding a new field (provisory name: Unique ID) to the product. The initial idea, described in #39577, is that this field can represent multiple unique identifiers, like GTIN, UPC, EAN, or ISBN. It also makes sense to add it to the Inventory tab of the legacy editor, if it's useful. This is a common demand and some extensions already implement similar behavior. We want to gather feedback before we decide how we should approach this.
Some points to discuss:
I've written a PoC that adds the field to the product and the new product editor. You can check it out here.
Proposed deadline: May 31st
Beta Was this translation helpful? Give feedback.
All reactions