EUDR SME deadline: 30 Jun 2027 — … days
03 / The platform

Seven gates. One verified record.
Reusable across the network.

Each verification flows through seven structured gates. The output is a single supplier record any platform client can consume — without commissioning a fresh verification.

// Click any gate to expand its activity FVF · v1.0 · seven sequential gates
01
Gate 01 · Identification

Legal status, registration, and export licences

Verification of legal status, registration data, and export licences against corporate registries (Registro Mercantil and country equivalents). The gate establishes that the supplier is a legitimate trading entity before any further evidence is collected.

Selected
EVIDENCE: registry certificates, export licence IDs
03.1 / Five platform modules

Five modules. One source of truth.

SVE is the engine room. The other four modules read from it — the verified supplier record is the single asset every client interaction depends on.

SVE
// Engine room

Supplier Verification Engine

The core module that orchestrates the seven gates and stores supplier records as the single source of truth. All other modules read from SVE. Every verified supplier becomes shared infrastructure on the platform.

FVF · 7-gate orchestration · evidence ledger · audit trail
DGM
// Output module

DDS Generation Module

Assembles Due Diligence Statement packages in TRACES NT-ready format. From verified supplier and shipment data to submission-ready package in under 15 minutes.

CML
// Monitoring layer

Continuous Monitoring Layer

Tracks changes to verified suppliers — certificate expirations, risk reclassifications, deforestation alerts. Latency under 24 hours.

RSS
// Scoring system

Risk Scoring System

15-criteria deterministic scoring across Environmental, Social, Governance, and Operational dimensions. Per-criterion breakdown plus aggregate score 0–100.

SVN
// Network effect

Shared Verification Network

Each verification is reusable across all platform clients. Marginal cost of serving an additional buyer falls as the catalogue grows. Economic anchor of the model.

03.2 / In practice

A Catalan compound feed manufacturer onboarding to Fontisera

// Onboarding flow · Phase 1

From contract signature to verified shipment in under two months

Day 1
Contract signed. Account provisioned within 2 hours. Roles assigned to the buyer's compliance team.
Day 2
Walkthrough session with a Fontisera analyst. Initial supplier list (12 entries) imported into SVE.
Week 2
First three suppliers verified through the FVF pipeline. RSS scores published. DDS packages generated for the current Brazilian soy shipment.
Month 2
Continuous monitoring active. Two of the three suppliers reusable from the SVN catalogue — no fresh verification required.
03.3 / Performance targets

Phase 1 targets, then automation

Phase 1 launches with expert-augmented workflows behind every commitment. Automation rolls out across Q4 2026 to Q2 2027, tightening verification turnaround and DDS generation times.

Metric Phase 1 (Q3 2026) Phase 2 (Q1 – Q2 2027) Measurement
Verification turnaround < 10 working days < 5 working days Median request to completion
DDS package generation < 15 minutes < 2 minutes Median request to package
Alert delivery latency (CML) < 24 hours < 24 hours Median end-to-end
Platform uptime 99.0% monthly 99.0% monthly Externally measured
Public API availability 99.5% monthly From Q1 2027

See the SME-accessible pricing.

Four revenue streams sized for the 96% segment. EUR 2,400 to 6,000 typical buyer annual cost.

See pricing