Skip to main content

EUDR: Completing the Product Origin Request (POR)

This article gives you an overview about what an EUDR product origin request is and how to use this feature within Prewave.

Sabine avatar
Written by Sabine
Updated over 2 weeks ago

Understanding Product Origin Requests

As the name already indicates, the Product Origin Request status provides details on where your product, or parts of it, originate from. In accordance with EUDR regulations Article 9, 1 (d) and to fulfil Due Diligence obligations, you are required to trace the product back to its origin. Product Origin Requests (PORs) are an essential tool to help businesses follow the EU Deforestation Regulation. They make sure that products imported and sold in the EU are not linked to deforestation, helping companies stay compliant, protect the environment, and build consumer trust.

How to request a Product Origin Request

There are three possible ways of adding a POR within Prewave:

Those three possibilities are to be found in the "Origins" column:

1. Status label

When clicking on the "Missing" status label, the below mask opens and will walk you through different steps to request an origin from your supplier via email:

You can here add additional information to your product, such as purchase order, shipment number and other information, which are all optional but recommended.

In the next step you will be asked to add the supplier's contact email, which you either already uploaded in the system and will auto populate or which you need to add by clicking on the "Add contact" button.

The third step here will be to adjust the email you're sending out by adding a comment to the email, selecting a copy to be sent to yourself or adding other emails in CC. A benefit of customizing your email can be to make your outreach more engaging and personalized.

Once you've made your selection you can finish the process by clicking on the "Send Request" button.

2. "+" symbol

If you have all necessary information yourself, you can add the origin information by clicking on the "+" button.

The form will ask you to fill in a production place description, a producer name*, the country of production*, a production date, the plot* and the plot area in hectare (ha) wherein all fields with a * are mandatory.

When entering the plot information, you can do so by either copy pasting information into the plot field or drawing a polygon directly on the map on the right hand side. You would need to further zoom in on your plot and then use the polygon tool to draw on the map. When drawing a polygon you need to make sure to end your shape where you started it by clicking again on the start point. You can also use the trash can item in order to delete the polygon you have already been drawing and start fresh.

The plot field will then automatically be populated by the information you've been drawing on the map. The plot area in hectare (ha) is automatically going to be populated when either drawing a polygon or pasting the data into the plot field. Once you've entered all the mandatory information you can save your selection and the origin will be added to your product.

3. "Import" symbol

You can also import a file in order to add an origin to your product. The only supported file type is .json and .geojson:

What status can my Product Origin Request be in?

There are 4 possible statuses that can appear:

Status

Explanation

Label

Missing

Whenever you create an inbound product, the “Missing” status in the “Origins” column will appear.

Requested

Once you have sent a POR to your supplier, the status “Requested” will be visible.

Rejected

This status will show whenever your supplier answered your POR and stated that the product you requested isn’t EUDR relevant.

Number of origins

This will show how many origins you have added for one product.

POR responses a customer can expect

Origins provided

When requesting a product origin request from a supplier, they might either provide the reference and verification number of a Due Diligence Statement (DDS) to indicate the product is covered, or confirm that the product is not covered by a DDS and provide the origin information through drawing on the map, Geojson data, or an uploaded Geojson file. The provided origin details will then be displayed in Prewave. You can expand the origins to view more detailed information about the provided data.


Origins rejected

If a supplier responds to a product origin request with “the product is not EUDR-relevant”, they must select a reason for this assessment and provide supporting proof. On the Prewave platform, the origins column will indicate that the origin was rejected. By hovering over the (1) “Rejected” label, you can view the reason provided (e.g., “The product is made from recycled materials”). (2) Clicking on the “Rejected” label will display additional details, including the date the origin request was sent, along with reference numbers such as PO, SN reference. (3) By clicking on the “eye icon“, a window will appear where you can view the supplier's comment explaining why the origin request was rejected, along with the supporting document for proof. (4) Clicking on the file icon will allow you to download the attached file provided by the supplier. If the origin information is rejected by the supplier—meaning the geolocation details of all plots of land where the relevant commodities used in the product were produced, along with the corresponding dates or time ranges—has not been provided, then the product cannot be placed on the EU market. This means it will not be eligible for import.

Request forwarded to another supplier

In some cases, the product may not be covered by a due diligence statement, and the supplier may not know the product's origin. In this situation, the supplier can forward the request to the next supplier. The request status in Prewave will remain as “Requested”. Once the supplier receives the origin information from another supplier, they must approve it by clicking “Send”. After approval, the status in Prewave will update from “Requested” to display the relevant origin details.

Did this answer your question?