New Apparel Size Requirements for Amazon

Article author
Store Automator
  • Updated

With Store Automator’s built-in templates, you can simply meet the new Amazon clothing size requirements.

Amazon requires new specifics attributes for each type of clothing listing to facilitate a more consistent customer experience. Sellers were free to insert any wording referring to their product size; now, they will need to choose newly added options. The attribute size_name will remain in the Amazon catalog but will no longer be available while listing.

You can publish your clothing listings with the Store Automator field mapping system easily. You just need to create necessary custom fields and mapping with required attributes. You can upload your listings in bulk upload field options. Therefore, you can update your listings or create new listings regardless of your number of listings in a minute. Store Automator assists its clients to implement their existing listings to related categories required templates.

 

IMPORTANT

All required fields are needed to be filled for parent products to create variation.

If you leave these fields blank, your variation will not be created correctly, and you will get errors. The values which are filled for parent is not necessary due to being accessory

 

New Amazon Apparel Size Attributes and Accepted Values

- Target Gender is required on all submissions

Valid Values: male, female, unisex

 

- Age Range Description is required on all submissions

Valid Values: adult, big kid, little kid, toddler, infant

 

Required attributes vary by product type

 

 

NOTE: To publish new clothing listings, new templates are needed to be created according to the size system. If you want to publish shirt listings, a shirt size system is needed. You cannot use apparel size systems or bottom size systems. Therefore, each size system needs to have its own template.

 

Apparel Size Attributes

- Apparel Size System is required on above product type listings submissions. (Dress,Sweater,Blazer,Coat,Vest.. etc)

Valid Values: as1,as2,as3,as4,as5,as6,as7,as8

 

- Apparel Size Class is required on the above product type listings submissions. (Dress,Sweater,Blazer,Coat,Vest.. etc)

Valid Values: numeric, numeric_range, alpha, alpha_range, age, age_range

 

- Apparel Size is required on the above product type listings submissions. (Dress,Sweater,Blazer,Coat,Vest.. etc)

Valid Values:

If Apparel Size Class is equal to Numeric; numeric_7, numeric_7_point_5, numeric_8 etc.

If Apparel Size Class is equal to Numeric range; numeric_7, numeric_7_point_5, numeric_8 etc.

If Apparel Size Class is equal to Alpha; one_size, s, m, l, x_l, etc.

If Apparel Size Class is equal to Alpha Range; one_size, s, m, l, x_l, etc.

If Apparel Size Class is equal to Age; 6_months, 2_years, 4_point_5_years, etc.

If Apparel Size Class is equal to Age Range; 6_months, 2_years, 4_point_5_years, etc.

 

- Apparel Size To When Apparel Size Class = numeric range, alpha range, or age range, the Apparel Size To attribute becomes required.

Valid Values:

Numeric: numeric_7, numeric_7_point_5, numeric_8 etc.

Alpha; one_size, s, m, l, x_l etc.

Age; 6_months, 2_years, 4_point_5_years etc.

 

NOTE: The value selected in Apparel Size To must be greater than the value selected in Apparel Size.

 

If Apparel Size is equal to s (small), then Apparel Size To must be greater than s (small). To be shown as Small-Medium in the dropbox, Apparel Size To must be defined as m (medium).

Examples: 30-32, Small-Medium, 3-6 Months

 

- Apparel Body Type is required on above product type listings submissions. (Dress,Sweater,Blazer,Coat,Vest.. etc)

Valid Values: big,slim,regular,plus

 

- Apparel Height Type is conditional required on above product type listings submissions (Dress,Sweater,Blazer,Coat,Vest.. etc). Sometimes-depends on product type and age range.

Valid Values: petite, regular, tall, extra_tall, long, short

 

Shirt Size Attributes

- Shirt Size System is required on shirt listings submissions.

Valid Values: as1,as2,as3,as4,as5,as6,as7,as8

 

- Shirt Size Class is required on shirt listings submissions.

Valid Values: numeric, numeric_range, alpha, alpha_range, age, age_range, neck, neck_sleeve

 

- Shirt Size is required on shirt listings submissions.

Valid Values:

If Shirt Size Class is equal to Numeric; numeric_7, numeric_7_point_5, numeric_8 etc.

If Shirt Size Class is equal to Numeric range; numeric_7, numeric_7_point_5, numeric_8 etc.

If Shirt Size Class is equal to Alpha; one_size, s, m, l, x_l, etc.

If Shirt Size Class is equal to Alpha Range; one_size, s, m, l, x_l, etc.

If Shirt Size Class is equal to Age; 6_months, 2_years, 4_point_5_years, etc.

If Shirt Size Class is equal to Age Range; 6_months, 2_years, 4_point_5_years, etc.

If Shirt Size Class is equal to neck or neck_sleeve: Shirt Neck Size becomes required. 12”, 18" etc.

 

