Key takeaways
- By March 2026, Google Merchant Center requires separate product IDs for items sold both online and in-store when price, availability, or condition differ; online attributes become the default record. Source
- Local Inventory Ads and any shopping-like promotions that point shoppers to physical locations will need cleaner inventory data and distinct feeds to avoid disapprovals and lost impressions. Local Inventory Ads info
- Service businesses that present bookings or in-clinic packages alongside retail SKUs must treat those offers as channel-specific products when attributes differ, or risk reduced ad reach and broken lead flow.
- Practical fixes include auditing multi-channel items, building a consistent ID and item group convention, separating online and local feeds, using supplemental feeds for fast updates, and automating inventory syncs via scheduled fetches or APIs. API reference
What changed and why it matters now
Google announced a March 2026 deadline requiring separate product IDs for multi-channel items whenever attributes such as price, availability, or condition differ between online and in-store versions. The online record will act as the default data source, and in-store variants must be created and managed as distinct entries in Merchant Center. Read the announcement
This is not a small housekeeping task. For local businesses that run Local Inventory Ads, promote in-store only offers, or sell services that can be booked online and purchased in-person at different prices, the requirement forces a more accurate mapping between what customers see in ads and what each location can deliver. If your feed strategy treats one product ID as a catch-all across channels, you will likely see disapprovals, mismatched pricing flags, and reduced eligibility for Local Inventory Ads.
Three concrete ways the rule affects local service companies
The impact extends beyond retail shelves. Service-forward businesses must think like retailers when they present packaged services in Google Shopping or Local Inventory Ads.
1. Visibility for Local Inventory Ads depends on truthful inventory
Local Inventory Ads rely on up-to-date stock and price data to decide when and where to show in-store offers. If you combine online and in-store attributes under a single ID, Google may disapprove the local offer or stop showing it in LIAs. That reduces impressions for nearby, high-intent searches and directly cuts foot traffic and walk-in conversions. Local inventory feed guidance
2. Lead flow for services that act like products becomes easier to measure or gets muddled
Many local brands model services as products in feeds: tune-ups, maintenance packages, installation appointments. When service pricing or availability differs by channel, separate IDs let you track whether bookings came from online offers or in-store promotions. Without separation, your reporting mixes channels, and you lose clarity on which promotions actually filled appointment slots or drove store visits.
3. Misaligned attributes raise the risk of disapprovals and wasted spend
If an ad lists a price or availability that the landing page or local store cannot honor, Google flags the mismatch. Repeated issues harm eligibility and can shrink your reach across Google Shopping surfaces. Clean IDs reduce that friction and keep ad spend driving valid clicks and quality leads.
How to adapt feeds and inventory workflows step by step
The businesses that meet the March 2026 deadline without scrambling are the ones that start now with a simple, repeatable workflow. The steps below are practical and grounded in tools you already have or can adopt.
Step 1: Audit every multi-channel product and service
Export your current Merchant Center catalog and your point of sale or PIM export. Include all SKUs and any services currently pushed as products. For each item, answer three questions: does the price differ by channel, does availability or stock differ by channel, and does condition differ by channel? If any of them is yes, create a channel-specific product in your plan.
Tag these items in a spreadsheet or PIM so they can be tracked during the ID migration. For services, treat the booking option and the in-store purchase as separate product-like offers when they differ on price or availability.
Step 2: Design a durable ID and item group convention
Good IDs are immutable, alphanumeric, and no more than 50 characters. Tie the IDs to internal SKUs so your operations and accounting teams can follow the same system. One recommended pattern is a base SKU plus a channel suffix, with a shared item group ID for variants.
Example pattern:
- Base SKU: 12345
- Online ID: 12345-on
- Store ID: 12345-st
- Item group ID: 12345-group
This keeps variants like size or color tied together while letting Google see distinct channel attributes.
Step 3: Separate online and local feeds and use supplemental feeds for agility
Set a primary feed listing your online offers, and a separate local products feed for in-store offers used in Local Inventory Ads. Use supplemental feeds to override specific fields, such as price, custom labels, or local availability, without rebuilding your entire primary feed. Supplemental feeds are ideal for limited-time promos or region-specific adjustments. Supplemental feeds guide
For many local service brands, this approach reduces friction when you run short-term in-clinic promotions or location-only bundles and want to push them into Local Inventory Ads quickly.
Step 4: Move from manual uploads to automation
Manual CSV updates are fragile. Use scheduled fetches from your website, direct API connections, or third-party feed platforms to reduce latency between the point of sale and Merchant Center. For complex catalogs, feed management platforms simplify the creation of multi-condition rules, bulk edits, and exclusions. Google’s developer docs explain API-based content management for higher fidelity syncs. Developers guide
Merchant Center Next offers features that can auto-detect titles, prices, and images from site content and includes AI tools that help surface missing attributes. Use these capabilities to complement strong source data rather than replace it. Merchant Center Next
Step 5: Test, measure, and iterate before the deadline
Roll changes out by product category or by region, and watch Merchant Center Diagnostics. Monitor disapprovals, price mismatches, and inventory flags and fix them before wider deployment. Track Local Inventory Ads impressions, click-to-call and store visit indicators, and booking volume split by online vs store IDs. Use that data to refine bids and smartly allocate budget to high-margin channel offers. Diagnostics guide
Practical examples for local service firms
Example 1: A flooring retailer that also books installation
The flooring itself is sold online at a set price. The in-store package includes a site survey and installation fee and has a different price. Create one product ID for the online SKU and another for the in-store package that includes the installation. Use the item group ID to tie the material variants together for reporting. That way, Local Inventory Ads show the store package only where the location can fulfill it, and the online offer remains eligible for e-commerce Shopping campaigns.
Example 2: An auto repair shop that sells parts and services
Parts sold on the website and available in-store should have distinct IDs when local pricing or stock differ. Service packages, such as a brake inspection that can be booked online but is priced differently in person, should be modeled as separate products when the channel attributes differ. Separate IDs let you see whether ad spend on parts is driving in-store sales or just generating clicks without conversions.
Example 3: Med spa with online retail and in-clinic packages
Gift cards and retail products sold online can be linked to online IDs. In-clinic bundles or limited-appointment packages with unique pricing require store IDs so Local Inventory Ads and location pages show accurate offers. Supplemental feeds are useful for time-limited package flags during promotion windows.
Tools and tactics to reduce the workload
Feed rules inside Merchant Center handle basic attribute fixes for smaller catalogs. For larger catalogs and multi-location setups, third-party feed platforms add bulk processing, mapping, and monitoring. Use supplemental feeds for localized promos and AI features in Merchant Center Next of detect missing assets. Schedule daily or hourly fetches where possible to shrink the mismatch window between actual stock and what Google sees.
What success looks like
Businesses that do this work now will avoid last-minute disapprovals and maintain Local Inventory Ads visibility during high-demand periods. Clean, channel-specific IDs give you clearer reporting, easier split testing of channel pricing, and better control over which offers drive visits and bookings. Over time, accurate feeds strengthen Google’s trust in your account and reduce friction across shopping and local surfaces.
If you want help aligning feeds with paid and organic strategies, our guidance on SEO for home improvement and on optimizing content for AI search pairs well with feed discipline, as consistent offers improve both ad and local content performance.
Checklist to start today
- Export the catalog and tag every multi-channel item
- Create a channel-aware ID convention and item group mapping
- Build separate online and local feeds and plan supplemental feed use
- Switch to scheduled fetches or API syncs where possible
- Run a pilot region and monitor diagnostics before broad rollout
FAQs
What exactly counts as a multi-channel item under the new rules
A multi-channel item is any product or service sold through more than one channel, such as an e-commerce site and a physical location. If price, availability, or condition differs by channel, you must create separate product IDs for those channel-specific versions. Source
Do I need separate product IDs when online and in-store offers are identical
If price, availability, and condition are exactly the same online and in-store, one ID can be used. Many merchants still choose to split IDs to gain clearer reporting and control, but splitting is required only when attributes differ.
What happens if I ignore the rule
Expect more product disapprovals, reduced eligibility for Local Inventory Ads, and potential account-level issues if Google detects repeated mismatches between ads and landing pages. That translates to lost visibility and wasted spend. Source
How should services and bookings be handled
Treat services that can be booked online and purchased in-clinic as separate product-like entries when their price or availability differ. Ensure landing pages and booking flows reflect the same attributes you submit to Merchant Center.
How can an agency help prepare
An experienced performance agency can audit your feeds, design an ID structure, implement separate online and local feeds, configure supplemental feeds for promos, and connect scheduled fetch or API syncs. For many local businesses that is faster and less error-prone than rebuilding feed workflows internally. See our posts about local SEO and content for companion work that improves ad performance such as FAQ content and schema and SEO for construction companies.
