Fashion and apparel product feeds carry attributes most other categories don't—size, color, gender, age group, and material—and each one is a common source of Google Shopping rejections. That's not a minor detail: apparel feeds have the highest disapproval rate of any Shopping category, precisely because of these variant requirements. If you sell clothing, footwear, accessories, or beauty, managing your feed is a different job than it is for electronics or homewares, and this guide covers what's actually different.
Why fashion feeds are harder than other categories
A single apparel product is rarely a single feed entry. A shirt in five colors and four sizes is twenty separate products in your feed—each needing its own complete, correct set of attributes, and all of them needing to be linked back together so Google understands they're one style. Multiply that across a catalog and the surface area for error explodes.
On top of that, Google requires apparel-specific attributes it doesn't ask of other categories, and missing any one of them disapproves the product outright rather than just limiting its performance. The combination of high variant counts and stricter required fields is exactly why apparel sits at the top of the disapproval charts—and why a spreadsheet stops scaling fast.
The apparel-specific attributes Google requires
Color, size, gender, and age group
Four attributes are required for apparel that most other products skip. Color is required for all Apparel & Accessories items, must be a human-readable name (not a hex code or internal SKU color), and supports up to three colors separated by a slash for multi-colored items. Size is required for clothing and shoes, in whatever standard format fits your market. Gender (male, female, or unisex) and age group (newborn, infant, toddler, kids, or adult) are required across all apparel.
These aren't just compliance boxes. They power Shopping's filters—when a shopper narrows to "Women's" or "Size 12," your product only appears if those values are present and correct. Miss them and you're invisible to filtered searches even when your product is a perfect match.
item_group_id — the one attribute to get right
If you fix only one thing in an apparel feed, fix this. Each size and color combination is submitted as its own product, but every variant of the same style must share the same item_group_id. That value is what tells Google these entries are one product with options, so it can show variant swatches and group them into a single listing.
Get it wrong and Google treats your navy small jacket and your navy large jacket as two unrelated products—fragmenting your listings and breaking variant grouping. The cleanest approach is to use the parent style code: if your base product is JK-2401, every variant carries JK-2401 as its item_group_id regardless of its individual id. A common mistake to avoid is reusing the same group ID across genuinely different products, which confuses Google about what belongs together.
Material, pattern, and sizing for international markets
Material and pattern help shoppers decide and improve matching. If you sell across borders, declare size_type (regular, petite, plus, tall, maternity) and size_system (US, UK, EU) so a "size 10" isn't ambiguous between markets. And use one image per color variant—reusing a single image across every color is both a quality issue and a missed chance to show the actual product.
GTINs for apparel (and when you don't have them)
In apparel, each variant needs its own valid GTIN where one exists. Many independent designers and handmade brands genuinely don't have GTINs—in that case set identifier_exists to false and supply a valid brand and mpn instead. Leaving the field blank or guessing a GTIN is a frequent, avoidable rejection.
Common feed errors for fashion and beauty brands
The patterns repeat across almost every apparel catalog: missing or inconsistent item_group_id so variants don't group; color values submitted as codes instead of names; size present on the product page but never mapped into the feed; one image reused across all colors; and missing gender or age group on an entire category at once. Because these errors hit whole groups of variants, one mapping mistake can disapprove hundreds of items—which looks catastrophic but is usually a single fix.
How to manage variants without duplicate or rejected products
The goal is every variant complete, correctly grouped, and consistent with its landing page. In practice that means three things: map size, color, gender, and age group from your store data into the right Google attributes for every variant; assign a shared item_group_id per style; and make sure each variant's price, availability, and image match its live page. The attribute mapping layer is where this is won or lost—solid mapping makes variant handling automatic instead of a per-product chore. Because apparel disapproves so readily, it's also worth understanding why products get disapproved before you submit.
Audit your fashion feed for free
Variant-level errors are easy to miss by hand—they hide across thousands of size and color combinations. IronFeed's free product feed audit scans every variant against Google's apparel requirements and flags the exact items missing a size, color, group ID, or identifier—before they cost you the rejection. Connect your feed and see what's failing.