Google Local Inventory Ads + Performance Max Guide 2026

FeedOps recommendation

Run local inventory through Performance Max when online and store outcomes both matter.

If your goal is to maximise both ecommerce revenue and local store demand, Local Inventory Ads inside Performance Max are usually the strongest starting point. Performance Max gives Google room to use product data, local availability, audience signals, creative assets, conversion value, store goals, and location context together.

The important caveat is feed quality. Performance Max cannot compensate for a broken local inventory setup. If store codes do not match, stock is stale, pickup details are missing, prices are wrong, or products are disapproved in Merchant Center, the campaign loses the local signal it needs. Treat the feed layer as the foundation of the campaign, not a technical afterthought.

How it works

Local Inventory Ads connect product, store, and shopper context.

A standard Shopping feed tells Google what you sell online. A local inventory feed tells Google what is available at each physical location. When both feeds line up, Google can show nearby shoppers that a product is available close to them. This can appear across Google surfaces where local shopping intent is present, including Search, Shopping, Maps, local panels, and other eligible placements.

The system depends on consistent identifiers. The product ID in the local inventory feed needs to match the relevant product in the primary feed. The store code needs to match the store information Google has for that location. Price, availability, quantity, and pickup details need to reflect reality closely enough that shoppers and Google can trust the information.

Local Performance Max vs Local Inventory Ads

Many retailers still use the phrase Local Performance Max, but the current practical setup is about local inventory data working inside the broader Performance Max framework. Earlier local campaign types were more focused on promoting locations. Local Inventory Ads add the product layer: the shopper can see what is in stock, where it is available, and whether it can be collected or purchased.

This is a meaningful difference. A location ad can tell a shopper there is a store nearby. A Local Inventory Ad can tell the shopper that the exact product they want is available nearby. That product-level relevance is why the feed matters so much.

Setup

How to set up Google Local Inventory Ads for Performance Max.

Local Inventory Ads are not difficult conceptually, but they require multiple pieces of data to agree with each other. Work through setup in this order so you avoid chasing campaign performance before the feed is ready.

1. Confirm store and business data

Make sure store locations, addresses, hours, phone numbers, and store codes are accurate. Store codes are the join between your local inventory data and the physical location Google understands. If the codes are inconsistent, local availability cannot be trusted.

2. Prepare the primary product feed

The primary feed should include clean product IDs, titles, descriptions, images, prices, availability, brand, GTIN, MPN where relevant, product type, Google product category, and landing pages. This is the product context that Google uses for matching and eligibility.

3. Build the local inventory feed

The local inventory feed shows which products are available in which stores. At minimum, it needs a product ID, store code, price, and availability. Depending on your setup, it may also include quantity, sale price, pickup method, and pickup SLA.

4. Complete inventory verification

Google may require an inventory verification process to confirm that the local feed matches real in-store stock. Treat this as a trust step. If the feed says a product is available and the store cannot fulfil it, shoppers lose confidence and Google may restrict the program.

5. Enable local products in Google Ads

Once Merchant Center is ready, connect the account to Google Ads and confirm local products are eligible for the right campaigns. In Performance Max, the campaign structure, location settings, conversion goals, and product groups determine how local inventory can be used.

6. Test before scaling

Start with a controlled set of stores, product categories, or regions if the catalogue is complex. Confirm that impressions, clicks, local product visibility, pickup behaviour, and store outcomes make sense before rolling the setup across every store and SKU.

The launch checklist matters because local inventory issues can be hard to spot once campaigns are live. A campaign can spend against a subset of products while hundreds or thousands of local SKUs are quietly excluded by diagnostics, mismatched store codes, stale availability, or feed processing issues. Do the unglamorous setup work before judging campaign performance.

Validation

How to get Local Inventory Ads validated.

Local Inventory Ads need more than a feed upload. Google needs enough confidence that your submitted local availability reflects what a shopper can actually buy, reserve, or collect from a nearby store. That is why validation is one of the most important steps in the launch process.

In practical terms, validation checks whether the local inventory feed, primary product feed, store data, pickup settings, landing pages, and real store availability are consistent. Google does not want a shopper to see a product as available nearby, travel to the store, and discover that the product was never there, the price was different, or the pickup promise could not be met.

