> 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/for-suppliers-link-plots-to-your-buyers-products.md).

# For suppliers: link plots to your buyers' products

This page is for suppliers. To request plot data from your own suppliers, see For buyers: request plot data.

### What your buyer is asking for

Your buyer has added a product they buy from you to TradeAware and shared it with you. They're asking which of your plots that product comes from. You answer once per product: your buyer then uses the plots you linked for every shipment of that product until you change them.

Important: before you start

* You must be connected to the buyer. See [Connect with your supply chain](https://docs.live-eo.com/tradeaware/using-the-tradeaware-web-app/connect-with-your-supply-chain).
* You can only link plots your own business owns. Plots that belong to your own suppliers can't be linked to a buyer's product.
* If the plots aren't in TradeAware yet, you can import them while you link (see below), or first upload them as described in [Upload and Analyzing Plots](https://docs.live-eo.com/tradeaware/using-the-tradeaware-web-app/upload-and-analyzing-plots).

### Find the request

* From the notification. You see "*\[Buyer] is requesting plots for \[product name]"* in your notifications. Select Go to to open the plot selection for that product directly.
* From the **Products page.** Select Products in the left navigation. Products shared with you show the buyer's name in the Buyer column. Open the row menu and select Link plots.

<figure><img src="https://1342046618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbenSEfMyYbRWLaKU6iTs%2Fuploads%2FTfWpOGnBZM3N7q7RMGSl%2FScreenshot%202026-10-07%20at%2015.11.57.png?alt=media&amp;token=9f73029c-1643-4144-9ef6-75dda3ce36da" alt="" width="375"><figcaption></figcaption></figure>

### Link plots to the product

The window Select plots for \[product name] lists your plots.

<figure><img src="https://1342046618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbenSEfMyYbRWLaKU6iTs%2Fuploads%2FASFH7HpUCRUxdO6ZLDpd%2FScreenshot%202026-10-07%20at%2015.13.12.png?alt=media&amp;token=311b2732-7182-4914-a53b-a5f9d57f50c1" alt="" width="375"><figcaption></figcaption></figure>

1. Find the plots. Only plots whose commodity matches the product are listed, for example cocoa plots for a cocoa product. Use the All plots and EUDR Compliant tabs, the search (name, ID, country or commodity) and the filters to narrow the list. For each plot you see Name, Commodity, Country, Area (ha), Risk and Status.
2. Tick the plots this product comes from. The tick box in the header selects every plot shown. The line at the bottom shows how many plots you selected and their total area.
3. Set "Mapping valid until" (optional). The date until which this selection holds, for example the end of your current sourcing season or your annual review. It is for information: your buyer sees it, and the product shows Expired once the date has passed.
4. Select Save and share. Your buyer is notified that you mapped plots to their product.

If none of your plots match the product's commodity, the window shows "No matching plots". Check that the product's HS code fits what you supply, and that your plots carry the right commodity.

#### Add new plots while you link

Select Import plots to upload new plots without leaving the window. It's the same import as on the Plots page. If your file contains plots that are already in your account, those rows are reported as already existing and the rest are imported. The new plots then appear in the list, ready to tick.

### Keep your answer up to date

* To change the plots or the date, open the product again with Link plots. Your current selection is already ticked. Change it and select Save and share. Each save replaces your previous selection for that product.
* Your buyer is notified when you add plots, not when you only remove plots or change the date.
* If you delete a plot, it's no longer linked to any product.
* If your buyer stops sharing a product with you, it disappears from your Products page and your links for it are removed.

### What your buyer sees

Your buyer sees the plots you linked (name, commodity, country, area, risk and status), the number of plots and your "Mapping valid until" date. You only ever see your own entry for a product, never the buyer's other suppliers.

### If you supply several buyers

Each buyer's product has its own link. If several buyers buy the same product from you, link the plots to each buyer's product separately.

### Good to know

* You can link up to 1,000 plots to one product.
* Link only the plots the product actually comes from. Your buyer declares these plots in their Due Diligence Statement, and every declared plot has to meet the EUDR requirements.

<br>


---

# 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/for-suppliers-link-plots-to-your-buyers-products.md?ask=<question>&goal=<user_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.
