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

In a move that signals a significant shift toward a unified omnichannel retail strategy, Google has officially confirmed that Local Inventory Ads (LIA) will be enabled by default for all Shopping campaigns beginning August 31. This update, recently detailed on the Google Ads Developer Blog, follows a preliminary notification sent to advertisers last week. The transition represents a fundamental change in how Google handles product visibility, moving away from a system where advertisers had to manually opt-in to local store promotions and toward a model where local availability is an intrinsic component of the Shopping experience.

For years, Google Shopping campaigns functioned primarily as a vehicle for e-commerce, driving traffic to online storefronts. Local Inventory Ads were treated as a specialized add-on, requiring specific configuration and a dedicated local products feed. By making LIA the default setting, Google is effectively removing the barrier between digital browsing and physical foot traffic, forcing a convergence that aligns with modern consumer behavior. This change ensures that if a retailer has local inventory data connected to their Merchant Center, that data will automatically be eligible to serve alongside online offers in standard Shopping campaigns.

Technical Specifications and API Transitions

The technical implementation of this change centers on the Google Ads API and how it handles campaign settings. Previously, advertisers and developers managed local product visibility through the enable_local field within a campaign’s ShoppingSetting. To serve products from a Local Inventory Ads feed, this field had to be explicitly set to true. Under the new mandate, Google will automatically toggle this setting to true for every Shopping campaign across the platform.

The implications for developers are immediate and require proactive code adjustments. According to Google’s technical guidance, developers utilizing Google Ads API version 25.1 or later must cease any attempts to programmatically set the enable_local field to false. Doing so after the August 31 deadline will trigger an API error, potentially disrupting automated campaign creation or management workflows. For those operating on API versions earlier than v25.1, the system will not return an error; however, any command to disable local inventory will be silently ignored, and the platform will treat the value as true regardless of the input.

This shift in API logic underscores Google’s desire to streamline its retail offerings. By standardizing the "Local products" setting, Google is bringing Shopping campaigns into parity with Performance Max for Retail. In Performance Max—Google’s AI-driven, cross-channel campaign type—Local Inventory Ads have been enabled by default since the product’s inception. This latest move suggests that Google is looking to harmonize its legacy campaign types with its newer, more automated systems, reducing the fragmentation of settings that can often lead to inconsistent performance across different campaign formats.

The Evolution of the Omnichannel Shopper

To understand why Google is making this change, one must look at the broader context of retail trends over the last five years. The concept of "omnichannel" retailing—the seamless integration of online and offline shopping experiences—has moved from a buzzword to a survival necessity. Data from various industry reports indicates that the modern consumer journey is rarely linear. A shopper might research a product on their smartphone while commuting, check local availability during their lunch break, and ultimately visit a physical store to make the purchase that evening.

Internal Google data has long supported this trend. Searches for "near me" and "available near me" have seen exponential growth, particularly in categories like home improvement, electronics, and apparel. Furthermore, industry statistics suggest that approximately 76% of people who search on their smartphone for something nearby visit a related business within a day, and 28% of those searches result in a purchase. By enabling Local Inventory Ads by default, Google is positioning itself to capture the full value of these high-intent searches, ensuring that retailers do not miss out on local conversion opportunities simply because of a misconfigured campaign setting.

The "Buy Online, Pick Up In-Store" (BOPIS) phenomenon, which accelerated during the global pandemic, has also played a crucial role in this transition. Consumers now expect to see real-time inventory levels before they commit to a store visit. Local Inventory Ads facilitate this by displaying a "store pickup" link or showing the distance to the nearest location directly within the search result. By mandating this feature, Google is essentially forcing retailers to adopt a more transparent and responsive inventory management style, which benefits the end-user and, by extension, the health of the Google search ecosystem.

Strategic Adjustments for Advertisers

While the change is designed to maximize visibility, it presents a challenge for advertisers who have historically kept their local and online inventory budgets separate. For some large-scale retailers, the decision to keep local inventory out of certain Shopping campaigns was a deliberate strategic choice, often dictated by different profit margins between online and in-store sales or specific regional marketing goals.

With the August 31 deadline approaching, advertisers who wish to prevent local products from serving in specific campaigns can no longer rely on a simple toggle switch. Instead, Google is shifting control toward inventory filtering. There are now two primary methods to manage local product distribution:

