sale_price [sale_price]: Definition

When to use

Optional for each product

If your product is on sale, submit the new price using the sale_price [sale_price] attribute. To submit the dates of your sale, use the sale_price_effective_date [sale_price_effective_date] attribute.

Format

Follow these formatting guidelines to make sure that we understand the data that you're submitting. 

Type	Number plus currency (use ISO 4217)
Repeated field	No

 

File format	Example entry
Text feeds	15.00 GBP
XML feeds	<g:sale_price>15.00 GBP</g:sale_price>

To format your data for Content API, have a look at the Content API for Shopping.

Guidelines

Follow these guidelines to make sure that you submit high-quality data for your products.

Minimum requirements

These are the requirements that you'll need to meet to show your product. If you don't follow these requirements, we'll disapprove your product and let you know on the Diagnostics page of your Merchant Center account.

• Meet the requirements for the price [price] attribute with some exceptions.

  • The sale price does not have to be the most prominent price on the landing page. For example, if you display price and sale price, the original price can still be in a larger font.
  • Clearly display both non-sale and sale prices on your landing pages. 
• Use a value for sale_price [sale_price] that matches the sale price that you display on your landing page.
• Submit the price [price] attribute with the full price of your product (the cost when it's not on sale), even when you submit sale_price [sale_price]. If your product is on sale and you don't submit the sale_price [sale_price] attribute, submit the sale price as the value of the price [price] attribute.
• Use a value that's less than the value you submit for price [price].
• Don't provide more than 2 digits after a decimal. If you include more than 2 digits after the decimal, they'll automatically be rounded to the nearest acceptable value. For example, 1.0234 will be rounded to 1.02 and 29.8999 will be rounded to 29.90.

Best practices

These best practices can help you go beyond the basic requirements to optimise your product data for performance.

• Submit a price that can be represented in your target country's currency (according to ISO 4217). For example, instead of 1.0012 GBP, submit 1.01 GBP. If your price can't be represented in your target country's currency, then we'll round it to a value that can. 
• Submit sale_price_effective_date [sale_price_effective_date] with the date range that the sale price applies. If you're submitting the sale_price [sale_price] attribute and don't also submit the sale_price_effective_date [sale_price_effective_date] attribute, the sale_price [sale_price] will be used for your product right away.
• Submit correct base prices to enable sale price annotations. When you lower the price of a product for a sale, submit the sale price in the sale_price [sale_price] attribute. Keep submitting the original base price that you charged previously in the price [price] attribute. Learn more about requirements to show sale price annotations for your products.

Examples