In short, for exporter and importer alike:
- The timeline doesn't move: 30 December 2026 for medium and large companies, 30 June 2027 for micro and small ones.
- Mass balance isn't valid under the EUDR, however carefully it's done: preserved identity is required, batch by batch, and that determines everything that follows in this article.
- Not resolving this has a real cost: penalties of up to 4% of turnover, confiscation of the product, and suspensions of up to 3 working days, extendable while the investigation continues.
- Simplification measures reduce compliance costs by 75%, but those savings don't reach everyone equally: if you move volume from a standard or high-risk country, your burden remains the full one.
- Soluble coffee and certain palm oil derivatives come within the scope of the regulation from 30 December 2027.
The EUDR problem at origin: where batch identity gets lost
Regulation (EU) 2023/1115 requires the seven commodities it covers (including coffee, cocoa, palm oil and rubber) to demonstrate, per shipment, geolocation of origin, no deforestation since 2020, and legality in the country of production, before 30 December 2026 (medium and large companies) or 30 June 2027 (micro and small). That evidence originates at source: on the farm, at the collection point, at the cooperative.
A coffee cooperative receives a request from its European buyer: it needs the complete file for a specific batch, with geolocation of each plot of origin, before the shipment can leave. The field technician has the data, but it's spread across a visit notebook and three different Excel sheets, one per collector who contributed to the batch. Gathering it all and consolidating it into a single document takes days, not minutes. The shipment waits.
That delay isn't a coincidence. Each plot's data (who works it, how many hectares, whether it borders forest) is usually recorded in field notebooks or, at best, in an Excel sheet the technician fills in after the visit. When the product passes through the collection point, it's common for it to be mixed with several farms' output before moving on, and that's exactly where what the regulation truly requires gets lost.
That mixing method is mass balance, and it isn't valid under the EUDR. The Commission's April 2025 FAQ update confirmed the complete end of mass-balance chains of custody, including those used by sustainability certification schemes common in the sector. What the regulation requires is preserved identity: that a specific batch, without mixing with any other of different origin, can be linked to the exact declared plots at every step of the chain. This is what the preserved-identity rule requires when applied to silos and tanks shared by several suppliers.
The technical standard demands precision even from those who want to do it right by hand: for plots larger than 4 hectares, geolocation must be declared as a polygon, with coordinates to six decimal places, and the EUDR information system only accepts the GeoJSON format. Any other format is rejected. An Excel sheet with loose coordinates, however precise, doesn't meet that technical requirement on its own.
The EUDR problem at destination: consolidating what already arrived broken
Whoever receives the product at destination, whether operator, downstream operator or trader, receives it already mixed, in whatever format each supplier chooses to use, and has to consolidate it by hand: one Excel tab per supplier, a different format for each, one person manually translating it all. It's tedious, but it's a downstream problem. The underlying problem comes earlier: if batch identity was lost at the collection point, there's no way to recover it afterwards, whoever receives it. Consolidating better at destination doesn't fix data that was already badly captured at origin.
How to manage the EUDR: the centralised digital system
A centralised EUDR compliance software doesn't replace the need to capture the data correctly at origin, but it changes what can be done with it once it exists. This applies equally whether you're the one capturing it, or the one receiving it at destination: EUDR digitalisation isn't a luxury for just one side of the chain.
With all suppliers and their farms geolocated in a single system, it becomes possible to continuously monitor each plot through satellite analysis, check for any history of deforestation, and assign a risk assessment per supplier and per plot before accepting the volume. Every batch and every transaction is recorded, so batch identity is maintained from collection through to shipment, without relying on manual reconciliation at the end of the process.
This monitoring isn't infallible: the accuracy of the most widely used satellite maps hovers around 85-92%, and none is considered a "reference map" for a competent authority. A centralised digital system doesn't eliminate the need to investigate an alert, but it does let you carry out that investigation with data that already exists, instead of starting from scratch.
The file per shipment (certificate, geolocation, due diligence report) exists per transaction; it isn't put together under pressure when someone asks for it. And it's archived with a date and a record of who verified what, for the five years the documentation retention rule requires, matching the same retention periods the regulation sets for all due diligence documentation.
This doesn't solve a problem if origin data was never captured differentiated by plot in the first place. But if the data exists, even if it arrives in a field notebook or a technician's Excel sheet, a centralised digital system lets you structure it, verify it with continuous monitoring, and keep it traceable instead of losing it in the next mix at the collection point.
EUDR comparison: paper and Excel vs. centralised digital system
| Scattered paper and Excel | Centralised digital system | |
|---|---|---|
| Where batch identity is lost | At the collection point, when mixing product from several plots without recording proportions | Preserved if the data is structured from the moment it's captured |
| Data format | Field notebooks, non-standardised Excel between suppliers, coordinates in invalid formats | Geolocation in GeoJSON format, required by the EUDR system |
| Mass balance | It's the usual method, but it isn't valid as proof, however it's done | Not used; preserved identity is maintained per transaction |
| Deforestation monitoring | Depends on someone manually reviewing each plot, whenever they have time | Continuous satellite monitoring per plot |
| Responding to a request or audit | Searching for the right file, in the right version | The file already exists, per shipment, ready to open |
| Documentation retention (5 years required) | Depends on nobody deleting or losing the file | Archived with date and verification record |
| Consequence in an audit with a 3-working-day deadline | Real risk of not gathering evidence in time, with successive extensions of the block while it's sought | The file already exists; the response is prepared in minutes, not days |
What to do about the EUDR, depending on where you are in the chain
- If you're an exporter, cooperative or producer: confirm that you capture geolocation per plot in a valid format (polygon with six decimals if over 4 hectares), and that you can prove a specific batch wasn't mixed with product of unknown origin at collection.
- If you're an importer, operator or trader at destination: confirm exactly which role you are (operator, downstream operator, trader) and what your specific role requires, before assuming "complying" means the same for everyone.
- If you depend on each other, as is often the case: agree on what data format you'll use before the first shipment, not after the first problem. An Excel sheet that works for origin may not be what destination needs to declare.
Common objections to the EUDR, and why they don't hold up in an audit
"We've worked this way for years and never had a problem."
The EUDR is a new regulation, with a physical traceability standard that didn't exist in the previous rule (the EUTR). Not having had problems so far says nothing about whether the current method can withstand a standard that starts applying on 30 December 2026.
"We already have a sustainability certification, that should be enough."
It isn't enough, and this isn't an opinion: the European Commission itself confirmed in April 2025 that the mass balance used by these certification schemes doesn't satisfy the EUDR's preserved identity requirement. Having a certification doesn't exempt you from this specific point.
"Our volume is small, they're not going to audit us."
Competent authorities are required to apply a minimum number of annual EUDR checks based on the risk level of the country of origin, not the size of each exporting company. If your country of origin is standard or high risk, your company's volume doesn't protect you from being checked that year.
"Changing systems costs time and money."
That's true, and it's a legitimate objection that deserves a real cost comparison, not dismissal. But the cost of sticking with the manual method is also real: manually consolidating data from dozens of suppliers is work that repeats with every shipment. And if it doesn't gather the evidence in time for a check with just a three-working-day deadline, the cost stops being just about hours of work.
"We don't have GPS or good internet on the farm, how are we supposed to digitalise this?"
You don't need professional GPS or a constant connection to capture geolocation with the precision the regulation requires: a basic mobile device is enough, and if there's no coverage at the moment of collection, the point can be saved and synced later.
"We still have months, we can leave it for later."
The timeline is fixed already, it won't move. Setting up data capture at origin, training suppliers on it, and testing it with real shipments takes longer than it seems, and rushing it in the final months is exactly when more mistakes slip through.
How Retexcycle solves EUDR compliance
Retexcycle responds directly to the objections above, not as a generic promise of digitalisation, but as the same opening scenario resolved differently. It works the same way for exporter and importer. Here's how, step by step:
Step 1. With Retexcycle Origins, each producer and their plot are registered and verified at origin, with deforestation risk analysis and attached legal documentation, with no need for professional GPS or a constant connection.
Step 2. Each collection is captured at the collection point with precise geolocation, linked to a unique alphanumeric code, at the moment it happens, not reconstructed afterwards in an Excel sheet.
Step 3. That code links to new ones with every blend, transformation or shipment, so preserved identity doesn't break between collection and shipment, even if the batch passes through several collectors or intermediaries.
Step 4. With Retexcycle Compliance Hub, that file arrives already structured to the operator or trader at destination, ready for their declaration.
With this process, the cooperative from the opening example wouldn't have had to gather anything under pressure. Nor would its European buyer: the file for that batch would already have existed before anyone asked for it.
To decide on your EUDR compliance, answer this
All of the above comes down to three questions, whoever answers them: you at origin, or your buyer at destination. If you're taking this decision to your team or a manager, here they are:
- Can you assemble the complete file for a specific batch in under three working days, without advance notice? That's the real deadline an authority gives before extending or lifting a suspension.
- Does your evidence depend on nobody losing an Excel sheet or a field notebook? If the answer is yes, it's not a question of if it will fail, but when.
- Do you know exactly how many hours it costs to manually consolidate each shipment? If you don't know, it's probably more than you think, and it repeats with every shipment, not just once.
If any of the three answers worries you, it's time to consider a centralised EUDR traceability software instead of continuing to patch the manual method. You can request a demo with your own data and see how your chain would look, from the plot to the declaration.