Keep Store Product Data Consistent With Google Merchant Center

Updated 5 November 2026 · Standard formula, shown below

Keeping product data consistent between your online store and Google Merchant Center helps prevent mismatched listings, disapprovals, and outdated prices or availability in Shopping results. You’ll need to identify which system supplies each product detail, then set up a reliable feed or integration and routinely check that Google receives the same current information customers see in your store.

What You’ll Need

Access to your store’s product catalog and its feed or Merchant Center integration settings.
Access to the relevant Google Merchant Center account and product diagnostics.
A product identifier for matching items, preferably a unique SKU or offer ID, plus GTINs and brand details where applicable.
A list of the countries, languages, currencies, and destinations where you sell.

Step-by-Step

Choose the source of truth. Decide where staff should make each change. For most stores, the product catalog is the authoritative source for title, description, price, availability, image, and identifiers; Merchant Center receives those details through a feed or integration. Avoid maintaining the same field independently in both places unless you have a documented reason. Record who owns product updates and how quickly they must be published.
Check how products reach Merchant Center. In Merchant Center, review the product data sources or feed settings and identify whether products arrive through a scheduled feed, an app or platform integration, an API, or another supported method. Check the source’s last update and processing status. If several sources submit the same products, determine which one supplies each field; overlapping sources can cause unexpected values.
Set stable product identifiers. Give every distinct item or variant a consistent offer ID, such as a SKU that does not change between feed updates. Keep variant IDs distinct while using the correct shared group identifier where variants belong together. Submit accurate GTIN and brand information when the product has them. Do not invent identifiers or reuse one item’s GTIN for another. For custom or unbranded goods, follow Google’s current identifier guidance rather than filling fields with guesses.
Map store fields to the required product attributes. Review the feed mapping for title, description, link, image link, price, availability, condition, shipping, and any category-specific attributes. Confirm values use the right format and match the item on its landing page. For example, a variant’s feed link should lead to that variant, and a sale price should be shown clearly on the page. Use the attribute requirements for your target country and product type; not every attribute is required for every item.
Make price and availability updates promptly. Synchronize price and stock changes whenever they happen, not just during occasional catalog exports. Use a suitable scheduled fetch or integration frequency, and confirm it is frequent enough for your rate of change. If the store supports automatic updates for price or availability, treat them as a backup, not a substitute for a working data source. Check that the feed and product page agree, including currency, sale dates, and whether an item can actually be purchased.
Align shipping, tax, and market settings. Ensure shipping information in Merchant Center is compatible with what shoppers see at checkout, and configure relevant country and currency settings consistently. Tax handling varies by market, so follow the applicable Merchant Center fields and local store setup rather than copying settings from another country. Make sure each source targets the intended country and language and that landing pages serve the same market.
Validate a small sample before relying on the full feed. Compare several products in the store with their processed Merchant Center records. Include a variant, a sale item, an out-of-stock item, and a product with special attributes if you sell them. Check the identifiers, title, URL, image, price, availability, and shipping details. Correct mapping or catalog problems at their source, then submit or wait for a fresh update and verify the processed result.
Monitor diagnostics and keep a change routine. Review Merchant Center’s product diagnostics and data-source status after changes, feed updates, and policy notices. Address disapprovals and warnings, then confirm the affected items are processed again. Keep a simple log of feed changes, owners, and update times. Periodically check a selection of live product pages against Merchant Center, especially after a store redesign, pricing change, or integration update.

Common Mistakes

Updating only one side: A price changed in the store may remain stale in Merchant Center until the next successful update. Fix the source or schedule, then confirm the new value was processed.
Using inconsistent IDs: Changing offer IDs between uploads can make matching and update history unreliable. Keep IDs stable and unique for the product or variant.
Guessing identifiers: A made-up GTIN or incorrect brand can trigger item issues. Omit optional identifiers when appropriate and follow current attribute guidance.
Sending different landing-page details: A feed price, selected variant, or availability that contradicts the page can lead to a mismatch. Check the customer-facing page, not just the catalog export.
Overlapping data sources: Multiple feeds or integrations may overwrite fields or create duplicates. Document source ownership and remove or correct redundant submissions.
Ignoring processing time: A submitted feed is not necessarily processed immediately. Check fetch and processing status before assuming a change failed.

Tips

Use a test or small product group when changing mappings, if your platform supports it.
Automate catalog changes at the point they occur, especially inventory and price updates.
Use consistent formatting and keep product titles descriptive and accurate; do not add promotional claims that are absent from the page.
Keep a record of field mappings, feed schedules, target markets, and who can edit each system.
Recheck representative products after app updates, theme changes, bulk imports, or changes to variant handling.

Troubleshooting

A price or stock value is wrong: Compare the store’s current product record, the submitted source, and the processed Merchant Center value. Check whether another feed or integration is overriding it, then correct the authoritative source and trigger or wait for a new update. Verify the live landing page shows the same purchasable option and value.

Products are missing or not updating: Check the data source’s last fetch, upload or API status, processing messages, and target country or language. Confirm the affected items are included in the submitted file and that IDs are valid. Resolve source errors, resubmit, and check diagnostics again after processing.

An item is disapproved for a mismatch or identifier issue: Open the item’s diagnostic details to see the reported attribute. Compare that field with the product page and catalog, correct the source, and provide valid identifiers where applicable. Do not repeatedly change unrelated fields; wait for the corrected data to be processed and review the item status.

Duplicate or conflicting products appear: Compare offer IDs and the sources submitting the items. Remove redundant submissions or align the IDs and source configuration, taking care not to delete the only valid listing. If the cause is unclear, use the source’s processing report and Merchant Center diagnostics to narrow it down.

Frequently Asked Questions

Should I edit products in my store or Merchant Center?
Usually, edit the store catalog and let its feed or integration send the update. Use Merchant Center settings for feed configuration and fields that are intentionally managed there.

How often should my product feed update?
Often enough to reflect changes before shoppers encounter outdated information. Stores with frequent price or inventory changes need more frequent synchronization than catalogs that rarely change; check your source’s schedule and processing status.

Do I need a GTIN for every product?
No. Submit a valid GTIN when one exists and is applicable. Do not make one up; follow Google’s current guidance for products without standard identifiers.

Can I use more than one data source?
Yes, but configure sources carefully so they do not submit duplicate items or contradict one another. Know which source controls each attribute and keep matching IDs consistent.

Why does Merchant Center show a different value from my store?
The feed may be stale, a different source may be overriding the field, or the landing page may show a different variant, currency, price, or availability. Compare the source data, processed item, and live page.

How can I confirm a fix worked?
Check that the source update succeeded, review the processed item and diagnostics, and compare it with the live product page. Allow for processing time before judging the result.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.