Google Mandates Local Inventory Ads by Default: Strategic and Technical Implications for Retail Advertisers

Main Facts: The Sunset of Manual LIA Disabling

In a move that further consolidates its automated, omnichannel advertising ecosystem, Google has officially confirmed that Local Inventory Ads (LIA) will be enabled by default for all Shopping campaigns starting August 31st. This announcement, published on the Google Ads Developer Blog, follows preliminary notifications sent to advertisers earlier this month.

For years, search engine marketers and developers have maintained granular control over whether their Google Shopping campaigns served local brick-and-mortar inventory alongside online products. By interacting with the Google Ads API, developers could explicitly toggle local inventory settings on or off at the campaign level.

Starting August 31st, this control mechanism will be deprecated. Google is removing the ability to disable Local Inventory Ads via the campaign-level toggle. Instead, the enable_local field in a campaign’s ShoppingSetting will automatically default to true.

For retail advertisers, this represents a fundamental shift in how campaign structures, budget allocations, and inventory feeds are managed. Those who rely on keeping local and online inventory strictly separated must immediately re-evaluate their technical integrations and campaign architecture.

+-----------------------------------------------------------------------+
|                      WHAT IS CHANGING?                                |
+-----------------------------------------------------------------------+
| Old Workflow:                                                         |
| [Shopping Campaign] -> ShoppingSetting -> enable_local = false        |
| (Local products excluded from serving)                                |
+-----------------------------------------------------------------------+
| New Workflow (Post-August 31):                                        |
| [Shopping Campaign] -> ShoppingSetting -> enable_local = TRUE (Forced) |
| (To exclude local products, advertisers must use inventory filters)   |
+-----------------------------------------------------------------------+

Chronology: The Road to Omnichannel Automation

The automation of Local Inventory Ads is not an isolated update; rather, it is the latest milestone in Google’s multi-year initiative to streamline retail advertising and push merchants toward a unified, omnichannel marketing strategy.

The Rise of Local Inventory Ads (2013–2019)

Google introduced Local Inventory Ads over a decade ago to help brick-and-mortar retailers showcase real-time, in-store product availability to nearby searchers. Initially, setting up LIAs required highly complex feed configurations, separate local product inventory feeds, and rigorous store verification processes. Because of these barriers, LIAs remained an opt-in, highly specialized ad format reserved for mature retail brands with sophisticated logistics.

The Pandemic and the Omnichannel Boom (2020–2021)

The COVID-19 pandemic dramatically accelerated consumer demand for hybrid shopping experiences, such as Curbside Pickup and Buy Online, Pick Up In Store (BOPIS). In response, Google optimized its local ad formats, making it easier for businesses to highlight local fulfillment options. During this period, the division between purely digital e-commerce and physical retail began to blur, prompting Google to encourage advertisers to merge their online and offline marketing budgets.

The Performance Max Era (2022–Present)

The launch of Performance Max (PMax) for Retail marked a turning point. Unlike legacy Standard Shopping campaigns, Performance Max campaigns were designed from the ground up with a "default-on" configuration for local inventory. If an advertiser linked a Google Merchant Center account containing local feeds to a PMax campaign, Google automatically served local products to nearby users.

The August 31st Transition

With the upcoming August 31st update, Google is officially aligning its legacy Standard Shopping campaigns with the automated standards of Performance Max. By making Local Inventory Ads the default behavior across all Shopping formats, Google is effectively removing the legacy silo between online-only and local-first campaigns.

Supporting Data: Technical API Impact and System Behaviors

For developers and marketing technologists, this update introduces immediate breaking changes to how code interacts with the Google Ads API. Below is a detailed breakdown of how the API will behave across different version releases after the August 31st rollout.

API Behavior in v25.1 and Later

For development teams utilizing Google Ads API v25.1 or any subsequent versions, any attempt to programmatically write or modify the enable_local boolean field to false will result in an API exception.

Specifically, the API will reject the mutation request and return a validation error:

• Error Code: CampaignError.CANNOT_DISABLE_LOCAL_INVENTORY (or equivalent API validation error depending on the exact client library).
• Result: The campaign creation or modification transaction will fail, preventing the update from saving.

Developers must audit their codebase and remove any automated scripts, internal tools, or third-party platform integrations that attempt to pass enable_local = false to the Google Ads API.

Legacy API Behavior (Prior to v25.1)

For legacy applications running on API versions earlier than v25.1, Google will implement a silent fallback mechanism.

• If an application sends a request setting enable_local to false, the API will not throw a hard error.
• Instead, the Google Ads system will simply ignore the parameter and treat the value as true.
• The campaign will be created or updated with Local Inventory Ads enabled, regardless of the developer’s intent.

Affected vs. Unaffected Campaign Types

This update specifically targets standard Shopping campaigns. The enable_local field will continue to function normally and can still be set to false for other campaign types that support local settings, including:

• Local Services Ads
• Performance Max campaigns that do not utilize a retail feed
• Specialized display or video campaigns targeting physical locations

