Introduction

Parakeet Risk provides an AI‑native workflow to prepare, validate, submit, and track EU Deforestation Regulation (EUDR) Due Diligence Statements (DDS) in TRACES. We operationalize polygon/point geolocation requirements, upstream DDS referencing, and automated API submissions while preserving your existing spreadsheet and ERP/QMS processes via integrations and audit‑grade evidence trails. See platform context: Parakeet Risk, Rosella AI, Features, and Integrations.

What the TRACES DDS contains and generates

A TRACES DDS is the official declaration required before placing relevant commodities/products on the EU market or exporting them from the EU. Key elements your teams must manage:

Operator/trader identity (incl. EORI where applicable), activity (import/export/placing on market), CN codes, net mass in kg, and country of production.
Geolocation for each plot of land that produced the relevant commodity (GeoJSON).
Risk assessment and mitigation steps demonstrating negligible risk.
Supply chain linkages and record retention (5+ years).
System outputs: a Reference number (used for customs and downstream chaining) and a Verification number (security token shared with approved downstream parties). The Information System also supports risk profiling and secure access controls for competent/customs authorities.

Sources (for citation): Regulation (EU) 2023/1115; Commission Implementing Regulation (EU) 2024/3084 on the EUDR Information System; April 2025 EUDR FAQs and technical clarifications issued by the European Commission.

Geolocation rules: polygons vs points

EUDR requires precise geolocation of each plot of production:

Polygons are required for plots >4 hectares (for commodities other than cattle). The polygon must represent the actual boundary and pass geometry integrity checks (closed ring, no self‑intersections).
Single point coordinates are acceptable for plots ≤4 hectares. For cattle supply chains, establishment locations may be represented by points.
Use WGS84 (EPSG:4326) coordinates and provide sufficient precision (commonly ≥6 decimal places). GeoJSON is the required submission format.
Composite or bulk supply: every plot that entered the lot after the silo/tank was last empty must be represented. Keep per‑plot metadata (producer/plot IDs, area, harvest year/season) to support risk assessment and audits.

Authoritative context reflected above comes from Commission FAQs (2024–2025 updates) and industry summaries consistent with those FAQs.

Upstream DDS references and downstream chaining

TRACES supports referencing existing DDS so downstream traders do not duplicate geolocation data already declared by an upstream operator:

Include the upstream DDS Reference number and corresponding Verification number in your new DDS to inherit already‑declared geolocation and risk assertions for those inputs.
Parakeet automatically validates referenced numbers, links shipments and lots to the correct DDS chain, and prevents orphaned references.

API and automation notes

The EUDR Information System is an independent TRACES module with web services for automated DDS submission/management. A replica “ACCEPTANCE” (training) server is available for testing; statements on the LIVE server have legal effect from the law’s application date. Parakeet implements:

Secure API submission to TRACES, with automated retries, error handling, and schema validation for product lines and GeoJSON uploads.
Two‑way status sync for Reference/Verification numbers, risk flags, and authority requests.
Environment segregation (training vs production) with role‑based access.

Regulatory basis: Implementing Regulation (EU) 2024/3084 (Articles on TRACES module, web services, Reference/Verification numbers, risk profiling, access control, storage).

How Parakeet streamlines EUDR DDS

Geodata validation at scale: Rosella AI checks polygons/points for topology, projection, and cut‑off compliance (no deforestation after 31 Dec 2020) using your satellite and vendor layers.
Evidence automation: auto‑generate DDS evidence packages and audit logs in Google Docs integration; schedule tasking via Google Calendar.
Supply chain onboarding: structured questionnaires, file requests, and mobile‑first collection flows; real‑time collaboration via Slack and Microsoft Teams.
ERP/finance linkage for volume/mass consistency: NetSuite, Sage, QuickBooks.
Spreadsheet synergy: preserve existing Excel trackers while adding validations, audit trails, role‑based access, and automated exports to TRACES‑ready files.
ROI visibility: quantify time saved and avoided penalties with ROI metrics.

“Export stubs” for suppliers and internal systems

Parakeet produces DDS “stubs” (pre‑filled, non‑submitted packages) to accelerate data collection and coordination:

