A product can be available in one delivery area and out of stock in another. If a shopping listing sends both shoppers to a page that shows the wrong stock or price for their area, the shopper sees a broken offer and the merchant risks a product-data mismatch.
Google Merchant Center’s regional availability and pricing (RAAP) feature lets eligible merchants define regions and submit regional inventory. Google documents Saudi Arabia for postal-code regions and Egypt for state or province regions. Eligibility and available granularity can change; check the account and current official country list before planning a launch. Google Merchant Center: Set up regional availability and pricing
Check whether regional overrides are needed
Start with actual operations. Do price, stock, or delivery eligibility differ by a defined service area? Identify the products and the areas affected, then compare them with inventory and fulfillment records. A city name in an ad is not a region design. Regions should reflect the service boundary, and the same product can need an override for only part of the catalog.
Confirm the country, account eligibility, region granularity, and minimum region requirements in Merchant Center. Google’s current help says regions must cover at least three square kilometers and locations of at least 1,000 people; postal-code granularity is supported in Saudi Arabia, while Egypt appears in the state/province list. The feature’s country support is specific to the product and account. Do not assume every commerce platform or feed supports the required setup automatically.
Make feed IDs and page behavior agree
Build a test matrix for each affected offer: product ID, region ID, price, currency, availability, landing-page URL, and expected visible result. Google’s documentation says the regional inventory source uses the offer ID and matching region ID. Its crawler appends region_id to the click-through URL; the landing page must accept it and show the correct regional price and stock. The primary product data source must contain the URL—putting the URL only in the regional source can make products fail to show.
Test the full rendered path, not just the feed file: load the URL with the region parameter, inspect the selected product variant, price, stock text, structured data, and add-to-cart behavior. Check that cookies, previous location choices, or IP-based logic do not silently override the parameter. Also test the national URL without the parameter; Google may verify both national and regional offers. Google specifies that regional currency must match the national offer currency, so do not model a Saudi riyal offer as a regional override of an unrelated Egyptian-pound national offer.
Roll out safely and diagnose mismatches
Test a small, representative group of products and regions first. Record feed fetch time, page deployment time, and observed price and stock. Inspect Merchant Center item issues after processing, then compare the same ID and region in the source, feed, landing page, and visible shopping result. A valid structured-data test does not prove feed approval, and a single screenshot does not prove consistency across every region.
Keep normal national values for offers without regional overrides. Avoid overlapping regions with conflicting price or availability; Google says one region may be selected at serving time. If a product is unavailable in certain areas, represent that clearly in both the regional source and rendered page. Never mark an unavailable item as purchasable simply to keep an ad live.
Short-video script: Check the region parameter end to end
Hook: “The same product can have different stock by delivery area. Does your landing page know the shopper’s region?”
Shot 1: Show one offer ID and its region ID in the feed test sheet.
Shot 2: Open the click URL with ?region_id=...; point to the visible price and stock.
Shot 3: Compare the page with its product data and structured information.
Close: “Test a sample first. A feed value is only useful when the landing page matches it.”
Educational carousel: Regional shopping feed QA
- Cover: One national product, multiple delivery realities?
- Confirm that the market and Merchant Center account are eligible.
- Define only real delivery regions that need an override.
- Match the product ID and region ID in the regional source.
- Pass the
region_idthrough the primary landing URL. - Render the expected price, currency, and stock on the page.
- Test add-to-cart, structured data, and the national URL too.
- Takeaway: The feed and shopper page must tell the same regional story.
Field experiment thread: Validate a regional override before broad rollout
This is a proposed implementation test, not a claim that a store has passed review.
1/ Select one product and two genuinely different service areas with documented price or stock differences.
2/ Verify country eligibility and supported region granularity in the current Merchant Center account.
3/ Record the product ID, region ID, price, currency, availability, and expected page output.
4/ Publish a controlled feed sample and wait for processing. Keep a timestamp for feed and page changes.
5/ Open the national URL and each regional click URL. Check selected variant, visible price, stock, schema, and cart behavior.
6/ Review item diagnostics and reconcile any mismatch across feed, rendered page, and operations data.
7/ Expand only after the sample is accurate. Roll back or fix incorrect availability before increasing coverage.
Tool-neutral prompt pack: Create a regional offer test matrix
Eligibility review: “For this target country [country], summarize only the supported region granularity and requirements from the supplied current Google documentation [source]. Mark account-level eligibility that must be checked in Merchant Center.”
Feed/page reconciliation: “Compare these redacted rows [feed], rendered page results [URLs/screenshots], and inventory records [data]. Join on product ID, variant, and region ID. Flag price, currency, stock, and URL mismatches. Do not infer an issue when fields are absent.”
Release checklist: “Based on this small test sample [matrix], draft a go/no-go checklist covering national URL, regional URL, region_id, page rendering, structured data, add-to-cart, feed processing, and item diagnostics. Identify untested regions and rollback conditions.”
Stop-doing swipe file: Replace vague regional setup claims
- Stop: “We serve Saudi Arabia, so regional availability is configured.” Use: “We verified the account, region definition, inventory source, and tested URLs for [specific areas].”
- Stop: Upload a region ID that has no matching page behavior. Use: Pass it through and display the corresponding offer.
- Stop: Assume a feed test proves the listing works. Use: Check processed item status and the rendered regional destination.
- Stop: Put the click URL only in the regional inventory file. Use: Follow Google’s current URL requirements for the primary data source.
- Stop: Reuse a currency that does not match the national offer. Use: Verify country, account, offer, and currency rules before launch.
- Stop: Mark every region available because national stock exists. Use: Reconcile actual stock and delivery coverage by region.
Hook–Value–Template: Approve one regional offer
Hook: “A product feed is not region-aware until the shopper lands on the right offer.”
Value: A single test matrix ties account eligibility, region definitions, feed rows, URL behavior, visible price and stock, and fulfillment reality together.
Template: “Country/account: [verified status]. Region and granularity: [definition and evidence]. Offer ID/variant: [value]. Region ID: [value]. National price/currency/availability: [values]. Regional override: [values]. Primary URL: [URL]. Regional test URL: [URL with parameter]. Expected page result: [price, stock, variant]. Observed result: [screenshot/time]. Feed processing/item status: [evidence]. Unresolved issues: [list]. Rollout decision: [go/no-go] with owner and rollback trigger.”
Use the current Merchant Center documentation and the account’s live eligibility before implementation. Regional feeds help represent a genuine regional offer; they do not guarantee product approval, impressions, or sales.