Should I fix product data in my shop or in feed rules?

Fix core facts like GTIN, Price, and Weight in your shop system. Use feed rules for channel-specific optimizations, such as title formatting or custom labels for ad campaigns.

Are feed rules bad practice?

No, they are an essential abstraction layer. However, using them to fix errors that should be handled by your primary database can lead to unnecessary complexity over time.

Can feed rules cause Merchant Center errors?

Yes, if a rule creates data that contradicts your landing page (like a different price), Google will flag it as a mismatch error.

How many feed rules are too many?

There is no hard limit, but if you have more than 20-30 rules per feed, it's often a sign that your source data needs a cleanup or your logic is becoming too fragmented.

Do feed management tools replace a PIM?

No. A PIM is for managing product information across an entire company. A feed management tool is for transforming and optimizing that information specifically for advertising channels.

Feed Rules vs Source Data: Where to Fix Product Data

In almost every feed setup discussion, a fundamental question arises: "Should I fix this in my shop, or should I create a rule for it?"

This isn't just a technical question—it's often a strategic one. Marketing teams want to optimize for performance now, while engineering teams want to maintain clean, scalable systems. Agencies often push for quick fixes because they don’t have access to the source data.

At 42feeds, we’ve seen this tension play out hundreds of times. The answer isn’t about theory—it’s about trade-offs. Structure beats shortcuts, but sometimes shortcuts are all you’ve got. Understanding the core workflow of import, transform, and export helps clarify these choices.

What Is Source Data?

Source data is the raw information stored in your primary systems—your CMS (Shopify, WooCommerce, Magento), ERP, or PIM (Product Information Management). It’s the "seed" from which everything else grows.

Strengths:

Permanence: It is the ultimate source of truth for your business.
Consistency: Changes here reflect across every channel, including your website's front-end.
Integrity: It defines core product facts like SKU, weight, and base price.

Limitations:

Inflexibility: Changing source data often requires development resources or manual bulk edits that are hard to undo quickly.
Context-Blindness: Your shop system doesn’t know that Google Shopping has different title requirements than TikTok or Meta.

What Are Feed Rules?

Feed rules are a logic layer that sits between your source data and your marketing channels. They are instructions that say: "When you see X in the source, do Y in the feed."

Common examples of Google Shopping feed rules include:

Appending the Brand name to the beginning of a title.
Mapping a custom field like "Material" to the official platform attribute.
Overriding a price for a specific seasonal promotion without changing it on the site.

Rules exist because the real world is messy. They’re often used not because they’re ideal, but because they’re the only place marketers have the autonomy to act.

The Core Difference: Responsibility vs. Transformation

The distinction between source data and feed rules is best understood as a division of labor.

Source Data owns Correctness. If the product is actually red, but the database says blue, that is a source data failure.
Feed Rules own Context. If the product is "Cherry Blossom," but Google users search for "Pink," the rule transforms the data for that specific audience.

Google and Meta care deeply about consistency. If your feed says one thing and your landing page says another, you will trigger Merchant Center feed errors. Rules should optimize the data, but they should never contradict the reality of the checkout experience. This balance is critical for classifying errors correctly. Understanding the feed structure validation process is key to maintaining this balance.

When to Fix Data at the Source

You should resist the temptation to use feed transformations to cover up fundamental database neglect. Fix it at the source when:

It is a Core Product Fact: If a GTIN is wrong or a weight is missing, fix it in your ERP or CMS. These are "immutable" truths.
It is Policy-Relevant: Data regarding safety warnings or regulated categories belongs in the primary record.
The Data is Reused Across All Channels: If you find yourself writing the same rule for Google, Meta, and Pinterest, you aren’t transforming; you’re repairing. Move that repair into the source.

If you use feed rules to fix broken source data repeatedly, you are accumulating technical debt.

When Feed Rules Are the Right Tool

Feed rules are the scalpel, not the hammer. They are the right tool for:

Channel-Specific Requirements: Google might want "Brand + Color + Size" in the title, while Pinterest might just want "Title + Description."
Temporary Overrides: Flash sales or short-term custom labels are perfect for rules.
Testing and Experimentation: Want to see if adding "Sustainable" to your titles improves CTR? A rule lets you test this in minutes without a database migration.
Error Mitigation: If a sudden shop update breaks your category mapping, a rule acts as a "buffer" to keep your ads running while you fix the root cause. As noted in our optimization checklist, rules provide the agility that shop systems lack.

The Hidden Risks of Overusing Rules

While powerful, a setup that relies too heavily on feed rules can suffer from "Rule Sprawl."

Debugging Nightmares: When rules stack on top of each other, it becomes difficult to trace why a specific product title looks a certain way.
Knowledge Loss: If the person who built the rules leaves, the feed becomes a "black box" that everyone is afraid to touch.
Temporary Rules Becoming Permanent: If a rule lives longer than six months, it deserves a second look. Is that "temporary" fix now a permanent part of your strategy?

How Feed Management Tools Implement Rules

Professional tools approach rules with a focus on transparency and predictability. Instead of hidden logic, they provide a visual way to see how data flows. A good system allows you to import the source, apply a visible transformation, and preview the output instantly.

This ensures you aren’t guessing what will happen—you are designing it.

How 42feeds Approaches Rules vs. Source Data

At 42feeds, we view ourselves as a pragmatic system, not a patchwork solution. We don’t want to replace your PIM; we want to make your data useful.

Separation of Concerns: We maintain a clear distinction between imports (what you have) and transformations (what you want).
Readable Logic: Our rule engine uses human-readable logic. You don't need a degree in Regex to change a title.
Primary and Secondary Imports: We support supplemental feeds, allowing you to merge Google Sheets for margin data without cluttering your main shop system.
A Usable Free Tier: We offer 2 live imports and 2 live exports for free, so you can set up professional rules without financial friction.

A Simple Decision Framework

Next time you are unsure, use this checklist:

Is this data true for the customer on the website? -> Source.
Is this data only for a specific ad platform? -> Rule.
Will I need this same change in 6 months? -> Source.
Am I just testing a hypothesis? -> Rule.
Is the shop database too hard to change right now? -> Rule (as a bridge).

Summary

Structure beats shortcuts every time. A good feed setup ages well because it respects the boundary between what the product is (Source) and how it is sold (Rules).

By being intentional about where you fix your data, you reduce technical debt and build a more resilient marketing machine. If you want clearer rules without turning your feed into a black box, 42feeds can help you bring order to the chaos.

Feed Rules vs Source Data: Where Product Data Should Be Fixed