Strategic Workarounds: How to Prevent Local Products from Serving

While the simple binary toggle is being retired, Google is not forcing advertisers to show local inventory if they have legitimate business reasons to keep it separate. Instead, the search giant is shifting the mechanism of control from a campaign-level setting to inventory filtering.

If your marketing strategy requires certain Shopping campaigns to remain strictly online-only, you must implement one of the following two workarounds before August 31st.

+---------------------------------------------------------------------------------+
|               STRATEGIES TO EXCLUDE LOCAL INVENTORY POST-UPDATE                 |
+---------------------------------------------------------------------------------+
|  Method 1: Channel Filtering                                                    |
|  * Configure campaign product filters to only allow "Online" products.          |
|  * Prevents "Local" channel products from entering the auction.                 |
+---------------------------------------------------------------------------------+
|  Method 2: Feed Exclusions in Merchant Center                                   |
|  * Exclude local inventory feeds from the "Shopping Ads" destination.           |
|  * Ensures only your primary e-commerce feed is eligible for Shopping campaigns.|
+---------------------------------------------------------------------------------+

1. Channel-Based Product Filtering (Recommended)

The most precise way to restrict a Shopping campaign to online-only products is to use inventory filters directly within the campaign settings.

In Google Merchant Center, products are classified by their shopping channel: Online or Local. To restrict your campaign:

• Navigate to your campaign’s Product Filter settings in the Google Ads UI or via the API.
• Apply a filter that restricts the campaign to only serve products where the channel is explicitly set to Online.
• By doing this, even though the campaign technically has enable_local set to true, the internal filters will block any local store inventory from serving.

2. Merchant Center Destination Controls

Another alternative is to manage inventory distribution at the feed level within Google Merchant Center.

• If you want to completely stop local products from serving across all standard Shopping campaigns, you can navigate to the Feeds section of your Google Merchant Center account.
• Select your Local Product Feed and adjust its Destination settings.
• Uncheck Shopping Ads as an eligible destination for the local feed, or pause the local feed entirely if it is no longer required.
• This ensures that only your primary online e-commerce feed is available to feed your Google Ads campaigns.

Official Responses and Rationale: Google’s Push for Omnichannel Consolidation

According to Google’s announcement on the Google Ads Developer Blog, this change is designed to simplify campaign management and maximize performance for retail advertisers.

Google’s Stated Rationale

Google asserts that by enabling Local Inventory Ads by default, they are helping merchants capture high-intent local search queries without requiring manual, complex campaign adjustments. In their developer communication, Google highlighted that:

• Consumers increasingly search for products "near me" with the intent of buying them immediately in-store.
• Enabling LIA by default ensures merchants do not miss out on valuable local foot traffic and offline sales.
• It unifies the retail product offering, creating feature parity between legacy Shopping campaigns and modern Performance Max campaigns.

Industry Reaction and Expert Concerns

While Google frames this update as a win for simplicity and performance, the paid search community has voiced several concerns.

Digital marketing experts point out that this change removes a critical layer of financial and operational control:

• Budget Leakage: Retailers with tight physical-store margins or limited local staff may not want their digital budgets spent on driving foot traffic.
• Inventory Synchronization Issues: Maintaining accurate, real-time local inventory is notoriously difficult for mid-sized retailers. If Google serves an LIA for an item that is actually out of stock at a local store, it leads to a poor customer experience and wasted ad spend.
• Attribution Discrepancies: Online sales are easy to track and attribute. Offline store visits driven by LIAs rely on Google’s estimated store visit metrics, which some advertisers find less reliable for calculating direct return on ad spend (ROAS).

Implications: The Broader Impact on the Retail Landscape

Google’s decision to make Local Inventory Ads the default setting carries significant strategic implications for the broader retail sector.

1. The Erosion of Granular Control

This update is part of a broader, industry-wide trend toward automated, "black-box" advertising. Over the past five years, major ad platforms—led by Google and Meta—have steadily removed manual knobs and switches (such as keyword match types, manual bidding strategies, and device bid adjustments) in favor of machine-learning-driven automation.

For agency partners and in-house marketing teams, the role of the modern search marketer is shifting away from technical campaign configuration and toward data curation, feed optimization, and strategic audience targeting.

2. Increased Competition for Local Search Real Estate

As LIAs become active by default for thousands of retailers who previously had them disabled, the local search engine results page (SERP) will become highly competitive. Local bid auctions are likely to see increased CPCs (costs-per-click) as more local product listings vie for the same map pack and local shopping carousels.

3. Operational Demands on Retailers

To avoid wasting ad spend on out-of-stock local products, retailers must invest in robust inventory management systems (IMS) that can sync with Google Merchant Center multiple times a day. Retailers who cannot maintain high feed accuracy may face account suspensions or negative customer reviews if shoppers arrive at stores only to find advertised items missing from shelves.

Ultimately, advertisers have until August 31st to audit their active Google Shopping campaigns, adjust their API integrations, and implement channel-based product filters to protect their budgets and preserve their preferred campaign structures.