Skip to content
Publishing

Send product data to marketplace channels

Resolve channel attributes from your records, see what is blocking, and push or export a feed with a full audit trail.

DPP Shield editorial team · Updated:

Resolve channel attributes from your records, see what is blocking, and push or export a feed with a full audit trail.

The channel catalogue

The platform ships reviewed attribute profiles for the channels it supports, each with its attribute set, types, length and value constraints, and a stated specification reference and review date. Read that reference: the profiles are a reviewed snapshot, and the channel's own documentation is authoritative.

Some attributes are always required, and some become required conditionally - for a category, or because another attribute resolved to a particular value. The catalogue shows which is which.

Readiness per product

Readiness reports, per passport, what is filled, which mandatory attribute is missing and why, so you can fix the data once instead of per listing. The page also aggregates the blockers that affect the most products in your portfolio.

Where each value came from

Every resolved attribute carries its source - declared in the passport, derived by a documented rule, missing, or invalid - and the path it was read from. A value that breaks a channel constraint is reported as invalid with the constraint quoted, and it is never truncated to fit.

The platform does not invent a value to complete a listing. It also honours your redaction: a field withheld from the public passport is not declared to a marketplace either, and the feed says what that costs you in readiness.

Feed and sync

  1. Open Channels and pick the channel.
  2. Check readiness and fix the blocking attributes.
  3. Preview the feed, then export it as CSV or run a sync.
  4. If a push endpoint is configured the feed is dispatched through the webhook stack; otherwise it stays prepared for a manual upload.
  5. Record the channel's own identifier when they accept it - that is the difference between sent and done.

The widget

For storefronts, the platform serves a dependency-free embed script. The snippet carries the passport identifier and a target element, and the widget renders a card with the QR image, issuer, product identity, badges and a compliance verdict labelled with how fresh it is.

A badge with no value is omitted rather than drawn as a zero, an unvalidated passport says so, and a score taken on an older version is labelled as such. The page previews the rendered widget before you paste the snippet.

Screen-by-screen reference

These pages were checked in the organization console on 8 October 2026 using an isolated sample organization. Controls can differ by role, plan, record state and configured providers. Each page below explains its purpose, a practical workflow, the visible controls and what to verify afterward.

Marketplace channels (/channels)

Channel profiles define required and optional attributes for Amazon EU, Zalando and Shopify, then build feeds from the published redacted passport.

Select a channel profile and a published passport, then inspect attribute resolution before creating a feed. Missing channel fields should be corrected at their product or passport source. Dry run shows the outgoing shape without recording a sync; afterward, distinguish a dispatched feed from a marketplace acknowledgement.

Dispatched is not the same as acknowledged by a marketplace.

Controls and options

  • Select a marketplace channel and Show channel to inspect its profile and passport readiness.
  • Open attribute resolution to see where each feed value came from and what is missing.
  • Use Dry run before Record sync; export JSON or CSV feed only after checking the result.
  • Save endpoint for a configured push destination; record a marketplace acknowledgement when it supplies its own identifier.
  • Build snippet links to the embeddable passport widget.

Passport widget preview (/channels/widget)

The widget preview lets a merchant test the embeddable public passport card for an active passport.

Preview the widget with the exact published passport and theme that a merchant intends to embed. Compare the visible identity, image, status, link, and QR destination against the public passport itself. Copy the snippet only after those public details are correct, because a draft has no consumer-facing widget payload.

A draft passport cannot appear in a public widget.

Controls and options

  • Choose a published passport and a theme, then Preview.
  • Check name, image, status, link and QR behavior in the preview.
  • Copy the generated snippet only after verifying the chosen product and public data.