Product Data Upload (EUDR Context)

Prewave evaluates product data to ensure compliance with EUDR requirements across a diverse range of items. A product dataset is defined as the unique combination of your product reference and the corresponding supplying site reference. Product datasets can pertain to:

Inbound products (Import, Domestic (EU))
Outbound products (Export, Domestic (EU))
Associations between inbound and outbound products

Prewave offers a streamlined process for uploading product data using designated templates. Please ensure that all product data is complete and accurate prior to submission, as this information is critical to comply with EUDR.

Please download the EUDR Discovery Template here.

Data Fields & Requirements

The full list of parameters can be found in the template. The color coding is consistent throughout this export and the template:

🟩 Green → Mandatory fields
🟨 Yellow → Optional fields
🟦 Blue → Mandatory by Traces but optional for project start

Input Supplier

Please not that each supplier needs to be validated by our automatic systems or in difficult cases by our team. Validation is a prerequisite to add your supplier to our public network and therefore unlock them for supplier engagement (SMA send-out and POR send-out).

The validation of a supplier may take up ot 5 business days and does not happen immediately.

You can consult other Discovery Template article only about supplier input requirements for more details.

Field	TYPE	Description	Example	Explanation
connection_type	ENUM	How the Site is associated with your organization. The allowed values are: SUPPLIER, CUSTOMER and OWN.	SUPPLIER, CUSTOMER, OWN_BUSINESS	To steer certain system behavior your relationship type needs to be defined. This makes sure your are only presented with relevant actions and features.
your_reference	TEXT	A textual identifier that uniquely identifies a Site connected to your organization.	C12345	To ensure cross system referencing between Prewave and your systems.
site_details_name	TEXT	The human-readable name for the site.	Prewave GmbH	For easy target recognition in the system.
country_code	CHAR(2)	Alpha-2 ISO Code of the address. See https://www.iso.org/obp/ui for details.	AT	Crucial for trade scenario detection and target validation.
locality	TEXT	Refers to the city/town portion of the address. In regions of the world where localities are not well defined or do not fit into this structure well, use closest locality instead.	Vienna	Crucial for target validation.
address_line	TEXT	Unstructured address lines describing the lower levels of an address. Usually this is a street name and house number.	Rothschildplatz 4, Austria Campus 4/3rd Floor	Crucial for target validation.
postal_code	TEXT	Postal code of the address. Not all countries use or require postal codes to be present, but where they are used, they may trigger additional validation with other parts of the address.	1020	Beneficial for an improved target validation success rate. Reduce your validation reject rate and provide the postal code wherever you can.
industry	TEXT	The industry which is relevant for your Site. Multiple industries can be added separated by a semicolon (;). These values will be mapped to Prewave industries or commodities.	IT / Software	Relevant for peer score obtention. Relevant for use cases like LkSG, CS3D or disruption, but NOT for EUDR.
website	TEXT	The authoritative website for this site, such as a business' homepage.	prewave.com	Beneficial for supplier validation success rate.
contact_1	TEXT	E-mail of the Site’s contact to complete to send out product origin requests.	[email protected]	Necessary for Supplier engagement. Try to provide the inboxes of real people and avoid generic inboxes.
contact_2	TEXT	Additional field to contact_1. Values will be joined together.	support @prewave.ai	Necessary for Supplier engagement. Try to provide the inboxes of real people and avoid generic inboxes.
contact_3	TEXT	Additional field to contact_1. Values will be joined together.	support @prewave.ai	Necessary for Supplier engagement. Try to provide the inboxes of real people and avoid generic inboxes.
external_reference_id	TEXT	External unique site identifier number.	300533068	Beneficial for cross system referencing with current or future partners of Prewave.
external_reference_type	TEXT	Required if external_reference_id is stated. Reference to the source of the unique site identifier.	DUNS, TAX, EORI etc.	Let us know to which system the previous identifier refers to.
collection_name	TEXT	The collection in which you want to group your Site. Multiple collections can be added separated by a semicolon (;). These collections can be mapped to Prewave industries or commodities for scoring.	IT-Suppliers;Grouping-A;Austrian Suppliers	Very helpful if you have to manage many suppliers and want to group them by internal responsibility, send out campaigns, project phases etc. Collections can be used anywhere in Prewave for target filtering.
prewave_id	INTEGER	A positive number that uniquely identifies a Prewave Site. If set, site_details_name, country_code, locality and address_line can be skipped.	6640371	Can be provided for instant matching and skipping validation.

Input Inbound

Inbound product information are needed to start engaging with your suppliers. Therefore each product needs to be associated with a supplier. Once the system knows this connection product origin requests can be send out in order to obtain the desired DDS reference numbers or product origins.

Leverage the product group field for an improved DDS generation experience! Providing the respective legal entities handling your inbound products will make you benefit from prefilled legal entity fields.

