INTEGRATIONS & DATA EXCHANGE

A connected process.
A clear starting point.

Move from source evidence to structured product data. Workspace exports are available; email, document intelligence and billing depend on configured providers.

View workspace services Check availability

ERP and PIM connectors are not available. Service availability is shown inside your workspace.

Product data

Source evidence

Supplier workflow

Data exports

MarketPassProducts. Evidence.
Review context.

Conceptual data flow. Connections are agreed during pilot discovery.

AVAILABILITY, WITHOUT THE GUESSWORK

What you can try.
What we need to scope.

Workspace exports and private source uploads are implemented. External services run only when their credentials and required controls are configured.

Workflow	Availability	What this means
Product CSV export	Workspace export	Download your organisation’s product inventory. Export permissions, organisation policy and usage limits are enforced by the server.
DPP draft JSON export	Workspace export	Download a product data draft with source references and unresolved fields. It is not a published or certified Digital Product Passport.
CSV / XLSX imports	Preview & explicit commit	Validate products or suppliers before creating records. Inspect row errors and duplicates, map to existing categories and suppliers, then explicitly commit valid rows with duplicate records skipped.
ERP & PIM systems	Not connected	Define the system owner, available interfaces, required fields and update responsibilities before committing to a connection.
Private source uploads	Implemented	PDF, PNG and JPEG sources enter versioned private storage and quarantine. Production storage and malware screening require deployment configuration.
Email, AI & billing	Configuration required	SMTP email, AI extraction and Stripe billing use configured providers. Queued requests remain distinct from successful delivery, processing or payment.

ERP/PIM connectors require separate implementation. Read API keys and signed metadata webhooks have owner controls; outbound destinations require operator configuration. Provider configuration is distinct from a successful provider acknowledgement.

GOOD CONNECTIONS BEGIN WITH GOOD MAPPING

Start with the information.
Then define the connection.

A focused collection gives your team a practical way to agree on the data that matters.

Agree on the product record.

Identify stable product IDs, model references, category information, suppliers and intended markets.

Decide which system owns each field and how conflicting values should be handled.

Keep the source visible.

Map evidence to the product it supports. Include the source reference, evidence type and current review state.

Define whether original documents are linked, copied or stored before connecting a repository.

Plan the full lifecycle.

Consider imports, updates, exceptions and exports together. Make ownership clear when data changes.

Test the agreed mapping with representative records before scaling the workflow.

A USEFUL TECHNICAL DISCOVERY

Bring a sample.
Leave with a clearer scope.

A representative record structure and a short description of your current process are enough to begin mapping the work. Share real files only after data handling arrangements are agreed.

What to include in your brief

The systems that hold product and document information
The fields your team needs in a product record
The people responsible for data updates and review
The outcomes a connected workflow should support

Prepare a pilot brief Submit your scope to the pilot enquiry form. Sending a brief does not activate a subscription.

A connected process.A clear starting point.

What you can try.What we need to scope.

Start with the information.Then define the connection.