---
title: "PIM to Google Merchant Center: the product-data workflow"
description: "PIM to Google Merchant Center: map PIM fields to Google's attributes, trace feed errors to their owner and link custom labels to profit, with free worksheets."
canonical: "https://www.productmetrics.io/blog/pim-to-google-merchant-center"
pageType: article
language: en
alternates:
  en: "https://www.productmetrics.io/blog/pim-to-google-merchant-center"
  nl: "https://www.productmetrics.io/nl/blog/pim-naar-google-merchant-center"
  de: "https://www.productmetrics.io/de/blog/pim-zu-google-merchant-center"
  x-default: "https://www.productmetrics.io/blog/pim-to-google-merchant-center"
publisher: "Product Metrics"
author: "Berend Vrakking"
datePublished: 2026-10-20
dateModified: 2026-10-23
image: "https://www.productmetrics.io/og/blog/pim-to-google-merchant-center.png"
---

> Content index: https://www.productmetrics.io/llms.txt

# PIM to Google Merchant Center: the product-data workflow

## Key takeaways

- Give every Merchant Center attribute one owning system, and keep one stable ID per variant across PIM, export and Merchant Center.
- Fix the first wrong value in the chain: an edit in Merchant Center is overwritten when the PIM or feed sends its next update.
- The free mapping and profit workbook maps 14 PIM fields to Google attributes and shows three products at a ROAS of 5 keeping €0, €15 and €30.

