Use the maximum retail price [maximum_retail_price] attribute to tell users how much the manufacturer suggests you should charge for your product. This information is shown to users in Free Listings.
On this page
When to use
Optional for each product
This attribute is only available in India.
Format
Follow these formatting guidelines to make sure Google understands the data you're submitting. Learn when and how to submit your product data.
| Formatting specifications | |
| Technical name | maximum_retail_price |
|---|---|
| Type | Price (Numeric + ISO 4217 code) |
| Repeated field | No |
| Schema.org property (Whatâs this?) | No |
File format examples
To ensure your attribute is recognized correctly, use the formatting specific to your data source type.
| Data source format | Examples |
| Text (TSV or CSV) data sources | 15.00 INR |
| XML data sources | <g:maximum_retail_price>15.00 INR</g:maximum_retail_price> |
| Merchant API | To format your data in the Merchant API, check the Merchant API resource. |
Minimum requirements
Make sure that the maximum retail price in your product data meets both the landing page and checkout requirements. Learn more About landing page requirements.
- Submit an amount and currency that match the maximum retail price on your landing page and the checkout pages. Learn more about currency requirements for your target country.
- Show the price in the currency of your target country prominently on your landing page and checkout pages.
- Donât change the maximum retail price of your product on your landing page based on a userâs location. Ensure that users can purchase the product online for the maximum retail price that you submit, regardless of their location.
- Display variants and maximum retail prices in a straightforward way on your landing page.
- Donât submit products with a maximum retail price that constantly changes, such as auctions and prices based on a live currency exchange.
- Keep your prices up to date. If the maximum retail price changes, make sure to provide the latest price value.
- Donât include shipping costs in your maximum retail price. Instead, use Merchant Center shipping settings or the shipping
[shipping]attribute in the data source. - Don't provide more than 2 digits after the decimal point. If you include more than 2 digits after the decimal point, they are automatically 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.
- Donât include activation fees for wireless plans in the price that you submit for mobile devices and tablets sold in the US. Wireless subscription plans aren't supported for Shopping ads and free listings in the US.
- Comply with local laws when submitting price information.
Best practices
These best practices can help you go beyond the basic requirements to optimize your product data for performance.
- Submit a price that can be represented in the currency of your target country according to ISO 4217. For example, instead of 1.0012 INR, submit 1.01 INR. If your price canât be represented in the currency of your target country, then we round it to a value that can.
- Highlight sales that promote your products. Use the sale price
[sale_price]attribute to tell users how much youâre charging for your product during a sale. During the period that you specify, your sale price will show as the current price for your product. If your original and sale prices meet certain requirements, your original price may show along with the sale price, allowing people to view the difference between the 2 prices. - Use currency conversion as an easy way to target a country that uses a different currency than the one on your website and in your product data. If you use currency conversion, the prices on your landing page, checkout pages, and in your product data must still match. We display the converted price in your ad or free listing, but the converted price doesn't need to appear on your landing page or at checkout. Learn more About currency conversion.
