Current migration checklist

Merchant API transition: what Shopify stores should check first

Google's current guidance distinguishes third-party connections from custom integrations. If a technology partner sends your data, it may handle the migration; if you maintain a custom Content API integration, the developer needs to review the compatibility path. The useful first step is to identify the owner of your connection and capture a small product-data baseline before making changes.

Use the checklist Check one public product page

This is a planning checklist, not API migration advice or a guarantee of Merchant Center eligibility.

Read Google's official migration guidance for provider and custom-integration details.

Identify who owns the product-data connection

Start with the technology that actually sends product data to Merchant Center.

If you use Shopify's Google & YouTube sales channel or another technology partner, confirm the provider's migration guidance before changing anything.
If you use a custom Content API integration, ask the developer or feed provider for its Merchant API migration status before the deadline.
Write down every active Merchant Center data source for one representative product. Avoid changing a field in multiple places at once.

Record a small baseline before making changes

A simple before-and-after record makes a sync problem easier to diagnose later.

Choose five representative products and note their current product IDs, price, availability, key attributes, and Merchant Center diagnostics.
Check the selected variant on the public product page, not only the parent product record.
Keep screenshots or an exported list of any current warnings instead of relying on memory after a provider update.

Separate migration questions from product-page questions

A correct public page and a correct data source are related, but one does not replace the other.

Use Merchant Center diagnostics to identify a feed, account, or API issue.
Use the storefront to verify that a buyer can see the current title, selected option, price, availability, and decision-critical details.
Do not assume visible schema alone fixes a Merchant Center diagnostic or guarantees an approval outcome.

If a rule does not carry over

Create one traceable handoff record before changing the catalogue

When a migration changes a label, shipping rule, or attribute, preserve the evidence for one affected item first. This keeps a private channel diagnosis separate from what a buyer can see on the storefront.

Capture these five things

One affected product or variant ID
The active Merchant Center data source and its owner
Custom labels, shipping rules, or supplemental sources used by that item
The exact diagnostic wording and date captured
The matching public-page title, selected option, price, availability, and delivery wording

Check one public page Compare page and feed signals

Public-page boundary

Use a public-page review to make the storefront side easier to verify

A focused mini-audit can check whether the buyer-facing title, selected variant, price, availability, policy context, and visible Product markup are consistent enough to inspect alongside the Merchant Center diagnostic.

Request a focused outside view

Share one collection and a short list of public product URLs. The review does not access Merchant Center or Shopify admin.

Request mini-audit See the method