A certificate is not a due diligence statement Claim per batch EUDR requires more than CoC

Custom chain of custody software for FSC and PEFC

The most persistent misconception in this area is that an FSC or PEFC certificate gets you through the deforestation regulation. It does not do so automatically. Chain of custody proves that material from a certified source has been tracked through your supply chain; the EUDR requires data that is not part of that, starting with the geolocation of the plot.

Two records that look alike

Chain of custody is the chain of control: it tracks certified material from forest to end product. The systems work with fixed methods. With physical separation, you keep certified material apart from non-certified material; with the percentage method, you pass a share on to the outgoing batch; with the credit method, you build up a credit balance that you can claim later. The method you use determines what your records look like.

The deforestation regulation asks for something different. It is about due diligence: demonstrating that a product is deforestation-free and legally produced, with geolocation data for the plots the raw material comes from. Both PEFC and FSC have published a separate module for this on top of the CoC standard, precisely because the basic standard does not cover it. The regulation applies to large companies from 30 December 2026 and to small and micro companies until the end of June 2027.

The practical consequence is that you keep two tracks for the same batch of timber. If you cram them into one spreadsheet, you find out at the first audit that the percentage calculation no longer holds once geolocation fields are added, or that a credit record cannot answer the question of which plot this plank comes from. Those are not shortcomings of your records but of the assumption that it is a single record.

How we build this

The batch is the unit here and the method determines the calculation rules. If you record for each incoming batch what it is and what happens to it, every claim follows from that.

1
Recording your method

Physical separation, percentage or credit, and sometimes different methods per product group. This is the first question and it determines the whole set-up; skipping it gives you a system that calculates in a way nobody actually works.

2
Linking incoming and outgoing

For each outgoing batch, which incoming batches it contains. With physical separation that is a reference, with percentage a calculation, with credit a debit.

3
Placing the EUDR data alongside

Geolocation, supplier and country belong to the incoming batch and not to the claim. We build them as a separate layer, so that one does not break when the other changes.

4
Rehearsing an audit

We take an outgoing batch from last year and trace it back. What fails to work then will not work at the audit either.

What the software actually does

The batch records carry everything; the claim and the due diligence data are two layers on top. Which components you need depends on your method and your place in the supply chain.

Incoming and outgoing batches linked

For each outgoing batch, which incoming batches went into it, with quantity and unit. This is the core of every chain of custody and, at most companies, the weakest point.

Calculation rules per method

Percentages and credits are calculated according to the method you apply, with the intermediate steps visible. A claim whose calculation cannot be followed will not hold up in an audit.

Supplier certificates monitored

Validity, scope and expiry date per supplier, with a warning before a certificate expires. An incoming batch dated after the expiry date invalidates the claim made on it.

Due diligence data as a separate layer

Geolocation, country and supplier on the incoming batch, kept separate from the CoC claim. This lets you substantiate an EUDR statement without cluttering your certification records. See also EUDR software.

Claim stored with supporting evidence per batch

Which claim was made on which outgoing batch, on what date and on what grounds. In an audit, what matters is not the claim but the evidence that underpinned it at the time.

Deviations with follow-up

A batch without a valid certificate, a percentage outside the permitted range, a missing geolocation. Each of these becomes an action with an owner rather than a line in a list.

Who we build for

Your position in the chain determines which method and which data apply to you. Four situations.

Timber trade and building materials

You buy in and sell on, often without processing. Your challenge is linking the purchase batch to the sales order, and that link currently usually sits in an inventory system that knows nothing about the claim.

Processors and manufacturers

You blend batches, and that is where the method becomes decisive. With percentage or credit methods the administration is heavier than with segregation, and the gain lies in calculating automatically instead of reconstructing after the fact.

Packaging, paper and print

Your customers ask for a claim on the end product while you are far removed from the forest. The chain is long and the data comes from your supplier; a portal works better here than an email exchange.

Projects with a certification requirement

