Manufacturer Center Drops Manual Edits: The API-Only Playbook

Google Manufacturer Center no longer accepts manual product edits — according to an email Google sent to account holders, the ability to add or update products directly in the console has been removed, and the Manufacturer Center API or a product file upload are now the only submission paths. Data submitted before July 9, 2026 stays in the account untouched.

If the headline sounds familiar, it should: we covered this change in one line inside our July 2026 Google Shopping reshuffle brief, alongside the same week’s other feed-ecosystem moves. That post is the news layer. This one is the part the news coverage skipped: what the two surviving submission paths actually involve, how to choose between them, and why disciplined feed-ops teams will barely feel this while hand-patchers face a genuine workflow rebuild.

Everything below is sourced from Google’s own developer and help documentation for Manufacturer Center, plus the Search Engine Roundtable report that first carried Google’s email. Where a claim rests on that forwarded email rather than a public Google page — including the July 9 date itself — we say so explicitly.

The change did not arrive as a blog post or a help-center rewrite. It surfaced when Menachem Ani, founder and CEO of the PPC agency JXT Group, posted a screenshot of Google’s email to Manufacturer Center account holders on X, and Search Engine Roundtable picked it up on July 16. The email confirms that the ability to manually add or update products directly in Manufacturer Center has been removed, and points affected users at two alternatives: the Manufacturer Center API, or uploading a product file.

One sourcing caveat matters enough to state plainly. As of this writing, Google’s own help center and announcements pages carry no public version of this notice — the July 9, 2026 cutover exists only in the emailed notice as reproduced by a third party. Treat the date as vendor-stated-via-forwarded-email, not as something you can point to on a Google-owned public page. Stranger still, Google’s “Manage your product data” help page still describes the manual product detail editor as if it were live. If you are reconciling what the help docs imply against what the email says, the email wins — but the docs lag is worth knowing about before you cite them internally.

This was not a surprise cutover for attentive account owners. Search Engine Roundtable’s Barry Schwartz noted that Google had been telegraphing the removal to users of the platform for some time before the email landed.

The headline “manual edits removed” overstates how much of the submission surface actually moved. Of the paths into Manufacturer Center, exactly one is gone: typing product data into the console editor. Every file-based path survives — including the one-off manual file upload, which is still a manual workflow, just not a field-by-field one. The table below is the reference we could not find anywhere in the coverage: every submission path, its status on each side of the cutover, and who feels the difference.

Read as a trend rather than an event, the table shows a multi-year direction, not a one-week decision. Google retired FTP uploads for Manufacturer Center on January 8, 2024 — announced back in September 2023 — leaving SFTP and scheduled fetch as the surviving push and pull mechanisms. July 2026 closes the manual editor. Each step removes a submission path that resists validation, automation, and audit, and keeps the ones that machines can drive end to end. That is the lens that makes the next two sections practical rather than academic: one of these two surviving paths is about to be your only workflow.

The Manufacturer Center API is a public REST API that lets applications interact directly with the platform — Google’s own documentation frames its value as “vastly increasing the efficiency of managing large or complex Manufacturer Center accounts.” That positioning matters: this API was built for scale operations, not as a replacement for casually editing one SKU. It exposes two distinct resource types, each with full create, read, update, and delete support.

Getting to production is a three-stage ramp, per Google’s quickstart guide. First, you need a Manufacturer Center account — the API operates on it, it does not replace it. Second, you can test calls through the API Explorer with no code at all, which is the fastest way to confirm your account and data model before committing engineering time. Third, production use requires a Google API Console project with a service account.

The auth model has one step teams routinely miss: Google recommends OAuth 2.0 for initial exploration and a service account for ongoing production access — and that service account must be explicitly added as an authorized user inside the Manufacturer Center account itself. Skipping that grant is the classic “the API returns nothing and I don’t know why” failure. Google ships client libraries with documented Java and .NET samples, so most stacks are not starting from raw HTTP.

If API integration is not on your roadmap, the file feed is the surviving alternative — and for many brand owners it is the pragmatic one, because it can piggyback on feed infrastructure you already run for Merchant Center. Per Google’s product-data documentation, bulk files must be prepared as Text/TSV or XML, and beyond the one-off manual upload into the console, three recurring delivery methods exist: scheduled fetch, where Google pulls the file from your server; Google Cloud Storage; and SFTP.

