Require store-level evidence before publishing local inventory

Define the product-store record

Google's local inventory specification uses product IDs and store codes to describe which stores have products, with matching product IDs across product and local inventory data. It includes required and conditional attributes. Verify current program, country and setup requirements before treating a valid-looking row as eligible to serve.

Define the unit of evidence as one sellable item at one identified store. An online inventory total is insufficient even if the same business owns the warehouse. Record which system supplies local facts and whether it measures shelf stock, available-to-promise units or another state. These distinctions matter when a displayed item is reserved, damaged or otherwise unavailable to an ordinary customer.

Validate both sides of the location join

Create a maintained mapping from the store's operational identifier to the location code used in the advertising setup. Check active, temporarily closed and relocated stores. A store-name match is fragile when several branches share a city name or a location changes its public trading name.

Validate the product mapping independently. Some point-of-sale systems use different codes for pack sizes or store-only variants. Do not solve an unknown mapping by copying the nearest online item. Test a sample with the store operator: show the exact item and configuration and ask which local record represents it. Keep unresolved product or store joins outside the approved release until the responsible owner can establish the relationship.

Choose a freshness and exception policy grounded in operations

Document the interval between a store sale, the stock system update, the local feed generation and the processed result. Then choose an internal safety policy for uncertain or stale records with the inventory owner. Do not advertise confidence that the source cannot support. A theoretical real-time connection is not evidence that every branch is connected today.

Define what happens during a store-network outage, stock count or transfer. Avoid automatically applying the last known positive state indefinitely. The right supported value depends on the current specification and the actual commercial situation. Have the owner approve the mapping of operational stock states to platform values. Keep marketing staff from reclassifying unavailable stock merely to preserve local reach.

Pilot with reconciliation rather than broad conversion

Start with stores that can supply dependable evidence and help investigate discrepancies. Reconcile a sample of submitted product-store records with current store observations and source-system facts. Include low-stock items, transfers and an intentionally unavailable item. A pilot should test failure handling as well as the easy in-stock case.

After processing, inspect the actual store association and displayed offer path. Track discrepancies by cause: bad key, stale data, incorrect stock-state mapping or program setup. Extend coverage only when the evidence supports it. Report the number of verified product-store pairs rather than claiming the whole online catalog is now locally available. This keeps the expansion tied to a promise each branch can actually honor.

Make the reasoning concrete.

A fictional bicycle retailer has an online warehouse and three shops. The marketing team proposes copying warehouse availability into every shop record to launch local listings quickly.

The team launches only the verified scope and tests low-stock and outage handling before adding stores. It does not convert online availability into local stock by assumption.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Store key

   Which active location does this code unambiguously identify?

2. Product key

   Does the local item match the same sold unit in product data?

3. Stock evidence

   Which source establishes saleable local availability?

4. Age

   How old can that evidence become and what happens then?

5. Pilot

   Which product-store cases prove both normal and exception behavior?

Watch for the wrong conclusion.

• Copying central warehouse stock into every store.
• Joining locations only by a similar display name.
• Keeping a positive stock state indefinitely during an outage.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis, not Google instructions or measured business results. Sources support only the specifically attributed platform facts. Platform controls and eligibility can change; verify current account guidance before implementation.

• Google Merchant Center: Local inventory data specification →Primary platform documentation · Supports: Supports product IDs, store codes, consistent product identity and required or conditional local inventory fields. Readiness and pilot controls are original editorial analysis.