INTRODUCTION
Local inventory advertising ka promise straightforward hai: customer ko nearby store mein available product dikhaiye. Execution mein difficulty product feed se zyada location matching mein hoti hai. Ek retailer “Connaught Place”, “CP”, “New Delhi 110001” aur billing-system address ke four variations use kare, to platform ke liye same store ko reliably join karna difficult ho sakta hai.
Google Merchant Center’s current help documentation labels the store address attribute, technical name store_address, as required for each applicable product in this data-source context. A valid postal address is mandatory; failure can lead to product disapproval. India is officially supported for local inventory ads and free local product listings.
This should be treated as an immediate data-quality task, not a reason to panic. Google’s page does not state a universal future deadline, and online-only Shopping listings should not be assumed to require local-store fields. The correct action is to identify participating local-inventory offers, validate their store relationships and watch Diagnostics.
WHAT GOOGLE’S DOCUMENTATION CONFIRMS
The attribute
Technical name: store_address
Type: Unicode string
Repeated field: No
Purpose: specify the postal address of the store.
Google marks the attribute “Required for each product” on the current Store address help page. It says the address must be valid and checked for typos or errors. Merchant Center should also contain the correct address.
Supported formats
For text, TSV or CSV data, the value is a postal-address string.
For XML, the format uses:
<g:store_address>…</g:store_address>
For Merchant API, Google directs implementers to the relevant Merchant API formatting resource. A legacy Content API assumption should not be copied without checking the current Merchant API schema and the account’s active data-source setup.
Disapproval risk
Google says products that do not meet the minimum requirements can be disapproved and the issue will appear in Merchant Center. This makes Diagnostics the operational source of truth for affected offers.
Local inventory programme context
Local inventory ads and free local product listings are available to Indian retailers with eligible brick-and-mortar locations. Stores must be places where customers can physically visit, view and buy the item. These local formats have policies distinct from standard online Shopping, including in-store purchase or pickup considerations.
Store code remains important
Google’s store_code attribute is required for local inventory products and must match the relevant Business Profile or store feed. Store_address does not remove the need for a stable unique store identifier. Think of store_code as the join key and store_address as location data that must be valid and consistent.
WHAT IS NOT CONFIRMED
Google’s help page does not provide a dated public launch announcement or universal compliance deadline. Do not invent one.
The page does not say every online-only product in Merchant Center requires a physical address. Scope should be evaluated against the merchant’s local inventory setup, data source and Diagnostics.
It also does not state that changing an address in one system automatically updates every connected source. Retailers should verify Business Profile, Merchant Center, feed generator, ERP/POS and store landing page separately.
WHY INDIAN MULTI-LOCATION RETAILERS SHOULD CARE
Address variation is common
Indian addresses frequently include landmarks, local abbreviations, shop numbers, floors, market names, PIN codes and alternative spellings. Human readers understand “Near Metro Gate 2”; data pipelines may not.
A clean canonical address should include the practical postal fields required by the platform and match the verified store identity. Do not stuff promotional text, directions, phone numbers or opening hours into store_address.
Franchise and dealer networks are harder
A brand may not control every dealer’s Business Profile, POS naming or landing page. If store_code belongs to one entity and the address belongs to another, product-location joins can fail or mislead customers.
Create an ownership register for each location:
- store code;
- legal or operating entity;
- verified Business Profile owner;
- canonical postal address;
- PIN code;
- landing-page URL;
- POS/ERP location ID;
- feed owner;
- last verification date.
Inventory accuracy affects trust
A valid address does not prove stock accuracy. Price, availability, product ID and store mapping must align. A customer travelling to a store for an unavailable item creates reputational cost even if the ad technically passed review.
THE DATA MODEL TO AUDIT
1. Store identity
Every physical location should have one persistent store_code. Do not reuse a code after a store closes and another opens elsewhere.
2. Canonical address
Choose one approved postal representation per store. Keep locality, city, state and PIN code consistent across Merchant Center, Business Profile and store page.
3. Product identity
Use stable product IDs. If online and local data sources join on product identifier, case, whitespace and variant mismatches can break the relationship.
4. Inventory facts
Price and availability should reflect the selected store, not national ecommerce stock. Define freshness SLA: how often POS/ERP data reaches Merchant Center and what happens during feed failure.
5. Customer-facing evidence
Store landing page should show a consistent address, current hours, contact route and location information. Avoid claiming pickup or same-day availability unless operations can fulfil it.
A PRACTICAL VALIDATION WORKFLOW
Step 1: define scope
List Merchant Center accounts using local inventory ads or free local listings in India. Separate online-only programmes. Identify primary, supplemental and local inventory data sources.
Step 2: export locations
Build a table of every store_code and the connected Business Profile. Flag blanks, duplicates, retired codes and unverified profiles.
Step 3: normalise addresses
Remove hidden characters and non-printing control characters. Google recommends UTF-8 and warns against invalid Unicode. Preserve genuine Indian characters only where supported by the actual data flow; test instead of assuming.
Check:
- spelling and PIN code;
- shop/floor/unit;
- city and state;
- commas and whitespace;
- accidental line breaks;
- landmark text;
- differences between feed and Merchant Center.
Step 4: reconcile products
For each local offer, validate product ID, store_code, store_address, price and availability. Sample high-volume and high-margin SKUs plus recently opened, relocated or renamed stores.
Step 5: submit in a controlled batch
Do not rewrite all locations immediately without rollback. Pilot one region or small store group, record the previous file, submission time and expected products.
Step 6: monitor Diagnostics
Watch item disapprovals, processing errors and local programme status. Capture before/after counts. If a product is disapproved, fix the source data rather than repeatedly editing only the Merchant Center interface.
Step 7: test customer experience
Search from relevant locations where policy and privacy allow, verify store information, click through and compare visible address, price and stock claim. Call a sample of stores to confirm fulfilment.
MERCHANT API AND AUTOMATION CONSIDERATIONS
Teams migrating from Content API to Merchant API should not hard-code an attribute merely because a spreadsheet export accepts it. Validate current API resource structure, required fields, update semantics and error responses.
Add pre-submission checks:
- address not blank;
- valid text encoding;
- one store_address value;
- store_code exists in master register;
- product ID exists;
- price and availability meet expected format;
- closed store blocked from export.
Log source record, transformation version, submission timestamp, response and retry result. A silent ETL transformation that truncates an address can create large-scale disapprovals.
Store identifiers aur location information ko consistent rakhne ke liye Google Business Profile promotion services ke scope mein Business Profile accuracy aur location-page alignment include karein.
30-DAY ACTION PLAN
Days 1–5: map Merchant Center accounts, local programmes, feed sources and owners.
Days 6–10: build canonical store register and reconcile Business Profiles.
Days 11–15: audit store_address, store_code and product joins; prioritise stores with high spend or recent changes.
Days 16–20: pilot corrections, retain rollback file and monitor processing.
Days 21–25: test customer-facing accuracy and store fulfilment.
Days 26–30: document SOP, add automated validation and schedule monthly location review.
KPIs should include eligible local products, disapproved products, feed freshness, address-error rate, store-page consistency and fulfilled local visits or pickups. Impression growth alone is not enough.
CONFIRMED FACTS VS ANALYSIS
Confirmed:
- Google’s current store_address page marks the field required for each applicable product and requires a valid postal address.
- Invalid data can cause product disapproval.
- The field is a non-repeated Unicode string.
- India is supported for local inventory ads and free local product listings.
- store_code is required for local inventory products and must match the store relationship.
Analysis:
- The most common Indian risk is inconsistent location data across feeds, Business Profiles, POS and landing pages.
- Multi-location retailers should maintain a canonical store register.
- Pilot corrections and Diagnostics monitoring reduce rollout risk.
- Address validation must be paired with price and stock accuracy to protect customer trust.
CONCLUSION
The store_address requirement is small at field level but important at customer-journey level. Local inventory only works when Google, retailer systems and the physical store agree on the location and stock.
Indian retailers should verify scope, clean the store master, submit controlled changes and watch disapprovals. Do not invent a deadline or apply the rule blindly to online-only catalogues. Treat Merchant Center Diagnostics and current official documentation as the source of truth.
Discuss Your Business Strategy
Merchant Center, store data aur local visibility ka coordinated plan chahiye? Hemant Kumar Sharma ke saath strategic digital marketing consultation explore karein. Call/WhatsApp: +91 98116 81687.
SOURCES
Google Merchant Center Help — Store address [store_address], accessed 15 October 2026:
Google Merchant Center Help — Store code [store_code], accessed 15 October 2026:
Google Merchant Center Help — Local inventory ads and free local product listings policies, accessed 15 October 2026: