Local Inventory Ads on by default Aug 31

Google has officially confirmed that Local Inventory Ads will be enabled by default for all Shopping campaigns starting August 31, 2026. The announcement follows an earlier heads-up to advertisers and was detailed on the Google Ads Developer Blog. For teams that have kept online and store inventory strictly separate, this is a hard deadline with direct impact on campaign structure, budgets, and API integrations.

What changes on August 31

Previously, advertisers had to explicitly set the enable_local field in a campaign’s ShoppingSetting to true so products from the Local Inventory Ads feed could serve. From the effective date, Google will automatically enable the “Local products” setting for every Shopping campaign. The Campaign.ShoppingSetting.enable_local field will be ignored and treated internally as true, regardless of the value submitted.

This brings Shopping campaigns closer to Performance Max for Retail, where Local Inventory Ads are already enabled by default. Google is unifying how local and digital product serving behaves and shifting control away from a simple campaign switch toward more precise inventory filtering.

• Shopping campaigns will always have Local Inventory Ads enabled.
• The enable_local field will no longer be evaluated in Shopping campaigns.
• Any submitted value will be interpreted by Google as true.

Why the change matters for marketing teams

Many retailers and agencies deliberately disabled Local Inventory Ads to keep budgets, bids, and reporting separate for online and store inventory. When local products start running automatically, click volume, conversion paths, and cost structures can shift noticeably—especially with strong local feeds, store networks, and mixed assortments.

For local SEO and local visibility, default enablement can even be beneficial: products with store availability may appear more often in local shopping results and better serve pickup intent. At the same time, uncontrolled local serving can drain online budgets or mix channels that were previously optimized separately.

Anyone whose workflows, automation scripts, or campaign frameworks rely on separating online and local inventory must update code and configuration before the rollout. Without countermeasures, mixed inventory, unclear attribution patterns, and inefficient budget control become likely.

What developers must change in the Google Ads API

Users of Google Ads API version 25.1 or later should stop trying to set enable_local to false. Such operations return the error ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT. On older API versions, existing code continues to work, but disable attempts are silently ignored and still treated as true.

In practice, checks, deployments, and CI jobs based on the old switch must be revised before August 31. Logging, validation, and campaign templates should reflect the new default state and cleanly handle forbidden write attempts.

Technical checklist before the deadline

• Review all scripts that set or read ShoppingSetting.enable_local.
• Update automated campaign creation for the new default.
• Add error handling for OPERATION_NOT_PERMITTED_FOR_CONTEXT.
• Refresh documentation and runbooks for account managers.

How local products can still be excluded

Advertisers who do not want local products to serve in specific Shopping campaigns have two alternatives. First, they can create a listing scope via CampaignCriterionService with product_channel set to ONLINE. That limits the campaign to the online channel.

Second, the inventory filter in Google Ads campaign settings can exclude local inventory and separate budgets between online and local products. Google is therefore moving control from a binary campaign flag to more granular filter and scope mechanisms.

For account structures, a clear split is advisable: campaigns focused on online demand, campaigns focused on store and pickup intent, and—where useful—mixed setups with intentionally enabled local inventory. That keeps bids, bidding strategies, and reporting understandable even after the old disable switch disappears.

What is not changing

The update applies only to Shopping campaigns. For other supported campaign types, the enable_local field continues to work as before. That includes Performance Max and Demand Gen in particular. Teams that deliberately control local inventory there do not necessarily need to change existing logic—but should check that parallel Shopping setups remain consistent.

The core logic of Local Inventory Ads also remains the same: making local product availability visible in Google’s shopping surfaces and reaching users with pickup or store intent. What is new is mainly the default and how advertisers configure exceptions.

Recommended actions for SEO and SEA teams

Teams should now check inventory feeds, store data, and product attributes for completeness. Incomplete local feeds can lead to weak relevance or unwanted serving after default enablement. A review of store codes, availability, and pricing rules is also worthwhile so local ads match the actual store assortment.

At campaign level, monitoring dashboards matter: the share of local impressions, cost per channel, store visits, and online conversions should be observable separately. Anyone who previously disabled Local Inventory Ads should define A/B-capable control groups or at least clear before-and-after measurement points to evaluate the default’s effect.

From a local SEO and online marketing perspective, the change signals that Google is pushing local product presence deeper into Shopping’s default behavior. Teams that take stores, pickup, and regional demand seriously should configure feeds and campaign filters so local visibility is used deliberately rather than allowed by accident.

Until August 31 there is still time for staging-account tests, code reviews, and account-team training. Early updates to API integrations and inventory filters prevent errors on launch day and preserve control over online versus local inventory—even though the simple enable_local switch in Shopping campaigns is going away.