Merchant API Migration: Keep Product Offers Accurate

The risk is an outdated offer, not just a failed connection

A buyer sees a product price, clicks through and finds a different offer. Another item remains advertised after its available stock has changed. For a cross-border brand, a product-update interruption can become a customer-facing problem before anyone notices a technical alert.

Google’s Content API sunset documentation, updated on September 10, 2026, says the legacy service reached sunset on August 18. Progressive degradation began on September 1: requests without an active extension can intermittently return HTTP 410. Full decommissioning is currently planned for early 2027, with timing subject to revision. An occasional successful request therefore does not prove that an old connection is dependable.

First establish who owns the connection

Google distinguishes custom integrations from third-party platforms: a technology partner manages migration for merchants using its integration. If your store relies on a supported platform connection, ask the provider for its migration status and an escalation contact before commissioning duplicate work.

A separately maintained warehouse script, agency connector or catalogue exporter may still need its own review. Make a short inventory of the systems that send product information, which account each serves, who maintains it, and when it last completed an update. Do not assume that moving the storefront also moves every background connection.

Select a small set of products that reveal real problems

Use a sample containing a normal item, a variant, a discounted product and an unavailable item. Compare each record in the source system, the receiving catalogue and the public destination. Check identity, currency, offer, availability and the variant selected by the landing page.

A practical review sheet needs the product identifier, expected value, observed value, time checked and responsible owner. If the sample exposes a mismatch, preserve the evidence and find the affected group before declaring the catalogue healthy. A headline count of uploaded products cannot answer those questions.

Treat price and identity as business acceptance checks

Google’s migration guide describes changes to resource identifiers and price representation, including amounts expressed in micros. It also notes that the former customBatch approach is not supported. These differences make the work more than replacing an address in a configuration file.

Ask the implementer to show the same item before and after migration, with the intended price and currency. A product must not become a duplicate or inherit another variant’s offer. Where a brand sells into several markets, validate the mapping separately for each destination rather than extrapolating from one successful domestic example.

Verify that changes arrive, not merely that requests leave

After a controlled update, confirm the resulting product state at the receiving side. Record failed items separately from completed items and identify whether delayed work will be retried, reviewed or paused. The operational owner should be able to see what remains unresolved.

For a hypothetical homewares brand, the critical trial might be a stock change on a fast-moving variant and the end of a temporary promotion. The expected result is the approved offer appearing at the correct destination. This is a proposed acceptance scenario, not a customer result or a promise about traffic.

Agree on a cutover and an exception route

Choose who authorizes the change, who compares the first results and who can pause an affected product group if the data is wrong. Preserve the previous configuration and a record of pending updates. Avoid two independent writers changing the same product without an explicit ownership rule.

A contingency must be usable after the old service becomes unavailable. Have the provider document the supported recovery route and the commercial decisions needed during an interruption. Repeatedly retrying the retired API is not a sustainable fallback.

Keep the customer promise in view

For manufacturers selling directly through a cross-border brand, this review connects product operations to a real acquisition channel. For enquiry-only manufacturers that do not use Merchant Center product feeds, there is no reason to build an API migration project solely because a platform announcement exists.

The useful deliverable is a verified product-update path with named owners, exception visibility and a clear recovery procedure. It protects the accuracy of what customers encounter. Migration success itself does not establish a ranking improvement, more impressions or more sales.

References

• Google: Content API deprecation and sunset (updated September 10, 2026) ↗
• Google: Migrate from Content API to Merchant API ↗