Google's Merchant API is now the path Google documents for managing Merchant Center data, while the Content API for Shopping reached its published sunset on August 18, 2026 and began experiencing progressive errors from September 1. The migration is also a data-source ownership decision.
Start with responsibility
Before choosing a source design, answer who owns canonical product data, which system owns price and availability, which updates need to be frequent, and who investigates or rolls back a failed processing event.
One source or separated responsibilities?
A small catalog may be easiest to operate with one clear source and one owner. A larger catalog may separate broad product content from frequent inventory or regional updates when the platform and API model support it. Each field should have one authoritative owner.
The source design checklist
- Identity: stable product IDs.
- Freshness: defined price and availability interval.
- Diagnostics: request, processing, and product issues.
- Scope: clear markets, destinations, and account relationships.
- Rollback: a way to stop or reverse a bad batch.
- Evidence: logs that connect change to result.
A safe migration sequence
- Confirm project and authentication.
- Test a representative product set.
- Verify source processing and product status.
- Compare price, availability, variants, and pages.
- Control duplicate ownership before parallel runs.
- Expand gradually and keep a rollback record.
Read the migration path for small merchants and agencies, then use the feed change-log runbook.
Source: Google Merchant API overview