Pajamas, Robes & Nightwear: Google Product Category IDs

If you just need the IDs, here they are, verified against Google’s official taxonomy file:

Pajamas: Apparel & Accessories > Clothing > Sleepwear & Loungewear > Pajamas (ID: 2580)

Robes: Apparel & Accessories > Clothing > Sleepwear & Loungewear > Robes (ID: 2302)

Nightgowns: Apparel & Accessories > Clothing > Sleepwear & Loungewear > Nightgowns (ID: 5513)

Loungewear: Apparel & Accessories > Clothing > Sleepwear & Loungewear > Loungewear (ID: 5713)

Paste the ID number or the full breadcrumb path into the google_product_category attribute of your feed. Google Merchant Center accepts either format. That covers the quick answer.

The harder question, and the reason most sleepwear feeds contain misclassified products, is deciding which of these four subcategories a specific product belongs to.

Let’s walk through the whole branch.

💡 Selling something else? Search all 5,000+ Google shopping categories instantly with our free CTX feed Google Product Category Mapping Feature.

The sleepwear branch at a glance

Google groups all nightwear under a single parent, Sleepwear & Loungewear (ID: 208), with exactly four child categories:

Product type	Category ID	Full path
Sleepwear (generic parent)	208	Apparel & Accessories > Clothing > Sleepwear & Loungewear
Loungewear	5713	… > Sleepwear & Loungewear > Loungewear
Nightgowns	5513	… > Sleepwear & Loungewear > Nightgowns
Pajamas	2580	… > Sleepwear & Loungewear > Pajamas
Robes	2302	… > Sleepwear & Loungewear > Robes

That’s the entire branch. There is no separate category for nightshirts, sleep shorts, onesies for adults, or “luxury silk pajama sets.” Every nightwear product you sell maps to one of these four leaves (or, rarely, to the parent itself).

How to classify pajamas: ID 2580?

Use 2580 for anything sold as a pajama set or pajama piece: two-piece PJ sets, pajama tops sold alone, pajama bottoms sold alone, footed pajamas, flannel sleep pants, matching family pajama sets, holiday pajamas.

Material, season, and audience gender never change the ID.

The variations live in other attributes:

What varies	Where it goes	Example
Material	material attribute	flannel, silk, cotton
Gender	gender attribute	male, female, unisex
Set vs. single piece	title + product_type	“Women’s 2-Piece Flannel Pajama Set”
Holiday theme	title	“Matching Family Christmas Pajamas”

One genuine exception: baby and toddler sleepwear has its own category, Apparel & Accessories > Clothing > Baby & Toddler Clothing > Baby & Toddler Sleepwear (ID: 5412). If you sell infant footed sleepers or toddler PJs, use 5412, not 2580.

The cutoff is the audience: products sized and marketed for babies and toddlers go in the baby branch, kids’ and adult sizes go in 2580.

How to classify robes: ID 2302?

Use 2302 for bathrobes, dressing gowns, spa robes, terry cloth robes, kimono-style robes worn as loungewear, hooded robes, and bridal party “getting ready” robes.

As with pajamas, fabric and style words belong in the title and attributes, while the category stays fixed.

Robe classification has two traps worth knowing:

Trap 1: kimono robes vs. actual kimonos. A satin “kimono robe” sold as loungewear is a robe, ID 2302. A traditional Japanese kimono garment is classified under Traditional & Ceremonial Clothing > Kimonos (ID: 5343), which has its own subcategories for furisode, tomesode, casual kimonos, and more.

The test is how the product is actually worn and marketed: bathroom and bedroom use means robe, traditional or ceremonial wear means kimono.

Trap 2: robes that aren’t clothing robes. Choir robes, graduation gowns, and judicial robes are uniforms or ceremonial garments, not sleepwear. Religious ceremonial robes, for example, map to Traditional & Ceremonial Clothing > Religious Ceremonial Clothing (ID: 5483).

If “robe” appears in your product name, make sure the product is actually nightwear before applying 2302.

Nightgowns vs. pajamas vs. loungewear: where to draw the lines

This is the decision that generates the most feed errors, so here are the practical rules:

Nightgowns (5513): one-piece dress-style sleep garments. Nightgowns, nighties, sleep shirts and nightshirts that hang like a dress, chemise-style sleepwear. If it’s a single pull-on garment designed for sleeping and shaped like a dress, it’s 5513.

Pajamas (2580): top-and-bottom style sleepwear, whether sold as a set or as separates. Sleep pants alone still count as pajamas.

Loungewear (5713): comfortable clothing designed for relaxing at home but not specifically for sleeping. Lounge sets, matching sweat sets marketed for home wear, lounge dresses. This is the fuzziest of the four, and the deciding question is the product’s primary marketing: “sleep” language points to 2580 or 5513, “lounge” and “relax” language points to 5713.

A chemise edge case: a cotton chemise marketed for sleeping is a nightgown (5513). A lace chemise marketed as intimate apparel belongs in Underwear & Socks > Lingerie (ID: 1772) instead. Same garment shape, different shopping intent, different category. When a product genuinely straddles both, pick the category matching your main product imagery and description, and keep it consistent across similar SKUs.

When in doubt, the parent is legal but weak. Submitting the generic ID 208 passes validation, but a precise leaf category gives Google a much stronger relevance signal for matching your products to shopping queries. Reserve 208 for genuinely unclassifiable items, which in practice almost never exist in this branch.

4 sleepwear mapping mistakes to avoid

1. Typing category names that aren’t in the taxonomy. “Nightwear,” “sleep sets,” and “PJs” are not valid values. Google only accepts the exact paths and IDs from its official taxonomy file, so always select from the real list rather than writing what sounds right.

2. Classifying by material instead of garment type. “Silk robe taxonomy” and similar queries suggest merchants look for material-specific categories. They don’t exist. Silk, flannel, fleece, and satin all go in the material attribute, and the category follows the garment type alone.

3. Sending adult IDs for baby products. Infant sleepers submitted as 2580 instead of 5412 is one of the most frequent apparel misclassifications. Audience age decides the branch before garment type does.

4. Letting categories drift across variants. When a robe comes in 12 colors as separate items or variations, every one must carry ID 2302. Hand-edited feeds often have a few variants left blank or mismatched, which can suppress individual offers while their siblings serve normally.

Map your whole sleepwear catalog automatically in WooCommerce?

Hand-assigning IDs works until your catalog grows. CTX Feed Plugin automates it through Category Mapping:

1. Go to CTX Feed > Category Mapping and create a new mapping for Google Shopping.
2. Match each of your WooCommerce categories to its Google counterpart: your “Pajamas” category to ID 2580, “Robes” to 2302, “Nightgowns” to 5513, “Baby Sleepwear” to 5412. Type a keyword and CTX Feed suggests the official path with the correct ID.
3. Apply the mapping to your Google Shopping feed.

Every current and future product then inherits the right google_product_category automatically, and the feed refreshes on your schedule, so a new robe colorway added on Tuesday is correctly categorized in Merchant Center by Wednesday without anyone touching the taxonomy file.

FAQs:

Working through your apparel feed? See the companion guide for jeans, socks, and general apparel IDs, or search any category in seconds with the free Google Product Category mapping Feature.