操作指南 · PIM FEEDS

如何为市场平台创建国家和语言 Feed

国家和语言 Feed 让卖家保留一个产品目录,同时按市场展示正确的标题、描述、价格、链接、图片和属性值。ChannelDock PIM Feeds 可把已审核的产品数据生成受控的 marketplace 导出,而不是一堆临时表格。

Base feed
one stable product record
Language feed
localized titles and descriptions
Country feed
prices, links, units and policy fields
你将搭建什么Controlled
01Base feedone stable product record
02Language feedlocalized titles and descriptions
03Country feedprices, links, units and policy fields
Master data → overrides → validation → publish

Meta 将国家和语言 Feed 定义为覆盖层,用来本地化价格、描述、标题、链接、颜色、尺码、材质和图片等目录数据。Google Merchant Center 和各市场平台也有自己的本地规则。因此关键不是能否翻译产品,而是哪些字段按语言、国家和渠道变化。

Local buyer experienceShoppers see the right language, currency, units and product page instead of the default catalog record.
Fewer feed rejectsLocalized fields are validated before publishing, not repaired after a rejected campaign or marketplace export.
One source of truthSKU, GTIN, stock and core attributes stay stable while ChannelDock feeds output market-specific values.
Faster expansionNew countries reuse the same field model, glossary and approval process instead of starting from a blank CSV.

准备:把主目录和本地覆盖层分开

国家或语言 Feed 是覆盖层,不是第二个目录。主产品记录仍然负责产品身份。

Master product identity

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.

Localized field list

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.

Approval owner

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.

实用规则:保持 Feed ID 稳定,只本地化周围的值。如果每个国家都生成新的 SKU 或商品组,报表、库存同步和广告学习都会被拆散。

步骤:创建国家和语言 Feed

此流程适用于 Meta 目录本地化、Google Merchant Center、市场平台扩张和多语言产品 Feed。

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.

Common mistake: building local feeds from separate exports. That creates different IDs, broken variants and no clear master record.

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.

Common mistake: treating language and country as the same thing. A French-language feed for Belgium may still need Belgian prices, links and shipping promises.

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.

Common mistake: translating descriptions but leaving color, size and material values in the source language.

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.

Common mistake: letting each translator choose a different word for the same material or product family.

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.

Common mistake: assuming one “localized_title” column will be accepted by every marketplace without channel-specific mapping.

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.

Common mistake: only checking whether a translation exists. Existing text can still be too long, in the wrong language or mapped to the wrong attribute.

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.

Common mistake: launching all countries at once and discovering after spend starts that links or descriptions still point to the default market.

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.

Common mistake: storing marketplace fixes in a separate sheet that never returns to the PIM.

可复用的 Feed 模型

很多指南只说本地化很重要,却没有解释身份字段和覆盖字段的运营拆分。这个拆分能保护库存、变体和报表。

国家或语言 Feed 应改变买家看到的市场上下文,而不是运营依赖的产品身份。

Base feed
Overrides
Validate
Publish

每一层应放哪些字段

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.

手工本地化文件 vs ChannelDock PIM Feeds

手工文件可以应付一次活动,但当产品数据、库存和平台规则每周变化时就会失效。

不用 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.

使用 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.

查看 PIM Feeds →

常见错误

  • 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.

国家和语言 Feed FAQ

It is an override feed that changes selected product fields for a country or language while keeping the item connected to the main product catalog. Typical overrides include title, description, price, link, color, size, material and images.

Usually yes at the export layer, because each channel has its own schema. The PIM should still keep one master product record and generate channel-specific country or language outputs from that source.

SKU, GTIN/EAN, item group ID, brand, core product facts and operational stock fields should normally stay stable. Localized feeds should change buyer-facing presentation and country rules, not the product identity.

AI can draft titles, descriptions and translations, but the output needs validation against glossary, character limits, marketplace policy and native-language review. Do not let AI invent missing compliance facts.

Use completeness checks per locale before export. Products with missing required language fields should stay in review or fall back according to an explicit rule, not accidentally publish with mixed-language content.

Use PIM Feeds for export generation, PIM Multilingual Listings for localized content and PIM Mapping for channel schemas.

相关 PIM 指南

这些下一步能让本地化产品数据更安全。

Translate listings

Build localized marketplace copy.

Read how-to

Set up PIM feeds

Publish product data to Amazon and bol.com.

Read how-to

Map PIM fields

Connect product data to channel schemas.

View feature

Explore PIM

See ChannelDock’s product-data workflows.

View feature

无需复制目录,也能创建本地化 marketplace Feed

用 ChannelDock PIM Feeds 从一个受控产品数据流程发布国家和语言版本。