> ## Documentation Index
> Fetch the complete documentation index at: https://help.polygon-one.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What Is Missing for This Supplier?

> Supplier gap labels: what each means and exactly what the supplier needs to provide

## Overview

Polygon One keeps a list of missing information for each supplier. These labels control reminder emails. They are **visible** in the supply chain's **Send message** dialog under **Missing compliance elements**, written as complete phrases such as “Geodata missing”, “Critical questionnaire issues” and “Legal documents under review”. In the supply chain itself, each article on a supplier card has three category indicators: **Geodata**, **Questionnaire** and **Legal documents**. **Notify pending suppliers** groups these more broadly into requested areas.

The headings below are this page's **short forms**, not the application's exact labels. The app uses complete phrases for the same points. Short forms make this reference easier to scan.

For each label, this page answers: **What does it mean?** and **What does the supplier need to do?**

> [!NOTE]
>
> Most labels describe **data availability**, not compliance. Three do both: **Questionnaire (critical)** and **Legal documents (non-compliant)** set the affected category to **Non-compliant**; **Invalid geodata** sets it to **Invalid**. Conversely, a supplier with no open data gaps may still have a risk finding — see the [Findings Catalogue](https://help.polygon-one.com/en/eudr/datensammlung/befund-katalog.md).

## Invitation

> [!NOTE]
>
> The two invitation labels exist **only for Tier 1 suppliers**, whose invitations you manage yourself. They are not generated for Tier 2 and above.

### Invitation not sent

No invitation has been sent to this supplier.

* **What the supplier must do:** As with Invitation pending, the reminder asks them to complete the onboarding form. But first you must send the invitation: it is your turn.
* **Your next step:** Send an invitation — see [Supplier Onboarding](https://help.polygon-one.com/en/eudr/datensammlung/supplier-onboarding.md). The supplier needs no account; they receive a secure link.

### Invitation pending

An invitation was sent, but the supplier has not completed it.

* **What the supplier must do:** Complete the onboarding form.
* **Your next step:** Send a reminder. Check invitation history to see whether it was opened. An unopened invitation is more suggestive of a delivery problem than inaction.

> [!TIP]
>
> If invitations are not reaching suppliers, check your [Sending Domain](https://help.polygon-one.com/en/eudr/versanddomain.md). Emails from an unverified sender domain are more likely to land in spam.

## Geodata

### Geodata

For at least one of this supplier's articles, analysis has not produced a usable geodata result. This is the aggregate undecided state. Usually plot coordinates are absent, but plots may also exist without an analysis status yet.

* **Why it matters:** Without plot coordinates, deforestation-free origin cannot be checked. Art. 9 EUDR requires geolocation.
* **What the supplier must do:** Upload geodata for their plots.
* **Your next step:** Request it or import it yourself if available — see [Plot Import](https://help.polygon-one.com/en/eudr/datensammlung/parzellenimport-pruefung.md).

### Invalid geodata

Geodata was supplied but classified as invalid, for example plots overlapping water or built-up land.

* **Why it matters:** The article is **Invalid**. This is a data error, not a risk finding: there is no reliable basis for analysis.
* **What the supplier must do:** Correct the invalid production-plot geodata.
* **Your next step:** Request a correction and name the affected plots. Common causes are reversed longitude/latitude, an incorrect coordinate format or an overly coarse polygon.

## Questionnaire

### Questionnaire

The compliance questionnaire has not been completed.

* **Why it matters:** It determines which legal risks need mitigation for the production country and which documents are relevant. The document list remains incomplete until the questionnaire is answered.
* **What the supplier must do:** Complete the legal compliance questionnaire with their production practices and legal status.

### Questionnaire (critical)

The questionnaire identified critical compliance issues.

* **Why it matters:** These **cannot be resolved by document uploads**. If an answer triggers a risk, the answer must be corrected.
* **What the supplier must do:** Resolve the critical questionnaire issues.
* **Your next step:** Request corrections to the affected questions specifically, rather than requesting the entire questionnaire again.

### Questionnaire (warnings)

The questionnaire flagged potential risks requiring review, without blocking compliance.

* **What the supplier must do:** Review the questionnaire warnings.
* **Your next step:** Optional. You may proceed to DDS with the warning open; it stays visible.

## Legal documents

### Legal documents

Legal documents have not yet been submitted.

* **Why it matters:** Permits and certifications substantiate compliance with local land-use, environmental and labour laws.
* **What the supplier must do:** Upload the required legal compliance documents.
* **Your next step:** Name the precise legal category. A generic “please upload documents” request regularly produces unsuitable files.
* **If the document does not exist:** The supplier can give a reasoned statement. You **Accept statement** or **Reject statement** in the compliance gaps view; accepting does not close the gap — see [Risk Mitigation](https://help.polygon-one.com/en/eudr/datensammlung/risiko-behebung.md#when-the-supplier-says-the-document-does-not-exist).

### Legal documents (pending)

Documents were submitted and are under review; proposed evidence assignments await confirmation.

> [!NOTE]
>
> This label can also originate **upstream**: an upstream supplier's pending legal review sets this label for the current supplier even if they submitted nothing themselves. Check whose review is pending before sending a reminder.

* **What the supplier must do:** Nothing — it is your turn.
* **Your next step:** Confirm or reject the proposed assignments. An uploaded document covers nothing until its use is confirmed.

### Legal documents (non-compliant)

Legal documents were reviewed and assessed as non-compliant.

* **What the supplier must do:** Provide corrected or additional documents.
* **Your next step:** Pass on the review feedback. A supplier cannot fix a rejection without knowing its reason.

## Remind suppliers

### All at once: Notify pending suppliers

Use **Notify pending suppliers** on the **Incoming** compliance dashboard to remind suppliers blocking your process. Each selected supplier receives precisely their open requests. The dialog states that existing requests are resent as reminders.

On opening, the dialog loads one row per pending supplier, with open areas — **Geolocation data**, **Legal documents**, **Legal compliance questionnaire**, **General information**, **Certifications** — and a **requested** marker where a request already exists. Everything that can be sent is preselected; **Deselect all** and **Select all** help choose a subset.

| Unselectable row | Meaning |
| - | - |
| **Not yet invited** | No portal link exists for the reminder to open. Invite first. |
| **No email address** | No address is recorded. Add contact details. |

Under **How would you like to send the invitation?**, select **Send email** (preselected and marked **Recommended**) or **Copy link**. The second option creates requests but sends nothing. The app explains that no email was sent and that you should open the supplier to copy the link.

Afterwards, each supplier shows **Sent**, **Reminded**, or a reason such as **Nothing outstanding**. Above the rows is a summary of sent, reminded and skipped counts. If an email could not be delivered, the row also shows **No email**.

> [!NOTE]
>
> **There is no waiting period between reminders.** A supplier reminded moments ago can be selected again immediately; this is intentional. Control the timing through your selection.
>
> EU-based suppliers are absent from this list: they do not owe you a separate due diligence statement in your role as a downstream operator. When many suppliers are pending, the dialog initially shows a subset and explicitly says so.

> [!WARNING]
>
> **This route cannot reach anonymised suppliers.** You do not have their contact details, and without an address the row cannot be selected. Work through the **upstream supplier** whose invitation protects that supplier's identity.

### Individually: from the compliance gaps view

If a supplier has an open request, **Send reminder (… requested)** appears at the top of the compliance gaps view on **all three tabs**, including **To review**. From an individual article, it is labelled **Remind supplier of all open requests (…)** because it covers **every** open request for that supplier, not just the article's. The same action is also in the request dialog footer.

The supplier receives **one** email covering all open points, with **Reminder: …** in the subject.

If reminders have already been sent, a line below shows how many and the latest time. With zero reminders, this line is absent.

> [!WARNING]
>
> **The application does not block a second reminder.** If the last was less than 24 hours ago, it only asks whether to remind again and shows the previous date. Confirming sends it. You control the courtesy interval.

## An order that saves time

**1. Invite first**

Without a completed invitation, there is no channel for the data to arrive. Address Invitation not sent and Invitation pending first.

**2. Then the questionnaire**

It determines which documents are needed. Asking for documents first often produces the wrong ones.

**3. Then geodata**

Satellite analysis needs plots. Only afterwards do you know which geo risks require further evidence.

**4. Finally, documents**

You now know the open legal categories and the plots each document must cover. Requests at this stage are precise and rarely need repeating.

## Related pages

> **[Supplier Onboarding](https://help.polygon-one.com/en/eudr/datensammlung/supplier-onboarding.md)**
>
> Invite suppliers and request information.

> **[Supplier Requests](https://help.polygon-one.com/en/eudr/datensammlung/update-anfragen.md)**
>
> Targeted correction and evidence requests from risk mitigation.

> **[Findings Catalogue](https://help.polygon-one.com/en/eudr/datensammlung/befund-katalog.md)**
>
> Individual findings in the compliance gaps view.

> **[Status Glossary](https://help.polygon-one.com/en/eudr/status-glossar.md)**
>
> What article and supplier compliance statuses mean.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.