Product Feed Management: What It Is, Feed Rules and Tools

Product feed management is the ongoing work of keeping the product data you send to Google Merchant Center complete, accurate and in step with your store. It covers where the data comes from, how it is transformed, how often it refreshes and who checks the result. A strong catalog with weak data still gets disapproved, shows with limited performance or never appears.

This guide explains what the work includes, how products reach Merchant Center, what Google requires in the data, how feed rules (now called attribute rules) work and how to choose between a platform app, feed management software and an API integration. If you would rather have specialists run it, see our Google Merchant Center agency page.

What does product feed management include?

Five jobs that repeat every week, not a one-off export. This split is an Avafa working method, not a Google form:

The weak point is usually the handover between jobs: nobody owns the rule that fixes titles, or nobody reads the issue list. Name one owner per job before you choose any tool.

How do products get into Merchant Center?

Through data sources. According to Google’s help center, a primary data source can be a file (uploaded manually or delivered by SFTP or Google Cloud Storage), a Google Sheets template or the Merchant API. Primary sources are the only type that can add or remove products, and Google recommends submitting all products in a single primary data source.

For a file hosted on your server, a scheduled fetch retrieves it automatically. The file address must start with HTTP, HTTPS, FTP or SFTP, point straight to the data file rather than an HTML page, stay under 4 GB and sit in a directory where Googlebot and AdsBot-Google are not blocked. A protected file needs the username and password added in the source.

Platform apps work without a file. The Google & YouTube app on Shopify, for example, syncs products directly; we cover its limits in our Shopify and Merchant Center guide.

Check your tooling for the Content API for Shopping. Google’s Merchant API guide says the Content API was sunset on August 18, 2026 and that requests face progressive errors from September 1, 2026. Any feed script or tool still calling it needs to move to the Merchant API.

What does Google require in the product data?

Treat the product data specification as the fixed point. These are the attributes that cause most trouble:

• id: unique per product, up to 50 characters, ideally the SKU and kept stable across updates. Google says to use the same ID for the same product across countries or languages.
• title: plain text up to 150 characters that identifies the product, with no promotional text such as free shipping and no all capitals.
• description: plain text up to 5,000 characters that matches the landing page.
• link and image_link: the link must use your verified domain. Google’s help pages announce a 500 x 500 pixel image minimum for all products, enforced from January 31, 2027.
• price and availability: price with an ISO 4217 currency code; availability as in_stock, out_of_stock, preorder or backorder.
• brand, gtin and mpn: brand is required for new products except movies, books and music. A GTIN must be a valid GS1 number, and Google warns that a wrong one causes disapproval, so never guess. An MPN is required only when the product has no manufacturer GTIN.
• Apparel: color, gender and age group are required for apparel targeted to markets that include the United States.

What are feed rules and when should you use them?

Google has renamed feed rules as attribute rules. They transform the data you submit so it meets the specification, and they need the Advanced data source management add-on, which you switch on under Settings, Add-ons.

The operations are set to, extract, take latest, prepend and append, find and replace, calculate, split and choose, and clear. Take latest works only for price and availability and compares two or more sources. Google’s own example builds a title by joining the brand column and the title column.

1. Open Data sources and select a primary product source.
2. Open the Attribute rules tab and add a rule for the attribute.
3. Save as draft, run Test rules, then Apply changes.
4. Reprocess the data source so the rule reaches your products.

Two cautions from Google’s page. Rules run in cascading order, and once Clear runs on a product no later rule acts on it. Clearing a required attribute can cause a disapproval.

Our rule of thumb, which is an Avafa method: fix data at the source first. Use rules for what the source cannot change quickly, such as adding a brand to titles or standardizing a color value, and write down why each rule exists.

A supplemental data source adds or updates details on products that already exist. It cannot add or remove products, it matches on the exact product ID and its data source label must equal the feed label of the primary source.

Which feed management software or approach fits your catalog?

Software is one option among several. Choose by how much transformation your data needs and how often it changes:

Google describes the Merchant API route as requiring technical knowledge, so budget developer time before you commit. Before buying any tool, answer these:

1. Which system holds the correct price, stock and identifiers?
2. How many channels need the same data? If you also sell through Microsoft or AI assistants, see one product feed for every AI channel.
3. Who writes and reviews titles?
4. Can the tool show why an item fails, not only that it failed?
5. Does it use the Merchant API rather than the retired Content API?
6. Who owns the Merchant Center account and the feed if you change provider?

How often should the feed refresh?

Google sets no single rhythm for every store. Its guidance on inaccurate prices lists a feed that was not updated when a sale started or ended as a common cause, and its price troubleshooter asks whether the feed was uploaded more than 48 hours ago.

Automatic updates for price, availability and condition are on by default in Merchant Center. They read the structured data on your product pages, so they only help if that markup is correct and matches what shoppers see. Treat them as a safety net, not as your refresh strategy. Our working rule: refresh at least as often as prices and stock change, and force a refresh before and after every promotion.

What should you check every week?

• The Needs attention tab and the Processing tab of each primary source.
• The CSV of affected items, sorted by number of products per issue. The causes are in our guide to products disapproved in Merchant Center.
• Warnings and emails from Google, which must reach someone who reads them.
• Any change in the store, theme or ERP since the last upload, which is the usual origin of new errors.
• The full account against our Merchant Center audit checklist at least once a season.

A clean feed also feeds newer channels. See the product data AI shopping agents read for the attributes they rely on.

How we work at Avafa

We start with an audit of the account and the data source, map where each attribute should come from, set up rules and the refresh schedule, and then review issues on a fixed rhythm. If you want that done for your catalog, talk to our agency specialized in Google Merchant Center.

Frequently asked questions

Do I need feed management software?

Not always. A small catalog on one platform can run on the platform app or a Google Sheets template. Software pays off when data needs heavy transformation or goes to several channels.

What is the difference between a primary and a supplemental data source?

A primary source can add and remove products. A supplemental source only adds or overrides details on products that already exist.

Did Google stop calling them feed rules?

Yes. Google’s help center now calls them attribute rules, and they require the Advanced data source management add-on.

What happens if my tool still uses the Content API?

Google says the Content API for Shopping was sunset on August 18, 2026 and that requests face progressive errors from September 1, 2026. Plan a move to the Merchant API.

Do I need a GTIN for every product?

Not for every product. Use the manufacturer’s GTIN when one exists. Without a GTIN, provide the brand and MPN, and set identifier_exists to no only when the product has neither.

Will automatic updates fix my price mismatches?

They can correct small gaps using the structured data on your pages. They do not replace a correct feed, and wrong markup makes things worse.

Who should own the feed?

One named person or team, with access to the store, the data source and Merchant Center. Also check who owns the Merchant Center account itself before changing provider.