1. Inventory Filtering via Campaign Settings: Advertisers can use "Inventory Filters" within the campaign configuration to exclude local products. This requires setting specific criteria based on product attributes (such as brand, condition, or custom labels) that distinguish local inventory from online-only inventory.
2. Merchant Center Feed Management: Advertisers can choose to remove the local products feed from the Merchant Center entirely if they do not wish to participate in LIA across any campaigns. Alternatively, they can adjust the "Included Destinations" attribute within the feed itself to exclude "Local Inventory Ads" for specific items.

This shift represents a transition from "campaign-level control" to "data-level control." It requires a more sophisticated understanding of feed management and product labeling. Advertisers who fail to update their strategies may find their budgets being consumed by local clicks that they had not accounted for in their original projections.

Chronology of the Rollout and Industry Response

The road to this mandatory update has been marked by several incremental steps. Over the past year, Google has been nudging advertisers toward local integration through recommendations in the Google Ads "Optimization Score" section. These recommendations often highlighted the potential "uplift" in store visits that could be achieved by enabling LIA.

The official timeline for the current mandate began in mid-July 2024, when Google started sending out email notifications to agency partners and high-spend retail accounts. These communications were followed by the formal announcement on the Google Ads Developer Blog in late July, providing the technical community with roughly six weeks to prepare.

Industry reactions have been mixed. Digital marketing agencies have generally welcomed the move as a way to simplify campaign setup, noting that many clients often forget to enable LIA despite having the necessary data feeds. However, some performance marketers have expressed concerns regarding "forced automation." The primary critique is that by removing the ability to disable LIA at the campaign level, Google is taking away a layer of granular control that is vital for managing complex account structures where local and online teams operate with separate P&L (Profit and Loss) statements.

Analysis of Broader Implications

The decision to enable Local Inventory Ads by default is not an isolated event; it is part of a broader competitive strategy. Google is currently locked in a fierce battle for retail dominance with Amazon and, increasingly, Walmart. Both Amazon and Walmart have invested heavily in their own retail media networks, offering advertisers deep integration with their logistics and physical storefront data.

By mandating LIA, Google is leveraging its greatest asset—the Search engine—to act as a digital storefront for the entire physical world. This move makes Google Shopping more competitive against Amazon by highlighting the one thing Amazon often cannot provide: immediate, same-day physical gratification through a local pickup.

Furthermore, this change has significant implications for small and medium-sized businesses (SMBs). For an SMB with a single physical location, the default enablement of LIA could be a major boon, automatically putting their local stock in front of nearby customers without requiring deep technical expertise. Conversely, for large enterprises with thousands of locations, the change necessitates a rigorous audit of their data feeds to ensure that the "local" traffic being generated is actually profitable and manageable by the individual store branches.

It is also important to note what is not changing. The August 31 update applies specifically to Shopping campaigns. Other campaign types that support local inventory, such as Demand Gen and Video campaigns, will maintain the existing functionality of the enable_local field. This suggests that Google is prioritizing the "high-intent" Shopping surface for this mandatory transition while allowing more experimental or awareness-based campaign types to remain flexible.

Final Preparations for the August 31 Deadline

As the deadline approaches, the "bottom line" for advertisers is clear: Local Inventory Ads will become a standard feature of the Shopping campaign architecture. To avoid disruption, businesses must take the following steps:

• Audit API Integrations: Developers must update their code to remove any logic that attempts to set enable_local to false for Shopping campaigns.
• Review Feed Attributes: Retailers should examine their Merchant Center feeds to ensure that local inventory data is accurate and that "Included Destinations" are correctly mapped.
• Implement Inventory Filters: If certain campaigns must remain online-only, marketing teams need to set up custom filters based on product attributes to exclude local offers.
• Re-evaluate Budget Allocation: With the expected increase in local-intent clicks, advertisers should monitor their spend closely in the first weeks of September to ensure that budget is being distributed effectively between online and local conversion goals.

Google’s shift to a "local-by-default" model reflects the reality of the modern marketplace. In an era where the distinction between a "web user" and a "foot traffic customer" has all but vanished, the advertising tools used to reach them are finally following suit. While the loss of a manual toggle may frustrate some proponents of granular control, the long-term trajectory points toward a more integrated, data-rich, and ultimately more effective retail advertising ecosystem.