Most DPP platforms sell you a list of named connectors — and most of those connectors are marked "planned". You end up waiting for the vendor to build the integration you need, and locked into their roadmap when they do.
TracePass takes the opposite approach. Your source of truth stays in your existing systems. TracePass reads product data through a documented REST API (read/write endpoints on every plan), a per-category CSV/Excel import, the free n8n community node, signed webhooks, or an MCP server for AI agents. Your integrator maps your fields once — to any system — and it keeps working.
The result: there's no connector to wait for, and nothing proprietary to be trapped by. The same openness is why your data exports as JSON-LD on demand and your passport URLs stay yours forever.
Light integration is enough because the hard part isn't the pipe — it's the data. TracePass reads your datasheets, certificates and test reports and fills each regulated field with a confidence score and a link back to the source document, for a human to approve. That extraction does the normalisation other platforms sell as a deep-integration project. A proprietary connector looks impressive in a demo and then becomes the thing you can't leave; we use the standards your systems already speak, so you keep control of the mapping.
Five ways in
REST API
Documented read/write endpoints on every plan, including Free. Your integrator maps your fields once; OpenAPI 3.1 spec, Idempotency-Key semantics, and HMAC-signed webhooks included.
CSV & Excel import
Per-category templates match every DPP field 1:1. Export from your ERP, map your columns to passport fields on screen, and TracePass fills the rest. Zero integration work to start.
n8n community node
Automate TracePass without writing code. The free community node installs from any n8n instance and wires products, passports, and EPCIS events into workflows alongside Shopify, Slack, and 400+ other apps.
Webhooks
HMAC-signed event callbacks push passport and EPCIS changes to your systems in real time. Your stack reacts to TracePass without polling.
MCP server (AI agents)
Connect Claude, Cursor, or any IDE agent directly to TracePass via the Model Context Protocol. Manage products, passports, and EPCIS events conversationally, using your existing API key.
How the systems you run connect
Every system below connects today through one or more of the methods above — no native plugin required. Pick the path your team already knows.
| System | Type | How it connects |
|---|---|---|
| SAP | ERP | RESTCSV Export product master data from SAP S/4HANA or ECC and push it to TracePass via REST API, or start with a CSV mapping. No SAP plugin to license. |
| Odoo | ERP | RESTn8nCSV Odoo's own REST/XML-RPC API pairs with the TracePass REST API or the n8n node to sync products into passports automatically. |
| NetSuite | ERP | RESTCSV Pull item records via NetSuite SuiteTalk/REST and map them to passport fields through the TracePass API, or bulk-load with CSV. |
| Microsoft Dynamics 365 | ERP | RESTCSV Expose product and BOM data through the Dynamics 365 OData/Web API and post it to the TracePass REST API, or stage a CSV export — no AppSource add-in to install. |
| Sage | ERP | RESTCSV Pull item and supplier records via the Sage API (or Sage's data export) and map them to passport fields through the TracePass REST API or a CSV import. |
| Infor | ERP | RESTCSV Infor's ION API exposes the product master discrete and process manufacturers hold; feed it to the TracePass REST API, or start with a CSV mapping per category. |
| Epicor | ERP | RESTCSV Epicor Kinetic's REST services expose part and BOM data; map it to passport fields through the TracePass API, or bulk-load with a CSV export. |
| Akeneo | PIM | RESTCSV Your PIM already holds the product attributes a DPP needs. Push them from Akeneo's API to the TracePass REST API, or export a CSV per category. |
| Pimcore | PIM | RESTCSV Pimcore is API-first, so its Data Hub / REST API maps cleanly onto the TracePass REST API — push product attributes straight into passports, or export a CSV. |
| Salsify | PIM | RESTCSV Export your product records from Salsify's API or a channel feed and post them to the TracePass REST API, or map a CSV per category. |
| Shopify | E-commerce | n8nREST Trigger passport creation on a new product or order with the n8n node (Shopify is a built-in n8n app), or call the TracePass API from your storefront backend. |
| WooCommerce | E-commerce | n8nREST Fire passport creation from a WooCommerce order or product event via the n8n node, or call the TracePass REST API from a WordPress hook — no plugin to maintain. |
| Snowflake | Data warehouse | RESTCSV Materialise the product rows you need and feed them to TracePass via the REST API or a scheduled CSV export — useful when compliance data is already modelled in the warehouse. |
Wire it once. Keep your stack.
Start free, read the API docs, and connect the systems you already run. No native plugin, no lock-in, no waiting on a connector roadmap.
Read the API docs