To participate in regional availability and pricing (RAAP), you'll need to set up regions, add regional inventory and update the landing page.
On this page
Set up regions
Activate the Regions add on
Ensure that your target country is eligible for RAAP to activate the Regions add-on.
Steps to activate the Regions add-on
-
Go to Add-ons under 'Settings'
in the left navigation menu.
- Select the Regions add-on card from the 'Discover' tab.
- Select Activate.
To complete the onboarding, the following steps are required:
- Create regions in the Merchant Center account
- Upload regional inventory data source
- Update landing pages
Create and manage regions
Regions definitions, requirements and support granularity
A region is used to define a geographic area in which products share the same non-national online price, availability or both. Regions are used by both the regional availability and price feature as well as regional delivery.
If using both features, depending on your business model, you may only need one set of regions for both, or you can create separate regions for each.
A region is defined by:
- A geographic area defined by a set of postcodes, states or provinces.
- A region ID uniquely identifying each region. It's used to indicate the region in the regional inventory data source.
If you are configuring regions via the 'Regions' page, define areas based on postcodes, state or province on the 'Regions' tab on the 'Business info' page of your Merchant Center account.
Regions may be configured within a single account utilising both postcodes and state/province borders. While it is necessary to select one type of granularity for each distinct region, the account is capable of accommodating both concurrently.
Region granularity support: All RAAP-eligible countries support state or province-based regions, and some countries also support more granular postcode-based regions as well.
| Postcode | Argentina (AR), Australia (AU), Brazil (BR), Canada (CA), Chile (CL), Colombia (CO), Switzerland (CH), Germany (DE), Denmark (DK), France (FR), Great Britain (GB*), Hungary (HU), Indonesia (ID), India (IN), Italy (IT), Japan (JP), Mexico (MX), the Netherlands (NL), New Zealand (NZ) (allowlist only), South Africa (SA), the United States (US), Vietnam (VN) |
| State or province | Algeria (DZ), Angola (AO), Argentina (AR), Australia (AU), Austria (AT), Bahrain (BH), Bangladesh (BD), Belarus (BY), Belgium (BE), Brazil (BR), Cambodia (KH), Cameroon (CM), Canada (CA), Chile (CL), Colombia (CO), Costa Rica (CR), Côte d'Ivoire (CI), Czechia (CZ), Denmark (DK), Dominican Republic (DO), Ecuador (EC), Egypt (EG), El Salvador (SV), Ethiopia (ET), Finland (FI), France (FR), Georgia (GE), Germany (DE), Ghana (GH), Greece (GR), Great Britain (GB), Guatemala (GT), Hungary (HU), India (IN), Ireland (IE), Israel (IL), Japan (JP), Jordan (JO), Kazakhstan (KZ), Kenya (KE), Kuwait (KW), Lebanon (LB), Madagascar (MG), Malaysia (MY), Mauritius (MU), Mexico (MX), Morocco (MA), Mozambique (MZ), Myanmar (Burma) (MM), Nepal (NP), the Netherlands (NL), New Zealand (NZ), Nicaragua (NI), Nigeria (NG), Norway (NO), Oman (OM), Pakistan (PK), Panama (PA), Paraguay (PY), Peru (PE), the Philippines (PH), Poland (PL), Portugal (PT), Romania (RO), Saudi Arabia (SA), Senegal (SN), Singapore (SG), Slovakia (SK), South Korea (KR), Spain (ES), Sri Lanka (LK), Sweden (SE), Switzerland (CH), Tanzania (TZ), Thailand (TH), Tunisia (TN), Türkiye (TR), Uganda (UG), Ukraine (UA), the United Arab Emirates (AE), the United States (US), Uruguay (UY), Uzbekistan (UZ), Venezuela (VE), Zambia (ZM), Zimbabwe (ZW). |
Note: In Great Britain, only the first two characters of postcodes are supported.
Example: For the postcode 'SW1A 1AA', 'SW' is the supported portion.Region requirements and best practices
- The currency used for a region must be the same as the currency used for the national product offer.
- Regions need to meet minimum geographic size and population requirements. They must cover an area of 3 km² and represent the locations of at least 1,000 people.
- Regions should ideally be geographically contiguous. Each contiguous area within a region is individually subject to the size and population limits mentioned in the bullet point above. Avoid adding unattached small areas to a region. A small area can be extended by clustering it with surrounding postcodes to make it larger. If the region doesn't meet these size requirements, an error message will be shown in the 'Issue' column on the 'Regions' page.
Region ID requirements
- Can be a postcode
- Can be alphanumeric
- Can't have symbols other than '_'
- Length of between 2 and 100 characters
- Lower-case only
Best practices
- Avoid including an area (such as a postcode, state or oblast) in more than one region. If two regions overlap and they have conflicting regional price or availability, one region and its corresponding price or availability will be selected at serving time.
- You don't need to set up regions for the entire country; you only need to cover the areas that require a regional override for an offer.
- If you have a physical warehouse or delivery hub, we recommend basing your regions around these locations.
- If you set your region ID to be a postcode that exists within the region, or to a shop ID that's already used internally by your site, it may make the landing page integration easier.
Create a region
Regions are configured at the individual account level, which can be done either through the 'Regions' page in Merchant Center, Content API or Merchant API. To create a region in Merchant Center, follow these steps:
- In your Merchant Center account, select Settings
in the left navigation menu.
- Select Business info
and then Regions.
- Select Add region to create a new region.
- Enter values for 'region ID', 'region name' and 'country'.
- The Region ID needs to be unique for each region and can consist of between 2 and 100 alphanumeric characters. Underscores ('_') and only lower-case letters are allowed.
- The region name helps you to identify the geographical area that you want to include in your region.
- Use the drop-down menu beside 'Country' to select which country this region will apply to.
- Create your region using postcodes, states or provinces.
- To use postcodes, enter one entry per line in any of the following styles:
- A postcode (e.g. 75008).
- A range of postcodes (e.g. 2000–2500).
- A range of postcodes using a prefix with a wildcard (*) (e.g. 94*).
- A range of postcodes using two prefixes with wildcards (*), using the same number of digits for both prefixes (e.g. 94*–95*).
- Note that there is a default 50K limit on the number of entries per Merchant Center ID. An entry is either an individual postcode (94043), a wildcard (940*), a range (94000–95000), an AA1 (e.g. 'California') or a radius area. If you require a limit increase, contact our support team via this form.
- To use states or provinces, select the correct ones.
Edit a region
- In your Merchant Center account, select Settings
in the left navigation menu.
- Select Business info
and then Regions.
- Select the particular region that you want to edit under 'Region name' and in 'Edit region' make changes in the relevant field.
- Note that you will need to separately update the region ID in your regional inventory data source to reflect updated region IDs if you've changed that field here.
- To edit the geographic area:
- Postcodes:
- Add new codes just like you did when you created the region, with one range per line. Select Add postcode.
- To remove a postcode, select the X next to it or select Clear all to remove all postcodes.
- States or provinces:
- Select or deselect the tick boxes.
Remove a region
Before you can remove a region, make sure that it's no longer in use.
- In your Merchant Center account, select Settings
in the left navigation menu.
- Select Business info
and then Regions.
Set up regional inventory
You can set up your regional data source either through the Merchant Center data source, Content API or Merchant API. Regional data must be updated at least once every 14 days, otherwise it will be considered stale.
To set it up through the Merchant Center data source, follow the steps below:
- In your Merchant Center account, select Settings
in the left navigation menu.
- Select Data sources and then the Supplemental sources tab.
- Note that the 'Supplemental sources' tab is visible only when you enable the 'Advanced data source management' add-on.
- Select Add regional inventory.
- Upload your regional inventory data source from a file. You can choose one of the following methods to upload a file:
- Enter a link to your file.
- We recommend the scheduled fetch input method. With scheduled fetch, you host your XML data source at a URL and specify when Google should fetch it. Your file location must begin with 'http://', 'https://' or 'sftp://'.
- Add a file using SFTP or Google Cloud Storage.
- Select View SFTP and Google Cloud Storage details to create a password and activate your SFTP account or add your Cloud Storage account if you haven't already done so.
- Upload a file from your computer.
- Configure your data source options for the method that you've chosen. If you're using scheduled fetch:
- Enter the file URL.
- Select the pencil icon
across the 'Edit schedule' field and select the fetch frequency and time from the drop-down menu, then select Save.
- If your URL is password-protected, provide your login info.
- Select Continue.
Regional inventory data sources support the following required attributes:
- ID
[id](offer id) - Region ID
[region_id](matches the retailer-defined value submitted in the Regions menu)
Regional inventory data sources also support the following optional attributes:
- Price [price]
- Sale price [sale_price]
- Sale price effective date [sale_price_effective_date]
- Availability [availability] (Note: Only
in_stockandout_of_stockvalues are supported) - Loyalty programme
[loyalty_program]
in_stock and out_of_stock for the availability [availability] attribute. The values preorder and backorder aren't supported.Example configurations
Since you can set different levels of regional availability for your products, it is important to determine beforehand what type of regional inventory settings and granularity you will require. For example:
- Is your product available in a subset of postcodes within a state? If yes, check below if your target country is supported on the region or postcode level
- Do all your products have regional pricing or availability, or both, or only a subset?
Use the table below as a guidance on possible ways to set up your regional data source:
| National product data source | Regional inventory data source | |||
| Availability | Price | Availability | Price | |
| All products regional price and availability | Out of stock | Highest of the regional prices | In stock | Regional price |
| All products regional availability only | Out of stock | National pricing | In stock | Blank |
| All products regional price only | In stock | Highest of the regional prices | Blank | Regional price |
For offers that don't have regional overrides, continue to manage national price and availability (in_stock or out_of_stock) in the primary data source as you normally would.
Offers are available nationally with the exception of a handful of states or areas
out_of_stock for those regions.| National product data source | Regional inventory data source | ||
| Availability | Price | Availability | Price |
in_stock |
National price | out_of_stock |
Blank |
Offers are only available in a handful of states or areas, not nationally
in_stock for those regions.| National product data source | Regional inventory data source | ||
| Availability | Price | Availability | Price |
out_of_stock |
National price | in_stock |
Blank |
Offers have regional pricing for some or all states or areas
| National product data source | Regional inventory data source | ||
| Availability | Price | Availability | Price |
out_of_stock |
National price* | Blank | Regional price |
*Use realistic pricing. Don't use values of 0 GBP or 1 GBP.
Offers are only available in a handful of states or areas, not nationally, and have regional pricing
in_stock for those regions and provide regional prices.
| National product data source | Regional inventory data source | ||
| Availability | Price | Availability | Price |
in_stock |
National price* | in_stock |
Regional price |
*Use realistic pricing. The pricing that is most common across states or areas.
Update landing page
The price and availability on your landing page must match the regional price or availability shown on Google surfaces from your regional data source. To ensure an accurate landing page experience, Google appends the region_id corresponding to the location of the shopper as a parameter to the click-through URL. You must adjust your landing pages so that they can accept this parameter and render a product landing page that shows the corresponding price and availability.
Note that the URL should be updated in the primary data source. If it's added to the regional data source, it could result in products not showing up.
Example:
Value provided in the link attribute: https://mystorewebsite.com/p/myproductlandingpage
Final URL: https://mystorewebsite.com/p/myproductlandingpage?region_id=123456
Value provided in the link attribute: https://mystorewebsite.com/p?offer=myproduct
Final URL: https://mystorewebsite.com/p?offer=myproduct®ion_id=123456Best practices
If your region IDs are postcodes or existing internal shop IDs and your landing page already has a location or a shop picker, you may be able to simplify your landing page integration by passing the region ID directly into the existing picker logic to update the price and availability.
- It is recommended that you follow the best practices for landing pages.
- To prevent crawling issues, check schema.org markup.
- You can use the rich results tool to test your landing pages.
- Maintain a stable landing page user experience and ensure that the region_id parameter is not overridden by cookies, previous visits or IP detection.
- Show the same price and availability on the product page as in the regional data source, even if the offer is set to 'out of stock'.
- If you use structured data, annotate each regional page (URL includes region_id=XXXXX) with the corresponding price and availability information.
Policies
Regional URLs must have a valid landing page where the regional details can be verified. The regional URLs must load or redirect to a web page within the same website where users can find the appropriate regional price and availability of the offer.
Our crawlers will occasionally check the availability and pricing of the products provided by you in your product data source. Pricing or availability mismatches may lead to item-level or account-level disapprovals. Learn more about issues in Merchant Center.