Field	Type	Description	Example	Explanation
your_inbound_product_reference	TEXT	Unique product identifier in your system.	INB-00123	Necessary for cross-system referencing.
your_inbound_product_name	TEXT	Name of the purchased/produced product.	Steel Rods	Improved product recognition.
hs_code	VARCHAR(4-6)	Harmonized System code for the product.	730890	Steering system behavior and product validation. Minimum 4 digits and all codes longer than 6 digits will be shortened to maximum 6 digits.
Scientific_name	TEXT	Necessary for all wood related Products. Mulitple genus can be separated by ";"	Genus species ✅ Quercus robur ❌ Wood	Only needed for wooden products and mandatory for TRACES submission.
your_site_reference	TEXT	Unique identifier of the supplying site.	SITE-9876	Necessary for supplier engagement.
product_group	TEXT	Name of Product Group (Buying Entity), multiple inputs can be provided by ";" separation	Prewave	Connecting product to product group or legal entity.

Input Outbound

The outbound product refers to the products leaving your sites.

The outbound product has a reduced input array, because many information will be referenced from the inbound products.
Leverage the product group field for an improved DDS generation experience! Providing the respective legal entities handling your outbound products will make you benefit from prefilled legal entity fields.

Field	Type	Description	Example	Explanation
your_outbound_product_reference	TEXT	Product/Good Identification Number from your Internal System	INB-00123	For cross-system referencing
your_outbound_product_name	TEXT	Name of your Outbound Product/Good	O-Ring	Improved product recognition.
hs_code	TEXT	Harmonized System code for the Outbound product.	4411000	Steering system behavior and product validation.
Scientific_name	TEXT	Necessary for all wood related Products. Mulitple genus can be separated by ";"	Genus species ✅ Quercus robur ❌ Wood	Only needed for wooden products and mandatory for TRACES submission.
product_group	TEXT	Name of Product Group (Selling Entity), multiple inputs can be provided by ";" separation	Prewave, Dealership A etc.	Connecting product to product group or legal entity.

Inbound-Outbound Mapping

For Outbound DDS creation it is important that Prewave knows which inbound products are bound to which outbound products. Following the rule if all inbound products are compliant the outbound product will also be, we can then reference from your outbound product to the respective inbound products and clear your outbound product.

Field	Type	Description	Example	Explanation
your_outbound_product_reference	Mandatory	Product/Good Identification Number from your Internal System	INB-00123	Connect Inbound to Outbound
your_inbound_product_reference	Mandatory	Product/Good Identification Number from your Internal System	INB-07583	Connect Outbound to inbound
your_site_reference	Mandatory	Unique identifier of the supplying site.	AB19210	An inbound product can be supplied by multiple suppliers. To identify the correct inbound source, the supplier site reference is needed.

Product Group as Legal Entity

Product Groups in Prewave are also designed to represent the legal entities handling the products on the inbound and/or the outbound side. Providing Legal entities improves your product handling in the DDS process, as your DDS modal will be already filled out with the legal entity information needed for DDS submission. Product Group to Product mapping is done in the inbound and outbound product entries.

The EORI (Economic Operators Registration and Identification) number is a mandatory requirement for all entities involved in cross-border trade within the EU. In this tab, you will need to provide key entity details such as company name, address, country, and the valid EORI number.

This information ensures that entities can be uniquely identified for compliance purposes and for entry into the EU TRACES system under EUDR. Please ensure that the EORI number follows the required format:

Example: FR12345678900014

Field	Type	Description	Example	Explanation
product_group_name	TEXT	Alias or abbreviated more readable identifier for your Legal Entity	Prewave AUT1	This value is used as key for the product-product group mapping in the inbound and outbound Input
Entity name (string)	TEXT	Name of the Entity	Test GmbH
Entity street + house # )	TEXT	(alpha numeric string)	One Street 12/3
Entity City	TEXT	City Name of where the Entity is located	Vienna
Entity Zip	TEXT	Postal Code Name of where the Entity is located	10231
Entity country	VARCHAR(2)	2 digit iso code	AT
eori number	TEXT	[CountryCode][Up to 15 alphanumeric characters]	FR12345678900014

Important Considerations when providing data

Unique Identification: The combination of your product reference and your site reference must be unique to generate a distinct product dataset.
EUDR-Specific Requirement: Each supplier must have at least one designated connection contact to support supplier engagement activities. This includes sending out questionnaires (SMA) and requests for product origin information.
Mandatory Inbound–Outbound Association: Every outbound product must be linked to an inbound product record, ensuring a complete and verifiable dataset for EUDR compliance.
HS Code Requirements: For products with specific HS Codes (e.g. 44, 47, 48, 49, 9401, 9403)—particularly wood-related items—the inclusion of a scientific_name is mandatory to satisfy EUDR standards.
Supplier data as a prerequisite for product upload: Prior to uploading any product data, ensure that that the respective supplier information has already been uploaded and a validation has been requested on the Prewave Platform.

By following these guidelines and using the designated templates, you enable us to process your product data accurately for EUDR compliance.

Change Log

New Product Groups (July 2025)

Product Groups work in a similar way to collections but are specifically designed for products uploaded to Prewave. They allow you to create logical groupings of products depending on your internal use cases.

Examples of grouping include: