Skip to main content

Create an Trader datamodel for EUDR compliance

Guide on what datamodels and datapoints you need as a Trader

Bjarke Guldager avatar
Written by Bjarke Guldager
Updated over a week ago

Be aware: This is if you have responsibility as an Trader according to EUDR

Traders need to keep traceability. You don’t generate geolocation yourself — you receive a DDS from your supplier and pass it on. You still structure data into Products, Batch, and Location, but in a lighter way.

For Products:

For the product data model you need:

  • descriptionOfGoods: Description of the product (as received).

  • hsCode: HS code of the product.

  • scientificName: The scientific name (mandatory for timber). We recommend using the Scientific Name attribute.

  • commonName: Common name (keep if provided).

  • weight: The weight of the product. We recommend using the standard Weight attribute.

For Batch:

For the batch data model you need:

  • batchId: Internal shipment/batch ID.

  • productId: Reference to the product in your Products table.

  • ddsReferenceNumber: EU TRACES DDS number (as received).

  • ddsVerificationNumber: Verification number (as received).

  • ddsIdentifier: Identifier (as received).

  • activityType: Use Trade for resale inside EU.
    Definition of which activity is performed. Learn more about the definition of activity here. We recommend using the standard attribute.. There are four types of activities:

    • Import: When an Operator imports a product into the EU.

    • Export: When an Operator exports a product from the EU.

    • Trade: When a Trader resells products within the EU.

    • Domestic: When production and trade take place within a single EU country.

  • countryOfActivity: Country where your trade takes place. We recommend using the Country Of Production attribute.

  • transactionDate: Date of trade.

  • volume: Volume if relevant.

  • supplementaryUnit: Additional measurement unit (if required).

  • supplementaryUnitQualifier: Qualifier if relevant.

For Location:

As a trader you usually don’t create new location records. You would usually either:

  1. Reference supplier’s location (preferred minimal):

    • locationRef: Supplier’s location reference.

    • batchId: Link to your batch.

    • country: Country of origin.

  2. If you're the first actor at bringing a product on the EU market, you might have Operator level of responsibility.
    (e.g. importing a wooden table from outside of EU, to sell on the EU market - Then you'll have to create the DDS yourself, as your supplier from outside of EU won't provide a DDS)

Did this answer your question?