Filovara now turns a reviewed Case into a complete manual-submission bundle instead of stopping at a generic preflight export. The authorised operator receives the exact DDS field set, product table, production GeoJSON and an offline step-by-step guide, while the fuller Filing Pack remains available for audit and evidence retention.
A practical preparation workflow
- 1
Complete the operator, product, quantity, production-period and geolocation fields.
- 2
Download the DDS Submission Bundle and follow its manual TRACES guide.
- 3
Record the official Reference Number and Verification Number after submission.
Use the DDS Submission Bundle for the external form
The ZIP contains the structured DDS fields, a product CSV, the selected production GeoJSON, a self-contained manual-submission guide, and a hash manifest. It is designed for an authorised user to transfer the prepared values without reconstructing the case from scratch.
Separate blockers from warnings and decisions
A missing required value is not the same as an unusual but reviewed value. Use explicit states so the submitter knows what must be resolved, what needs attention, and what has already received a documented human decision.
- Blocker: a required technical input is absent or invalid.
- Warning: the data can be exported but warrants review.
- Decision: an authorized person accepted or corrected a candidate.
Record the boundary between systems
Keep the external Reference Number, Verification Number and submission time with the exact DDS draft. Those official numbers—not the downloaded ZIP—close the submission loop. Keep the richer Filing Pack alongside them for later audit and evidence review.
What to check
- Complete Annex II operator and product values
- Validated production GeoJSON and plot associations
- Exact operator confirmation and authorised reviewer
- Official receipt numbers linked to the submitted draft
Filovara prepares complete materials for manual transfer. The authorised user signs in and submits through the EU Information System; technical preparation does not guarantee acceptance.
Questions teams ask
Does Filovara submit directly to TRACES?
No. It provides complete manual-submission materials and instructions; the authorised user signs in with their own EU Login and submits, then records the official receipt in Filovara.
Can a prepared export become stale?
Yes. Any change to relevant facts, evidence, rules, or decisions should produce a new export version.
Is a successful technical preflight a compliance decision?
No. It is a completeness and consistency check under a stated mapping version.