Google Merchant Center for Omnichannel Retail: The Complete Guide for Physical + Online Stores

What Omnichannel GMC Actually Means

The term "omnichannel" gets thrown around loosely, but in the context of Google Merchant Center it has a specific technical meaning: you're managing both an online product feed (for Shopping ads that drive website traffic) and a local product inventory feed (for Local Inventory Ads that drive foot traffic to physical stores).

Google has been investing heavily in bridging the gap between online search and physical retail. When a shopper searches "running shoes near me" or "MacBook Air in stock," Google can show them a Local Inventory Ad that pulls your in-store inventory in near real-time. That's powerful — but only if your GMC setup supports it.

There are three distinct omnichannel scenarios, each with different GMC requirements:

Scenario	GMC Requirement	Feed Type
Online store only	Standard GMC account	Primary feed (online)
Physical store only	GMC + Google Business Profile	Local products feed + local inventory feed
Both online + physical	GMC + GBP + omnichannel setup	Primary feed + local feeds + in-store pickup config

This guide focuses on that third scenario — operating both channels and making Google understand your full inventory picture.

Linking Google Business Profile

The foundation of any local retail GMC setup is a correctly configured and verified Google Business Profile (GBP). Without it, you can't run Local Inventory Ads or access local features in GMC.

Linking Process

In Google Merchant Center, go to Settings → Linked accounts → Google Business Profile. You can link one GMC account to multiple GBP locations, which is useful if you have multiple store locations.

NAP Consistency Is a Compliance Requirement

NAP stands for Name, Address, Phone — and Google requires these to be exactly consistent between your GBP listing, your GMC account, and your website. A mismatch (e.g., "St." in GBP vs "Street" on your website, or a different suite number) can trigger misrepresentation flags because it creates ambiguity about the legitimacy of the business.

Before linking, audit your NAP across:

• Google Business Profile listings (each location)
• Your website contact page and footer
• GMC account business information
• Your domain registration

Store Hours and Real-Time Updates

Keep GBP store hours current. If Google shows a customer your Local Inventory Ad and they drive to your store to find it closed, that's a trust signal failure. During holidays or special hours, use GBP's "special hours" feature rather than changing your regular hours.

Local Inventory Ads Setup

Local Inventory Ads (LIAs) are Shopping ads that show a product's in-store availability and the address of the nearest store. They appear in Google Shopping, Google Maps, and Google Search results when a shopper's location is near one of your stores.

The Two-Feed Requirement

To run LIAs, you need two additional feeds beyond your standard online product feed:

1. Local Products Feed — contains the products available in your stores. This is a separate feed from your online feed and uses attributes like store_code instead of a landing page URL.
2. Local Inventory Feed — updates the quantity, price, and availability of each product at each store location. This feed should update frequently (daily at minimum; hourly is better for high-velocity inventory).

Required Attributes for Local Products Feed

The local products feed shares most attributes with your online feed but has key differences:

• id — product identifier (can match your online feed ID)
• title — product name
• description — product description
• gtin or mpn — product identifier (GTINs are preferred)
• brand — manufacturer brand
• price — in-store price (may differ from online price)
• image_link — product image URL

Required Attributes for Local Inventory Feed

• store_code — must match the store code in GBP exactly
• id — must match the product ID in the local products feed
• price — current in-store price
• availability — in stock, out of stock, or limited availability
• quantity — optional but recommended for accuracy

LIA Verification Step

Before LIAs go live, Google requires a store verification process. A Google representative (or partner) will visit your store to verify that the store exists, products are genuinely available, and that prices match. This is not optional and can take several weeks. Plan ahead before your target launch date.

In-Store Pickup and Curbside

In-store pickup (also called "buy online, pick up in store" or BOPIS) is one of the most valuable omnichannel features in GMC. It lets you show a "Pick up today" badge on your Shopping ads, signaling to nearby shoppers that they can get the product immediately.

Setting Up In-Store Pickup

To enable in-store pickup in GMC:

1. Ensure your GBP is linked and stores are verified
2. Go to GMC → Programs → Local Inventory Ads → In-store pickup
3. Configure pickup SLA (same-day vs. next-day)
4. Add the pickup_method and pickup_sla attributes to your local inventory feed

Pickup Attribute Values

