DPP Agent docs

Delogue PLM — integration guide

Delogue is a Danish fashion-PLM widely used across Nordic apparel and accessories brands. DPP Agent reads Styles + Variants from Delogue and maps each colour × size combination into a DPP row.

The default field mapping was tuned against typical Nordic-apparel catalogues. If anything in the default mapping doesn't match your tenant, the per-tenant attr_* overrides described below let you remap without code changes.

What the adapter does, in one sentence

DPP Agent paginates Delogue's /v1/styles endpoint, flattens each Style into one DPP row per GTIN-bearing variant, and ingests through the conflict-aware pipeline. Read-only, no Delogue-side schema changes, no write-back.

Authentication

Bearer token issued from your Delogue account admin. Delogue tenants are subdomained — pass the full origin as base_url:

GET <base_url>/<api_version>/styles?page=1&pageSize=50
Authorization: Bearer <token>

Credential envelope is identical to the other adapters: AES-256-GCM at rest, redacted in the UI, decrypted in-memory only, never logged. Revoke in Delogue → next sync run fails cleanly with HTTP 401.

Scope limitation

1. Per-tenant read scope

Delogue's API tokens are scoped to the issuing tenant — we cannot read another brand's styles even if their base_url were probed.

2. Field allowlist on response

The mapper only extracts the fields covered by the attr_* settings (see Settings reference below). Everything else in the Style JSON is dropped at the response parser — supplier costs, internal product narrative, designer notes never leave Delogue's response into our ingest pipeline.

3. Collection filter (optional)

settings.collection_filter = "AW26,SS26" restricts the pull to one or more named collections. Pre-launch you typically point a single sandbox collection at us, validate field mapping, then widen.

4. Sync mode (skeleton vs full)

Skeleton mode reads identifiers + variants only — no BOM, supplier list or care label. Useful for first sync, mapping validation and incremental cron heartbeats. Full mode pulls the AGEC-relevant fields (materials → composition, suppliers → journey steps, care label).

Settings reference

Setting Required Purpose
base_url yes https://<your-brand>.app.delogue.com
api_version no Default v1
page_size no Default 50
collection_filter no Comma-separated collection codes
sync_mode no skeleton (default) | full
attr_gtin no Variant field that holds the EAN/UPC. Default ean.
attr_color no Default color
attr_size no Default size
attr_composition no Default materials
attr_care no Default careInstructions
attr_image no Default images[0].url

Sync semantics

Conflict policy is the platform default:

  • Draft DPPs are overwritten
  • Active DPPs spawn dpp_revisions(status=pending) for human review
  • Withdrawn / archived / recalled DPPs are skipped

Deletion: if a Style disappears from Delogue, the corresponding DPP remains in dpp_runtime. EN 18219 §4.4 + EN 18223 §4.1.2 require the DPP to outlive the upstream catalogue entry for the regulatory retention period. The brand explicitly changes status when ready (withdrawn / archived / recalled).

Onboarding sequence

  1. Delogue admin: generate API token, share base_url (tenant subdomain)
  2. Paste token + base_url into DPP Agent → Integrations → Add Delogue
  3. Connection test pulls the first page and reports style + variant count
  4. Skeleton sync, sync_max_pages = 2-3, on a sandbox collection
  5. Review the generated drafts — tune attr_* overrides if the default field names don't match your Delogue setup
  6. Full sync with sync_mode = full once mapping is validated
  7. Cron takes over (6h default, per-tenant configurable)

Compliance hooks

ESPR / AGEC field Delogue default path
espr.pid.gtin variants[].ean
espr.pid.product_name name
espr.pid.product_brand (from tenant.brand_name)
espr.pid.color variants[].color
espr.pid.size variants[].size
espr.mat.composition materials[]
espr.care.instructions careInstructions
tex.product.hero_image_url images[0].url
tex.journey.steps suppliers[] (in full mode)

Delogue carries supplier rows on the Style, which is exactly what AGEC tex.journey.steps expects. This makes Delogue one of the few PLM adapters that can populate the AGEC traceability timeline without an extra TrusTrace connection.

Troubleshooting

  • HTTP 401 on probe — token rotated or scope downgraded
  • Empty styles array — collection_filter excludes every active collection, or the tenant has no live styles
  • Missing variants[] — the Style record is in draft state in Delogue; only published styles return variants
  • GTIN missing — variants exist but ean field is empty. Backfill in Delogue, or remap attr_gtin to the field your brand uses
  • Slow sync — switch to sync_mode = skeleton for the first pass

Open a ticket at support@dppagent.com with the integration ID and last sync log entry.