Google Mandates Local Inventory Ads by Default for All Shopping Campaigns Starting August 31

Google has officially confirmed a significant structural update to its advertising ecosystem, announcing that Local Inventory Ads (LIA) will be enabled by default for all Shopping campaigns starting August 31. This move, initially communicated to advertisers through preliminary notifications and now formalized on the Google Ads Developer Blog, represents a pivot toward an omnichannel-first approach for retail marketers. By removing the manual opt-in requirement for local product promotion, Google is aligning its traditional Shopping campaigns with the automated standards already established in Performance Max for Retail.

The transition marks a departure from the long-standing workflow where advertisers had to explicitly choose to serve local inventory. Under the new mandate, the "Local products" setting will be automatically activated for every campaign categorized as a Shopping campaign. For the global retail sector, which has increasingly leaned into "buy online, pick up in store" (BOPIS) models, this change reflects Google’s broader strategy to bridge the gap between digital discovery and physical foot traffic. However, the shift also necessitates immediate technical and strategic adjustments for digital marketing departments and software developers who manage large-scale Google Ads accounts via the API.

Understanding the Core Shift in Campaign Architecture

Previously, the inclusion of local inventory within a Shopping campaign was controlled via the enable_local field within a campaign’s ShoppingSetting. Advertisers who wished to promote items available in their physical storefronts were required to set this field to true and maintain a verified Local Products Feed within the Google Merchant Center. This allowed for a clear demarcation between e-commerce-only campaigns and those designed to drive store visits.

With the August 31 rollout, Google is effectively removing this toggle for Shopping campaigns. The platform will now treat all Shopping campaigns as local-capable by default. This does not mean that local ads will serve without the necessary backend data; rather, it means that if a local feed exists and is linked to the account, the campaign will automatically begin utilizing that data to serve "near me" results and local inventory cards to users in proximity to the advertiser’s physical locations.

This change is exclusive to Shopping campaigns. Google has clarified that the enable_local field will continue to function as a manual toggle for other campaign types, including Video, Display, and Demand Gen campaigns. This distinction suggests that while Google is pushing for total omnichannel integration in its primary retail product, it is maintaining flexibility for brand-awareness and demand-generation formats where local inventory might not be the primary conversion goal.

Technical Implications for Developers and API Integration

For developers and marketing technology firms, the update introduces a strict new set of rules regarding API interactions. Those utilizing Google Ads API v25.1 or later must cease any programmatic attempts to set the enable_local field to false for Shopping campaigns. If a developer attempts to disable the setting in these newer versions of the API, the system will return a specific error, preventing the update from being processed.

For organizations still operating on API versions earlier than v25.1, the system will exhibit a "silent override" behavior. While existing code that attempts to set the field to false will technically "work" without throwing a hard error, Google’s backend will ignore the command. The system will treat the value as true regardless of the input provided by the developer. This discrepancy between API versions requires developers to audit their codebases to ensure that campaign creation and update scripts are not built on the assumption that local inventory can be toggled off at the campaign level.

Strategic Context: The Rise of Omnichannel Retail

The decision to enable Local Inventory Ads by default is not an isolated technical update but a response to shifting consumer behaviors. Data from various retail studies indicates that "Near Me" searches have seen exponential growth over the last five years. According to industry benchmarks, over 70% of shoppers who conduct a local search on their smartphone visit a related store within 24 hours. By making LIAs the default, Google is ensuring that retailers do not miss out on these high-intent shoppers simply due to a misconfigured campaign setting.

Furthermore, this move brings Shopping campaigns into parity with Performance Max (PMax). Since its launch, PMax has been Google’s flagship "all-in-one" campaign type, where local inventory is integrated from the start. By standardizing this behavior across both Shopping and PMax, Google is simplifying its product offering, making it easier for smaller retailers to compete without needing deep technical knowledge of specific ad formats.

Chronology of the Transition

The timeline for this rollout has been swift, catching some segments of the advertising community by surprise.

1. Early August: Google began sending out email notifications to high-volume advertisers and agency partners, warning of a change to the default behavior of local inventory settings.
2. Mid-August: The Google Ads Developer Blog published the technical specifications of the change, outlining the impact on API versions and specific error codes.
3. August 31: The official "Go-Live" date. From this point forward, the enable_local field is permanently set to true for all new and existing Shopping campaigns.
4. Post-August 31: Advertisers will need to monitor their "Store Visit" conversions and "Local Reach" metrics to assess how the automatic inclusion of local inventory is impacting their overall Return on Ad Spend (ROAS).

Alternative Methods for Inventory Control

While the campaign-level toggle is being deprecated, Google is not forcing advertisers to show local products if they have a legitimate business reason to avoid doing so. Instead, the company is shifting the mechanism of control from a "simple switch" to "inventory filtering."

Advertisers who wish to prevent local products from serving in specific campaigns now have two primary alternatives:

• Inventory Filtering via Custom Labels: Within the Google Merchant Center, retailers can apply custom labels to their local inventory. In the Google Ads campaign settings, they can then set filters to only include products that do not carry the "local" designation.
• Feed Selection: Advertisers can refine which feeds are associated with specific campaigns. By excluding the Local Products Feed from a specific Shopping campaign’s data source, the campaign will naturally revert to serving only online inventory.

This shift toward filtering represents a more granular, albeit more complex, way of managing ad spend. It moves the responsibility of inventory management from the campaign settings menu to the product data feed itself.

Industry Reactions and Broader Implications

The reaction from the digital marketing community has been mixed. On one hand, many performance marketers welcome the change as a way to reduce friction. "Enabling local inventory by default removes one of the many ‘hidden’ hurdles for retailers who have physical stores," noted one PPC strategist. "It ensures that the digital-to-physical loop is closed by default rather than by exception."

On the other hand, some advertisers express concern over budget liquidity. Local Inventory Ads often have different cost-per-click (CPC) structures and conversion rates compared to standard Shopping ads. By enabling them by default, Google may inadvertently shift budget toward local clicks in campaigns that were originally optimized for e-commerce volume. This could lead to a temporary dip in online ROAS as the algorithm recalibrates to account for the new mix of local and national traffic.

Additionally, the change places a premium on the accuracy of Local Product Feeds. If a retailer’s local inventory data is out of sync—showing an item as "in stock" when it is actually sold out—the automatic enablement of LIAs could lead to a poor customer experience and wasted ad spend. Retailers will now be under greater pressure to ensure their Google Merchant Center feeds are updated in near real-time.

Analysis of the Long-Term Impact

In the long term, this update is likely to accelerate the adoption of local-digital integration. As Google continues to compete with Amazon for product search dominance, its primary advantage remains its map integration and its ability to drive traffic to physical stores—something Amazon is only beginning to explore through its physical footprints like Whole Foods and Amazon Fresh.

By making local inventory the "standard" rather than the "option," Google is reinforcing its position as the essential utility for the "phygital" (physical + digital) shopper. For the advertiser, the message is clear: the distinction between an online customer and an in-store customer is disappearing. Campaigns must now be built with the assumption that the consumer is mobile, local, and looking for immediate fulfillment.

As August 31 approaches, the "bottom line" for advertisers is one of preparation. Those relying on legacy campaign structures or specific API workflows must act immediately to update their integrations. While the removal of a setting might seem like a minor UI update, it represents a fundamental change in how Google views the retail journey—shifting from a world of siloed channels to a unified, inventory-driven ecosystem.