Rules are one of the most useful tools in feed management because they let teams adapt data without waiting for a full platform release. They can map stock states, build channel-specific titles, normalise values, combine fields and supplement missing channel attributes. That speed is valuable.
The same speed can also create technical debt. A retailer discovers that colour is poor in the source, so a rule fixes it for Google. Then another rule fixes titles. Then a supplemental source holds brand corrections. Six months later the website, Google, Meta and a marketplace each contain a different version of the product because nobody repaired the underlying catalogue.
Google’s current Merchant Center terminology is useful here: attribute rules transform product data from one or more data sources, while supplemental data sources can enrich or override existing details. Google’s own local guidance also says required attributes should be added directly to the data source for accuracy and data management where practical, with rules used to supplement.
What attribute rules are good at
A channel rule is a sensible tool when the requirement is genuinely channel-specific or when you need a controlled transformation of otherwise reliable data.
- Mapping values: converting an internal stock state into an accepted channel availability value.
- Channel-specific title structure: combining good source fields into a title optimised for Google without changing the customer-facing PDP title.
- Taxonomy mapping: translating an internal product hierarchy into a destination taxonomy.
- Conditional logic: adding a value only for a defined category, brand or market.
- Temporary remediation: stabilising an urgent issue while an upstream fix is being built, provided the temporary rule has an owner and removal plan.
Google’s attribute-rules feature supports operations such as setting values, extracting data and applying conditions. It also lets teams test draft rules before applying them. Use those capabilities deliberately rather than treating production data as an experiment.
What usually belongs in source data
Dealing with feed errors or missing products? Request free Merchant Center triage
If a value is a factual description of the product and should be consistent across the storefront and multiple channels, I normally prefer an upstream fix.
| Data | Usually best home | Why |
|---|---|---|
| Brand, GTIN, MPN | Source catalogue / PIM / ERP | Core identity should not differ by destination. |
| Current sell price | Authoritative commerce / pricing source | Every customer-facing channel needs the same commercial truth. |
| Availability / stock state | Inventory or commerce source | Channel mappings may translate states, but the fact should originate upstream. |
| Colour, size, material, capacity | Catalogue source | These attributes also power onsite UX, filters and other destinations. |
| Google-specific title order | Feed / attribute rule | It is an optimisation of good source fields for one destination. |
| Google product category | Feed mapping or product-data layer | It is destination taxonomy, not necessarily the retailer’s customer-facing hierarchy. |
| Custom labels | Feed / business-data layer | They are channel segmentation tools, often derived from commercial logic. |
The repeatability test
If the same correction must be recreated for Google, Meta, marketplaces, the website and internal reporting, you probably do not have a channel problem. You have a source-data problem.
A decision framework for where a fix should live
I use five questions before adding another rule:
- Is the value a fact about the product or a presentation choice for one channel?
- How many destinations need the corrected value?
- Can the source system represent the value cleanly?
- How quickly does the business need the fix?
- Who can own and test the rule after the person who created it leaves?
The answer can legitimately be “rule now, source later”. That is often the commercially sensible choice during a live issue. The important part is that later is recorded as a real backlog item rather than forgotten.
Example: missing brand
If every product from supplier X is missing brand but the supplier file has a reliable manufacturer field, a rule can map it quickly. If the storefront, marketplaces and customer service exports also need brand, the permanent correction belongs where the business creates or ingests that product record.
Example: title optimisation
The ecommerce site may deliberately use “Air Max Dn8” as the PDP title while Google benefits from a constructed title containing brand, product type, gender and colour. That is a good candidate for channel transformation, assuming the component fields are accurate upstream.
Signs that attribute rules have become technical debt
- nobody can explain why a rule exists;
- several rules write to the same target attribute;
- rule order matters but is undocumented;
- the same business logic is copied in several channels;
- temporary static values have been in production for months;
- source teams assume “the feed team fixes that”;
- changes are made directly in Merchant Center with no ticket or release note;
- a new feed platform cannot be launched because no one can reconstruct the transformation logic.
Google notes that attribute rules can cascade, meaning later processing can depend on earlier rules. This is useful, but it also means complexity grows non-linearly when many transformations touch the same data.
How to unwind rule debt without breaking production
Inventory the rules
Export or document each target attribute, condition, source field, owner and business reason. Mark rules whose purpose is unknown.
Classify by intent
Separate channel adaptation, emergency fixes, data enrichment and source-data repair. Only the last category is an obvious candidate for moving upstream.
Find the authoritative system
Do not move a correction into the ecommerce platform if the ERP or PIM is the true owner. Put the fact where future teams will expect to maintain it.
Backfill the source
Correct historical products, not just the new-product process, and define validation so the bad state cannot return silently.
Compare old and new outputs
Before deleting a production rule, compare representative processed products, edge cases and total affected offer counts.
Remove the obsolete rule
Once source data is stable and downstream outputs match, simplify the channel layer and record the architectural change.
Where supplemental data sources fit
A supplemental data source can enrich or override details on products that already exist in a primary source. It cannot act as a standalone source to add or remove products. That makes it useful for controlled enrichment such as additional attributes or business data without rebuilding the primary data flow.
For a worked example and help with unmatched item IDs, see our Merchant Center supplemental feeds setup and troubleshooting guide.
The same architectural discipline applies: if the supplemental source contains a temporary channel enrichment, fine. If it has quietly become the only place your organisation stores accurate product facts, ask whether the data belongs upstream.
Rule governance matters more than rule count
A sophisticated retailer may legitimately have many transformations. The problem is not “too many rules” in isolation. The problem is rules with unclear ownership, duplicated business logic, no test coverage and no understanding of which system owns the truth.
What changed in 2026 for this issue?
Checked against Google’s announcements on 31 October 2026.
The relevant 2026 changes are below. They do not by themselves explain every problem. Check your Merchant Center diagnostics before acting on an update about feed rules and source data:
- Merchant API migration affects direct API integrations. Google sunset the Content API for Shopping on 18 August 2026. From 1 September 2026, clients without an approved extension may see intermittent HTTP 410 errors; full decommissioning is planned for early 2027. Custom integrations should migrate to the Merchant API. If you use an ecommerce platform’s official Google integration, the platform provider normally manages its API migration. File uploads, scheduled fetches and Google Sheets are separate data-source methods (Google’s official timetable).
- Bigger minimum image size. From 31 January 2027 product images must be at least 500 x 500 pixels. Smaller images already show the warning “Image too small for upcoming enforcement”. Google will enlarge some small images automatically, but replacing them with proper images is the safer fix (Google’s 2026 product data update).
Common questions
Are feed rules still called feed rules?
Google’s current Merchant Center documentation calls them attribute rules. Many teams still use the older “feed rules” terminology, so both phrases remain common in practice.
Should all errors be fixed in the source?
No. Channel-specific formatting, taxonomy and segmentation often belong downstream. The goal is to keep shared product facts authoritative upstream while using rules for real destination-specific needs.
Can a supplemental data source replace a primary source?
No. Google describes supplemental sources as a way to add or update details on products already provided by a primary source; they cannot independently add or remove products.
How do I test a rule safely?
Merchant Center supports draft rule testing and preview. Test representative products and edge cases before applying a change across a large catalogue.
Official Google references reviewed for this guide
- Attribute rules (formerly feed rules)
- Create and manage product data sources
- Google Merchant Center product data specification
Merchant Center changes over time. This guide was reviewed against current Google documentation on 29 September 2026.
Want a second pair of eyes on the actual setup?
Start with the free Merchant Center & Feed Triage. No account access is needed for the first look. Send the website, catalogue size and the symptom and we will tell you where we would investigate first.
