Variant MPN feed audit
Shopify Variant MPN Google Merchant Center Feed Audit
Check Shopify variant-level MPN values for Google Merchant Center feed readiness, separate legacy product-level MPN from variant metafield columns, and export a supplemental feed worksheet for manual review.
Browser-side scan
Drop a product or variant metafield CSV
No CSV selected
Shopify merchants can store variant-level MPN values, but those variant MPNs may not reach a Google Merchant Center feed the way product-level values do. This audit runs locally in your browser with the File API, with no data uploaded to a server. It matches variants by SKU or Variant ID, detects whether MPN comes from the legacy product-level 'Google Shopping / MPN' column or from a variant-level metafield column, flags missing or duplicate MPN values per variant, and exports a supplemental feed worksheet plus a reconciliation report for manual review. It does not call the Google & YouTube app or the Merchant Center API and does not write data to any platform.
Import blockers
Common causes this scan checks
- Variant-level MPN values do not always appear in a Google Merchant Center feed even though product-level values do.
- The product export includes only the legacy product-level 'Google Shopping / MPN' column, which does not carry variant-specific MPN values.
- Variants are missing the SKU or Variant ID needed to match MPN rows in a supplemental feed.
- Multiple variants accidentally share the same MPN, creating duplicates that Merchant Center may reject or merge.
Workflow
How to use the cleaned CSV
- Upload a Shopify product export or variant metafield CSV and confirm a Variant ID or Variant SKU column is present.
- Review the detected MPN source: legacy product-level 'Google Shopping / MPN' versus a variant-level metafield column.
- Resolve variants flagged with a missing MPN and review any duplicate MPN values before export.
- Export the supplemental feed worksheet and check variant identity, MPN values, and MPN source before any manual Merchant Center upload.
Auto-fix policy
What the export can safely change
- Detects the legacy 'Google Shopping / MPN' product-level column separately from variant-level metafield MPN columns.
- Matches variants by Variant ID or SKU to align each MPN value with an individual variant.
- Flags missing variant identity and missing MPN values that would block a supplemental feed.
- Groups duplicate MPN detections by row so merchants can decide on consolidation before export.
- Trims MPN and variant identity cells for cleaner feed matching without rewriting the underlying values.
CSV example
CSV example: variant MPN audit for Merchant Center feeds
The audit shows row 2 sourcing MPN from a variant metafield while row 3 relies on the legacy product-level column, separates the two sources in the worksheet, and marks each row's readiness before any manual Merchant Center upload.
Handle,Title,Variant SKU,Google Shopping / MPN,Variant Metafield: custom.mpn widget-blue,Blue Widget,BLUE-001,,Mfr-Blue-2024 widget-red,Red Widget,RED-002,XYZ-100,
id,mpn,Variant ID,Variant SKU,Title,MPN source,Review note,Source row BLUE-001,Mfr-Blue-2024,,BLUE-001,Blue Widget,variant metafield,Ready for supplemental feed worksheet,2 RED-002,XYZ-100,,RED-002,Red Widget,legacy product-level,Ready for supplemental feed worksheet,3
FAQ
Shopify CSV questions
Why might variant MPNs not reach Google Merchant Center?
Variant MPN values are stored per variant, but feeds and product CSVs often surface only product-level columns. A supplemental feed worksheet bridges that gap by pairing each variant row with its identifier and MPN for manual upload.
What is the difference between 'Google Shopping / MPN' and a metafield MPN column?
'Google Shopping / MPN' is a legacy product-level column that does not capture variant-specific values. A variant-level metafield column stores MPN per variant and needs its own planning before a supplemental feed export.
Do I need both SKU and Variant ID?
No. Use whichever column matches your feed: SKU is common for existing catalogs and Variant ID is explicit. The worksheet can use either as the unique identifier.
Can I upload this worksheet straight to Google Merchant Center?
No. The tool produces a local CSV worksheet for manual review. You decide whether and how to upload it to Merchant Center yourself; the tool never submits data to Google.
Feedback
How is this tool working for you?
Found a bug, a false alarm, or a missing check? Tell me — a human reads every note.