How price and sale price work together
A product feed holds the normal selling price in one field and, when an item is discounted, the reduced price in a second. The pair is what allows a listing to show a saving: the sale price is what a shopper pays, and the original price is the reference struck through beside it. Send only the first field and the item simply shows one price.
Each value carries its currency, and the currency has to be the one your customers are actually charged in that country. Whether tax is included depends on the market you are selling into, so the same product exported to two countries may need the tax handled differently in each. A sale can also carry an effective date range, telling Google when the discount starts and ends so the listing reverts on its own.
Why pricing attributes matter
Price is checked, not accepted. Google reads the landing page and compares the figure it finds there with the figure in the feed, and a difference is treated as a serious fault rather than a warning. Items can be disapproved individually, and a widespread mismatch can affect the whole account. Of all the reasons Shopping campaigns stop delivering, this is among the most common and the most avoidable.
It also matters commercially. Price is visible in the listing before anybody clicks, so shoppers filter on it and compare with competing offers immediately. A struck-through original price with a genuine reduction beside it is one of the few pieces of persuasion available in a format with almost no room for words.
Where pricing goes wrong
Timing causes most of it. A promotion goes live on the website at midnight and the feed is fetched hours later, so for that window every discounted product disagrees with its page. The same happens in reverse when a sale ends.
Currency and tax handling come next, especially when one export serves several countries and the site displays a converted price that the checkout does not honour. Then there are the misuses of the sale field: inflating the reference price to manufacture a bigger saving, which is a pricing-practices problem as well as a policy one, and leaving a permanent sale price in place so the discount is not a discount at all. Prices that depend on a logged-in account, a coupon or a quantity threshold are a third category, because the figure Google’s check sees is not the figure the customer sees. Fixing any of this by overriding the value in a feed rule makes matters worse, since the page still disagrees.
How to get it right
Make the website the single source of the price and let the feed follow it, rather than maintaining two lists. Schedule promotions using the sale effective dates so the change lands in the feed and on the page together, and fetch the feed more often around a sale.
Show the same currency and the same tax treatment in the feed, on the product page and at checkout. Keep discount conditions out of the feed price entirely: if a customer needs a code to reach the figure, that figure does not belong in the field. Watch the price-mismatch warnings in Merchant Center after every promotion, and check the effect on your Shopping campaigns alongside availability, since the two fields usually break together.
