# How to connect a product feed to Google Shopping or a marketplace

> A poorly structured product feed rarely produces an error you can see straight away: products simply get rejected or silently de-indexed by Google or the marketplace. How reliably the feed stays current matters as much as building it in the first place.

- Source canonique : [https://allaux.fr/en/guides/connecter-flux-produits](https://allaux.fr/en/guides/connecter-flux-produits)
- Langue : EN
- Dernière mise à jour : 2026-09-30

## Direct answer

> A product feed is a CSV or XML file, generated automatically on a regular schedule, listing each product with its required attributes (ID, title, price, availability, image). It must stay in sync with the real catalogue to avoid rejections and outdated listings.

## Setting up a reliable feed

1. **Choose the expected format** — Google Merchant Center accepts a CSV or XML feed structured to its specifications; each marketplace generally imposes its own format and its own specific required fields.
2. **Generate the feed from the store** — On both PrestaShop and WooCommerce, a dedicated module or extension generates the feed from the existing catalogue, mapping internal fields (name, price, reference) to the fields expected by the destination.
3. **Fill in the required attributes** — Unique ID, title, description, product link, image, availability, price and category are the most commonly required fields; missing or incorrectly formatted values are the leading cause of rejection.
4. **Schedule automatic regeneration** — The feed must regenerate on a regular schedule, without manual intervention, to reflect stock and price changes. A daily frequency is a common minimum for an active catalogue.
5. **Monitor rejections** — Google Merchant Center and most marketplaces report rejected products with the exact reason; fixing them one by one at first makes it possible to identify recurring errors that need addressing at the source.

## The most common rejections

Most rejections come from inconsistencies between the feed and the actual product listing: a different price in the feed versus the product page, a missing or low-resolution image, or availability shown as "in stock" when the product is actually sold out on the site. These inconsistencies are detected automatically and lead to a rejection, or account suspension if they recur.

Product categorisation is another frequent source of error: Google imposes a precise category taxonomy (Google Product Category), distinct from the store's internal categories, which must be mapped explicitly rather than left blank or misassigned.

Finally, a feed generated once and never regenerated eventually drifts from the real catalogue: a product withdrawn from sale keeps appearing in results, which harms the user experience and the destination platform's trust in the feed.

## The feed doesn't replace account monitoring

> A technically valid feed alone doesn't guarantee product visibility: Google Merchant Center and marketplaces also enforce their own compliance rules (commercial policies, return conditions, legal notices), which can suspend an account regardless of the feed's quality itself.

## Common mistakes

- Generating the feed once at launch and never checking again that it keeps regenerating automatically over time.
- Leaving required fields blank instead of filling them with a consistent default value, which causes the product in question to be rejected systematically.
- Ignoring non-blocking warnings flagged by Merchant Center, which often turn into rejections once the platform later tightens its rules.

## Tracking performance once the feed is approved

1. **Check the approval rate regularly** — Merchant Center shows the proportion of approved products relative to the total feed; a sudden drop generally points to a recent change on the catalogue side or on the platform's rules.
2. **Cross-check against click statistics** — A product that's approved but gets no impressions or clicks may indicate an unappealing title or categorisation rather than a technical feed problem.

## FAQ

### Do I need a different feed for each marketplace?

Generally yes: each marketplace defines its own required fields and its own format, even though the data source (the store's catalogue) stays the same.

### How long before products appear on Google Shopping?

Once the feed is approved, indexing typically takes anywhere from a few hours to a few days, and can vary with catalogue size and the Merchant Center account's history.

### Can the feed include product variants (colour, size)?

Yes, and it's actually expected: each sellable variant must appear as a separate entry in the feed, with its own ID, its own availability and, where relevant, its own price.