1. Make the Merchant Center account eligible first

Before focusing on local inventory validation, make sure the Merchant Center account is healthy. The primary product feed should be approved, the target country should be correct, policies should be clean, and item-level diagnostics should be manageable. If the main feed is full of product disapprovals, missing identifiers, price mismatches, or landing page issues, local inventory validation becomes much harder.

Local products inherit much of their product meaning from the primary feed. A local inventory feed can say that SKU 123 is available in store A, but Google still needs the primary product data to understand what SKU 123 is, what it costs online, what image represents it, which category it belongs to, and whether it is eligible to advertise.

2. Confirm store codes before uploading inventory

Store codes are where many launches go wrong. The store code in the local inventory feed must match the store location Google understands. If your point-of-sale system uses one location ID, your ecommerce platform uses another, and Google Business Profile has a third naming convention, create a clean mapping table before launch.

Do not treat store code mapping as a one-time admin task. Store openings, closures, relocations, franchise changes, and system migrations can all break the relationship between store data and local product data. When that relationship breaks, products may be eligible in the feed but disconnected from the physical stores they are meant to represent.

3. Submit local inventory data that can survive a real-world check

The local inventory feed should reflect the stock reality a shopper will experience. At minimum, it should use stable product IDs, correct store codes, accurate availability, and the right local price. If you include quantity, sale price, pickup method, or pickup SLA, those fields need to be governed carefully as well.

Fast-moving inventory deserves extra caution. If stock changes every few minutes but the feed updates once a day, the local inventory promise may become unreliable. For high-demand, seasonal, clearance, limited-stock, or promotional products, increase feed update frequency where possible and consider whether limited availability should be represented differently from deep stock.

4. Prepare for Google's inventory verification process

Depending on the account, country, and setup, Google may require some form of inventory verification. This can involve checking submitted product availability against store reality, reviewing sample products, confirming that prices and availability match, and verifying that pickup information is accurate. The exact process can vary, but the principle is consistent: the submitted data needs to be trustworthy.

Make validation easier by keeping a simple evidence trail. Know which system is the source of truth for product ID, stock, price, pickup promise, and store code. Keep internal screenshots or reports available for sample products. Make sure store teams know that local inventory data may be checked. If a product is submitted as in stock, someone should be able to explain where that stock status came from.

Common reasons validation fails

Validation usually fails because the feed is technically present but commercially unreliable. Common causes include stale stock, mismatched store codes, products marked as available with no real store stock, pickup promises that differ between feed and website, prices that do not match, product pages that hide local availability, and product IDs that do not match between feeds.

If validation fails, avoid making random campaign changes. Go back to the data chain. Pick a handful of products, trace them from the primary feed to the local inventory feed, then to the product page, store stock system, pickup flow, and Merchant Center diagnostics. Once a few examples are clean end to end, the broader pattern usually becomes obvious.

Shopping Ads activation

How to activate Local Inventory Ads in Standard Shopping campaigns.

Standard Shopping campaigns can still be useful for Local Inventory Ads when you want more direct control over product groups, bids, budgets, and campaign structure. Performance Max is often the broader omnichannel engine, but Standard Shopping can be a good fit for testing, tighter category control, local-only experiments, or situations where you want cleaner product-level visibility.

The activation process starts in Merchant Center, not in the campaign. Before changing campaign settings, confirm that local inventory is approved, the correct Merchant Center account is linked to Google Ads, the local inventory feed is processing, and the products you want to advertise are eligible for the local inventory destination.

1. Link Merchant Center and Google Ads

The Google Ads account must be linked to the Merchant Center account that contains the approved product and local inventory data. If you use a multi-client account or have several Merchant Center accounts for regions or brands, double-check that the campaign is pulling from the right account.

2. Use the correct Shopping campaign and product scope

In a Standard Shopping campaign, make sure the campaign is using the correct feed, country of sale, and product scope. Product groups should include the products that have local availability. If you filter the campaign by brand, product type, custom label, channel, or item ID, confirm that those filters are not accidentally excluding local products.

