Review your WebShop product feeds
A product feed supplies catalogue information to another service. A working feed address and an accepted catalogue are separate checks: review the data and the receiving service’s current requirements before relying on it.
Identify the intended feed
ShopTill-e’s existing feed addresses use the public shop address followed by /feeds/googlexml for Google product data, /feeds/facebookxml for Facebook/Instagram product data or /feeds/nearst for NearSt. Confirm the intended service and exact working address with support before connecting an account.
Review the actual output
- Confirm the intended shop and public domain.
- Open the relevant feed address and check it returns the intended catalogue, not a login, error or another shop.
- Compare representative product identifiers, titles, descriptions, links and images with the actual product pages.
- Compare price, currency and stock availability, including relevant variants and locations.
- Check brand and product identifiers such as GTIN where applicable. Keep identifiers exact.
- Check which products are included, especially inactive items, till-only products, restricted ranges and additional storefronts.
- Review the receiving service’s actual fetch result and item diagnostics after an intended connection.
Example: a bag offered in several sizes
Compare how the product and its options appear in the feed with what a customer can actually buy. Do not assume every option is supplied as a separate item or that one availability value describes every size.
If data differs
Keep the feed address, product/option reference, observed value, expected shop value and time for support. Check the receiving service’s last retrieval and error details before changing multiple product fields or repeatedly adding the same source. Do not assume a saved product change appears immediately everywhere.
Keep services distinct
Google Search Console’s sitemap is different from a product feed. Service account eligibility, catalogue approval and advertising are also separate steps; a feed alone does not activate a campaign or guarantee acceptance.
Brand and GTIN · WebShop stock visibility · Sitemap guidance.
Search ownership and sitemap setup
Use the feed fields to investigate a specific product
| Information | What to compare |
|---|---|
| Item identifier and title | Use the exact feed item reference from the receiving service’s diagnostics to identify the intended product. Do not assume two similar titles represent the same item. |
| Product link | The intended public domain and exact product page, including its available options. |
| Price and currency | The displayed feed value and the current customer-facing price for the intended choice, including relevant option additions. |
| Availability and stock quantity | A general availability label is separate from a numeric quantity where the feed supplies one. Check the required service fields and actual product/option/location stock. |
| Image, brand and identifiers | The actual image destination and appropriate product details. A placeholder image or blank field needs review against the intended catalogue and receiving service’s requirements. |
If the feed says in stock but the page differs
- Match the feed item reference and exact product link before comparing values.
- Inspect the product’s actual choice labels and stock messages. A product-level feed entry does not prove every option is available.
- Compare the relevant product/option stock, availability settings and location scope, then the feed and receiving service’s retrieval times.
- Keep the observed values, choice labels, addresses and time for support. Do not change unrelated products or repeatedly add the same feed to force a match.
Check the intended purchase journey separately. A displayed in-stock label or a generated XML file does not establish that a particular option can be bought or that a provider has accepted it.
If you want to use product data in Shopping ads
Review the catalogue and the receiving service's product issues before preparing advertising. Google Ads and Merchant Center are separate accounts; Google's current guidance requires them to be linked before creating Shopping campaigns.
- Confirm the intended business accounts and the person responsible for advertising.
- Use Google's account-linking guidance to review the available setup and account access. Check whether the proposed connection is to Merchant Center only or a wider Business Manager connection.
- Review campaign settings and budget separately before any intended launch. Supplying a feed or linking accounts is not confirmation that products are approved or advertising is running.
