Google Merchant Center API now manages product reviews

Google now documents submitting and managing product reviews through the Merchant API, not just through a manual data-feed upload. Google’s developer documentation describes creating a review data source and then adding or updating individual reviews with an API call, a shift that moves product review data into the same programmatic pipeline retailers already use for prices, inventory, and product attributes. For a chain running large product catalogs across many markets, it turns review handling into a governed, automatable operation instead of a spreadsheet upload.

What happened

Google’s Merchant API documentation now lists an API method for product reviews: retailers create or reuse a review data source, then use the insert method to create or update a review programmatically. Google’s guide sets out the prerequisites, an active product review feed in Merchant Center and enrollment in the Product ratings program, and notes that access is gated behind an allowlist request through the Shopping API support form. Industry outlets flagged the update in mid-September 2026. Google has expanded the Reviews sub-API since its 2024 beta, and its product reviews guide now documents the full submit-and-manage cycle through the API.

The mechanics are ordinary API plumbing: a review is attached to a data source, submitted through the insert method, and takes a few minutes to propagate. What is new is that the whole cycle no longer depends on scheduling and re-uploading a file.

Why it matters

Product reviews and ratings are not a cosmetic detail for large retailers. They surface as star ratings in Google’s free product listings and Shopping surfaces, and review content increasingly feeds the AI answers that summarize products for shoppers. When that data is accurate and fresh across the whole catalog, a retailer competes better in exactly the surfaces where buying decisions now start. When it is stale, wrong, or missing in one market, that gap shows up in front of customers. Moving submission to an API is how a national or multi-market retailer keeps thousands of SKUs current without a person babysitting feed uploads.

What this means for retail

For a central retail team, the API is a governance tool, not just a convenience. It lets review ingestion run on the same schedule and controls as the rest of the product data pipeline, with one integration covering every market instead of separate manual feeds per region. That is the same discipline multi-location brands already apply to their reputation management for store and location reviews on Google and Facebook: centralize the data, keep it consistent everywhere, and treat accuracy as an operational metric rather than an afterthought.

It is worth being precise about scope. These are product reviews inside Google’s Shopping ecosystem, which sit alongside, not on top of, the location reviews that shape how each store shows up in local search and maps. A retail estate has both, and both increasingly feed AI-generated answers, so the same question applies to each: is the data accurate, complete, and current across every location and every market? Keeping local listings and reviews clean at the location level, and product review data clean at the catalog level, are two halves of the same job. For teams formalizing that work, our review management guidance covers the location-review side of the estate.

You can use the accounts.productreviews.insert method to create or update a product review.

Google, Merchant API product reviews guide

The bottom line

The Merchant API change is small in isolation and large in aggregate: any single review upload was already possible, but automating the whole flow lets a retailer treat product reviews as live, governed data across the entire catalog. Retailers running product feeds should scope the allowlist request now, and treat product review accuracy with the same rigor they already apply to location data.