Reconcile Online Product Pages With Store Pickup Promises Before Advertising Local Stock

The product page and the feed must tell the same story

A retailer can send store-level availability data to Merchant Center while its product page or checkout flow displays a different pickup promise. Customers may see an item as available at one branch but discover at checkout that pickup is unavailable, delayed or tied to a different store. Feed correctness and customer promise correctness need separate checks.

Google Merchant Center documents local inventory data requirements and, for certain pickup methods, conditions involving product pages or checkout flows that show store pickup options and timing. See local inventory data upload guidance and store code requirements. Eligibility and requirements vary by method and destination.

Test the promise from search to confirmation

Choose a sample of products and branches that includes high sellers, low-stock items, products unavailable in some stores and pickup options with different lead times. For each test, capture:

1. Product and variant ID.
2. Branch selected by the customer.
3. Availability shown on the product page.
4. Pickup method and promised date.
5. Availability at checkout.
6. Final order confirmation and fulfilment branch.

The expected result is not simply “the page loads.” It is that the customer can complete the action under the stated conditions, or receives a clear explanation when the promise changes.

Define the source of truth by field

Inventory systems may own quantity; ecommerce may own pickup eligibility; store operations may own opening windows; Merchant Center may receive a transformed feed. Document which system owns each field and how often it updates. A feed should not be treated as authoritative if it is generated from stale or partial data.

Edge cases worth testing

• Quantity drops to zero between product view and checkout.
• The branch accepts pickup only after a preparation window.
• The customer changes from delivery to pickup.
• Two variants share a product family but have different stock.
• A branch is open but not participating in pickup.
• An order is transferred to another store after placement.

Record whether the behaviour is expected, disclosed and reflected in the relevant data source. Do not publish a precise pickup promise unless the operating process can support it.

Reconciliation cadence

Compare feed snapshots with checkout outcomes and cancellation reasons. Group defects by root cause: product ID mapping, store-code mismatch, stale quantity, pickup rule, or UI state. Fix the upstream rule rather than patching one product row at a time.

Rollback criteria

If a feed or website release creates widespread false availability, pause the affected product/store combinations or destination according to the approved commerce process. Keep unaffected branches running where the platform allows precise control. Restore only after a known-good test passes.

Distinction from profile management

A Google Business Profile helps represent the physical business location; it does not automatically guarantee that a specific SKU is in stock. Local inventory and pickup features have separate Merchant Center requirements. Keep the branch listing, product feed and checkout promise connected but do not treat them as one system.

Sources

• How to upload your local inventory data to Merchant Center — Local inventory data attributes and upload options.
• Store code [store_code] — Store code format and matching requirements.
• In-store inventory automatically added from your online shop to Merchant Center — Automatic inventory feed limitations and requirements.