- Shirt Size To When Shirt Size Class = numeric range, alpha range, or age range, the Shirt Size To attribute becomes required.

Valid Values:

Numeric: numeric_7, numeric_7_point_5, numeric_8 etc.

Alpha; one_size, s, m, l, x_l etc.

Age; 6_months, 2_years, 4_point_5_years etc.

 

NOTE: The value selected in Shirt Size To must be greater than the value selected in Shirt Size.

If Shirt Size is equal to 6_months, then Shirt Size To must be greater than 6_months. To be shown as 6 Months- 9 Months in the dropbox, Shirt Size To must be defined as 9_months.

Examples: 30-32, Small-Medium, 3-6 Months

 

- Shirt Body Type is required on shirt listings submissions.

Valid Values: big,slim,regular,plus

 

- Shirt Height Type is required on shirt listings submissions.

Valid Values: petite, regular, tall, extra_tall, long, short

 

Bottoms Size Attributes

- Bottoms Size System is required on the above product type listings submissions. (Pants, Shorts, Overalls).

Valid Values: as1,as2,as3,as4,as5,as6,as7,as8

 

- Bottoms Size Class is required on above product type listings submissions. (Pants, Shorts, Overalls).

Valid Values: numeric, numeric_range, alpha, alpha_range, age, age_range, waist, waist_inseam

 

- Bottoms Size is required on the above product type listings submissions (Pants, Shorts, Overalls).

 

Valid Values:

If Bottoms Size Class is equal to Numeric; numeric_7, numeric_7_point_5, numeric_8 etc.

If Bottoms Size Class is equal to Numeric range; numeric_7, numeric_7_point_5, numeric_8 etc.

If Bottoms Size Class is equal to Alpha; one_size, s, m, l, x_l, etc.

If Bottoms Size Class is equal to Alpha Range; one_size, s, m, l, x_l , etc.

If Bottoms Size Class is equal to Age; 6_months, 2_years, 4_point_5_years, etc.

If Bottoms Size Class is equal to Age Range; 6_months, 2_years, 4_point_5_years, etc.

If Bottoms Size Class is equal to Waist: Bottoms waist size becomes required.

If Bottoms Size Class is equal to waist inseam: Bottoms waist size and Bottoms inseam size become required.

 

- Bottoms Size To When Bottoms Size Class = numeric range, alpha range, or age range, the Bottoms Size To attribute becomes required.

 

Valid Values:

Numeric: numeric_7, numeric_7_point_5, numeric_8 etc.

Alpha; one_size, s, m, l, x_l etc.

Age; 6_months, 2_years, 4_point_5_years etc.

 

NOTE: The value selected in Bottoms Size To must be greater than the value selected in Bottoms Size.

If Bottoms Size is equal to numeric_30 (30), then Bottoms Size To must be greater than numeric_30 (30). To be shown as 30-34 in dropbox, Bottoms Size To must be defined as numeric_34 (34).

Examples: 30-34, Small-Medium, 3-6 Months

 

- Bottoms Body Type is required on the above product type listings submissions (Pants, Shorts, Overalls).

Valid Values: big,slim,regular,plus

 

- Bottoms Height Type is conditional required on above product type listings submissions (Pants, Shorts, Overalls)—Sometimes-depends on product type and age range.

Valid Values: petite, regular, tall, extra_tall, long, short

 

Skirt Size Attributes

- Skirt Size System is required on skirt listings submissions

Valid Values: as1,as2,as3,as4,as5,as6,as7,as8

 

- Skirt Size Class is required on skirt listings submissions

Valid Values: numeric, numeric_range, alpha, alpha_range, age, age_range, waist.

 

- Skirt Size is required on skirt listings submissions

 

Valid Values:

If Skirt Size Class is equal to Numeric; numeric_38, numeric_38_point_5, numeric_39 etc.

If Skirt Size Class is equal to Numeric range; numeric_38, numeric_38_point_5, numeric_39 etc.

If Skirt Size Class is equal to Alpha; one_size, s, m, l, x_l, etc.

If Skirt Size Class is equal to Alpha Range; one_size, s, m, l, x_l, etc.

If Skirt Size Class is equal to Age; 6_months, 2_years, 4_point_5_years, etc.

If Skirt Size Class is equal to Age Range; 6_months, 2_years, 4_point_5_years, etc.

If Skirt Size Class is equal to waist: Skirt waist size becomes required.

 

- Skirt Size To When Skirt Size Class = numeric range, alpha range, or age range, the Skirt Size To attribute becomes required.

 

Valid Values:

Numeric: numeric_40, numeric_40_point_5, numeric_41 etc.

Alpha; one_size, s, m, l, x_l etc.

Age; 6_months, 2_years, 4_point_5_years etc.

 

NOTE: The value selected in Skirt Size To must be greater than the value selected in Skirt Size.

