Brazil is the world's largest soybean producer and the EU's biggest single source of soy products. It is also where EUDR's 2020 cutoff does the most work, because Brazil's soy sector already runs a private deforestation regime, and the two do not match. This page adds the Brazilian specifics to the soy guide: the Cerrado gap, the CAR data advantage, and what a compliant bulk cargo looks like.
The moratorium is not the regulation
Since 2008 the Amazon Soy Moratorium has kept the major traders from buying soy grown on newly deforested land in the Amazon biome. It works, but it maps poorly onto EUDR. The moratorium covers one biome; EUDR covers every plot. The moratorium's cutoff is 2008 in the Amazon; EUDR's is 31 December 2020 everywhere. Above all, the Cerrado, where most recent conversion for soy has happened, has no moratorium at all. Matopiba frontier municipalities have seen extensive post-2020 clearing of native vegetation for cropland, so this is where your screening attention belongs. One nuance cuts in your favour: EUDR's forest definition (FAO-based) covers dense cerradão woodland but not open savanna formations, so "cleared Cerrado" and "deforestation under EUDR" are not synonyms. Convergence of evidence, not a single loss layer, separates the two; the risk assessment guide covers how.
Geometry: polygons exist, ask for them
Brazilian soy farms sit far above the 4-hectare line, so polygons are mandatory, and they already exist twice over: every rural property holds a CAR registration with its boundary polygon, and the major traders maintain farm databases built for their own commitments. The negotiation is about release, not creation. Contract for the polygon set per origination area or elevator, cross-check it against CAR records, and validate the geometry before it goes anywhere near a filing. Watch the property-versus-plot distinction: EUDR wants production plots, and on a 10,000-hectare fazenda the soy blocks and the reserva legal are different places with different histories.
Bulk cargo, one statement
A vessel of soybeans or meal is one placing on the market and can carry one DDS, with the polygon file covering every contributing farm. The practical constraints are volume-shaped: TRACES caps producers per statement and total geolocation payload per DDS, so a cargo aggregating thousands of farms needs a deliberately compact file (simplified polygons, no needless vertices) or a split across statements. Traders increasingly sell "EUDR-ready" segregated flows where a defined farm set feeds a defined chain and the file travels with the parcel; buying that product moves the data problem upstream, but the filing and the negligible-risk conclusion remain yours.
Legality: the Forest Code layer
As with Brazilian coffee, legality under Article 3 pulls in the Forest Code: legal reserves, protected riparian strips, and IBAMA embargoes. An embargoed farm is a legality fail even where the soy blocks predate 2020. Embargo lists are public and coordinate-searchable; run every polygon against them as part of screening.
Sequence for Brazilian soy buyers
- Contract polygon files per origination area, with CAR numbers for cross-checking.
- Screen against the 2020 cutoff with Cerrado-aware evidence layers, plus embargo and protected-area checks.
- Budget file size: compact geometry, or split statements for large cargoes.
- File in TRACES per cargo and archive the polygon set with the screening run.
Argentina presents the same crop with a different frontier (the Gran Chaco) and a sector-wide traceability platform; Brazilian timber shares the CAR and embargo infrastructure described here.