Cómo crear feeds de país e idioma para marketplaces
Los feeds de país e idioma permiten mantener un solo catálogo y mostrar por mercado el título, descripción, precio, enlace, imagen y atributos correctos. PIM Feeds de ChannelDock convierte datos aprobados en exportaciones controladas para marketplaces.
one stable product record
localized titles and descriptions
prices, links, units and policy fields
Meta define los feeds de país e idioma como feeds de override para localizar datos del catálogo como precio, descripción, título, enlace, color, talla, material e imágenes. Google Merchant Center y los marketplaces añaden sus propias reglas. La pregunta operativa es qué campo cambia por idioma, país y canal.
Preparación: separa el catálogo maestro de los overrides locales
Un feed de país o idioma es una capa de override, no un segundo catálogo. El registro maestro sigue siendo la identidad del producto.
Lock SKU, GTIN/EAN, brand, variant group, base image set and source category in your ChannelDock PIM. These fields usually should not change just because the buyer is in another market.
Decide which fields may change per locale: title, description, color label, material label, size text, link, price, sale price, unit price, product page URL and country-specific images.
Assign an owner for language quality, legal claims and feed validation. AI can draft localized copy, but regulated claims, safety warnings and compatibility statements need controlled review.
Paso a paso: crear feeds de país e idioma
Usa este flujo para Meta, Google Merchant Center, expansión en marketplaces y feeds multilingües.
Define the base feed
Create a primary product feed that contains the stable product facts: id, SKU, GTIN, brand, availability, base image, product type, item group ID and the default title and description. This feed should be publishable by itself before you add local overrides.
Choose your market matrix
List every language-country-channel combination you need: Dutch for bol.com Netherlands, French for Belgium, German for Kaufland, English for Amazon, or French and German country feeds for Meta ads. Keep the matrix small at first and launch one pilot category before the full catalog.
Create override fields in the PIM
Add locale-specific fields for title, description, color, size, material, link, price and image references. Use PIM Multilingual Listings for language variants and keep numeric or identity fields language-neutral unless the channel explicitly requires a country format.
Build a glossary and controlled values
Create approved translations for product types, materials, colors, sizes, care terms and words that should never be translated, such as brand names or model codes. Controlled values keep filters and variant groups consistent when copy is localized.
Map fields to each channel
Use PIM Mapping to connect internal fields to the target channel. Meta language feeds use override fields, Google uses country and language rules in Merchant Center, and marketplaces often combine category, country and attribute requirements.
Validate feed rules before export
Run checks for missing translations, unsupported language codes, invalid currency, wrong product page links, title length, duplicate words, image references and category-specific attributes. Validate the override feed against the base feed so every localized row has a matching product ID.
Publish a pilot feed and compare the live result
Send one category or a small group of high-value SKUs first. Check how product cards display in the target country: language, URL, price, image, availability, size label, color filter and mobile layout. Then publish the rest of the feed.
Turn rejects into reusable rules
When Meta, Google, Amazon, bol.com, Zalando or Kaufland flags a localized field, do not patch only that row. Decide whether the fix belongs in the glossary, mapping, validation rule, source data or approval workflow. That is how every next country launch becomes faster.
El modelo de feed reutilizable
Muchas guías hablan de localización, pero no explican la separación entre campos de identidad y campos de override. Esa separación protege stock, variantes e informes.
Un feed de país o idioma debe cambiar el contexto de mercado para el comprador, no la identidad del producto que usa la operación.
Qué campos van en cada capa
Master feed
ID, SKU, GTIN, brand, item group ID, stock status, base category, default image and source product facts. These are the anchor fields for integrations and reporting.
Language feed
Localized title, description, bullet points, material labels, color labels, search terms and customer-facing warnings in the buyer language.
Country feed
Currency, sale price, product page link, shipping promise, unit price, country image overrides, legal notes and market availability.
Review queue
Missing translations, risky AI output, compliance claims, category exceptions and rows where the override conflicts with the master record.
Archivos manuales vs ChannelDock PIM Feeds
Los archivos manuales sirven para una campaña. Fallan cuando cambian cada semana los datos, el stock y las reglas del marketplace.
Sin ChannelDock
- Every country has its own spreadsheet, naming logic and upload schedule.
- IDs, URLs and localized copy drift apart after a few updates.
- Feed errors are discovered in channel dashboards after campaigns are planned.
- Teams cannot see which country uses which value, image or approval status.
Con ChannelDock
- Base data, localized fields, mappings and validation live in one PIM workflow.
- Country and language feeds reuse the same SKU and product identity.
- Marketplace-specific checks happen before export through PIM Feeds.
- Corrections become reusable rules for the next country, channel or category.
Errores comunes
- Using automatic translation as the final feed value without native or policy review.
- Localizing copy but forgetting links, prices, image text, unit price and country-specific availability.
- Changing SKU, GTIN or item group IDs inside a language feed.
- Building a feed for every country from scratch instead of using override layers.
- Ignoring fallback behavior when a localized value is missing.
FAQ sobre feeds de país e idioma
Guías PIM relacionadas
Estos pasos hacen más segura la publicación de datos localizados.
Crea feeds localizados sin duplicar tu catálogo
Usa ChannelDock PIM Feeds para publicar variantes de país e idioma desde un flujo controlado de datos de producto.