TRIMIT data mapping

This article explains how the mapping works between Delogue PLM and TRIMIT.

Introduction & Best Practice:

Automatic integration between Delogue and TRIMIT ensures that data flows seamlessly and will reduce the need for manual data entry and minimize errors. As a result, you can maintain accurate, real-time data, leading to more efficient and reliable master data.

NOTE: To set up the integration, you must create a Custom Export in Admin to get the API key for TRIMIT to use. You'll be able to read more about the Custom Export here.

Before You Start

Before exporting data from Delogue to TRIMIT, ensure all necessary connections are set up. Validate the following data points:

Brand ID must match in both Delogue and TRIMIT
Group values must contain the same options in both Delogue and TRIMIT
Supplier ID must be the same in both Delogue and TRIMIT
Season names must match in both Delogue and TRIMIT.
Color numbers must follow the same logic and amount of digit as in TRIMIT.
Create a Custom Field in Delogue for mapping the Template in TRIMIT.

Mapping of Fields in Delogue to TRIMIT

We have created an overview of all the standard fields in Delogue and their corresponding TRIMIT fields.

You can download the complete overview, which includes comments and requirements, here.

Notes to the below table:

ID / Value: Indicates whether the ID or the Value from Delogue is used in the integration.

Mandatory: Specifies if the field is mandatory for the integration.

Auto. create: If YES, values are automatically created in TRIMIT through the integration.

Update: If YES, updates made in Delogue will be reflected in TRIMIT.

Add: If YES, information can be added after the first export.

Delogue field name	TRIMIT field name	ID / Value	Mandatory	Auto. create	Update	Add
Style no.	No.	Value	YES	YES	NO	NO
Style name	Description	Value	YES	YES	YES	NO
State	Status Code	Value	YES	NO	YES	NO
Brand	Brand Code	ID	YES	NO	YES	NO
Style logo (image)	Master Picture	URL	NO	NO	YES	YES
Group	Multiple choices: - Statistic group - Item category - Global dimension	Value	NO	NO	YES	YES
Supplier on style	Vendor No.	ID	YES	NO	YES	YES
Season on style	Multiple fields: - Collection No. - Season Code	Value	YES	NO	NO	NO
Colors in Admin	Color table (VarDim type)	ID + Value	NO	YES	NO	YES
Color on style	Variant 1	ID	YES	YES	YES	YES
Sizes on style	Variant 2 / 3	ID	YES	YES	YES/NO	YES
Measurement tags	PDM measurement lines	ID + Value	NO	YES	YES	YES
SKU	SKU	Value
CARE INSTRUCTIONS
Layer	Composition lines - Description	ID	NO	NO	YES	YES
Materials	Composition lines - Value in %	Value	NO	NO	NO	YES
Icons	Care label	ID	NO	NO	YES	YES
Instructions	Care label	ID	NO	NO	YES	YES
PRICES
Supplier cost price	Unit price	ID + Value	NO	YES	NO	YES
Price field (e.g. Landed cost)	Purchase price	ID + Value	NO	YES	NO	YES
CUSTOM FIELDS
Template in Trimit	Variant table	ID	YES	NO	NO	NO
Custom field (e.g. drop)	Period code	ID	NO	YES	YES	YES

Visual Data Mapping

The image below provides a visual example of the mapping within TRIMIT.

Red text highlights the placement of Delogue data fields in the integration.

Note: The image below can be found here for a larger view.

Trimit example

Additional Notes

This guidance helps you understand the connection between Delogue PLM and TRIMIT
The integration is built and supported by TRIMIT.
For any add-ons to your integration, please contact TRIMIT directly.