Severity: Warning. The file may be accepted, but something is probably wrong, or the evidence in your statement is weaker than it should be.
Fixed automatically?: No, this needs a decision only you can make.
In short: Check the units of your source data. This is our own plausibility check, not a rejection reason in the Information System.

What the Information System does

Not a rejection reason in the Information System. This is our own check, with deliberately wide ranges per commodity chosen to catch only obvious units mistakes (Our own check, not an Information System rule).

Why it happens

These ranges are ours, not the regulation's, and they are wide on purpose. For cocoa and coffee the checker questions plots under 0.05 hectares or over 5,000; for oil palm and rubber, under 0.1 or over 50,000; for wood, over 500,000. The full table is on the commodity pages.

Anything outside those bounds is almost never a real plot. It is a units error, a decimal point in the wrong place, or a layer in the wrong coordinate system.

A broken example

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {
        "ProducerCountry": "CI",
        "ProductionPlace": "Enormous",
        "Area": 200000
      },
      "geometry": {
        "type": "Polygon",
        "coordinates": [
          [
            [-8, 5],
            [-3, 5],
            [-3, 10],
            [-8, 10],
            [-8, 5]
          ]
        ]
      }
    }
  ]
}

What the checker reports for this file:

This plot is 30525411 hectares, unusually large for a plot. Check whether the units of your source data were hectares and not square metres. This is our own check, not a reason the Information System would reject the file., line 4, column 5

Before. Centred on 7.5000° N, 5.5000° W.

Fix it in EUDRplot

Set the commodity. Choose the commodity in the checker so the right range is used.
Check the units. A plot in square metres entered as hectares is 10,000 times too big; hectares entered as square metres, 10,000 times too small. A projected layer read as degrees produces absurd areas too.

Fix it in QGIS

Measure the plots. With the project ellipsoid set to WGS 84, add a field ha with $area / 10000 and sort by it to see the outliers.
Check the layer's CRS. Implausibly huge polygons often mean the layer's CRS is wrong. Check Layer Properties › Source.

Try it: check the example, or your own file

Drop a GeoJSON, KML, shapefile or CSV here, or .

Open the full checker

Checked in your browser. The file is not uploaded, stored or sent anywhere.

Sources

Our own check, not an Information System rule, recorded as A5 in our specification notes

Rule PLAUS-003, rule set 2026.09.2. The same rule runs in the checker, the free tools and the command-line tool.

Last verified against these sources on 23 September 2026.