Link a supplier's DDS reference once, at intake. Every pack cut from that delivery, and the invoice line it ships on, carries the same reference back to source — without anyone re-typing it.
5 packs a month, no card required · Free forever
At intake, the operator links the supplier's DDS reference to the delivery — or marks it explicitly not applicable, never a silent blank.
Action: At intake, the operator links the supplier's DDS reference to the delivery — or marks it not applicable, with a reason — never a silent blank.
Result: The delivery carries an EUDR status — OK, Missing, or N/A — before a single log from it has been cut.
Every pack cut from that delivery keeps a computed chain back to its source — vendor, delivery, log pile — without anyone retyping it.
Action: The log pile is cut into packs. Every pack keeps a computed chain back to its cutting operation, log pile and the original delivery.
Result: Any pack's own Origin panel resolves the DDS reference back to source and reports the same EUDR status the delivery carries.
Every DDS reference the mill has ever received lives in one registry — searchable, instead of a folder of PDFs.
Action: Every DDS reference the mill has ever received — number, supplier, country of harvest, date issued — is searchable in one registry.
Result: One place to see every reference on record and whether it's still marked valid, instead of a folder of PDFs.
PEFC, FSC, Bois Suisse and EUDR are built-in certification types, each with its own certificate number and validity window.
Action: PEFC, FSC, Bois Suisse and EUDR are built-in certification types. Record a certificate number and validity window once, on the vendor.
Result: A plot's certification status is a lookup on the vendor record, not a phone call to the supplier every time it's asked.
Was: proving which DDS covered which shipment meant asking whoever handled the delivery, months later, and hoping they remembered. Now: the reference is attached to the delivery once and inherited by everything cut from it.
Was: a supplier's reference re-typed or re-uploaded on every single delivery it actually covers. Now: the registry recognizes a number it has already stored and reuses that record instead of duplicating it.
Was: "yes, that plot is FSC-certified" over the phone, unrecorded anywhere. Now: certificate type, number and validity window recorded once on the vendor's forest-plot record — checked, not assumed.
One DDS reference, linked once at intake, carried automatically through every pack and invoice it touches.
DDS reference — number, supplier, country of harvest, issue date — or an explicit "not applicable" with a reason.
On the delivery, on every pack cut from it, and on the invoice line it ships on — the same reference, not three different ones.
DDS-to-delivery links, shipment-to-pack links and stored documents feed the EUDR compliance page as one export.
Nothing runs out — Free never expires. Every new account opens on a guided tour through a working demo mill inside your own organization, on real screens with real (demo) data — not a separate demo login. Follow a DDS reference from delivery to pack yourself, then leave the tour whenever you're ready to switch to your own data.
Start freeWe don't verify a DDS number against the EU Information System.
A DDS number that isn't the standard 22-character format gets a soft warning icon — a formatting hint, never enforced. We don't call the EU registry to confirm a number is real, unused, or actually belongs to this shipment. That check happens at the point of the official submission, not here.
We don't record GPS coordinates of a harvest plot.
A forest-plot record here is a name, region, country, forest manager and certifications — a supplier's own bookkeeping of a plot it manages. It is not the geolocation obligation EUDR places on whoever first places the wood on the EU market; that data comes from the DDS itself. See EUDR compliance for that distinction in full.
No. Linking a reference here records it against a delivery so it can be carried through cutting, drying and the invoice — it is not a submission channel. The EU Commission's own portal is where a DDS is actually filed; this app makes the data behind it easy to find when someone asks for it.
The pack inherits that status rather than showing a blank. Its own Origin panel reports the same not-applicable state its source delivery was given, with the reason attached — nothing is silently dropped on the way from delivery to pack.
Yes. The registry recognizes a DDS number it has already stored for your organization and reuses that record instead of creating a duplicate — one reference, linked to every delivery it actually covers.
No. A certification — PEFC, FSC, Bois Suisse, EUDR — is recorded on the vendor's forest-plot record, one level up from an individual delivery. It is a lookup you can do, not an automatic check the app runs against each shipment.
No, it's optional. A delivery can be linked to a forest-plot record when you know which plot it came from; when you don't, the delivery still carries its DDS reference on its own — the forest-plot link is extra context, not a requirement to record the reference at all.
Free forever. No card. No contract.
Deadlines & obligations — EUDR compliance → · Pricing → · Back to overview →