Skip to content
English
  • There are no suggestions because the search field is empty.

Data Import Q&A

Data Completeness Before Import

When should my data be complete?

We strongly recommend that your data be complete before importing into our systems. Any subsequent modifications would require manual intervention from our analysts, which would extend processing times and could generate additional costs.

 

Operating Mode: Trading vs. Manufacturing

Which approach should I adopt based on my production mode?
  • For trading: For component analysis, you may use our frameworks if you do not have the information available. This means you will not need to submit component information; components will be automatically created based on the product created.
  • For manufacturing: We recommend focusing first on analyzing main components (main fabric, lining) to avoid supplier fatigue and ensure their buy-in to our working method. Important: for manufacturing, you must have a unique component reference per supplier, collection, etc., in accordance with our componentRef uniqueness requirement.

 

Material Codification (BOM)

Is it mandatory to codify my materials before import?

No, you can proceed without prior material codification (BOM). However, in the long term, we strongly recommend involving your Production teams in material codification. This approach offers several advantages:

  • Facilitates the data collection process
  • Better ability to identify priority elements to trace (for example, focusing on main components rather than accessories with lower impact)

How should I proceed if I don't have material codification yet?

We offer a progressive approach to clients in this situation:

Phase 1 - Framework Approach (without codification)

  1. You declare only the finished product to us (example: "Jacket") with:
    • Its product category
    • Its associated supplier or agent (your tier 1)
  2. We then send your suppliers a framework (study template) containing typical components for the relevant category. Example: a jacket typically includes a main fabric, lining, buttons, etc.
  3. The supplier(s) contacted can:
    • Add specific components
    • Declare the composition associated with each component
  4. This framework allows us to collect information about the product's manufacturing processes and stages.

Special case: If you already have some partial information about components (example: main fabric and lining) but without composition details, you can declare them by associating them with the same supplier as the finished product.

Phase 2 - Targeted Approach (with codification)

Once material and component codes are integrated into your PLM:

  1. You declare only the components you want to analyze
  2. We assess exclusively these declared components in the study
  3. We query suppliers only about these targeted elements

Advantages of this progressive approach:

  • Simplifies results collection
  • Enables feeding your PLM or analysis tools (BI) with structured data
  • Ability to analyze impacts not only of finished products but also of individual components

Uniqueness Rules

Product / Analysis Uniqueness

A product is made unique in Fairly Made by the values productRef (SKU), productCollectionRef (season), productColorCode (optional, default value "DEFAULT"), and soon by its purchaseOrder (optional, default value "DEFAULT").

If, for the same uniqueness combination (productRef, productCollectionRef, productColorCode, purchaseOrder), some other fields required by our data model may still vary, we recommend concatenating them to the SKU and populating this extended value in the productRef field.

Component / Supplier / Packaging Uniqueness

For these three data families, only the Ref (componentRef, supplierRef, packagingRef) makes the object unique. An object corresponds to one traceability record in our systems.

If you can have the same Ref with multiple suppliers (in the case of Components and Packaging), across multiple categories, etc., we recommend concatenating these values in the object's Ref.

For Components, it's important to include the season in the concatenation, so that the component can be re-analyzed if its traceability has changed from one season to another.

 

Weight Data

When should I provide product weights?

Weight data typically comes later in the process. You can send it to us afterwards without any problem. This data doesn't impact traceability analysis alone, but becomes important for environmental impact measurement.

What if I don't have the data?

Our frameworks will fill in the data with a default value established according to the product or component category. In the long term, we recommend integrating this data into your systems so we can refine your analyses and provide more accurate results.

I have multiple sizes for the same study— which data should I use?

We recommend referring to the reference sizes provided by Ecobalyse as part of the environmental cost assessment. Since this data is used to calculate the product’s impact, it is also possible to model the product by choosing:

  • The most produced size, or

  • The heaviest size.

 

Packaging Information

How should I manage packaging information?

Product-related packaging information is required for compliance with AGEC law. It may be necessary to establish specific rules according to product category. You have two options:

  • Define rules together by product category
  • Send us all available packaging information for all your products
How do I determine my response for the compostability, recyclability, and possibilityReUse columns?

This corresponds to what has been declared to the relevant French Extended Producer Responsibility (EPR) organization (e.g., Citeo, Adelphe, Léko). Find more details on our Knowledge Hub here and on the government website here.

 

Product Images

Can I send images after the initial import?

Yes, you can send us product images afterwards without any issue. This won't block the initial import process.

What format is expected?

A file containing the images must be sent or shared in .png or .jpeg format.
The images must be named using the product reference and its color code.

This information can also be sent directly via the API using the picture field, which expects a URL format.

 

QR Codes

Is it possible to obtain QR codes before production?

Yes, it's possible to have QR codes in advance. You'll need to request this from your analyst. You'll then need to add a qrCode column in your spreadsheet (BDC) with the chosen link corresponding to each relevant product.

You are responsible for the correct qrCode / Product Analysis association.

If you are confident about the product data but are still waiting for component information, for example, you may also import the products in advance. This way, you will be able to retrieve the QR codes upon product creation (via API) or through the QR Codes extract available on the platform.

 

Transaction Certificates

How should I organize references for collecting transaction certificates?

You can work with the material-PO reference to collect transaction certificates for materials.

 

Custom Extracts

Can I obtain specific export formats?

Standard extracts are available on our platform. If you need a particular extract that isn't offered, you can make an internal request to our teams, who will study the feasibility and potential additional cost.

 

Cegid Integration

Is there an integration with my Cegid system?

Yes, a standard BDC extract is currently in development with Cegid. If you're using Orli v25, this integration might interest you. Don't hesitate to contact us to learn more.