What is the difference between a primary feed and a local inventory feed?

A primary feed contains general product information like titles and descriptions. A local inventory feed contains store-specific data like stock levels, availability, and local pricing mapped to specific physical locations.

How often should local inventory feeds be updated?

Ideally, local inventory feeds should be updated at least daily, but for stores with high foot traffic, hourly updates are recommended to prevent stockouts and data drift.

Why are my store codes not matching in Google Merchant Center?

This usually happens because the store codes in your inventory feed do not exactly match the codes provided in your Google Business Profile. These codes are case-sensitive and must be identical.

Do I need a separate feed for every physical store?

No, you can include data for all physical stores in a single Local Product Inventory Feed by using multiple rows per SKU, with each row identifying a different store_code.

Can I show local pricing that is different from my website price?

Yes, the local inventory feed allows you to provide a 'price' attribute that overrides the primary feed's price for specific locations, enabling store-specific pricing strategies.

Mastering Local Inventory Ads (LIA): Technical Feed Guide

For omnichannel retailers, the biggest challenge isn't just selling online—it's proving that digital intent can drive physical foot traffic. Local Inventory Ads (LIA) are the primary bridge for this gap, allowing platforms like Google to show users exactly what is in stock at a store near them right now.

Unlike standard product feeds, LIA requires a sophisticated data architecture that balances static product attributes with highly volatile, location-specific inventory signals.

To succeed with LIA, you must stop treating it as a standard shopping feed and start treating it as a distributed inventory system.

1. The Multi-Feed Architecture of LIA

Standard Google Shopping relies on a single Primary Feed. In contrast, Local Inventory Ads are powered by a three-layer feed architecture.

Layer 1: The Primary (Online) Feed

This is your standard product catalog containing id, title, description, and image_link. For LIA, this serves as the "anchor" for your product data.

Layer 2: The Local Products Feed

This feed defines which products are actually eligible to be sold in physical stores. It maps your internal SKUs to the physical locations (Store IDs) registered in your Google Business Profile.

Layer 3: The Local Product Inventory Feed (The Volatility Layer)

This is the most critical and difficult layer to maintain. It contains:

store_code: The unique identifier for the physical branch.
item_id: Matching the ID in your primary feed.
quantity and availability: The real-time stock status at that specific location.
price: Localized pricing (if it differs from your online price).

2. Synchronization: The Battle Against Latency

The biggest point of failure in LIA is data drift. If a customer sees a "Limited Stock" label on a Google search result, drives to the store, and finds an empty shelf, you haven't just lost a sale—you've damaged brand trust.

Real-Time vs. Batch Updates

Most CMS systems are designed for online-only stock management. Synchronizing offline POS (Point of Sale) data with a digital feed layer requires a dedicated feed management system that can handle high-frequency delta updates.

Rule: Your Local Product Inventory Feed should be updated as frequently as your POS system allows. In high-volume retail, this often means hourly updates or even near-real-time API pushes.

3. Common LIA Anti-Patterns

Using "Online-Only" Logic for Store Data

Many retailers attempt to use their online availability status as a proxy for store stock. This fails because it ignores store-specific stockouts, "click and collect" reserved items, and shrinkage.

Neglecting Store Codes

Google identifies your physical locations via store_code. If the code in your inventory feed doesn't match the code in your Google Business Profile exactly (case-sensitivity included), your LIA will not serve.

Static Pricing

Retailers often forget that local store prices can fluctuate due to regional promotions or clearance events. If your LIA shows the national online price while the store has a different price, it can lead to Merchant Center warnings and customer frustration.

4. Optimization Signals: Beyond "In Stock"

LIA is not just about showing that you have a product; it’s about showing why the user should visit your store now.

Store Pickup (Curbside & In-Store): Use attributes like pickup_method and pickup_sla to signal convenience.
Inventory Enrichment: Supplement your local feeds with transformation rules that exclude low-margin items or items that are difficult to transport, even if they are in stock.
Proximity Bidding: While this happens in the ad platform, the signal comes from the feed. Ensure your store_code mapping is 100% accurate to allow the algorithm to favor users nearest to high-stock locations.

5. Building a Reliable LIA Pipeline

To scale LIA, you need to decouple your inventory logic from your CMS. A modern feed layer (e.g. 42feeds) acts as the orchestration point where:

Raw POS data is ingested and validated.
Store codes are mapped and normalized.
Inventory thresholds are enforced (e.g., only show "In Stock" if quantity > 2 to account for buffer).
Data is pushed to Google Merchant Center with high-frequency scheduling.

6. What Comes Next

Mastering LIA is the first step toward a true omnichannel strategy. Once your inventory feeds are stable, the next challenge is mastering supplemental feeds to add seasonal local attributes or local-only promotions.

LIA turns your physical stores into a competitive advantage against online-only giants. Treat the data as a system, and the performance will follow.

Mastering Local Inventory Ads (LIA): Connecting Digital Feeds to Physical Storefronts