We’re having difficulties satisfying the required fields for Apparel listing, as we encountered multiple inconsistencies in the Amazon files (XSD and Comprehensive list of apparel size valid values)
Error 1) “Compliant_Size_Values_Apparel” files with Incorrect Values (unnecessary Spaces)
XSLX file with Compliant_Size_Values_GB_Apparel contains many values that look the same to the eye but are not identical values to the computer.
For example, please follow below Amazon link, download the file, pick the sheet "Apparel Size", check the cell E3463, and you can confirm the same
Another example, same file, Sheet “Shirt Size”, check and compare the Values from cells E73271 and E73272
If you have tens of thousands of active listings in apparel, the only efficient option to match them with the latest guidelines is to use Spreadsheets and formulas.
If Amazon put unnecessary spaces on the file, there is a risk that not everyone will be able to use the given table (a pure VLOOKUP or INDEX/MATCH function would not work correctly anymore, and the functions together with TRIM could cause someone to upload unnecessary values to their 3rd party apps.
So now please imagine mapping all of your tens of thousands Apparel Listings Size Names to New Required Size Names (e.g. old Size Name "3XL Reg" mapped to new "3XL")
Then add New Required Fields to New Required Size Names
(Apparel Size System, Apparel Size Class, Apparel Size Value, Apparel Size To Value, Apparel Size Body Type, Apparel Size Height Type)
Then map New Required Size Names to XSD values
"4XL" =" 4x_l", but
Then you realize there is the value "4XL [space] [space]", so you map it to "4x_l" as well
Then you realize there is the value "4XL [space] [space] [space]", so you map it to "4x_l" as well
Then you realize there is the value "4XL [space] [space] [space] [space]", so you decide to fix all the tables with Values and delete all the unnecessary spaces.
There are 7x files (UK, DE, FR, ES, IT, NL, US) x 6 sheets (Apparel, Bottoms, Headwear, Shapewear, Shirt, Skirt). You must first fix the tables with the values from Amazon before you even start repairing your listings and adjusting them to the new requirements!!!
Error 2) There is no logical consequence as how sizes are classified in the Apparel Size Class .
a) download link for Amazon XSLX file with Compliant_Size_Values_GB_Apparel
https://images-na.ssl-images-amazon.com/images/G/02/rainier/help/defects/Compliant_Size_Values_GB_Apparel.xlsx
Why size "M" for UK on "Headwear Size" Sheet has Apparel Size Class=Numeric, while size "M" on "Apparel Size" Sheet has Apparel Size Class=Alpha?
b)download link for Amazon XSLX file with Compliant_Size_Values_GB_Apparel
https://images-na.ssl-images-amazon.com/images/G/03/rainier/help/defects/Compliant_Size_Values_DE_Apparel.xlsx
Why size "S" for DE on the "Headwear Size" Sheet has Apparel Size Class=Numerisch, while size "M" on has Apparel Size Class=Alphanumerish?
c) Another example: FR Shirts
download link: https://images-na.ssl-images-amazon.com/images/G/08/rainier/help/defects/Compliant_Size_Values_FR_Apparel.xlsx)
4XL has Shirt Size Class = Taille de col… while 5XL has Shirt Class= Alpha/letters
I bet 4XL should have Shirt Size Class = Alpha/letters
There are hundreds of mistakes on these files like these two samples above, and if you are using 3rd party app and have tens of thousands of active listings in apparel on multiple Amazon markets, you had, have or will have fun times with Amazon files
Error 3) Some of the product we sell are in "XS/M" size, but such a value does not exist according to Amazon US .
“XS/M” exists on the manufacturer’s website, labels, packaging etc.
Here’s the sample:
https://t.gyazo.com/teams/military1st/8fe2e4b628e97d398377d45239c45f3b.png
I was looking for the value “X-Small-Medium” on Compliant_Size_Values_US_Apparel file, but such size doesn’t exist over there.
(download link: https://amazon-fashion-seller-documentation.s3.amazonaws.com/Compliant_Size_Values_US_Apparel.xlsx)
If we adjust the actual size to the closest one (in this case, "Small-Medium"), we open the way to returns for which we will have to pay
Is there any reason the size is missing from Valid Values?
Error 4) Let’s say you want to list some Apparel with size name “M Long” on the UK market…but it seems be impossible
You can easily find the value "M Long" on the file Compliant_Size_Values_GB_Apparel
Download link: https://images-na.ssl-images-amazon.com/images/G/02/rainier/help/defects/Compliant_Size_Values_GB_Apparel.xlsx
Apparel Size Height Type for the Value "M Long" is "Long"
Here’s the screen for your convenience:
https://t.gyazo.com/teams/military1st/dcb110559b0a19928a5f3012a8f65cf4.png
But you are not able to use the same value "M Long" via Amazon Seller Central/Add Product as the value (Long" is not populated on Apparel Size Heigh Type
Here’s the screen for your convenience:
https://t.gyazo.com/teams/military1st/41c3f65a8831426925c89582388f033c.png
So different Sellers with the same product may use different values to describe the Size Name. It could cause errors in drop-down menus on the product pages and a negative shopping experience.
Error 5) Different values for ApparelHeightType (XSD vs XSLS vs SellerCentral)
ProductClothing.xsd
There is no value "Long" for GB (value "Long" acceptable only on JP)
https://t.gyazo.com/teams/military1st/865b564a7d96dccea11880d5b4f326aa.png
Compliant_Size_Values_GB_Apparel.xlsx
There is value "Long" acceptable on GB
https://t.gyazo.com/teams/military1st/dcb110559b0a19928a5f3012a8f65cf4.png
SellerCentral/Add Product
There is no value "Long"
https://t.gyazo.com/teams/military1st/b1791e7f010eca1721f6a61f94250d48.png
So "Long" is acceptable or not? And if yes, so where?
I know with error 3 you should be using the size to range
so in the one field you put XS and in the size to range you would put M
Can’t help with the rest though as we use Linnworks to list to amazon and having to deal with idiocy if the XSD file values example xx_l instead of xxl is enough to drive you mad.
We’re having difficulties satisfying the required fields for Apparel listing, as we encountered multiple inconsistencies in the Amazon files (XSD and Comprehensive list of apparel size valid values)
Error 1) “Compliant_Size_Values_Apparel” files with Incorrect Values (unnecessary Spaces)
XSLX file with Compliant_Size_Values_GB_Apparel contains many values that look the same to the eye but are not identical values to the computer.
For example, please follow below Amazon link, download the file, pick the sheet "Apparel Size", check the cell E3463, and you can confirm the same
Another example, same file, Sheet “Shirt Size”, check and compare the Values from cells E73271 and E73272
If you have tens of thousands of active listings in apparel, the only efficient option to match them with the latest guidelines is to use Spreadsheets and formulas.
If Amazon put unnecessary spaces on the file, there is a risk that not everyone will be able to use the given table (a pure VLOOKUP or INDEX/MATCH function would not work correctly anymore, and the functions together with TRIM could cause someone to upload unnecessary values to their 3rd party apps.
So now please imagine mapping all of your tens of thousands Apparel Listings Size Names to New Required Size Names (e.g. old Size Name "3XL Reg" mapped to new "3XL")
Then add New Required Fields to New Required Size Names
(Apparel Size System, Apparel Size Class, Apparel Size Value, Apparel Size To Value, Apparel Size Body Type, Apparel Size Height Type)
Then map New Required Size Names to XSD values
"4XL" =" 4x_l", but
Then you realize there is the value "4XL [space] [space]", so you map it to "4x_l" as well
Then you realize there is the value "4XL [space] [space] [space]", so you map it to "4x_l" as well
Then you realize there is the value "4XL [space] [space] [space] [space]", so you decide to fix all the tables with Values and delete all the unnecessary spaces.
There are 7x files (UK, DE, FR, ES, IT, NL, US) x 6 sheets (Apparel, Bottoms, Headwear, Shapewear, Shirt, Skirt). You must first fix the tables with the values from Amazon before you even start repairing your listings and adjusting them to the new requirements!!!
Error 2) There is no logical consequence as how sizes are classified in the Apparel Size Class .
a) download link for Amazon XSLX file with Compliant_Size_Values_GB_Apparel
https://images-na.ssl-images-amazon.com/images/G/02/rainier/help/defects/Compliant_Size_Values_GB_Apparel.xlsx
Why size "M" for UK on "Headwear Size" Sheet has Apparel Size Class=Numeric, while size "M" on "Apparel Size" Sheet has Apparel Size Class=Alpha?
b)download link for Amazon XSLX file with Compliant_Size_Values_GB_Apparel
https://images-na.ssl-images-amazon.com/images/G/03/rainier/help/defects/Compliant_Size_Values_DE_Apparel.xlsx
Why size "S" for DE on the "Headwear Size" Sheet has Apparel Size Class=Numerisch, while size "M" on has Apparel Size Class=Alphanumerish?
c) Another example: FR Shirts
download link: https://images-na.ssl-images-amazon.com/images/G/08/rainier/help/defects/Compliant_Size_Values_FR_Apparel.xlsx)
4XL has Shirt Size Class = Taille de col… while 5XL has Shirt Class= Alpha/letters
I bet 4XL should have Shirt Size Class = Alpha/letters
There are hundreds of mistakes on these files like these two samples above, and if you are using 3rd party app and have tens of thousands of active listings in apparel on multiple Amazon markets, you had, have or will have fun times with Amazon files
Error 3) Some of the product we sell are in "XS/M" size, but such a value does not exist according to Amazon US .
“XS/M” exists on the manufacturer’s website, labels, packaging etc.
Here’s the sample:
https://t.gyazo.com/teams/military1st/8fe2e4b628e97d398377d45239c45f3b.png
I was looking for the value “X-Small-Medium” on Compliant_Size_Values_US_Apparel file, but such size doesn’t exist over there.
(download link: https://amazon-fashion-seller-documentation.s3.amazonaws.com/Compliant_Size_Values_US_Apparel.xlsx)
If we adjust the actual size to the closest one (in this case, "Small-Medium"), we open the way to returns for which we will have to pay
Is there any reason the size is missing from Valid Values?
Error 4) Let’s say you want to list some Apparel with size name “M Long” on the UK market…but it seems be impossible
You can easily find the value "M Long" on the file Compliant_Size_Values_GB_Apparel
Download link: https://images-na.ssl-images-amazon.com/images/G/02/rainier/help/defects/Compliant_Size_Values_GB_Apparel.xlsx
Apparel Size Height Type for the Value "M Long" is "Long"
Here’s the screen for your convenience:
https://t.gyazo.com/teams/military1st/dcb110559b0a19928a5f3012a8f65cf4.png
But you are not able to use the same value "M Long" via Amazon Seller Central/Add Product as the value (Long" is not populated on Apparel Size Heigh Type
Here’s the screen for your convenience:
https://t.gyazo.com/teams/military1st/41c3f65a8831426925c89582388f033c.png
So different Sellers with the same product may use different values to describe the Size Name. It could cause errors in drop-down menus on the product pages and a negative shopping experience.
Error 5) Different values for ApparelHeightType (XSD vs XSLS vs SellerCentral)
ProductClothing.xsd
There is no value "Long" for GB (value "Long" acceptable only on JP)
https://t.gyazo.com/teams/military1st/865b564a7d96dccea11880d5b4f326aa.png
Compliant_Size_Values_GB_Apparel.xlsx
There is value "Long" acceptable on GB
https://t.gyazo.com/teams/military1st/dcb110559b0a19928a5f3012a8f65cf4.png
SellerCentral/Add Product
There is no value "Long"
https://t.gyazo.com/teams/military1st/b1791e7f010eca1721f6a61f94250d48.png
So "Long" is acceptable or not? And if yes, so where?
We’re having difficulties satisfying the required fields for Apparel listing, as we encountered multiple inconsistencies in the Amazon files (XSD and Comprehensive list of apparel size valid values)
Error 1) “Compliant_Size_Values_Apparel” files with Incorrect Values (unnecessary Spaces)
XSLX file with Compliant_Size_Values_GB_Apparel contains many values that look the same to the eye but are not identical values to the computer.
For example, please follow below Amazon link, download the file, pick the sheet "Apparel Size", check the cell E3463, and you can confirm the same
Another example, same file, Sheet “Shirt Size”, check and compare the Values from cells E73271 and E73272
If you have tens of thousands of active listings in apparel, the only efficient option to match them with the latest guidelines is to use Spreadsheets and formulas.
If Amazon put unnecessary spaces on the file, there is a risk that not everyone will be able to use the given table (a pure VLOOKUP or INDEX/MATCH function would not work correctly anymore, and the functions together with TRIM could cause someone to upload unnecessary values to their 3rd party apps.
So now please imagine mapping all of your tens of thousands Apparel Listings Size Names to New Required Size Names (e.g. old Size Name "3XL Reg" mapped to new "3XL")
Then add New Required Fields to New Required Size Names
(Apparel Size System, Apparel Size Class, Apparel Size Value, Apparel Size To Value, Apparel Size Body Type, Apparel Size Height Type)
Then map New Required Size Names to XSD values
"4XL" =" 4x_l", but
Then you realize there is the value "4XL [space] [space]", so you map it to "4x_l" as well
Then you realize there is the value "4XL [space] [space] [space]", so you map it to "4x_l" as well
Then you realize there is the value "4XL [space] [space] [space] [space]", so you decide to fix all the tables with Values and delete all the unnecessary spaces.
There are 7x files (UK, DE, FR, ES, IT, NL, US) x 6 sheets (Apparel, Bottoms, Headwear, Shapewear, Shirt, Skirt). You must first fix the tables with the values from Amazon before you even start repairing your listings and adjusting them to the new requirements!!!
Error 2) There is no logical consequence as how sizes are classified in the Apparel Size Class .
a) download link for Amazon XSLX file with Compliant_Size_Values_GB_Apparel
https://images-na.ssl-images-amazon.com/images/G/02/rainier/help/defects/Compliant_Size_Values_GB_Apparel.xlsx
Why size "M" for UK on "Headwear Size" Sheet has Apparel Size Class=Numeric, while size "M" on "Apparel Size" Sheet has Apparel Size Class=Alpha?
b)download link for Amazon XSLX file with Compliant_Size_Values_GB_Apparel
https://images-na.ssl-images-amazon.com/images/G/03/rainier/help/defects/Compliant_Size_Values_DE_Apparel.xlsx
Why size "S" for DE on the "Headwear Size" Sheet has Apparel Size Class=Numerisch, while size "M" on has Apparel Size Class=Alphanumerish?
c) Another example: FR Shirts
download link: https://images-na.ssl-images-amazon.com/images/G/08/rainier/help/defects/Compliant_Size_Values_FR_Apparel.xlsx)
4XL has Shirt Size Class = Taille de col… while 5XL has Shirt Class= Alpha/letters
I bet 4XL should have Shirt Size Class = Alpha/letters
There are hundreds of mistakes on these files like these two samples above, and if you are using 3rd party app and have tens of thousands of active listings in apparel on multiple Amazon markets, you had, have or will have fun times with Amazon files
Error 3) Some of the product we sell are in "XS/M" size, but such a value does not exist according to Amazon US .
“XS/M” exists on the manufacturer’s website, labels, packaging etc.
Here’s the sample:
https://t.gyazo.com/teams/military1st/8fe2e4b628e97d398377d45239c45f3b.png
I was looking for the value “X-Small-Medium” on Compliant_Size_Values_US_Apparel file, but such size doesn’t exist over there.
(download link: https://amazon-fashion-seller-documentation.s3.amazonaws.com/Compliant_Size_Values_US_Apparel.xlsx)
If we adjust the actual size to the closest one (in this case, "Small-Medium"), we open the way to returns for which we will have to pay
Is there any reason the size is missing from Valid Values?
Error 4) Let’s say you want to list some Apparel with size name “M Long” on the UK market…but it seems be impossible
You can easily find the value "M Long" on the file Compliant_Size_Values_GB_Apparel
Download link: https://images-na.ssl-images-amazon.com/images/G/02/rainier/help/defects/Compliant_Size_Values_GB_Apparel.xlsx
Apparel Size Height Type for the Value "M Long" is "Long"
Here’s the screen for your convenience:
https://t.gyazo.com/teams/military1st/dcb110559b0a19928a5f3012a8f65cf4.png
But you are not able to use the same value "M Long" via Amazon Seller Central/Add Product as the value (Long" is not populated on Apparel Size Heigh Type
Here’s the screen for your convenience:
https://t.gyazo.com/teams/military1st/41c3f65a8831426925c89582388f033c.png
So different Sellers with the same product may use different values to describe the Size Name. It could cause errors in drop-down menus on the product pages and a negative shopping experience.
Error 5) Different values for ApparelHeightType (XSD vs XSLS vs SellerCentral)
ProductClothing.xsd
There is no value "Long" for GB (value "Long" acceptable only on JP)
https://t.gyazo.com/teams/military1st/865b564a7d96dccea11880d5b4f326aa.png
Compliant_Size_Values_GB_Apparel.xlsx
There is value "Long" acceptable on GB
https://t.gyazo.com/teams/military1st/dcb110559b0a19928a5f3012a8f65cf4.png
SellerCentral/Add Product
There is no value "Long"
https://t.gyazo.com/teams/military1st/b1791e7f010eca1721f6a61f94250d48.png
So "Long" is acceptable or not? And if yes, so where?
I know with error 3 you should be using the size to range
so in the one field you put XS and in the size to range you would put M
Can’t help with the rest though as we use Linnworks to list to amazon and having to deal with idiocy if the XSD file values example xx_l instead of xxl is enough to drive you mad.
I know with error 3 you should be using the size to range
so in the one field you put XS and in the size to range you would put M
Can’t help with the rest though as we use Linnworks to list to amazon and having to deal with idiocy if the XSD file values example xx_l instead of xxl is enough to drive you mad.
I know with error 3 you should be using the size to range
so in the one field you put XS and in the size to range you would put M
Can’t help with the rest though as we use Linnworks to list to amazon and having to deal with idiocy if the XSD file values example xx_l instead of xxl is enough to drive you mad.