Price Rules in Product Feeds: When and How to Adjust Prices

Short answer: Price rules in a product feed are safe when they make the feed price match what shoppers see on the page: fixing formats, adding tax where the store stores net prices, applying the same rounding as the site, or converting currency with the same rates. They are risky when they create a price that no landing page shows, such as an arbitrary markup or discount only in the feed, because platforms compare feed and page and flag mismatches. Test any rule on a sample before applying it to the whole catalog.

The golden rule: feed price equals page price

Every shopping platform that uses product feeds checks the price you submit against the landing page. Google crawls the page and reads the visible price and structured data; Meta and others do similar checks or rely on shopper feedback. The price in the feed must be the price a shopper from the target country sees on the linked page, including tax where required, in the same currency.

That rule defines what price rules can and cannot do. A rule that brings the feed closer to the page is a fix. A rule that moves the feed away from the page creates a mismatch, no matter how good the business reason. There is no feed setting that allows you to advertise a price your website does not show.

With that in mind, price rules are still useful. Store data is often stored differently from how it is displayed, and rules bridge that gap.

It helps to think of the feed as a translation, not an editorial layer. Its job is to express the page’s offer in the format the platform understands. A price rule is part of that translation when it changes how a price is written or calculated to match the page, and it is outside that job when it changes the offer itself.

Safe price rules

• Formatting: convert “1.299,00 €” into “1299.00 EUR”, remove symbols and thousands separators, add the currency code.
• Adding tax: if the store stores net prices but displays gross prices in the target country, multiply by the correct tax rate so the feed matches the display.
• Rounding: if the website rounds prices, for example to .99 or whole numbers after tax, apply the same rounding so there are no one-cent differences.
• Currency conversion: if the site shows converted prices, use exactly the same rates and rounding as the site, updated as often as the site’s.
• Choosing the right source field: using the sale price field when a sale is active, or the variant price instead of the parent price.

Each of these makes the feed more accurate. They are also the rules most stores need at some point, especially stores that sell in several countries or whose platform stores prices without tax.

A typical example: a WooCommerce store in Germany enters prices without VAT and displays them with 19% VAT added. The raw store price for a product is 25.21, and the page shows 30.00 EUR. A rule that multiplies by 1.19 and rounds to two decimals produces 30.00 EUR, matching the page. Without the rule, the feed would send 25.21 EUR and every product would mismatch by the same percentage. If some products use a reduced VAT rate, the rule needs to know which rate applies to which product, usually from the tax class stored with each product.

Risky price rules

• Feed-only discounts: showing a lower price in the feed to win clicks, while the page shows the normal price. This is a mismatch and can be treated as misleading.
• Feed-only markups: raising feed prices, for example to cover channel fees, while the page shows lower prices.
• Coupon prices: sending the price after a coupon that shoppers must enter at checkout.
• Approximate conversions: converting with a different exchange rate than the site, which creates small but systematic mismatches.

If you want different prices on different channels, the website must support it: for example a dedicated landing page or a URL parameter that shows the channel price to everyone who arrives through that link. Without that, the rule simply produces disapprovals.

When in doubt, ask one question: if a shopper clicks this listing right now, will they see exactly this price on the page? If the answer is anything other than a clear yes, the rule needs to change.

Channel-specific pricing done properly

Some businesses legitimately charge different prices by channel or market. A marketplace might require a price that includes its fees; a country-specific store might have its own price list. The feed can reflect these prices when the shopper who clicks sees them too.

For most small stores, the simplest and safest policy is one price per market, shown everywhere.

Remember also that consumer protection rules in many countries require the advertised price to be the price the consumer pays, including mandatory fees. A feed price that is lower than the checkout total, because of hidden surcharges, is a problem for platforms and potentially for regulators.

Sale prices and price rules

Price rules interact with sales. If a rule adds tax to the regular price, it must also add tax to the sale price. If a rule rounds prices, it must round both in the same way. A common error is a rule applied to price but not to sale_price, which produces a sale price that is lower or higher than the page shows.

When sales are scheduled, also check that the rule respects effective dates. The feed should carry the sale price with its dates, and rules should not strip the dates or apply the sale early.

Testing a price rule

1. Choose a sample of products that covers the edge cases: different tax rates, variants with different prices, items on sale, very cheap and very expensive items.
2. Apply the rule and export the resulting feed values for the sample.
3. Open each product page as an anonymous visitor in the target country and compare prices to the cent.
4. Only roll out the rule to the full catalog when every sample item matches.
5. After rollout, watch price mismatch diagnostics for a week.

Document each rule: what it does, why it exists and who approved it. Price rules that nobody remembers are a classic source of mysterious mismatches months later.

Automatic item updates in Merchant Center can hide a faulty price rule for a while by correcting prices from the page’s structured data. That is useful as a safety net, but check the diagnostics for signs that updates are constantly being applied, because that often means a rule is producing wrong values.

When to fix prices in the store instead

If a rule compensates for a problem in the store, such as inconsistent price formats entered by different staff, it is better to fix the store data. Rules that work around messy data tend to multiply and become fragile. Keep feed rules for genuine differences between how data is stored and how it must be presented, and fix everything else at the source.

The same goes for pricing decisions. If a product is overpriced compared with competitors in Shopping results, change the price in the store, where it applies to every channel, rather than creating a feed-only exception.

How Feeds helps

Feeds includes price rules for product feeds built from WooCommerce, Shopify or a CSV link, and detects the currency automatically. That lets you adjust feed prices where store data and displayed prices differ, alongside rules that skip out-of-stock products and rewrite titles. The output is a Google product XML file that Merchant Center and Meta can fetch. Plans are on the pricing page.

Related reading

• How to Fix Price Mismatch Errors in Google Merchant Center
• Sale Prices in Product Feeds: sale_price and Effective Dates
• Multi-Country Product Feeds: Currency, Language and Prices

The bottom line

Use price rules to make the feed match the page: formatting, tax, rounding and consistent currency conversion. Avoid rules that create prices no landing page shows. If you need channel-specific prices, the linked pages must show them too. Test every rule on a sample of edge cases, apply it to sale prices as well, and document why it exists.

KKK

Can I show a lower price in Google Shopping than on my website?

Only if the page shoppers land on shows that lower price to them. Otherwise it is a price mismatch and can be treated as misleading.

Is it safe to add VAT to prices with a feed rule?

Yes, if your store stores net prices but displays gross prices. The result must match the displayed price exactly, including rounding.

Why do I get one-cent price mismatches?

Usually because of different rounding between the site and the feed, often after adding tax or converting currency. Apply the same rounding as the site.

Should price rules also apply to sale prices?

Yes. Any tax, rounding or conversion rule applied to price must be applied to sale_price in the same way.

Can I use price rules to cover channel fees?

Only if the linked landing page shows the higher price. Otherwise the feed and page do not match, and items will be disapproved.