Attribute	Accepted Values	Notes
pickup_method	buy, reserve, ship to store, not supported	Use "buy" for immediate purchase for pickup
pickup_sla	same day, next day, 2-day, 3-day, 4-day, 5-day, 6-day, multi-week	Be conservative — missing SLA kills trust

Curbside Pickup

Google supports curbside pickup through the same mechanism as in-store pickup. Use pickup_method: buy and add a note in your store details. Currently, Google does not have a separate "curbside" badge — it's displayed the same way as in-store pickup to the shopper.

Managing the Omnichannel Feed

Running three parallel feeds (online primary, local products, local inventory) creates data management complexity. Here's how to structure it without creating sync problems.

Use Shared Product IDs

Your online feed id and local products feed id don't have to match, but it's strongly recommended to keep them identical. This makes it much easier to reconcile data, troubleshoot disapprovals, and build custom labels that apply across channels.

Feed Update Frequency

• Online primary feed: Daily is typically sufficient; 2-4 hours for high-velocity inventory
• Local products feed: Weekly updates are usually fine since product data doesn't change often
• Local inventory feed: Daily minimum; hourly if you have fast-moving inventory or frequently change in-store prices

Price Differences Between Channels

Online and in-store prices are allowed to differ. In fact, many retailers run in-store-only promotions that don't apply online. Google allows this explicitly — the key is that the price shown in the LIA matches the in-store price, and the price shown in the online Shopping ad matches the website price. The two don't need to match each other.

Out-of-Stock Handling

When a product sells out in-store, update the local inventory feed with availability: out of stock as quickly as possible. Google will stop showing the LIA for that product at that store location. Leaving an out-of-stock product as "in stock" in your local feed will show shoppers a product they can't buy — a misrepresentation trigger.

Omnichannel Compliance Pitfalls

The compliance requirements for omnichannel retailers overlap significantly with standard GMC requirements — but there are additional failure modes specific to the local setup.

1. Mismatched Store Codes

The store_code in your local inventory feed must exactly match the store code in your Google Business Profile listing. A mismatch (including case sensitivity) will cause the inventory data to not associate with the correct store, and LIAs will not serve for affected locations.

2. Unverified Store Locations

Each physical store location in GBP must be individually verified before it can show LIAs. If you open a new store, submit the new GBP listing for verification immediately — verification can take 2-4 weeks.

3. Landing Page vs. Store Page Mismatch

For omnichannel ads, Google sometimes shows a product landing page with a "Check in-store availability" feature. If your website doesn't have a page for that product, or the product page doesn't match the ad, you risk disapproval. Ensure your online product catalog matches your local feed products.

4. Policy Pages Apply to Both Channels

Your return and refund policies must cover both online purchases and in-store purchases. If your in-store return policy differs from your online policy (e.g., shorter return window), you must explicitly state this. Ambiguous or missing in-store policy text is a compliance gap. See our return policy guide for requirements.

Measuring Omnichannel Performance

One of the challenges of omnichannel retail is attribution — how do you know a Local Inventory Ad drove someone to your store? Google provides several tools to measure this, though none are perfect.

Store Visit Conversions

Google Ads can estimate store visits from Shopping ad clicks using aggregated, anonymized location data from users who have opted in to location history. This appears in your Google Ads conversion column as "Store visits." It's an estimate, not an exact count, but it gives you a directional signal on the offline impact of your campaigns.

To enable store visit tracking: link your Google Ads account to GMC, and verify that each store location in GBP meets Google's minimum traffic thresholds (stores with very low traffic may not qualify for store visit measurement).

Local Actions in GMC

In Merchant Center, you can see local-specific metrics including:

• Local impressions — how often LIAs appeared for your stores
• Local clicks — clicks on LIAs
• Directions requests — shoppers who tapped "Get directions" after seeing your ad
• Calls — shoppers who called your store from the ad

Omnichannel ROAS Calculation

If you're calculating return on ad spend for omnichannel campaigns, remember to include store visit revenue — not just online conversions. A common mistake is attributing only e-commerce revenue to Shopping campaigns, which artificially depresses the apparent ROAS of LIA campaigns. Use your store's average transaction value multiplied by Google's store visit estimate to get a complete picture.

For a comprehensive account health check before launching omnichannel features, run the GMCUnbanned free scan. It flags the most common compliance issues that would prevent LIAs from going live or cause account-level problems.