Local inventory ads extend standard product listing ads with real-time stock information from a retailer's physical stores, letting a shopper searching nearby see not just that a product exists, but that a specific store around the corner currently has it in stock. Instead of driving traffic only toward an online checkout, local inventory ads are built to pull shoppers into a physical location, making them one of the few ad formats designed explicitly to connect online search intent with offline retail. They run on a separate local feed layered on top of the standard feed, refreshed often enough that an "in stock nearby" claim stays true by the time a shopper walks in.

Why it matters for feed management and e-commerce

Retailers with brick-and-mortar locations lose a meaningful share of nearby foot traffic to competitors simply because online search doesn't surface what's on the shelf around the corner. Local inventory ads close that gap, but only if the underlying local feed is genuinely kept in sync with store systems — a feed reporting stock that sold out that morning damages trust in the exact moment a shopper is deciding whether to drive over. Because these ads live and die on freshness, they push retailers toward tighter integration between their inventory management systems and their ad feeds than standard online-only listings typically require, since a stale local feed doesn't just cost a sale, it sends a shopper to a store for nothing.

How it works

Local inventory ads require two things layered together: a standard product listing ad feed and a separate local feed reporting per-store fields like store code, quantity on hand, and pickup method, both submitted through Google's retail tools. Google matches a shopper's location against the nearest stores carrying the searched product using geotargeting, then displays store name, distance, and stock status alongside the usual product details. Because the format depends on a store-level feed refreshing frequently — often multiple times a day — retailers typically automate the sync directly from their point-of-sale or inventory system rather than updating it by hand, since any lag between a sale ringing up in-store and the feed reflecting it directly undermines the format's core promise.

Example

<item>
  <store_code>STORE-014</store_code>
  <id>SKU-29187</id>
  <quantity>6</quantity>
  <price>54.00 USD</price>
  <pickup_method>buy</pickup_method>
  <pickup_sla>same day</pickup_sla>
</item>

This row exists in the local feed alongside — not instead of — the main product feed entry for SKU-29187; store_code ties it to a specific physical location, and quantity is the field that has to stay current or the ad promises stock that isn't actually there. Our case study on how Bilyoner ran catalog ads for the first time and lifted ROAS 49% shows how a retailer stood up this kind of feed structure from scratch.

Related Concepts

Local inventory ads are really product listing ads with a store-aware layer added on top, matched to shoppers through geotargeting and kept honest by tight inventory management discipline — remove any one of those three and the format stops delivering what it promises.