This is where feed labels and custom labels can help. You might isolate products with strong store coverage, high local margin, click and collect eligibility, or deep stock. A label such as local_priority, pickup_ready, high_store_coverage, or clearance_local can help you build cleaner product groups and avoid spending on local products that are not ready.

3. Target locations where stores can actually fulfil demand

Local inventory campaigns should be aligned with the physical footprint. If a campaign targets regions where you do not have stores or where local stock is thin, it can waste budget or confuse reporting. Start with locations that have reliable store inventory and enough demand to generate learning.

4. Set budgets and bids for the local objective

Budget and bidding should reflect why you are using Standard Shopping. If the goal is control, keep the structure simple enough to read. If the goal is local testing, avoid spreading budget across too many stores and product groups at once. If the goal is profitability, use product labels and local stock depth to give stronger visibility to products with a real chance of converting.

5. Check that local products are actually receiving traffic

After launch, review product group data, Merchant Center diagnostics, location performance, search terms where available, and product-level activity. Do not assume that campaign activity means local inventory is working. Confirm that eligible local products are receiving impressions, that shoppers are seeing relevant local availability, and that store or pickup outcomes are moving in the right direction.

Performance Max

Choose the campaign goal that matches the local outcome.

Performance Max can support different commercial goals. The right setup depends on whether the retailer cares most about online purchases, click and collect, store visits, or a blended omnichannel outcome. The wrong goal can make the campaign look efficient while missing the real business objective.

Use purchase value when online sales and click and collect matter most

If ecommerce revenue and pickup orders are the main outcome, optimise around purchases and conversion value. This allows Performance Max to use local availability as part of the shopping journey while still measuring revenue through online conversions. Products that are in stock nearby can become more compelling for shoppers who want speed and certainty.

Use store visits when foot traffic is the main goal

If the goal is to bring shoppers into physical stores, store visits can become a primary conversion action where available. Assign a sensible value to store visits based on average order value and in-store conversion rate. For example, if a store visit is worth roughly a quarter of an average in-store order, use that value to help bidding understand the commercial signal.

Use location groups when store strategy matters

Not every store needs the same treatment. You may want separate campaigns or asset groups for flagship stores, clearance stores, regions with different stock, or stores with different margins. Segment carefully, because too much fragmentation can reduce learning, but no segmentation can hide important local differences.

PMax activation

How to activate Local Inventory Ads in Performance Max.

Performance Max uses Merchant Center product data, local inventory signals, conversion goals, creative assets, location context, and audience signals together. To activate Local Inventory Ads properly inside PMax, the campaign needs both eligible local inventory and a campaign setup that gives Google permission and reason to use it.

The mistake to avoid is thinking that PMax activation is just a switch. The campaign can only use local inventory well when the feed layer is clean, the store layer is connected, and the campaign goal values local behaviour. Otherwise, local inventory may technically exist but contribute very little to delivery.

1. Confirm local inventory approval in Merchant Center

Start by checking Merchant Center. Local inventory data should be approved, processing successfully, and free of major item-level or account-level issues. Review diagnostics for the primary feed and the local inventory feed. Products need to be eligible as products first before PMax can use them effectively as local products.

2. Connect store data and location assets correctly

Performance Max needs reliable location information to connect local inventory to shopper intent. Make sure the right business locations, store groups, or location assets are connected to the Google Ads account. If you only want certain stores to participate, use store groups carefully and keep the store mapping clean.

For larger retailers, store groups can support regional rollouts. You may launch local inventory in one state, one city, one store format, or one group of reliable stores before expanding. That gives the team time to prove that stock, pickup, store operations, and reporting can handle the extra visibility.

3. Choose conversion goals that value the local journey

If PMax is only optimising for ecommerce purchases, it may undervalue store visits or offline outcomes. If the goal is store traffic, store visits need to be available and valued appropriately. If the goal is click and collect, purchases and pickup-related conversion value should be tracked cleanly. If the goal is omnichannel growth, use a conversion setup that reflects both online and local value without double counting.

4. Include eligible local products in listing groups

