Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unique Identifiers #8

Closed
Kaschman opened this issue Oct 29, 2019 · 14 comments
Closed

Unique Identifiers #8

Kaschman opened this issue Oct 29, 2019 · 14 comments

Comments

@Kaschman
Copy link
Contributor

SD has a specific SD SKU

Do we use UPCs?

@cmbirk
Copy link
Contributor

cmbirk commented Oct 30, 2019

We likely will have both. Taking a look at schema.org/product It looks like a UPC would be a gtin value, whereas sku has its own attribute as vendor-specific.

@cmbirk
Copy link
Contributor

cmbirk commented Oct 30, 2019

Added to the product schema.

@cmbirk cmbirk closed this as completed Oct 30, 2019
@Kaschman
Copy link
Contributor Author

Kaschman commented Oct 30, 2019

Do we need to save Seller SKU and Retailer SKU? Or just SD's internal SKU?

Also - and making a new ticket for this - is a Product saved at a Style level or a SKU level? If it's at a Style level, a Product will have many SKUs. #9

@cmbirk
Copy link
Contributor

cmbirk commented Oct 30, 2019

I think this is in reference to a product-level sku

@Kaschman
Copy link
Contributor Author

sku-level product? : ) haha

@jrphilo
Copy link

jrphilo commented Oct 30, 2019

We will almost certainly want to have https://en.wikipedia.org/wiki/International_Article_Number built in somehow, and because this is mapping to the SD stuff, we will need to figure out how to map from an EAN (public standard) to SD's internal SKU (purely an SD product ID).

I do not know how an EAN gets built up.

An SD SKU is built along the lines of 0011223344

00 Department
11 Category
22 Style
33 Color
44 Size

This is not exactly right but close enough to give you a gist.

@Kaschman @cmbirk

@jrphilo
Copy link

jrphilo commented Oct 30, 2019

Please make sure with some of these questions you queue them up in a questions list to talk to people (like Dave Barton) about so we are matching existing accepted practices where relevant

@cmbirk
Copy link
Contributor

cmbirk commented Oct 30, 2019

Yep. Regular SKU fits for SD-specific here. Will open a ticket for the International Article Number

@Kaschman
Copy link
Contributor Author

ok it looks like GTIN is a 12 digit code, IAN is a 13 digit code
https://www.gs1uk.org/our-industries/retail/selling-on-marketplaces/ultimate-guide-to-gtins-eans-and-upcs-for-amazon-ebay-google
you can convert GTIN to IAN by adding a 0 - should we be saving everything as IAN?

@Kaschman
Copy link
Contributor Author

oh hang on - Schema.org has this. https://schema.org/gtin
a 13-digit number is an IAN, a 12 digit number is a GTIN

@cmbirk
Copy link
Contributor

cmbirk commented Oct 30, 2019

Yep, and GS1 is a specific standards organization that registers your product ids. It's the org that Eytan told us about previously. Not sure it would benefit us to go down that path at this moment.

@Kaschman
Copy link
Contributor Author

what path specifically? Seems to me we need to add a 'gtin' field that can take a 12 or 13 digit numeric value and serves as a unique identifier for a product

@cmbirk
Copy link
Contributor

cmbirk commented Oct 30, 2019

I believe GTIN codes are specifically assigned from GS1 ( see https://schema.org/gtin12 ). They aren't any generic 12 or 13 digit values. We can use a different identifier for a non-GS1 code.

@Kaschman
Copy link
Contributor Author

we need GTIN for sure
the SKU is an internal identifier from the seller whether it is a marketplace seller or SD - it is the owner of the inventory

should SKU be a part of inventory?

SD SKU is optional (check on this with RC/Bob's)
unsure if seller SKU needs to be included

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants