Categories, IDs and shipping
Product ID
feed attribute: id
A unique identifier per item, max 50 characters, stable over time — it is how a platform tracks your item.
Google Merchant Center
Required attribute: unique per product, maximum 50 characters.
Meta
Required for a catalogue item and used as the item's identity across updates.
What the requirement says
- Every item needs an id: unique within the feed, at most 50 characters.
- The id is the item's identity over time. Keep it stable: change it and the platform treats the product as new, losing its performance history and its learned matching.
- Variants are separate items, so each one needs its own id — normally the variant's SKU or its variant id, not the parent product's.
Why products lose visibility when it fails
- A missing id is a required-attribute failure: the item cannot be tracked, so it cannot serve.
- A value longer than 50 characters fails the documented maximum.
- Duplicate ids mean two items are claiming one identity: one of them overwrites or hides the other, and neither can be measured properly.
- Reusing an id for a different product mixes unrelated performance data into one item.
The checks we run on it
Straight from the audit engine, with the basis each one is judged on. “Commonly suppresses” means the failure is the kind that stops a product serving, so it is weighted more heavily in your score.
| Check | Basis | Requirement | What to do |
|---|---|---|---|
Product ID missing criticalcommonly suppressesid_missing | required | Id is required and must be unique per product. | Submit a unique ID for every item (the SKU works well). |
Product ID over 50 characters minorid_too_long | required | Id allows a maximum of 50 characters. | Use a shorter SKU-style ID. |
Duplicate product ID criticalcommonly suppressesid_duplicate | required | Every item needs a unique id — this ID is used by more than one item. | Give each variant its own ID (add the size/colour to the SKU). |
Want to know which of your own products fail this requirement?
Audit my ID free →How to fix it in Shopify
- A store scan uses the variant id as the item id (falling back to the product id where there is no variant id), which is unique per variant by construction.
- If you build your own feed, use the variant id or the variant SKU — not the product handle, because all variants of a product share one.
- Bulk check: Products → Export and eyeball the Variant SKU column for blanks or repeats.
How to fix it in WooCommerce
- WooCommerce's product id is unique per product; variation ids are unique per variation. A feed can use SKU instead if every product has one.
- If you use SKU as the id, make sure it is filled in — a blank SKU column produces an empty id and fails the check.
- Careful with duplicated SKUs created by cloning products: they show up here as duplicate ids.
Worth knowing
- Never reuse an id for a different product, and never renumber your catalogue wholesale — both reset the item's history.
- Shopify handles can look like ids but are not unique per variant.
How FeedGuard checks it
- We count each id across the whole catalogue (so a repeated id is caught no matter where the duplicate sits), check the value is present, and check the 50-character maximum.
- A store scan reads the variant id, which is unique per variant by construction.
Every failure names the field and shows the value at fault, counted over up to 250 products per scan. A requirement that does not apply to an item is left out of both sides of the score rather than counted as a pass, and a requirement our source cannot see at all is excluded from the score and listed as “not checked from this source” with the reason. Where a value can be corrected without inventing anything, the row is fixed in the corrected CSV you can download; anything we would have to make up (a real barcode, a brand, a price, a category) is listed for you to supply instead.
What each kind of scan can see
A store scan reads the public catalogue the store itself publishes (Shopify's /products.json). A pasted feed URL or an uploaded CSV is the file the shopping platform reads, so every attribute can be judged against it. This is the difference that decides whether a check can run at all.
| Attribute | Store scan (Shopify) | Your feed URL or CSV upload |
|---|---|---|
| id | read from the store variant id | read from your file read from your file |
Read the engine's own rules for this requirement on the results page: every failing row links back to this guide. All 49 checks are listed on what we check.
Run the free audit on your store
Paste your store domain, paste your product feed URL, or upload a product CSV. You get a scored report of every requirement above, the products failing each one, the exact fields at fault, and a corrected CSV to download. No account, no card.
Run the free audit on your storeA store scan reads the public catalogue and skips the attributes it cannot see (barcodes and platform-only fields among them); a feed URL or CSV gets the full audit.
Other categories, ids and shipping requirements
- Google product category
Google's own category for the product, from its published taxonomy — a missing or wrong one is a common cause of disapproval.
- Product type
Your own category path — recommended, and it is what makes your catalogue legible in reporting.
- Shipping weight
Optional for most accounts, required for carrier-calculated rates — and the value needs a unit.