Spreadsheet vs Software for Plant Passport Records
· 9 min lezen
Key takeaways
- A spreadsheet can legally serve as your plant passport register, but it cannot enforce links between batches, dispatches, and passports.
- The four structural spreadsheet weaknesses are no enforced record links, no audit trail, no access control, and no recall query.
- Italian D.Lgs. 19/2021 requires plant passport records to be kept at least two years after dispatch, so traces can reach back 18 months or more.
- A spreadsheet is still defensible if you issue under roughly 50 passports a month, sell to a short list of known B2B buyers, and handle no protected zone material.
- FloraPass costs a flat €79/month with unlimited passports and covers passports, availability lists, dispatch, and compliance records, but not ERP functions like accounting.
Spreadsheets work for issuing plant passports but fail at traceability and recall: when a phytosanitary inspection asks you to trace one batch back through 18 months of rows, manual records collapse. This article maps each stage of the passport lifecycle to where spreadsheets break down, and ends with a size-and-risk rule so you know which side your nursery falls on.
What records must you legally keep for plant passports?
Elements A to D as your minimum record
Every EU plant passport must carry four elements: A (the botanical name), B (your operator code and registration as a professional operator), C (a traceability code identifying the batch), and D (the EU member state and, where relevant, the protected zone). Reg. (EU) 2016/2031 requires registered operators to keep records that let authorities trace each batch back to its source and forward to every buyer, so your passport copies, availability lists, and dispatch notes form one connected record. The official regulation text sets out these obligations for professional operators, and our inspections guide covers what phytosanitary inspectors ask for.
How long records must be kept under Italian law
Italian D.Lgs. 19/2021 requires you to retain these records for at least two years after dispatch, long enough for a recall or inspection to reconstruct the full batch chain.
Where do spreadsheets work for plant passport records — and where do they fail?
What a spreadsheet does fine
If you issue a handful of plant passports a day, a spreadsheet is honest, cheap, and yours. It holds the elements A to D, your operator code, and the batch numbers without any setup. Printing the passport from a template row works well enough at low volume. For a nursery issuing a few hundred passports a season, that is not negligence — it is a reasonable tool doing a reasonable job.
The four structural weaknesses
The failure is not in the cells. It is in what a spreadsheet cannot do structurally, no matter how carefully you maintain it.
First, no enforced link between records. A spreadsheet has no rule that a batch on your availability list must trace back to a passport, or that a traceability code exists before dispatch. Every link lives in your head or in a note column, and one mistyped batch number breaks the chain silently. Software like FloraPass enforces those links at entry: a passport cannot reference a batch that does not exist, and every dispatch is tied to a compliance record by construction (verify any passport here). That is the single biggest difference between the two approaches.
Second, no audit trail. A spreadsheet shows you the current value of a cell, not who changed it, when, or what it said before. Third, no access control — anyone with the file can edit anything, including past records. Fourth, no recall query: answering "which customers received this batch?" means manually searching every sheet, which is the one moment you cannot afford slowness.
Where does a spreadsheet break at each stage of the passport lifecycle?
Issuing: label data drifts from the sheet
Your spreadsheet says one thing; the printed passport on the pallet says another. A batch number gets retyped, a protected-zone mark gets skipped, and elements A to D no longer match what left the nursery. There is no system forcing the label and the record to be the same object, so drift is a matter of when, not if.
Traceability: batch links live in someone's head
A spreadsheet records what you typed, not what actually happened. When a lot is split across three orders, the link between the original incoming batch and each outgoing consignment usually survives only in the memory of whoever did the split. That person takes two weeks of holiday and the chain is gone.
Recall: one infected batch, 18 months of rows
A quarantine pest finding means tracing every consignment that touched the batch, plus its suppliers and customers. In a spreadsheet that means filtering 18 months of rows by hand, and every gap is a consignment you cannot notify. Software built for the lifecycle, including tools like FloraPass, keeps those links as data so a recall is a query, not an archaeology project. FloraPass's own limits are real, though: it is built for passport and traceability records, not for general nursery ERP like stock planning or accounting.
Inspection: the inspector asks for a history you cannot produce in minutes
An inspector can ask for the record of any consignment from the past retention period set by Legislative Decree 19/2021. If answering means opening files and scrolling, you have already failed the practical test.
| Stage | Spreadsheet failure mode |
|---|---|
| Issuing | Label and record drift apart |
| Traceability | Batch links held in memory, not data |
| Recall | Manual filtering of months of rows |
| Inspection | History not producible on demand |
How does a recall trace back through a spreadsheet versus software?
Say a consignment of Viburnum from batch V-2417 turns out to carry a quarantine pest. You must show every customer who received that batch, and every batch that came into it. If you cannot, the whole consignment chain is suspect.
The forward trace: who received the batch
In a spreadsheet, you filter your dispatch sheet for "V-2417". That works if the batch code appears on every row. It fails the moment someone shipped under the lot number instead, or the batch was split and relabelled, because nothing forces consistency across rows. In software, each passport you issue carries elements A to D, so the traceability code ties the dispatch to the batch automatically. Either way, run your own records through a check like the plant passport check before an inspection finds the gap.
The backward trace: where the batch came from
Backward is harder. You need the supplier's RUOP code and the origin batch behind V-2417. A spreadsheet holds this only if you typed it in; software keeps the inbound record linked to the outbound one, so both directions resolve in minutes.
What happens during an inspection if your records are in a spreadsheet?
An inspector typically asks for two things: proof that each batch leaving the nursery carries a correct EU plant passport with all four elements (the plant species, the operator code, the traceability/batch code, and the country of origin), and evidence you can trace a suspect batch back to its source. The official requirements for these elements come from EU Commission guidance on the plant passport format. With a spreadsheet, you can usually produce a printed passport, but tracing a batch means filtering rows across supply, production, and dispatch sheets by hand while the inspector waits. If your sheets don't reconcile, the inspector records a non-conformity. Software responds the same way for the passport itself; the difference is recall speed. FloraPass pulls the full chain for a batch in one search, and you can see how we handle inspections with our partners at https://florapass.eu/for-partners.
When is a spreadsheet still good enough for your operation?
The size-and-risk test
A spreadsheet remains adequate if you issue plant passports occasionally, sell to a short list of known B2B buyers, and can reconstruct a batch's history from your own memory and paper files. If your operator code rarely changes, you handle no protected zone material, and a recall would touch at most a handful of batches you could name from the top of your head, the €79/month for FloraPass buys you little. The same logic applies to Qualità CE paperwork at low volumes.
Where FloraPass falls short too
FloraPass assumes you want unlimited passports on a flat €79/month, which is poor value if you issue a few dozen per season. It also does not replace your ERP, stock management, or invoicing; it covers passports, availability lists, shipment dispatch, and compliance records only. If your bottleneck is inventory rather than documentation, software here solves the wrong problem.
What does switching from spreadsheet to software actually involve?
What to migrate first
Start with your registered operator data: RUOP code, operator name and address, and the species list you are authorised to trade. That is what fills element A and B of every passport, so getting it right once saves rework on every document after. Second, import your current batch inventory with quantities and traceability codes. Historical passports can usually stay archived on paper; inspections focus on current stock. Run a month in parallel before you stop writing the spreadsheet.
Tools in this space and what they cover
FloraPass covers passport issuing, availability lists, shipment dispatch and compliance records for a flat €79/month, with no demo or sales call required. Fitoware positions itself around nursery management and traceability workflows, while Feedentity Nursery offers nursery-specific management including catalogue and commercial features. Atlas Core Cloud and Plant Pass also target this space. The honest gap in FloraPass: if you need full ERP functions like accounting or payroll, you will still run separate tools alongside it.
How do you decide which option fits your nursery's size and risk?
Use three questions as your decision rule.
First, volume. If you issue fewer than roughly 50 plant passports a month and your Qualità CE batches are few, a disciplined spreadsheet with one row per batch is still defensible.
Second, exposure. If you ship into protected zones or handle host plants for quarantine pests, recall traceability stops being optional. A recall request that takes days in a spreadsheet, versus minutes in software like FloraPass, is the difference between a clean inspection and a problem.
Third, customers. Once B2B buyers start asking for availability lists and traceability codes by email weekly, manual re-keying becomes your bottleneck.
If you fail any one of these three, move to software. FloraPass costs €79/month flat with unlimited passports, no demo or sales call required.
FAQ
Is an Excel file acceptable to the phytosanitary authorities as a plant passport register?
Nothing forbids a spreadsheet as your register, and at low volume it can pass. The real test is practical: an inspector may ask you to trace any consignment from the past two years while they wait. If your sheets reconcile and you can produce a batch chain quickly, Excel works. If not, you get a non-conformity.
How many years do I have to keep plant passport records in Italy?
Italian D.Lgs. 19/2021 requires at least two years of retention after dispatch. That window is what makes traceability hard for spreadsheets: a recall or inspection can reach back through 18 months of rows, so your records must stay consistent and reconstructable for the whole period. Archived paper passports alone rarely satisfy this.
Can I keep using my spreadsheet and only print labels with software?
Partially. Printing passports from a template solves label drift, the stage where the printed passport stops matching the record. It does nothing for the other three weaknesses: no enforced links between batches and dispatches, no audit trail, and no recall query. You would still filter rows by hand when a trace runs backward or forward.
What does a plant passport software cost for a small vivaio?
FloraPass charges a flat €79/month with unlimited passports, no demo or sales call required. That is poor value if you issue a few dozen passports per season; it makes sense once volume, protected-zone exposure, or weekly B2B requests make manual re-keying your bottleneck. Competitors like Fitoware and Feedentity Nursery target the same space.