Overview

Ympact is a supply chain traceability platform for the fashion and luxury industry. Brands use it to issue purchase orders, track execution across their supplier network, and build an auditable record of every material movement.

When a brand issues a purchase order, the supplier must keep Ympact up to date — shipments, delivery plans, attached documents, and production processes. This guide is for the System Integrators (SI) who connect the supplier's ERP to Ympact to automate that data flow.

Your role as a System Integrator

Your job is to map the fields in the supplier's ERP to the entities Ympact expects, and send that data through the integration channel agreed with Ympact during onboarding.

Ympact manages authentication, UI components, and the brand portal. Your integration has one responsibility: send the right data, in the right format, at the right time.

What the supplier must send

For each purchase order, the supplier is expected to communicate the following information:

Entity	Domain	Description
Shipment	Tracking	Each physical shipment dispatched against the order
Delivery Plan	Tracking	Planned delivery schedule for each order line
Document	Tracking	Attached files — packing lists, invoices, AWBs, DDTs
Process	Mapping	Production or processing operations performed on the material

Not all entities are required for every supplier — the brand configures what is expected. When in doubt, refer to the onboarding documentation provided by Ympact or contact Support.

Sending order

The order in which entities are sent matters:

1. Shipments and Delivery Plans — send these first. They can arrive simultaneously but must precede documents and processes.
2. Documents and Processes — send these after the corresponding shipments are in place.

Sending a document or a process before its related shipment exists in Ympact may cause processing errors.

Integration channels

Ympact supports two integration channels. The channel is chosen once during onboarding and applies to all entities:

• Message queue — send JSON payloads to a dedicated queue provisioned by Ympact. This is the recommended channel for real-time, event-driven integrations.
• SFTP — deposit semicolon-delimited CSV files on a dedicated SFTP server. This channel is suited for batch integrations or legacy ERP systems.

Both channels carry the same entities and the same data model. The choice of channel does not affect what you send — only how.

How access works

Ympact provisions all credentials. There is no self-service registration. As part of onboarding, you will receive:

• Access credentials for the integration channel (queue credentials or SFTP credentials)
• Credentials for each environment (dev, test, stage, demo, production)

See Credentials & access for details on what you receive and how to use it.

What's in this guide

Section	What you'll find
Quickstart	Send your first payload in the dev environment
Environments	Base URLs and configuration for each environment
Credentials & access	What credentials you receive and how to configure them
How it works	End-to-end data flow from brand order to Ympact
Order lifecycle	What to send and when, with a concrete example
Field mapping	How to map ERP fields to Ympact entities
Guides	Per-entity payload references and CSV specifications