No market access without a statement
The operator placing the product on the EU market for the first time must submit a due diligence statement. Its suppliers must give it what it needs to prepare it.
Traceability and compliance
Due diligence file
Your due diligence statement, ready to submit.
For each shipment, Sankora assembles the Annex II information and the evidence behind it. A second person signs, then you submit the statement in TRACES yourself and record the reference you receive.
Why it matters
Why the file matters
Scattered evidence
Geolocation, analyses, risk assessment, internal policies: gathering them by hand takes weeks. Every gap delays the shipment or weakens the statement.
Geolocation in the required format
The EU Information System expects a precise GeoJSON file, with at least six decimal places and polygons for plots over 4 hectares. Preparing it by hand invites errors.
At least five years of record-keeping
Information must be kept for at least five years and found quickly during an inspection. You need to be able to show exactly what was declared.
How it works
From shipment to statement
- 1
Opening the file
A file is created for a vessel shipment (exporter) or a truck shipment (cooperative). Sankora automatically attaches the lots, the plots of origin and their analyses.
- 2
Items to resolve
Sankora lists what is missing: operator details, HS code, analyses, a risk assessment covering each lot. Blocking items are kept apart from simple remarks.
- 3
Generating the file
The file brings together the statement (Annex II), GeoJSON in the EU Information System format, the plot list, analyses, the risk assessment, a PDF report and a fingerprint manifest. Each generation is kept as a version.
- 4
Four-eyes signature
An authorised person signs on behalf of the organisation. Neither the person who generated the version nor those who entered the statement details can sign.
- 5
Sharing and submission
The signed file is shared with your customer, who finds it in their own space. The user submits the statement in TRACES themselves, then records the reference and verification number in Sankora.
Real application screenshots · fictitious demo data
Features
- Annex II information: operator and EORI, HS code, description, scientific name, quantity, country, declaration, signature
- Article 9 information: production period, suppliers, customer, legality
- GeoJSON in the EU Information System format, farmers pseudonymised
- Blocking items rechecked before signature and before the reference is recorded
- Content fingerprint checked: any changed data requires a new version
- Approved policies and procedures attached to the file
- PDF due diligence report and SHA-256 fingerprint manifest
- Every version kept for at least five years
Who it is for
Cooperatives
Prepare a file for each shipment and pass it to your exporter with all its evidence.
Exporters
Produce the file for each vessel shipment from containers that are already traced and assessed.
Buyers and brands
Find the statement details, items to resolve and GeoJSON for the EU system in your own space, then record the reference of your statement there.
What you get
A complete, signed file for every shipment, ready for you to submit in TRACES.
Frequently asked questions
Your questions about this service.
Does Sankora submit the statement in TRACES?
No. Sankora prepares a complete statement. The user submits it in the EU Information System, then records the reference and verification number in Sankora.
Why can't the person who prepares the file sign it?
That is the four-eyes rule: a second authorised person reviews and commits the organisation. Sankora enforces it automatically on every version.
What if data changes after the file is generated?
The content fingerprint is recomputed before signature and before the reference is recorded. If plots, analyses or statement details have changed, a new version must be generated.
How long is the file kept?
At least five years. Every generated, signed or submitted version stays downloadable with its fingerprint, and nothing is overwritten.