Google Ads

Price And Sale Price

Also called price attribute, sale_price, sale effective date

Paired feed fields holding the normal and discounted price of an item, both verified against the landing page before ads run.

Quick facts: Price And Sale Price

Category
Google Ads
Also called
price attribute, sale_price, sale effective date
Level
Beginner
Affects
Product approval, listing appeal, account standing
Where to see it
Google Merchant Center diagnostics, your shop's pricing rules
In this article4
  1. How price and sale price work together
  2. Why pricing attributes matter
  3. Where pricing goes wrong
  4. How to get it right

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.

Do and do not

Do

  • Let the website be the single source of price
  • Schedule discounts with sale effective dates
  • Match currency and tax treatment across feed and checkout

Do not

  • Put coupon or login-only prices in the field
  • Inflate the original price to enlarge the saving
  • Override a price in a rule to clear an error

Questions people ask about this

Why do I get price mismatch errors during a sale?

Almost always because the website changed before the feed did. Google compares the figure on your landing page with the one it last fetched, and any window where the two disagree produces mismatch errors. Schedule discounts using the sale effective dates so both change together, and fetch the feed more frequently while a promotion is running.

Should the feed price include tax?

It depends on the country you are selling into, because markets differ in whether displayed prices are expected to include tax. The rule that never changes is consistency: the feed, the product page and the checkout must all show the same treatment. A price that excludes tax in the feed but includes it on the page will be read as a mismatch.

Can I show a discount that needs a coupon code?

Not in the price fields. The figure there must be what any shopper pays when they land on the page, with no code, login or minimum quantity required. A discount that depends on a condition belongs in a promotion rather than in the price attribute, otherwise the automated check will find a page price that does not match.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.