A [PIM](https://www.productmetrics.io/glossary/pim "A product information management (PIM) system is software for maintaining and enriching product information so teams can publish consistent details across sales channels.") (product information management system) is where your team keeps product descriptions, specifications, images and translations.

Connecting it to [Google Merchant Center](https://www.productmetrics.io/glossary/google-merchant-center "Google Merchant Center (GMC) is a free Google tool where a shop uploads and manages its product data, so its products can appear on Google Shopping and across Google.") means mapping the fields it owns to Google's product attributes, delivering them through a supported data source, and checking what Merchant Center actually processed.

Most feed problems are ownership problems: a price the PIM sends but the shop sets, or an ID that changes between exports.

## Which system owns which field?

The one that holds the current, approved value. A PIM rarely owns everything: a well-kept description can sit next to a price that changed five minutes ago in the shop.

| System | Usually owns | The next system needs |
|---|---|---|
| ERP or stock system | Costs and stock | Current values on the right variant |
| PIM | Descriptions, specifications, images, translations | Approved content per language |
| Shop | Product pages, checkout prices, sellable stock | An offer shoppers can buy |
| Feed tool or connector | Mapping, transformations, delivery | Valid output with an update time |
| Merchant Center | Processing and eligibility | Accurate data, compliant pages |
| Google Ads | Product selection and campaigns | Eligible products and reliable measurement |

Give each owner an update rule too: descriptions can wait for editorial review, prices and stock can't. [What Merchant Center does](https://www.productmetrics.io/blog/what-is-google-merchant-center) covers the account's wider role.

## How do you map PIM fields to Merchant Center?

Map the sellable variant, not its parent, to the attributes in Google's [product data specification](https://support.google.com/merchants/answer/7052112?hl=en-GB):

| Your source field | Google attribute | Check |
|---|---|---|
| Variant SKU | `id` | Stable and unique per variant |
| Parent key | `item_group_id` | Groups only real variants |
| Approved name | `title` | Names the actual variant |
| Product copy | `description` | Right language version |
| Manufacturer barcode | `gtin` | Belongs to this variant |
| Brand and part number | `brand`, `mpn` | Manufacturer values |
| Product URL | `link` | Opens the buyable variant |
| Image URL | `image_link` | Shows the right product |
| Checkout price | `price` | Matches page and checkout |
| Sellable stock | `availability` | Current, supported value |
| Categories | `google_product_category`, `product_type` | Google's category and yours kept apart |
| Grouping rule | `custom_label_0` to `_4` | One owner per slot |

Country, category and condition add requirements of their own.

Never invent a barcode to pass validation; Google's [identifier guidance](https://support.google.com/merchants/answer/160161?hl=en) covers products without one. Keep IDs stable through a PIM migration, because a new ID starts a new product history ([ID specification](https://support.google.com/merchants/answer/6324405?hl=en)).

**From source fields to a product decision**

1. **ERP, PIM and shop.** Agree which system owns each field. Product descriptions may come from the PIM; live prices and sellable stock may come from the shop or ERP.
2. **Mapping and delivery.** The connector or feed tool combines the approved fields, transforms them for the destination and sends the product data.
3. **Merchant Center.** Check the processed product, its source and its issues. Validate the exact variant against its landing page and checkout.
4. **Listings and campaigns.** Eligible products can appear in free listings. Linked Google Ads campaigns use selected products for Shopping ads or Performance Max.
5. **Profit review.** Compare advertising spend with contribution profit, then use agreed labels and campaign settings to increase or lower product priority.

### Free mapping and profit workbook

The [Excel workbook](https://www.productmetrics.io/downloads/pim-to-merchant-center-worksheet.xlsx) holds instructions, blank and sample mapping sheets, product-profit formulas and a print layout. The same content comes as CSV: a [sample mapping](https://www.productmetrics.io/downloads/pim-to-merchant-center-field-mapping.csv), a [blank mapping](https://www.productmetrics.io/downloads/pim-to-merchant-center-field-mapping-blank.csv) and the [worked profit example](https://www.productmetrics.io/downloads/pim-to-merchant-center-profit-priority.csv). No email needed.

## How do you check delivery and the processed product?

Test a small sample first: a normal product, a variant, an out-of-stock item and a discounted one. Google accepts [product data sources](https://support.google.com/merchants/answer/14990942?hl=en) as files, Google Sheets or the Merchant API, and an upload that succeeds only proves the data arrived:

| Checkpoint | Evidence to keep | What it catches |
|---|---|---|
| Source approval | Variant, owner, approved value | Unapproved content |
| Export | Output row and generation time | A transformation that used old input |
| Delivery | Submission result | An export that never reached Google |
| Processing | Final attributes and issues | A rule that overwrote the value |
| Shop comparison | Variant page and checkout | An offer that differs from the shop |

A supplemental source must match the primary product's ID, language and data source label, and it enriches existing products rather than creating them.

Preview any [attribute rule](https://support.google.com/merchants/answer/14994083?hl=en) before applying it, and keep the previous version.

## Who fixes which Merchant Center error?

Whoever owns the first wrong value. Editing the final product in Merchant Center lasts only until the next upstream update.

| Symptom | First check | Owner |
|---|---|---|
| Wrong description in the source | PIM approval and language | Product-content team |
| Source right, exported title wrong | Mapping and transformations | Feed manager |
| Export right, processed price stale | Delivery time, source order, rules | Integration owner |
| Variant price differs at checkout | Variant, promotion, currency | Ecommerce team |
| Policy disapproval | The exact issue and destination | Merchant or compliance owner |
| Approved, but weak return | Spend, demand, margin | PPC specialist |

Google's [product-data view](https://support.google.com/merchants/answer/16488801?hl=en) shows source, update time, price and status together. [Google Merchant Center errors](https://www.productmetrics.io/blog/google-merchant-center-errors) lists the common issues by name, and an account suspended for misrepresentation has [its own route](https://www.productmetrics.io/blog/google-merchant-center-suspended-misrepresentation).

## How do PIM fields become custom labels and profit decisions?

Through a reserved custom-label slot with one writer.

An approved PIM field `season = winter` can map to `custom_label_1 = winter`, and a campaign can then select winter products. Google provides [five custom labels](https://support.google.com/merchants/answer/6324473?hl=en-GB), one value each per product:

| Slot | Example | Writer and purpose |
|---|---|---|
| `custom_label_0` | `stars` | Product Metrics: approved performance segment |
| `custom_label_1` | `winter` | PIM mapping: season |
| `custom_label_2` | `margin_high` | Margin rule: economics |

A season label says nothing about profit. That needs costs: three trainers each earn €100 revenue excl. VAT on €20 of ads, a [ROAS](https://www.productmetrics.io/glossary/roas "Return on ad spend (ROAS) is the revenue your ads generate for every euro you spend on them.") of 5, and keep very different amounts:

| Illustrative product | Variable costs | [Contribution margin](https://www.productmetrics.io/glossary/contribution-margin "Contribution margin is the revenue from a sale minus its variable costs, such as product cost, shipping, payment fees and returns.") | Break-even ROAS | Left after €20 of ads |
|---|---|---|---|---|
| Trainer A | €80.00 | 20% | 5 | €0.00 |
| Trainer B | €65.00 | 35% | 2.86 | €15.00 |
| Trainer C | €50.00 | 50% | 2 | €30.00 |

**Figure: The same ROAS of 5 produces three different profit returns.** At €100 revenue and €20 advertising spend per product, a 20% contribution margin only covers the ads; a 50% margin leaves €30 after ads.

![Bar chart of POAS for three trainers that all have a ROAS of 5, illustrative data: 1 at a 20% margin, 1.75 at 35% and 2.5 at 50%, against a break-even of 1.](https://www.productmetrics.io/images/blog/pim-to-google-merchant-center/same-roas-different-profit.png)

| Product and contribution margin | POAS |
| --- | --- |
| Trainer A (20%) | 1 |
| Trainer B (35%) | 1.75 |
| Trainer C (50%) | 2.5 |

Reference line: Advertising break-even (1).

_Source: Illustrative data. POAS = revenue excluding VAT × contribution margin before advertising ÷ advertising spend._

[Break-even ROAS](https://www.productmetrics.io/break-even-roas-calculator) is 1 ÷ contribution margin, and [POAS](https://www.productmetrics.io/glossary/poas "Profit on ad spend (POAS) is contribution profit before advertising divided by ad spend.") (ROAS × margin) breaks even at 1 ([POAS vs ROAS](https://www.productmetrics.io/blog/poas-vs-roas)). [Product Segmentation](https://www.productmetrics.io/product-segmentation) segments every product by ad clicks and ROAS or POAS and writes only the labels you approve; the [campaign structure method](https://www.productmetrics.io/blog/product-segmentation-google-shopping-pmax) decides when a group needs its own campaign.

> **Get more revenue out of Google Shopping.** Every product segmented and labelled in Merchant Center, so your top performers get more priority. [Analyse your products for free](https://app.productmetrics.io/) Log in with Google, no credit card.

## Do you need a PIM for Google Shopping?

Only when governing product information is the bottleneck. A PIM won't fix an undefined field owner or a campaign that ignores its labels.

| Your situation | Start with | When a PIM helps |
|---|---|---|
| One shop, reliable product content | The platform connector | When content work outgrows it |
| Many suppliers with conflicting data | Shared field definitions | When central enrichment saves repeated fixes |
| Several countries or languages | Localised content and offers | When teams need controlled versions |
| Accurate feed, weak ad profit | Costs and product-level results | It doesn't: that is a profit question |

Before choosing a connector, ask who maintains it, which variants and markets it supports, how fast changes arrive and where failed updates show. Test the answers on your sample products.

## Final thoughts

A feed is only as reliable as its least-owned field; most Merchant Center firefighting stops once every attribute has a name next to it.

Fill in the owner column of the [mapping workbook](https://www.productmetrics.io/downloads/pim-to-merchant-center-worksheet.xlsx), trace your four sample products end to end, and check them again after the next scheduled update. Google's requirements were checked on 20 October 2026.

## Frequently asked questions

### Can a PIM connect directly to Google Merchant Center?

Some PIM providers offer a Merchant Center connector; others export data to a separate feed tool. Check which fields and markets the connector supports, how it handles variants and how it reports failed updates.

### Why is Merchant Center showing an old price from my PIM?

Trace the same variant through the source system, exported row, delivery timestamp and processed Merchant Center product. A stale export, failed delivery or overriding rule can preserve an old price. Compare the result with the landing page and checkout before deciding where to fix it.

### Do custom labels automatically change Shopping or Performance Max campaigns?

No. Custom labels group products for campaign selection and reporting. Your product groups or listing groups must use those values, and adding a label does not create a separate budget or change a campaign target.

## Keep reading.

- [How Google Shopping ads work, from feed to sale](https://www.productmetrics.io/blog/how-google-shopping-ads-work)
- [Google Merchant Center suspended for misrepresentation: a dropshipper's checklist](https://www.productmetrics.io/blog/google-merchant-center-suspended-misrepresentation)
- [Google Shopping Ads: A Beginner's Guide to Setup and Cost](https://www.productmetrics.io/blog/google-shopping-ads-beginners-guide)

Also available in: [Nederlands](https://www.productmetrics.io/nl/blog/pim-naar-google-merchant-center) | [Deutsch](https://www.productmetrics.io/de/blog/pim-zu-google-merchant-center)

---

Written by Berend Vrakking, founder of Product Metrics. Last updated 2026-10-23.

HTML version: https://www.productmetrics.io/blog/pim-to-google-merchant-center