{"schemaVersion":"1.0","canonicalUrl":"https://www.iamgeorgekelly.com/field-guide/google-product-category-vs-product-type","markdownUrl":"https://www.iamgeorgekelly.com/field-guide/google-product-category-vs-product-type/index.md","editorialNote":"AI-assisted research and drafting. Provider-specific claims link to primary sources. Frameworks are editorial proposals; worked examples are illustrative and are not employer performance results.","publication":{"name":"iamgeorgekelly","url":"https://www.iamgeorgekelly.com"},"citation":"George Kelly. Google product category vs. product type: choose the right mapping iamgeorgekelly. Updated 2026-10-17. https://www.iamgeorgekelly.com/field-guide/google-product-category-vs-product-type","slug":"google-product-category-vs-product-type","title":"Google product category vs. product type: choose the right mapping","description":"Separate Google’s predefined taxonomy from your merchant product_type hierarchy. Review category IDs, breadcrumbs, ambiguous products, and six fictional mapping cases.","category":"Product data","status":"published","published":"2026-10-17","updated":"2026-10-17","author":"George Kelly","answer":"Use google_product_category for a predefined Google taxonomy value and product_type for the merchant hierarchy. Google assigns categories automatically; the submitted category attribute is generally optional, with product-specific requirements and defined override uses. Keep the two decisions separate, verify any supplied Google ID or full path, and hold ambiguous mappings for evidence.","actions":[{"label":"Compare the two fields","section":"two-classifications"},{"label":"Review the six cases","section":"fictional-cases"},{"label":"Download the worksheet","section":"manual-worksheet"}],"sections":[{"id":"two-classifications","title":"Separate classification from a required feed field","paragraphs":["Google categorizes products automatically. Its category documentation and product data specification label google_product_category as optional. The current product_type page also describes Google classification as mandatory; that wording does not establish a universal requirement to submit the category attribute. Check the applicable product-specific instructions.","The category page lists three override uses: correcting category-driven attribute requirements, Google-category campaign grouping, and incorrect alcohol categorization. A merchant hierarchy serves a separate purpose."],"table":{"headers":["Decision","google_product_category","product_type"],"rows":[["Who defines the vocabulary?","Google’s predefined taxonomy","The merchant"],["What value belongs here?","One valid numeric ID or full official path","The merchant’s category breadcrumb"],["What if the values happen to match?","The shared value must be supported by Google","Equality can be valid; it is not a general mapping rule"]]},"sources":["google-category","google-type","google-spec"]},{"id":"verify-google-entry","title":"Verify the Google entry before using it","paragraphs":["When supplied, the Google field takes either an official numeric ID or the full category path. A final label, invented path, or unrelated system ID is insufficient. Select for the product’s evidenced main function and examine the most specific applicable entry.","The official English file retrieved on October 4, 2026 carries the header Google_Product_Taxonomy_Version: 2021-09-21. The retrieval date records this check; it is not a new taxonomy version. These two ID/path pairs were checked in that served file:"],"table":{"headers":["Google ID","Full path in the checked file"],"rows":[["2169","Home & Garden > Kitchen & Dining > Tableware > Drinkware > Mugs"],["152","Cameras & Optics > Cameras > Digital Cameras"]]},"sources":["google-category","google-invalid","google-taxonomy"]},{"id":"merchant-hierarchy","title":"Keep the merchant breadcrumb deliberate","paragraphs":["product_type allows a merchant-defined hierarchy of up to 750 characters and up to five values. Google uses only the first for Shopping campaign bidding and reporting. Its guidance recommends one value for that task, the complete breadcrumb, and spaces around the > separator.","Choose that first value as a commercial decision. A store may group the same mug with gifts or kitchen goods. Record the approved primary hierarchy before exporting; an alphabetical sort of navigation paths should not decide reporting structure.","In the fictional mug example, Home > Gifts > Ceramic Mugs describes the store’s organization. The Google candidate is the verified ID 2169. Review the meaning of each field independently even when the destination permits identical values."],"code":"{\n  \"fictional_mapping_fragment\": {\n    \"google_product_category\": \"2169\",\n    \"product_type\": \"Home > Gifts > Ceramic Mugs\"\n  },\n  \"scope\": \"Candidate fragment only; not a complete feed or a submitted merchant record.\"\n}","sources":["google-type","google-taxonomy"]},{"id":"manual-review-method","title":"Review the mapping in six steps","paragraphs":["This is a proposed manual review method by George Kelly. It separates product evidence, destination vocabulary, and merchant organization. It is not an automatic classifier.","Keep the observed value and proposed value in separate columns. A review candidate means the next decision is inspectable; it does not mean Google received or accepted anything. Hold the unresolved classification rather than filling it with a plausible guess."],"list":["Identify the exact item or bundle and capture evidence of its main function. Resolve conflicting descriptions first.","Record the merchant source hierarchy and its owner. Preserve source IDs with their original namespace.","Identify the reason for a Google override, or record that no override is proposed. Inspect any applicable product-specific requirement.","If proposing a Google value, look it up in the current official taxonomy. Record the ID, full path, file header, retrieval date, and evidence for its fit.","Choose the merchant product_type breadcrumb and the intended first value. Record why that hierarchy supports the reporting task.","Review the actual export representation. Retain unknowns, assign an owner, and separate the review decision from later Merchant Center processing."],"sources":["google-category","google-type","google-invalid"]},{"id":"fictional-cases","title":"Six fictional cases expose different mapping failures","paragraphs":["Every product, store hierarchy, campaign purpose, and review decision below is fictional. The two Google taxonomy entries are real entries checked for this edition. The cases illustrate review logic rather than merchant outcomes.","A correct taxonomy lookup is only one part of the decision. C01 and C06 have explicit product-function evidence; C03 and C04 lack it. C05 holds the merchant reporting hierarchy even though no Google override is proposed."],"table":{"headers":["Case","Supplied situation","Review decision"],"rows":[["C01 — Separate vocabularies","Drinking mug; merchant groups it under gifts","Review ID 2169 separately from the merchant breadcrumb."],["C02 — Leaf label","Verified drinking mug; Google field contains only Mugs","Review replacement with the valid ID or full official path."],["C03 — Unverified number","Invented number 999999999; no mapping or function evidence","Hold; the number is absent from the checked taxonomy."],["C04 — Ambiguous function","Ceramic vessel described as both decor and drinkware","Hold both classifications for product-owner evidence."],["C05 — Multiple hierarchies","Two merchant navigation paths; primary grouping undecided","Hold the ordering decision; first value controls Shopping grouping."],["C06 — Main-product bundle","Digital camera with a bag; main product explicitly established","Review ID 152 and a separate merchant starter-bundle breadcrumb."]]},"sources":["google-category","google-type","google-invalid","google-taxonomy"]},{"id":"manual-worksheet","title":"Download a manual mapping review worksheet","paragraphs":["Use the Markdown worksheet for one real item at a time. It asks for evidence, both classification decisions, the exact proposed representation, an owner, and the next action. Blank facts remain unknown.","The accompanying JSON holds the same six fictional cases, the checked taxonomy entries, source references, and a blank record. It has no executable validator or provider connection. Replace fictional evidence references before applying the method to a real product."],"download":{"url":"/downloads/product-category-mapping-worksheet.md","label":"Download the manual mapping worksheet (Markdown)"}},{"id":"case-records","title":"Keep review evidence separate from processing evidence","paragraphs":["Keep a local review record even after preparing a candidate change. After an authorized update, inspect the actual destination result separately. A well-formed field, a successful transfer, and an accepted offer are different observations.","This guide resolves the category decision. Use the broader field reference to review the rest of the record and the ownership register to assign responsibility for unresolved facts."],"download":{"url":"/downloads/product-category-mapping-review.json","label":"Download six fictional cases and a blank review record (JSON)"},"links":[{"slug":"product-feed-field-reference","label":"Review the surrounding feed fields","reason":"Category evidence does not establish correct identifiers, price, availability, or variant identity."},{"slug":"product-data-ownership","label":"Assign the product-data owner","reason":"An ambiguous mapping needs a responsible reviewer and evidence source."}]}],"sources":[{"id":"google-category","title":"Google Merchant Center: Google product category","url":"https://support.google.com/merchants/answer/6324436?hl=en","note":"Automatic categorization, optional submission, the three listed override uses, one predefined ID or full path, main function, specificity, and main-product bundles.","checked":"2026-10-17"},{"id":"google-type","title":"Google Merchant Center: Product type","url":"https://support.google.com/merchants/answer/6324406?hl=en","note":"Merchant-defined hierarchy, 750-character limit, up to five values, first value for Shopping bidding/reporting, full breadcrumbs, and supported values when fields are identical.","checked":"2026-10-17"},{"id":"google-spec","title":"Google Merchant Center: Product data specification","url":"https://support.google.com/merchants/answer/7052112?hl=en","note":"Both category submission attributes are labelled optional; product-specific requirements still apply. This supports the distinction between automatic classification and universal submission requirements.","checked":"2026-10-04"},{"id":"google-invalid","title":"Google Merchant Center: How to fix invalid product category","url":"https://support.google.com/merchants/answer/12469137?hl=en","note":"Invalid or leaf-only category values can be rejected. Omitting the field invokes automatic categorization; product_type is a separate merchant classification.","checked":"2026-10-04"},{"id":"google-taxonomy","title":"Google: English product taxonomy with IDs","url":"https://www.google.com/basepages/producttype/taxonomy-with-ids.en-US.txt","note":"Official file served on October 4, 2026, with version header 2021-09-21. Exact ID/path pairs 2169 (Mugs) and 152 (Digital Cameras) were checked; demonstration ID 999999999 was absent.","checked":"2026-10-17"}],"related":["product-feed-field-reference","product-identifiers-sku-gtin-variants","product-data-ownership","product-feed-portability-experiment"]}