If Skirt Size is equal to numeric_30 (30), Skirt Size To must be greater than numeric_30 (30). To be shown as 30-34 in dropbox, Skirt Size To must be defined numeric_34 (34).

Examples: 30-34, Small-Medium, 3-6 Months

 

- Skirt Body Type is required on skirt listings submissions

Valid Values: big,slim,regular,plus

 

- Skirt Height Type is conditionally required on skirt listings submissions. (Sometimes-depends on product type and age range).

Valid Values: petite, regular, tall, extra_tall, long, short

 

Shapewear Size Attributes

- Shapewear Size System is required on the above product type listings submissions (Bra, Swimwear, Undergarment slip, Corset).

Valid Values: as1,as2,as3,as4,as5,as6,as7,as8

 

- Shapewear Size Class is required on the above product type listings submissions (Bra, Swimwear, Undergarment slip, Corset).

Valid Values: numeric, numeric_range, alpha, alpha_range, age, age_range, cup size, band size.

 

- Shapewear Size is required on the above product type listings submissions (Bra, Swimwear, Undergarment slip, Corset).

 

Valid Values:

If Shapewear Size Class is equal to Numeric; numeric_38, numeric_38_point_5, numeric_39 etc.

If Shapewear Size Class is equal to Numeric range; numeric_38, numeric_38_point_5, numeric_39 etc.

If Shapewear Size Class is equal to Alpha; one_size, s, m, l, x_l, etc.

If Shapewear Size Class is equal to Alpha Range; one_size, s, m, l, x_l, etc.

If Shapewear Size Class is equal to Age; 6_months, 2_years, 4_point_5_years, etc.

If Shapewear Size Class is equal to Age Range; 6_months, 2_years, 4_point_5_years, etc.

If Shapewear Size Class is equal to Cup Size: A, B, C, D, AA, GG, FF, DD, etc.

If Shapewear Size Class is equal to Band Size: 44, 46,48, 50,52 etc.

 

- Shapewear Size To When Shapewear Size Class = numeric range, alpha range, or age range, the Shapewear Size To attribute becomes required.

 

Valid Values:

Numeric: numeric_40, numeric_40_point_5, numeric_41 etc.

Alpha; one_size, s, m, l, x_l etc.

Age; 6_months, 2_years, 4_point_5_years etc.

 

NOTE: The value selected in Shapewear Size To must be greater than the value selected in Shapewear Size.

If Shapewear Size is equal to numeric_44 (44), then Shapewear Size To must be greater than numeric_44 (44). To be shown as 44-46 in the dropbox, Shapewear Size To must be defined numeric_46 (46).

Examples: 44-46, Small-Medium, 3-6 Months

 

- Shapewear Body Type is required on the above product type listings submissions (Bra, Swimwear, undergarment slip, corset).

Valid Values: big,slim,regular,plus

 

- Shapewear Height Type is conditionally required on Shapewear listings submissions. (Sometimes-depends on product type and age range).

Valid Values: petite, regular, tall, extra_tall, long, short

 

Headwear Size Attributes

- Hat Size System is required on Hat listings submissions

Valid Values: as1,as2,as3,as4,as5,as6,as7,as8

 

- Hat Size Class is required on Hat listings submissions

Valid Values: numeric, numeric_range, alpha, alpha_range, age, age_range.

 

- Hat Size is required on Hat listings submissions

 

Valid Values:

If Hat Size Class is equal to Numeric; numeric_38, numeric_38_point_5, numeric_39 etc.

If Hat Size Class is equal to Numeric range; numeric_38, numeric_38_point_5, numeric_39 etc.

If Hat Size Class is equal to Alpha; one_size, s, m, l, x_l, etc.

If Hat Size Class is equal to Alpha Range; one_size, s, m, l, x_l, etc.

If Hat Size Class is equal to Age; 6_months, 2_years, 4_point_5_years, etc.

If Hat Size Class is equal to Age Range; 6_months, 2_years, 4_point_5_years, etc.

 

- Hat Size To When Hat Size Class = numeric range, alpha range, or age range, the Hat Size To attribute becomes required.

 

Valid Values:

Numeric: numeric_21, numeric_21_point_5, numeric_22 etc.

Alpha; one_size, s, m, l, x_l etc.

Age; 6_months, 2_years, 4_point_5_years etc.

 

NOTE: The value selected in Hat Size To must be greater than the value selected in Hat Size.

If Hat Size is equal to numeric_21 (21), Hat Size To must be greater than numeric_21 (21). To be shown as 21-22 in dropbox, Hat Size To must be defined as numeric_22 (22).

Examples: 30-34, Small-Medium, 3-6 Months

 

- Hat Body Type is required on Hat listings submissions

Valid Values: big,slim,regular,plus

 

- Hat Height Type is conditional required on Hat listings submissions. (Sometimes-depends on product type and age range).

Valid Values: petite, regular, tall, extra_tall, long, short

Was this article helpful?

0 out of 0 found this helpful