In a move that signals a significant evolution in how retail advertisers manage their omnichannel presence, Google has officially announced that Local Inventory Ads (LIA) will be enabled by default across all standard Shopping campaigns starting August 31. This update, confirmed via the Google Ads Developer Blog, effectively removes the ability for advertisers to opt out of local inventory integration through the standard API settings. For digital marketers and inventory managers, this represents more than just a software update; it is a fundamental shift in how Google expects retailers to bridge the gap between their digital storefronts and physical brick-and-mortar locations. By mandating that local inventory be accessible to all Shopping campaigns, Google is pushing the retail ecosystem toward a more unified, "phygital" (physical-digital) advertising experience. Main Facts: The End of the "Opt-Out" Era The core of this announcement is the deprecation of the enable_local field within the ShoppingSetting of the Google Ads API. Historically, this boolean field allowed advertisers to explicitly toggle their local inventory feeds on or off, granting granular control over whether a campaign served ads based on local stock levels. Starting August 31, the enable_local field will essentially become a legacy setting. For all new and existing Shopping campaigns, Google will automatically set this value to true. Attempts to manually set this value to false via the API will either trigger an error in newer versions (v25.1 and later) or be silently ignored by the system, which will proceed to treat the campaign as if it were enabled. This alignment brings standard Shopping campaigns into parity with Performance Max (PMax) for Retail, where local inventory integration has been a mandatory, non-configurable feature since the product’s inception. Chronology: The Road to Universal Local Integration The transition toward this mandatory integration has been brewing for several quarters as Google refined its automated bidding and inventory management tools. Pre-2024: Advertisers maintained a strict separation between online-only campaigns and local-inventory-enabled campaigns to manage ROAS (Return on Ad Spend) and inventory discrepancies. Performance Max Adoption: With the aggressive rollout of Performance Max for Retail, Google socialized the concept of a unified "Inventory" approach, where the distinction between online and local stock was blurred to maximize conversion opportunities. Mid-August 2026: Google began issuing formal notifications to API developers and stakeholders, warning of the impending change and providing technical documentation on how to handle the transition. August 31, 2026 (The Effective Date): The automatic enforcement begins. Any campaign structure that relied on the manual disabling of local inventory will be forced into the new default behavior. Why This Matters: Implications for Retailers For the average e-commerce manager, this change may seem minor, but it carries profound implications for campaign management and inventory strategy. 1. Loss of Granular Control Many retailers have historically separated their campaigns to prevent local inventory from cannibalizing online sales or to account for regional pricing discrepancies. If a retailer’s local fulfillment centers have higher costs or different tax structures, they might have previously preferred to keep those inventory streams separate. Advertisers must now accept that all campaigns will consider both online and local data points when Google’s algorithms bid for auction placement. 2. The Shift to Inventory Filtering Google is explicitly moving the point of control from "campaign settings" to "inventory filtering." Advertisers who do not want certain products appearing in local ads can no longer just flip a switch at the campaign level. Instead, they must implement more sophisticated feed management, utilizing inventory filters or custom labels to exclude specific items or locations from their Shopping feeds. 3. API Workflow Disruptions Developers and agencies managing custom automated bid management systems or campaign creation scripts must audit their codebases. In versions of the API prior to v25.1, the code may continue to run without crashing, but the behavior will change, potentially leading to "ghost" inventory appearing in campaigns that the manager thought were online-only. Technical Guidance for Developers For those managing Google Ads integrations, the transition requires proactive maintenance. Developers using API v25.1 or later must stop calling the enable_local field with a false value. Attempting to do so will result in an INVALID_ARGUMENT or similar configuration error. For legacy systems that cannot be updated immediately, Google has confirmed that the backend will ignore the false command. While this prevents a complete system failure, it creates a "black box" scenario where the API reporting and the actual ad serving behavior might diverge. It is highly recommended that all technical teams prioritize updating their campaign creation logic to align with the new reality before the August 31 deadline. How to Manage Inventory Post-Update With the manual toggle gone, advertisers are left with two primary levers to control their local inventory presence: Inventory Filtering: Advertisers can utilize inventory filters within their campaign settings to limit the scope of their Shopping ads. By filtering based on specific product attributes (such as brand, product_type, or custom_label), retailers can ensure that only the desired subset of products is eligible for local bidding. Feed-Level Exclusions: If a specific location or SKU is problematic for local ad serving, the most effective method is to adjust the feed data itself. By setting the excluded_destination attribute to Local_Inventory_Ads for specific items, advertisers can ensure those products are removed from local consideration regardless of the campaign settings. Official Perspective and Industry Impact Google’s rationale for this change is rooted in the "omnichannel" consumer journey. Data suggests that consumers increasingly interact with ads that bridge the gap between mobile search and physical store visits. By mandating LIA across all campaigns, Google is ensuring that retailers capture users who are looking for immediate product availability. "This change is a clear indicator that Google wants to move away from the fragmented management of inventory," says Anu Adegbola, Paid Media Editor at Search Engine Land. "The platform is betting on the idea that more data—specifically real-time, local stock data—leads to better machine learning outcomes and, ultimately, more sales for the retailer." However, this does place an increased burden on retailers to keep their local inventory feeds accurate. If a retailer’s POS (Point of Sale) system is not perfectly synced with their Merchant Center, the new default settings could lead to ads promoting out-of-stock items, resulting in wasted ad spend and poor customer experiences. Conclusion: Preparing for the Future The move to enable Local Inventory Ads by default is a harbinger of a more automated, less manual future in search marketing. As Google continues to deprecate granular manual controls in favor of algorithmic efficiency, retailers must pivot their focus toward data hygiene and feed optimization. Advertisers who rely on complex, segmented campaign structures should use the remaining time before August 31 to conduct a thorough audit of their Google Ads accounts. They must identify any campaigns currently disabling local inventory and devise a strategy to manage that inventory through filtering or feed-level adjustments. While the change reduces the "overhead" of managing campaign settings, it increases the importance of data accuracy. In the modern Google Ads landscape, your campaign performance is only as good as the feed you provide. As the industry moves toward August 31, the retailers who will succeed are those who treat their product feeds as a strategic asset rather than a background technical necessity. Search Engine Land is owned by Semrush. We remain committed to providing high-quality coverage of marketing topics. Unless otherwise noted, this page’s content was written by either an employee or a paid contractor of Semrush Inc. Post navigation The Ethics of Ambiguity: Why PPC Reporting Requires More Than Just Data