Ecommerce

Product feed — structured catalogue data for marketing

A product feed is a structured catalogue provided to an advertising, shopping or marketplace system. It describes items using identifiers, names, prices, availability, images and other required attributes.

Published: Updated: 3 min read
Scheme: Product feed. Catalog - Export - Platform.

What is a product feed?

A product feed is a structured catalogue provided to an advertising, shopping or marketplace system. It describes items using identifiers, names, prices, availability, images and other required attributes. It is different from the website’s XML sitemap and from Schema.org markup, although the information across these systems should agree.

What data is most important?

Each product needs a stable identifier, the correct address and an image consistent with the offer. The price, currency and availability must correspond to the website and the ability to complete the order. Variants require correct differentiation, such as size or color. Use actual manufacturer identifiers as documented; don't make up GTINs just to make the missing field message go away. The requirements depend on the product type and market.

Quality of titles and descriptions

The name should precisely identify the product and its essential features, without an artificial accumulation of promotional words. Match the order of information to the search method in a given category. The description should correspond to the actual properties and not add unconfirmed applications. Check character encoding and removing HTML elements that the recipient does not support. Well-organized source data reduces the need for complex corrections to the export itself.

Update and compatibility

Set a synchronization frequency appropriate to changes in prices and stock levels. If the file is updated rarely, the product may be advertised with an outdated price. Monitor last valid export time, item count and processing errors. A one-time successful import does not confirm the reliability of the integration. After changing addresses or variant structure, check the continuity of identifiers so as not to accidentally create new offers instead of updating existing ones.

Feed and store SEO

A correct feed helps the target system understand the offer, but does not replace indexable product cards and good store navigation. Maintain alignment between feed, viewable content, structured data and purchase. Discrepancies may result in rejections or misrepresentation. Do not create separate, poor pages only for export, if the user should be provided with a complete and accessible offer on the website.

How to control effectiveness?

View platform diagnostics, rejected items, warnings and inventory coverage. Also analyze your ad results by margin and availability, not just the number of clicks. Enter alert for empty file, sudden drop of products and download errors. Store secure logs without customer data. A good feed is a continuously maintained catalog integration, not a one-time document that can be left unattended after uploading.

How to handle variants and stable identifiers?

Color and size may create separate sold variants that must be properly associated and described. The ID should not change every time the name is updated. Check if the link opens the correct variant with price and availability consistent with export. The same parent model does not justify copying a random price to all variations. Do not fill in missing data with a feature taken from another product.

When migrating your catalog, keep your ID map and test updating existing offers, not just adding them again. Monitor rejections when you change currency, tax or image addresses. When exports have zero items, integration should not without reflection consider this as a valid withdrawal of the entire product range. You need an alert and a distinction between an actual offer change and a data source failure.

Sources and further reading

Use the primary documentation to check the principles and limitations described in this article.

How we prepare the glossary

These articles combine original editorial work, AI support for editing and translation, and checks against linked primary documentation. Examples are illustrative unless stated otherwise; they do not represent client results. Dates refer to publication and actual content changes.

From knowledge to action

Need help putting this into practice?

Tell us about your website or process. We will define the scope and the next practical step.

Discuss your project