Use listing groups to confirm that local products are included. If you split PMax by product type, margin, brand, inventory depth, or priority label, make sure the local products you care about are not sitting in an excluded group. Product filters can be useful, but they can also hide a local inventory setup from the campaign.

A strong local PMax setup often uses feed labels or custom labels to guide product inclusion. For example, a retailer may prioritise products with strong store coverage, high local margin, or reliable pickup availability. Products with unstable stock, low margin, poor titles, or weak images may need feed work before they deserve campaign scale.

5. Build asset groups around real local intent

Asset groups should support the shopper journey. If the campaign promotes local availability, creative and landing pages should not feel generic. Use assets that reinforce nearby availability, store pickup, fast access, local range, or product expertise where appropriate. The feed still does much of the heavy lifting, but creative can help PMax understand and support the local proposition.

6. Watch early delivery carefully

After activation, review Merchant Center diagnostics, PMax product performance, location performance, store visits where available, click and collect orders, and product-level conversion value. Early delivery can reveal whether PMax is finding local demand or simply spending on the online parts of the catalogue.

Once the campaign is live, give the system enough data to learn, but do not leave the feed unattended. PMax may find demand patterns faster than your operations team expects. If products move quickly, store stock is thin, or pickup promises are not reliable, the campaign can expose those operational gaps quickly.

Store data

Store-level data quality determines whether local intent can be trusted.

Local Inventory Ads depend on a clean relationship between product data, store data, and inventory data. The product feed answers, "What is this item?" The local inventory feed answers, "Where is it available?" Store data answers, "Which physical location can fulfil this shopper's local intent?" If any of those answers are inconsistent, the system becomes unreliable.

Store codes are one of the most important details. They need to be consistent between Merchant Center, the local inventory feed, Google Business Profile, point-of-sale systems, ecommerce platforms, and any middleware or feed management layer. If different systems use different location IDs, create a mapping table and treat it as a controlled data asset.

Pickup and fulfilment data

Pickup settings can make local inventory more useful for shoppers. If a product is available for same-day pickup, next-day pickup, ship to store, or store pickup after transfer, the feed should reflect that accurately. Overpromising pickup speed creates poor store experiences and can undermine trust. Underusing pickup data can reduce the value of local availability for shoppers who want certainty before travelling.

For click and collect retailers, local inventory is part of the conversion experience. The ad promise, product page, checkout, collection instructions, and store fulfilment all need to agree. A shopper who clicks because a product appears available nearby should not arrive at a product page that shows a different location, unavailable status, or unclear pickup timing.

The operational side matters here. A feed can be perfectly formatted and still fail commercially if store stock is not updated often enough. High-velocity products, seasonal products, promotions, and store transfers need special attention because they create the biggest gap between what systems say and what customers experience.

Feed optimisation

Local Inventory Ads are only as good as the feed behind them.

The local feed tells Google where a product is available, but the primary Shopping feed still carries much of the product meaning. If the title is vague, the image is weak, the product type is broad, or the identifiers are missing, local availability will not fix the matching problem.

Optimise local inventory campaigns with the same feed discipline used for Google Shopping ads. Product titles should be specific and readable. Product types should reflect your real catalogue hierarchy. GTINs and brands should be accurate. Images should match variants. Price, sale price, and availability should match the product page and the store reality.

If you need a broader framework, use the Google Shopping Feed Optimization Guide. If titles are the main gap, use the Google Shopping Title Optimization Guide. For campaign structure, labels, ROAS bands, and product-level review, use the Google Shopping Ads Management Guide. If products are blocked by diagnostics, work through the relevant Google Merchant Center errors first.

Use labels to separate local products intelligently

Custom labels can help distinguish products that should be pushed locally from products that should stay online-only. For example, a retailer might label products by store availability depth, margin band, seasonal priority, clearance status, pickup eligibility, or local demand. Those labels can support Performance Max listing groups, reporting, and future campaign segmentation.

Be careful not to over-segment too early. A useful label should support a decision. If a label does not change budget, bidding, reporting, creative, feed rules, or operational priority, it may be noise. Start with labels that help answer practical questions: which local products are high margin, which are store-only, which are available across most stores, which are pickup-ready, and which are risky because stock changes too quickly.

