In a significant move to unify its retail advertising ecosystem, Google has officially confirmed a structural shift in how Shopping campaigns operate. Following an initial notification sent to advertisers last week, the company announced via the Google Ads Developer Blog that Local Inventory Ads (LIA) will be enabled by default for all standard Shopping campaigns effective August 31.

This update represents a fundamental change in campaign management, effectively removing the granular control advertisers previously held over their local inventory exposure via the Google Ads API. For retail marketers and developers who rely on automated workflows to bifurcate online and offline inventory, this transition requires immediate attention to avoid potential disruption in campaign performance and inventory reporting.

The Core Change: Moving to a Universal Default

Starting August 31, the "Local products" setting will be automatically toggled to "on" for every Shopping campaign across the Google Ads platform. Previously, advertisers were required to manually configure their ShoppingSetting within the Google Ads API by setting the enable_local field to true if they wished to serve ads for products stocked in physical store locations.

This change serves as a strategic alignment between standard Shopping campaigns and Performance Max for Retail, the latter of which has already operated with local inventory enabled by default. By eliminating the opt-in requirement, Google is effectively forcing a "omnichannel-first" approach to retail advertising.

For developers, the implications are immediate. When using Google Ads API v25.1 or later, any attempt to programmatically set the enable_local field to false will result in a validation error. For those utilizing legacy versions of the API, the system will simply ignore the false value, treating it as true regardless of the input provided.

A Chronology of the Transition

The path to this mandatory update has been signaled by Google’s broader strategy of integrating local store data into the wider search and shopping experience.

• Pre-August 2024: Advertisers maintained total control over whether their Shopping campaigns showcased products available for immediate in-store pickup or browsing. This allowed for distinct bidding strategies between e-commerce-only campaigns and hybrid omnichannel campaigns.
• Late August 2024: Google began notifying account managers and developers of the upcoming deprecation of the opt-out feature.
• August 31, 2024: The enforcement date. From this point forward, the platform treats all standard Shopping campaigns as local-enabled by default.
• Post-August 31: Google’s internal algorithms will prioritize local inventory based on user proximity and stock availability, shifting the burden of control from campaign settings to inventory filtering.

Why This Matters: The Shift in Strategic Control

The removal of the enable_local disable function is not merely a technical update; it is a shift in how retail inventory is governed. Historically, many retailers maintained separate campaigns for local and online inventory to ensure that budgets were not diverted from high-margin e-commerce sales to low-conversion store visits, or vice versa.

By enabling local inventory by default, Google is signaling that it considers the physical store an inextricable component of the online shopping funnel. For advertisers, this means that their standard Shopping campaigns will now begin competing for visibility in the "Local" section of Google Shopping results, even if they have not historically prioritized that traffic.

The Impact on Campaign Architecture

Retailers who rely on strict separation between their "Online-Only" and "Brick-and-Mortar" budgets must now audit their entire account structure. If a brand has specific SKUs that are not intended for local promotion—perhaps due to exclusive online pricing or logistical constraints—they can no longer rely on the campaign-level enable_local switch to suppress these items.

Developing New Strategies: Managing Inventory Filtering

With the campaign-level toggle removed, advertisers must pivot toward more sophisticated inventory management techniques to maintain the desired level of control over their ad spend. Google is effectively forcing a migration from "Campaign-level control" to "Inventory-level filtering."

1. Feed-Based Filtering

Advertisers should now look to the Merchant Center feed as their primary control mechanism. By utilizing the shopping_ads_excluded_countries or specific custom labels, retailers can effectively hide certain products from appearing in local inventory ads without needing to disable the entire campaign’s local functionality.

2. Store Code Restrictions

For those who only want to advertise specific stores, or want to exclude certain high-traffic, low-conversion locations, managing the "Store Code" attribute within the Local Inventory Feed becomes vital. By limiting the store data submitted to Google, advertisers can implicitly control which locations the Local Inventory Ads algorithm considers for serving.

3. Implementing Inventory Filters

Within the Google Ads platform, the "Inventory filter" setting can be used to select specific subsets of products based on Brand, Category, or Custom Labels. This remains the most effective way to ensure that only the desired inventory is serving, regardless of the default "Local products" status.

Official Guidance and Developer Requirements

Google’s developer documentation is clear regarding the transition. For those building or maintaining custom scripts or automated bidding systems, the following guidelines are mandatory:

• API Versioning: Developers using v25.1 or later will receive an error if they attempt to set enable_local to false. This is a hard stop. Teams should perform a full sweep of their codebase to identify and remove these specific lines of code.
• Legacy Behavior: In versions older than v25.1, the code will remain functional in terms of execution, but the result will be ignored. This is arguably more dangerous than an error, as it could create a false sense of control in automated reports and dashboards. It is highly recommended that developers upgrade their API integrations to avoid this "silent failure."

The Scope of the Change: What Stays the Same

It is important for advertisers to understand that this change is limited specifically to standard Shopping campaigns.

Google has explicitly stated that other campaign types—including Local Campaigns (where applicable) and other supported formats—will continue to respect the enable_local field as they have in the past. If you are running campaigns outside of the standard Shopping format, your current configurations should remain unaffected.

Furthermore, this update does not impact the underlying data feeds themselves. Your Local Inventory Ads feed, your Primary feed, and your Store Feed will continue to function according to their existing upload and processing schedules. The change is purely at the campaign-delivery layer.

Implications for Retail Marketing Strategy

This shift marks a maturation of Google’s retail advertising suite. For years, the barrier between online and offline shopping was a distinct technical choice for the retailer. Google’s decision to move to an "enabled-by-default" model reflects the reality of modern consumer behavior: the "ROPO" (Research Online, Purchase Offline) effect is now the standard for a significant percentage of retail transactions.

However, for retailers with complex logistical setups—such as those with distinct pricing between their online storefront and physical outlets—this change could lead to friction. If an online price is lower than an in-store price, and a user clicks an ad that leads them to an in-store pickup option at the higher price, the risk of customer churn increases.

Key Takeaways for Advertisers:

1. Audit immediately: Review all Shopping campaigns to see which were previously set to enable_local: false.
2. Update documentation: Ensure internal SOPs for campaign setup reflect the new reality that local inventory is now an always-on feature.
3. Refine Inventory Feeds: If you need to keep certain items out of the local auction, move your control logic from the campaign level to the product/feed level immediately.
4. Monitor Performance: Watch your impression share and local store visit metrics closely in the weeks following August 31. You may see an uptick in store-related metrics that were previously suppressed, which may require a recalibration of your ROAS (Return on Ad Spend) targets.

Final Thoughts

The mandate to enable Local Inventory Ads by default is a clear signal that Google is doubling down on its "store-centric" advertising strategy. While this reduces the flexibility for some power users, it streamlines the process for the vast majority of retailers who want to maximize their reach across both digital and physical touchpoints.

For the modern marketer, the days of managing "siloed" inventory are coming to an end. The future of retail advertising on Google is inherently omnichannel, and the most successful brands will be those who adapt their data feeds and filtering strategies to match this new, integrated reality. Advertisers who fail to prepare for this change by the August 31 deadline risk losing control over their inventory exposure and potentially misallocating their ad budgets toward local placements they are not operationally prepared to support.