What happened
As of July 9, 2026, Google removed the ability to add or update products by hand inside Manufacturer Center. Every submission now goes through the API or a file upload. Nothing gets deleted — data submitted before July 9 stays in the account — but the interface is no longer a place where you can change it.
That closes a workflow plenty of small brands relied on. Manufacturer Center is where brand owners, as opposed to resellers, hand Google the authoritative version of their product data — the attributes that flow into Shopping results across every retailer selling the product. For a brand with a small, slow-changing catalog, hand-editing in the interface was the path of least resistance — building a feed for a handful of products felt like overkill. That option is gone.
Why this matters
The immediate risk isn't dramatic — it's the correction that can't ship. A spec changes, a description needs fixing, a new product launches, and the person who always handled it in the interface discovers there's no edit button. Until someone builds the feed or wires the API, the error sits live in Google's product data, propagating to every retail listing that pulls from it.
This also fits a pattern worth internalizing: across Google's merchant stack, interfaces are becoming dashboards you read, while data goes in through feeds and APIs. The quick-fix-in-the-UI escape hatch keeps disappearing, product by product. Structured, automated data pipelines aren't a nice-to-have for working with Google anymore — they're the only door left.
One clarification for BigCommerce merchants who own their brand: your Merchant Center feed and your Manufacturer Center submission are separate things with different purposes. Fixing your Shopping feed does not touch Manufacturer Center data. If your brand maintains both, both now need an automated path.
What to do about it
Find out this week who hand-edits Manufacturer Center
Ask directly: does anyone on the team update products in that interface? If yes, that routine died on July 9 and needs a replacement before the next launch or spec correction hits. Don't discover this during a product recall or a pricing dispute.
Stand up a file upload first, API later
A spreadsheet-based file upload is the fastest replacement and fine for a small, slow-changing catalog. Reserve the API build for catalogs that are large or change weekly. Getting a working file feed live matters more than getting the elegant integration built.
Export and audit your pre-July-9 data
Everything submitted before the cutoff is still in the account, including any errors. Review what's there now, because from here on the only way to correct it is through your new feed — and you want the first feed run to be a clean overwrite, not a mystery merge.
Write down the new submission path before it lives in one person's head
Name an owner for the Manufacturer Center feed, store the file template somewhere the whole team can reach, and set a cadence — even quarterly beats never. The manual interface forgave improvisation; a feed process doesn't. When the person who built it leaves, the document is what keeps your product data from going stale.