PIM and product content

Product content syndication to retailers and marketplaces

Quick answer

Product content syndication is the automated publishing of product data and assets from a PIM to retailers, marketplaces, distributors and data pools, in each recipient's format and taxonomy. Brands use four routes: GDSN data pools, direct retailer and marketplace APIs, feed management platforms, and industry exchange formats such as BMEcat and ETIM.

Key takeaways

  • Syndication runs through four routes: GDSN data pools, direct retailer and marketplace APIs, feed management platforms, and B2B exchange formats such as BMEcat and ETIM.
  • Attribute mapping is the main cost driver; onboarding a new major channel typically takes 5 to 15 working days of mapping and testing (editorial estimate).
  • Since 13 December 2024, Article 19 of the General Product Safety Regulation (EU) 2023/988 requires online listings to show manufacturer details, product identification with an image, and safety warnings.
  • Track acceptance rate, time to listing and channel content score per recipient to manage syndication as an operational process.

Product content syndication is the automated publishing of product data and assets from a PIM to retailers, marketplaces, distributors and data pools, each in its required format and taxonomy. Brands and manufacturers syndicate through four routes, and most European suppliers use at least two of them. Done well, syndication shortens time to listing from weeks to days and cuts manual re-entry in retailer portals.

The four product content syndication routes

The four routes differ by recipient type and data standard, so start by mapping each customer to one route. The table covers the European situation.

Route Typical recipients Format or standard Examples
GDSN data pools Grocery, drugstore, DIY and healthcare retailers GS1 GDSN attributes, GTIN-based GS1 Data Source (Netherlands), 1WorldSync
Direct APIs and portals Large marketplaces and retailers Recipient-specific schemas Amazon Selling Partner API, bol Retailer API
Feed management platforms Marketplaces, comparison sites, ad channels Platform mapping to many outputs Productsup (Berlin), Channable (Utrecht), Salsify, Syndigo
B2B exchange formats Wholesalers, installers, distributors BMEcat, ETIM classification Electrical, sanitary, HVAC and industrial trade

GDSN works through GS1-certified data pools connected to the GS1 Global Registry: the supplier publishes once to its pool, and subscribing retailers receive updates automatically. The so what: every GDSN recipient adds little marginal effort once the first connection is live, while every direct API adds its own mapping work. Background on the standards sits in GS1, GDSN and ETIM.

Attribute mapping is where syndication effort sits

Mapping internal attributes to each recipient's taxonomy is the main cost driver, so model it explicitly. Amazon organises listings by product type, each with its own required attributes, while a DIY retailer may expect ETIM features and a grocer expects GDSN nutrient and allergen fields. One PIM attribute, such as colour, often maps to a different option list per recipient. As an editorial estimate, onboarding a new major channel takes 5 to 15 working days of mapping and testing, plus ongoing maintenance when the recipient changes its schema. Store mappings in the PIM or the feed platform, never in spreadsheets outside version control.

EU listing requirements every syndicated product must meet

European regulation defines a minimum content set for online listings, and syndication must carry it to every channel. Article 19 of the General Product Safety Regulation (EU) 2023/988, applicable since 13 December 2024, requires distance sales offers to show the manufacturer's name and contact details, product identification including an image, and warnings or safety information. Regulation (EU) No 1169/2011 requires mandatory food information, such as ingredients and allergens, to be available before a distance purchase is concluded. Accessibility rules add requirements for alt text and accessible assets. Treat these fields as blocking: a product missing them should never reach a channel.

How to measure syndication performance

Three metrics show whether syndication works as a process.

  • Acceptance rate: the share of items accepted by the recipient on first submission. Rejections usually point to missing mandatory attributes or invalid values.
  • Time to listing: working days from product approval in the PIM to live listing per channel.
  • Channel content score: the recipient's own completeness or quality score, where available, or a PIM completeness score per channel.

Report these per recipient each month. Rising rejections at one retailer usually signal a schema change, while low scores across all channels point to an upstream product data quality issue.

Build, buy or combine

Most companies combine PIM connectors with a specialist route, so decide per recipient type. PIM platforms such as Contentserv and Pimcore offer export profiles and connectors, which suit a limited number of stable channels. Feed management platforms suit companies with many marketplaces and frequent rule changes. Syndication networks such as Salsify and Syndigo focus on retailer requirements and content scoring at scale. Images follow the same routes: deliver URLs from a DAM where recipients accept them, as described in PIM and DAM integration.

What to do next

  1. List every recipient and assign it to one of the four routes.
  2. Collect each recipient's mandatory attribute list and image requirements.
  3. Add GPSR and, where relevant, food information fields as blocking attributes in the PIM.
  4. Estimate mapping effort per recipient and prioritise by revenue share.
  5. Start monthly reporting on acceptance rate, time to listing and content score.

Frequently asked questions

What is the difference between product content syndication and a product feed?

A product feed is a single export file or API payload for one channel. Syndication is the end-to-end process of mapping, validating, publishing and monitoring product content across many recipients, including feedback on rejected items. Feeds are one technical output of a syndication process.

Do I need GDSN to sell through European supermarkets?

Many European grocery, drugstore and DIY retailers require suppliers to publish product data through a GS1-certified GDSN data pool. Requirements differ per retailer and country, so check each retailer's supplier onboarding guide and the data pool used by your national GS1 organisation.

Can a PIM syndicate directly to Amazon and other marketplaces?

Several PIM systems offer native connectors or apps for major marketplaces, and Amazon exposes the Selling Partner API for listings. Companies with many marketplaces often add a feed management platform between PIM and channels to handle mapping, rules and error feedback per marketplace.

Sources

  1. GS1: How GDSN works
  2. Regulation (EU) 2023/988 on general product safety (EUR-Lex)
  3. Regulation (EU) No 1169/2011 on the provision of food information to consumers (EUR-Lex)

Related guides

PIM and product content

GS1, GDSN and ETIM: product data standards in Europe

GS1 standards identify products (GTIN) and locations (GLN) and synchronise product master data between brands and retailers through GDSN, a network of certified data pools. ETIM…

4 min read