When MPN values are visible in Shopify but missing from Google Merchant Center, the problem is often not the value itself. The failure is usually somewhere in the identity chain between a Shopify variant, the field that stores its MPN, and the item ID Google receives.
This becomes especially confusing when products without variants work correctly while products with variants do not. A product-level MPN can look valid in a CSV and still fail to describe each sellable variant.
1. Identify the real source field
Start by confirming where the MPN is actually stored.
Shopify exports may contain the legacy Google Shopping / MPN column, while the Google & YouTube app can use app-managed fields or variant metafields. Those are not automatically interchangeable. Do not assume that seeing a value in one Shopify screen proves it is present in the feed Google receives.
For each affected item, record:
- Shopify variant ID
- Variant SKU
- Product title and option values
- The MPN value
- The field or column the value came from
That small table makes field-source mismatches visible.
2. Reconcile at variant level
Treat every sellable variant as a separate row. A shirt with three sizes is not one Merchant Center item with one shared identifier unless the manufacturer truly assigned the same MPN to all three variants.
Check for:
- Blank MPNs on continuation or variant rows
- One product-level MPN copied across distinct variants
- Duplicate MPNs assigned to unrelated SKUs
- SKUs that changed after the feed connection was configured
- Variant IDs present in Shopify but absent from the exported comparison file
Use SKU or variant ID as the reconciliation key. Product title alone is too weak because titles can repeat or change.
3. Separate missing data from feed eligibility
Merchant Center may omit or reject identifiers for reasons beyond an empty MPN. Before changing data, review whether the item also has a valid brand and GTIN where applicable, and whether the product is custom-made or manufacturer-assigned.
The goal is to avoid βfixingβ a feed by inventing identifiers. An MPN should come from the manufacturer. If no manufacturer MPN exists, the correct feed treatment may be different from supplying a placeholder.
4. Build a reviewable supplemental feed
If the app-managed feed still does not carry variant MPNs, a supplemental feed can be a controlled workaround. Keep it minimal:
-
id: the exact item ID Merchant Center expects -
mpn: the verified manufacturer part number
Before uploading it, compare every supplemental-feed ID against a Merchant Center export or diagnostics report. A correct MPN attached to the wrong item ID will not solve the problem.
A browser-side Variant MPN and Merchant Center feed audit can help turn a sanitized Shopify export into a reconciliation worksheet and supplemental-feed draft. It does not connect to Shopify or Google, and it does not submit the feed for you.
5. Test a small group first
Choose one product with two or three variants and verify the full path:
- Confirm each variant's SKU, variant ID, and MPN.
- Confirm the Merchant Center item IDs for those variants.
- Upload or schedule only the small supplemental-feed sample.
- Wait for processing and review item-level diagnostics.
- Expand only after the sample maps correctly.
This workflow is slower than blindly re-uploading a full catalog, but it gives you a precise answer: whether the issue is missing variant data, a field-source mismatch, an item-ID mismatch, or Merchant Center eligibility.
