Independent AI agent for EU Deforestation Regulation compliance, not affiliated with the EU. Scope & disclaimer →
eudr.dev

Penalties and enforcement

The Regulation leaves penalty design to the Member States (Art. 27) but sets a floor: "effective, proportionate and dissuasive." In practice this means substantial fines, confiscation of the non-compliant consignment, and temporary exclusion from the EU market.

Member-State competence (Art. 27)

Each Member State designates a competent authority (Art. 14) to police compliance within its territory. The competent authority can:

Penalty floor (Art. 27(2))

The Regulation lists the minimum penalty types Member States must include:

Public registry of penalties (Art. 27(3))

Member States publish, by Member State, the final penalty decisions taken against legal persons under EUDR. The decisions are made public on the Member State's competent-authority website and remain available for at least 5 years.

Substantiated concerns (Art. 31)

Any natural or legal person can submit a "substantiated concern" to the competent authority alleging that a specific operator is failing the Regulation. The authority must investigate without undue delay; the complainant has a right to be informed of the outcome.

For NGOs and civil-society bodies this is the primary enforcement lever. It sidesteps the Member State's internal prioritisation and forces an investigation.

Check rates (Art. 16)

Member States must check a minimum percentage of operators sourcing from each country tier, per year:

Country tierMinimum check rate
Low risk1 % of operators
Standard risk3 % of operators
High risk9 % of operators AND 9 % of the quantity of each relevant commodity.

Plus an obligation to check operators after every substantiated concern (Art. 31(5)).

What eudr.dev does and doesn't do for enforcement

The engine produces signed receipts that an operator can hand to a competent authority as evidence of due-diligence. The receipt is offline-verifiable (BLAKE3 + ed25519 + CIDv1). The regulator does not need to call our infrastructure to confirm authenticity. See verify offline.

The engine does not report operators to competent authorities, file substantiated concerns, or initiate any enforcement action. Those are competent-authority and complainant prerogatives respectively.

What an enforcement-friendly receipt contains

The signed receipt is designed to make a regulator's job easier:

A competent authority running an Art. 18 check can take the receipt, the operator's records, and re-verify the entire chain against emem.dev independently.

See also

Authoritative sources