Find out which area is affected
A store page, a submitted product record and an account notice are three different observations. Write down where the issue actually appears before you change anything.
For a product issue, save the product ID and the exact notice. For a website finding, save the URL and the content you saw.
Compare records that describe the same product
Feed data and store data can only be compared for the same product, the same variant and the same target market. The date of the observation counts as well.
If the page changed recently, an older feed record may simply not be synced yet. Check synchronisation first; that alone does not show whether the cause is in the store, a mapping or the transfer.
Document what you cannot access
A review of the public website without account access cannot inspect the product data that was actually submitted.
A supplied screenshot of an account notice documents that one state. It does not replace a full data export and it says nothing about settings that are not shown.
Plan the correction and its verification together
Describe the change at the documented cause and decide in advance where you will verify it. For a data mapping, those points can be the source field, the generated record and the matching landing page.
Read those locations again after the change. Keeping the sources apart also shows which checks need access to your Merchant Center settings or submitted product data.
Sources
Official references for this article.
Next step
Read more about the related service, or write to us on WhatsApp and we talk through your situation together.