> For the complete documentation index, see [llms.txt](https://docs.live-eo.com/tradeaware/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.live-eo.com/tradeaware/using-the-tradeaware-web-app/products-and-plot-linking.md).
# Products and plot linking
Product-to-plot linking lets you prepare your EUDR data at the level of the products you trade. A buyer lists the products they buy and asks the suppliers who deliver each product which plots it comes from. Each supplier links its plots once, and the buyer's transactions for that product use those plots for the Due Diligence Statement (DDS). Nobody has to pick plots again for every shipment.
### How it works
1. The buyer adds the products they buy on the Products page.
2. The buyer requests plot data from the connected suppliers who deliver each product.
3. Each supplier links the plots that product comes from, with an optional "Mapping valid until" date.
4. The buyer adds the product to a transaction. The supplier and the linked plots are filled in.
Who does what:
What happens
Buyer
Supplier
Add products to the product list
Yes
No
Request plot data for a product
Yes
No
Link plots to a product
No
Yes
Use the product in a transaction
Yes
No
### Choose your guide
* You buy products and need plot data from your suppliers: see [For buyers: request plot data.](/tradeaware/using-the-tradeaware-web-app/products-and-plot-linking/for-buyers-request-plot-data.md)
* A buyer asked you for plot data: see [For suppliers: link plots to your buyers' products](/tradeaware/using-the-tradeaware-web-app/products-and-plot-linking/for-suppliers-link-plots-to-your-buyers-products.md).
Buyers and suppliers both work on the Products page (the tag icon in the left navigation). The Buyer column shows whose product it is: "You (your business name)" for your own products, or the name of the buyer who shared the product with you.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.live-eo.com/tradeaware/using-the-tradeaware-web-app/products-and-plot-linking.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.