Tenders ask for a claim per delivery, not per company. That means you must be able to show, per project, which batches went into it. Capturing this on site runs through the batch origin app.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

The standards and the EUDR modules are still being revised. Everything to do with calculation rules and fields should be configurable and stored per version, so that an old claim remains readable against the rules of the time.

Node.js / Python / .NET PostgreSQL Incoming and outgoing batch administration Configurable calculation rules per method Certificate monitoring per supplier Geolocation and origin as a separate layer Claim history per outgoing batch Deviation management with an owner Supplier portal Integration with inventory, ERP or production Export for audit and statement Version history on standards Audit logging Hosting in the EU

Why Appfront

A certificate is not a due diligence statement

Chain of custody supports the EUDR but does not cover it. We build both layers separately and tell you where one stops and the other begins.

The method determines the system

Segregation, percentage and credit each require different record-keeping. We start from your method rather than from a standard model.

An expired certificate invalidates claims

We monitor validity and scope per supplier and warn you in advance, because discovering it afterwards means reversing claims.

Your inventory system stays in place

Batches and quantities are already recorded somewhere. We connect to them through integrations instead of building a second inventory administration.

Security and privacy

The data here is commercially sensitive on both sides. Your purchase batches, with suppliers, volumes and prices, are valuable to a competitor, and the geolocation data your supplier provides reveals their own sources. In the portal, a supplier therefore sees only their own batches, and origin data is shielded from anyone who does not need it.

On the evidence side, there is a requirement that makes this record-keeping unusual. A claim must still be defensible years later against the version of the standard that applied at the time, even if the standard has since been revised and the supplier no longer exists. We therefore store the values as they were delivered, the rule version used for the calculation and the claim as it was made. A system that only knows the current state cannot explain, in an audit, why a batch was assessed differently back then. How we handle security ourselves is set out in our information security policy; external reports go through our CVD policy.

Frequently asked questions about chain of custody

No. Certification supports your due diligence system and strengthens the evidence, but the regulation requires data that the basic standards do not capture, in particular the geolocation of the plots. Both schemes have therefore published a separate module on top of chain of custody. Check with your certification body what this means for your scope.

That depends on your process. Physical separation is the simplest administratively but requires space and discipline in the warehouse. The percentage method and the credit method offer more flexibility and require more administration. We build the calculation rules around the method you apply; which method is permitted for your product group is determined by the standard.

For large companies from 30 December 2026, and for small and micro companies until the end of June 2027. Note that timber has a position of its own within this regulation. Check the current dates and your category, as this regulation has been amended several times in recent years; see also EUDR software.

A stock system knows how many cubic metres are in storage and what they cost. Chain of custody knows which incoming batch ended up in which outgoing batch and which claim applies to it. That is a different question about the same plank. We therefore integrate with what you already have; see timber trade software.

For importers this is the hardest part, and it does not resolve itself. What works is keeping the request small, in your supplier's language, with a clear view of what is still missing, and starting early because the first round rarely produces usable answers. Without this data you cannot substantiate a statement, however good your certificate is.

Longer than most companies expect, and the retention periods differ per standard and per regulation. In practice it means that the substantiation of a claim must remain readable once the version of the standard has been revised and the supplier has disappeared. That is why we store the delivered values and the rule version alongside the claim itself.

Yes, and that is often necessary because customers ask for different claims. The batch administration is shared; the calculation rules and claim definitions differ per scheme, so we keep them configurable. What you do not want is a separate administration per scheme, because then the batch data drifts apart.

That depends on your method, the number of product groups and whether the supplier portal and the EUDR layer are included. The batch administration with the claim calculation is usually usable quickly; the portal and integrations cost more. We give a substantiated estimate after the discovery phase.

Ready to get your claims substantiated?

Take an outgoing batch from last year and try to trace which incoming batches went into it and which certificate applied to them then. Where that trail stops, the work begins. We build this as a standalone application and as part of a broader custom software project.

Edit content