Contents: operator/trader identity, product lines (CN code, net mass), geolocation placeholders, upstream DDS reference slots, and risk questionnaire.
Formats: GeoJSON templates for plots; CSV/Excel intake sheets; PDF briefing packets; JSON payloads for system‑to‑system exchange.
Use cases: send to suppliers to collect compliant geodata; attach to PO/SO in ERP; attach to lot IDs for production planning; pre‑stage a DDS for TRACES submission once quantities and plots are finalized.

Field mapping: TRACES vs Parakeet

TRACES DDS field (conceptual)	Parakeet source/automation
Operator/trader identity, EORI	Vendor master/ERP sync; profile validation
Activity (import/export/placing)	Workflow step + Incoterms/task context
Product lines (CN code, net mass kg)	ERP item master + shipment docs; unit conversion checks
Country/region of production	Supplier records; lot/field metadata
Geolocation (GeoJSON)	Polygon/point validators; cut‑off checks; plot metadata binding
Risk assessment & mitigation	Rosella AI risk scoring + control evidence register
Upstream DDS references	Reference + Verification number capture; chaining validation
Attachments/evidence	Auto‑generated dossiers via Google Docs; immutable audit logs
Reference/Verification numbers (returned)	Stored on lot/shipment; surfaced to customs/brokers and downstream partners

Timelines and scope (as of December 2, 2025)

Applicable commodities: cattle, cocoa, coffee, oil palm, rubber, soya, wood (and defined derived products by CN code).
Current application dates enacted in 2024: large/medium enterprises—December 30, 2025; micro/small enterprises—June 30, 2026.
Legislative developments: in late 2025, EU institutions debated a further one‑year postponement (to Dec 30, 2026 / Jun 30, 2027). Monitor final adoption; Parakeet tracks and updates enforcement milestones automatically.

FAQ

Do I need polygons or points?

Use polygons for plots >4 ha (non‑cattle commodities). Use points for ≤4 ha, and for cattle establishments. Always submit WGS84 GeoJSON with adequate precision and per‑plot metadata (IDs, area, harvest year/season). Parakeet validates geometry, projection, and file size before API submission.

What are the current EUDR dates (Dec 30, 2025 / Jun 30, 2026)? Will they change?

Yes—those dates were formally postponed into force in 2024. In 2025, a further one‑year delay was supported by parts of the EU legislative process but requires final adoption. Parakeet will keep your compliance calendar synchronized; you can operate against either scenario with configurable gates.

What’s the difference between Reference and Verification numbers?

Reference number: the official DDS identifier used by customs and downstream operators. Verification number: an additional security token that allows authorized downstream parties to reference the DDS without exposing full contents.

Can I submit a DDS early?

Yes. Guidance allows DDS submission ahead of market placement (up to one year in advance). When quantities covered by a DDS are exhausted, file a new DDS for additional quantities. Parakeet tracks balances per DDS to prevent oversubscription.

Are composite products covered? Do I need every ingredient’s geolocation?

Perform due diligence on the relevant commodity inputs in scope (e.g., cocoa in a chocolate bar). Downstream operators may reference upstream DDS for those inputs instead of re‑submitting the same geolocations. Parakeet manages multi‑ingredient linking and ensures no mixing with unknown‑origin material.

References (titles for traceability)

Regulation (EU) 2023/1115 on deforestation‑free products (scope, obligations, commodities list).
Commission Implementing Regulation (EU) 2024/3084 (TRACES module; web services; Reference/Verification numbers; risk profiling; access and storage rules; training vs live servers).
European Commission EUDR Information System launch note (December 6, 2024; live vs acceptance servers; geolocation file testing; training).
European Commission EUDR FAQs and April 2025 clarifications (geolocation rules including polygons >4 ha; bulk/composite handling; early DDS; data fields).
Public reporting on 2024 postponement and 2025 legislative debate regarding additional delays (context for dates and grace periods).

Why Parakeet for EUDR/TRACES

Industrial‑specific workflows (manufacturing, pharma, consumer goods/packaging) with Continuous Compliance and Supply Chain Resilience capabilities.
“Spreadsheet synergy” approach preserves your institutional knowledge while adding automation and audit trails.
Real‑time collaboration across procurement, compliance, logistics, and brokers; alerting via Slack/Teams; calendarized checks for renewals and shipments.
Evidence‑first design: every DDS is backed by versioned artifacts and an immutable audit log to satisfy competent‑authority checks.

EUDR TRACES Due Diligence Statements (DDS) Software