積載

Channel Requirement Profiles

A Channel Requirement Profile defines how a company prepares product and offer information for a particular external channel. Its version specifies the destination, market, language, category scope, source edition and supported field mappings.

A Catalog Publication pins the selected requirement version. Passport Profiles and Passport Category Mappings belong to the independent DPP workflow; they do not define marketplace content.

For example, a channel version can obtain a title from Product information, price from the commercial offer, availability from authoritative warehouse reports and an origin declaration from a supported trade record. The preview shows which source supplied each result.

What a mapping describes

Typed bindings connect named destination fields to supported source paths. They can select category attributes, expected units, approved value lookups and permitted Reference Collections. Required fields and supported conditional rules determine whether content is ready.

Destination-specific overrides are limited to explicitly permitted fields. An override used in one listing is not a correction to Actualog's canonical technical Product information. If the source fact is wrong, correct its owning record and review a new content version.

Who maintains profiles

Integration Managers and Company Administrators with integration configuration authority maintain channel requirement definitions. Catalog Managers use these definitions to preview and approve the offers they are authorized to publish.

Working with a requirement version

  1. Open Data Integration → Catalog Publishing → Channel requirements.
  2. Search existing profiles before selecting Create new requirement profile.
  3. Select the Connector and category by name and enter the intended language, market and source edition.
  4. Configure supported destination fields, source paths, unit handling and permitted values.
  5. Save the version and use it in a catalog publication.
  6. Preview representative external listings and inspect issues, field lineage and source versions before approving content.

Do not invent destination fields or assume a source path is supported merely because it resembles a familiar attribute name. The editor provides supported field examples; the actual preflight determines whether the selected information can be represented.

Blockers and maintenance

Missing required values, duplicate destination bindings, incompatible units, unknown reference values and unsupported channel representations require correction. Fixed, starting and on-request pricing are distinct local modes; a destination may support only some of them.

Maintain a new requirement version when channel rules or mappings change. Reassign publication configuration deliberately and review affected listings. The existing Google XML preparation and API delivery use the same channel content composition, so their approved data should agree even though generating a file and sending it externally are different operations.

Related topics: Catalog Publications, External Listings, Passport Category Mappings.