Whichever delivery method you pick, the content bar is the same — and it is stricter than Merchant Center’s for the equivalent fields. Per Google’s Manufacturer Center FAQs, every product must carry six mandatory attributes: GTIN, ID, brand, title, description, and image link. Every product needs both a distinct ID and a GTIN, no two products may share an identifier, and all GTINs must conform to GS1 standards. A single product may reuse the same value for both its GTIN and its ID, but uniqueness across products is absolute.

The shortcut most teams should evaluate first: an existing Merchant Center feed will populate Manufacturer Center correctly as long as it includes those six mandatory fields — Merchant-Center-only attributes in the file are simply ignored. If your core product-feed strategy already produces a clean Merchant Center feed, the file path into Manufacturer Center may be a routing change rather than a build.

The right path depends on catalog size, update frequency, and what you already run — not on which option sounds more modern. Four common operating models, and where each should land:

For the broader question of which attributes and automations are worth investing in across channels — not just this one console — our cross-channel feed-optimization decision matrix is the companion piece to this playbook.

Here is the reframe the headlines missed: for anyone maintaining data quality properly, Manufacturer Center was already a no-manual-edits product. The Diagnostics section — the console’s issue-flagging surface — has always resolved problems one way: fix the data in your feed and resubmit the feed. Google’s own guidance reads, “To fix the issues, correct the item issues in your feed and re-submit your feed.” Manual UI editing was never the sanctioned repair path for flagged issues.

Diagnostics distinguishes two issue tiers, and the difference determines urgency. Item issues — an invalid GTIN or brand, for example — disapprove the entire product from appearing at all. Attribute issues are gentler: the product stays live, but the specific flagged attribute is dropped and Google substitutes its own inferred value. An item issue is an outage; an attribute issue is a quiet erosion of the content you meant to control. Both get fixed the same way: in the feed, then resubmit.

That is why this change is lower-disruption than the headline suggests for mature operators and higher-disruption for everyone else. If your team treated the feed as the single source of truth and used Diagnostics as the fix queue, July 9 formalized your existing habit. If your team hand-patched single SKUs in the console — and reconciled the feed later, or never — the change removes the crutch entirely, and the same pattern is spreading across platforms: Microsoft Ads’ feed diagnostics push the identical fix-in-feed discipline.

The vocabulary overlap here — feeds, quotas, product data — makes a specific mistake easy, and none of the news coverage bothered to head it off. Manufacturer Center and Merchant Center are different Google products with different APIs. Manufacturer Center manages brand-owner product data — specifications, images, rich content — that Google blends into Search, Shopping, and Images results. Merchant Center, and its Merchant API (the successor to the Content API for Shopping), manages the sellable listings and pricing that actually run as Shopping ads and free listings. A brand can live in both; the integrations are separate.

The practical trap is quota math. The Merchant API publishes documented limits — including product-update throttling — and it is tempting to assume the Manufacturer Center API inherits them. It does not, as far as anyone can show: no public rate-limit or quota figure for the Manufacturer Center API existed at the time of writing. If you are sizing an integration, budget conservatively, test against your own account, and do not copy a number from the Merchant API’s quota page into a Manufacturer Center design doc. It is a different product’s ceiling.

The forward-looking read: an API-first mandate is exactly the interface that agentic feed tooling is built to talk to. A manual console editor was never automatable — no agent could click through a product detail form at catalog scale, and no audit trail survived a human typing into a text box. A REST API with full CRUD, service-account auth, and machine-readable diagnostics is a different substrate entirely: an agent can detect a flagged GTIN, correct the record in the PIM, push the update, and verify the flag cleared — end to end, with every step logged. We laid out that architecture in our piece on agentic PIM and product-data agents; Manufacturer Center going API-only makes it strictly more relevant, because the escape hatch that undermined automated pipelines — someone quietly editing the console — no longer exists.

Our projection: expect more of Google’s feed surfaces to follow this trajectory, because every step in the two-year pattern — FTP retired in 2024, manual edits removed in 2026 — trades a human-friendly path for a machine-verifiable one. Teams that invest now in a single governed pipeline (PIM or feed platform as source of truth, API or scheduled feed as transport, diagnostics-driven repair loops) will absorb the next removal as a non-event too. If you want senior help designing that pipeline — or deciding whether API integration, a managed platform, or a Merchant-feed reroute is right for your catalog — our ecommerce engineering services and AI transformation engagements start with exactly this kind of feed-ops audit.