DPP Agent

Centra integration

Turn every Centra product into a compliant passport.
One Bearer token. Two-pass sync.

DPP Agent connects to Centra through its GraphQL Integration API. The flow is the same for any Centra catalogue: authorise once, watch draft passports appear for every product, publish when ready.

7-day free trial · no credit card · read-only scopes

01 · What you get

The essentials, done right.

  • GraphQL Integration API with Bearer token — no plugin install on the Centra side.
  • Two-pass sync: skeleton first (fast overview), enrich second (full attributes).
  • Per-market locale sync + Centra product status (ACTIVE/INACTIVE) kept on each passport, separate from its own draft/active status.
  • Supply-chain tier attributes map straight into DPP Agent journey steps.

02 · How it works

From authorisation to publish in four steps.

  1. 1

    Authorise

    Paste your Centra shop URL + Bearer token. DPP Agent verifies the endpoint responds and returns your product filter.

  2. 2

    Skeleton pass

    First sync pulls product IDs + SKUs + names — you see the catalogue shape in seconds.

  3. 3

    Enrich pass

    Second sync (on-demand or scheduled) pulls full attributes: composition, journey, images, GTIN. Draft passports are ready to review.

  4. 4

    Publish

    Flip a passport to active — reachable at yourbrand.dpp.dppagent.com or your own custom domain.

03 · Auth & security

Read-only. Encrypted. Auditable.

Bearer token issued in Centra Admin → Integrations. DPP Agent stores it in a per-tenant encrypted vault; auto-refresh before expiry is on the roadmap.

See the full posture at /trust. Data is stored in the EU (Frankfurt).

04 · Why DPP Agent

Multi-source by design.

Built for Nordic DTC. Journey steps, care symbols, and OEKO-TEX / GOTS badges are first-class. No hacky attribute mapping.

The same DPP works with additional data sources over time. Add Centra alongside Akeneo, roll in a PLM, drop in a CSV for a legacy line — the passport URL never changes.

05 · Frequently asked

Questions we hear.

GraphQL or REST?

GraphQL. Centra recommends its GraphQL Integration API for new integrations, and that is what we call.

How do markets translate to locales?

Each Centra market you opt in maps to a locale in DPP Agent (Sweden → sv_SE, UK → en_GB). Consumer scans pick the right language via Accept-Language.

What about custom attributes?

Every Centra product attribute lands in centra.raw.* on the DPP. We surface known ones (composition, weight, images); the rest stay queryable for future mapping.

ACTIVE vs INACTIVE?

Centra status is recorded on each passport but never changes the passport status: every synced product arrives as a draft, and you choose what to publish. A sync can be limited to ACTIVE products.

Ready to start

A passport for every Centra product.
In an afternoon, not a quarter.

Start free trialSee pricing

7-day free trial · no credit card · cancel anytime