Measurement

Measure both online performance and local store impact.

Local Inventory Ads sit between digital and physical retail, so measurement needs more than one view. Google Ads can show campaign metrics such as impressions, clicks, conversions, conversion value, ROAS, and store visits where available. Merchant Center can reveal product and feed health. Store systems can show whether local demand actually changed.

Online performance

Review conversions, conversion value, ROAS, click-through rate, and product performance. Compare products and categories with local inventory against products that are online-only. Look for stronger click and collect behaviour, better conversion rates from nearby shoppers, and products that perform differently by region.

Store visit and offline signals

Where store visit reporting is available, use it carefully. Store visits are modelled and should be interpreted with business context. Compare campaign trends with POS data, store manager feedback, pickup orders, regional revenue, and foot traffic data if available. The goal is not perfect attribution; it is enough confidence to make better budget and feed decisions.

Product-level diagnostics

Product-level reporting helps you separate feed problems from demand problems. Products with local stock but no impressions may have weak titles, missing identifiers, poor category mapping, or low demand. Products with clicks but poor outcomes may have price, pickup, landing page, or store fulfilment issues.

Measure at three levels. At the campaign level, review spend, revenue, ROAS, store visits, and conversion value. At the store or region level, review which locations are receiving local visibility and whether that matches stock, demand, and business priorities. At the product level, review which SKUs receive impressions, clicks, pickup behaviour, store visits, and sales.

If store visit data is not available or is too modelled for your needs, supplement it with practical business signals. Compare stores included in local inventory campaigns with similar stores that are not prioritised. Ask store teams whether customers are mentioning online product discovery. Review click and collect orders by store. Look at product-level pickup demand. None of these signals is perfect alone, but together they can show whether local visibility is changing shopper behaviour.

Troubleshooting

When Local Inventory Ads do not work, diagnose feed, store, and campaign layers separately.

Local Inventory Ads can fail quietly. The campaign may be active, the products may exist in Merchant Center, and the store data may look correct at a glance, yet local ads still do not show as expected. Avoid guessing. Work layer by layer so you can identify whether the issue is product eligibility, inventory data, store matching, pickup settings, or campaign structure.

No local impressions

If local products receive no impressions, first confirm Merchant Center eligibility and local inventory status. Check whether the products are approved for the right country, whether local inventory data has processed, whether store codes match, and whether the products are included in the campaign's listing groups. Then check demand and search relevance. Some products may be eligible but rarely searched for locally.

Clicks but poor store outcomes

If ads receive clicks but store results are weak, look at the shopper path. Is the product page clear about local availability? Is pickup visible? Does the store shown in the ad match the store shown on the landing page? Are stock levels accurate enough? Are store staff able to fulfil the promise? Sometimes the campaign is doing its job and the issue is fulfilment or landing page clarity.

Disapprovals or mismatches

Price and availability mismatches are common because they involve several systems: ecommerce platform, POS, local inventory feed, primary product feed, Merchant Center, and the live landing page. Find the source of truth for each field. Then check update frequency, transformation rules, variant handling, sale price logic, and out-of-stock behaviour.

Mistakes

Common Local Inventory Ads mistakes.

• Using inconsistent product IDs between the primary feed and local inventory feed.
• Letting store codes drift between POS, Merchant Center, Google Business Profile, and feed systems.
• Showing products as available when store stock is stale or unreliable.
• Missing pickup method or pickup SLA data when pickup is important to the shopper journey.
• Optimising only the campaign and ignoring weak product titles, images, product types, and identifiers.
• Using store visit goals without assigning a realistic value to offline visits.
• Rolling out every store at once before testing feed quality and local reporting.

The biggest mistake is treating local inventory as a media toggle. Local Inventory Ads are a data program before they are a campaign program. If the store-level data is wrong, Performance Max may still spend, but the shopper experience and local trust can break down quickly.

Related guides

Keep improving your Shopping feed and campaign system.

Official references

Check the Google source material before launch.

Use this guide as the practical workflow, then verify account-specific requirements against Google's official documentation before changing live feeds or campaigns.

FAQ

Google Local Inventory Ads Performance Max FAQ.