Plant Passport Requirements for Selling Plants Online
· 10 min lezen
Key takeaways
- Any regulated plant for planting moving within the EU needs a plant passport, even for domestic online orders.
- The passport must be issued before dispatch, with printing keyed to the batch at the packing stage.
- The label must carry elements A to D: botanical name, operator code, traceability code, and country or protected-zone marking.
- Deliveries to protected zones require the PZ marking and a pest-free record, so check the postcode at order confirmation.
- Keep dispatch records that let an authority reconstruct where each batch went and which passport covered it.
If you are a registered professional operator selling plants online across the EU, you must issue an EU plant passport for every consignment of regulated plants before dispatch, whether the buyer is in Italy, the Netherlands, or a protected zone. The passport is issued at order fulfilment, not at listing, and each e-commerce stage from picking to dispatch triggers a specific passport action. This guide maps those actions stage by stage.
Do I need a plant passport for every online order, or only cross-border shipments?
Both. Any regulated plant for planting moving within the EU needs a plant passport, whether it travels to another region of Italy or to the Netherlands. The passport follows the plant, not the sales channel.
Which species and plants for planting trigger the requirement
The obligation applies to plants listed in the Union regime under Commission Implementing Regulation (EU) 2019/2072, which also lists protected zones where stricter rules apply. Exempt material, such as most houseplant species outside the regulated lists, needs no passport even when sold online. If you are unsure whether a species is covered, our guides walk through the lists in Italian.
Why selling online does not change the obligation, only the logistics
An order confirmed through your shop or a marketplace is still a B2B movement of a registered professional operator's stock. The passport must be issued before dispatch, exactly as it would for a phoned-in order from a garden centre. What changes online is volume and timing: you may issue dozens of passports a day against orders you never saw coming, which is where manual workflows break.
At what point in the order fulfilment process must the plant passport be issued?
The rule is simple: as a registered professional operator, you must issue the passport before the plants physically leave your holding. In practice, that means issuance and label printing belong at the packing stage, keyed to the batch the plants are picked from.
Listing stage: what you may state about passport status in the availability list
Your availability list can say a batch is passported, but the passport itself does not exist yet. Avoid printing traceability codes on the list, because the code must match the batch actually shipped, and availability changes.
Order confirmation: reserving batch and traceability code
At confirmation, reserve stock from a specific batch and lock the traceability code against that order. This prevents two orders from drawing on the same passported batch inconsistently.
Packing stage: issuing and printing the label
Packing is where elements A to D are generated and the label printed. FloraPass does this at €79/month flat, unlimited passports, with demo data from Vivai Bellavista in Pistoia so you can test without a sales call. Anyone receiving the document can confirm it at https://florapass.eu/verify.
Dispatch: attaching the passport to the shipment
| Stage | Passport action | Who does it |
|---|---|---|
| Listing | State passport status only | Sales |
| Confirmation | Reserve batch + code | ERP/shop |
| Packing | Issue and print label | Operator |
| Dispatch | Attach label to shipment | Warehouse |
Attach the printed passport to the shipment before the courier collection scan. If the label goes on after the pallet leaves the gate, the issuance moment is wrong even if the paperwork is dated correctly.
What must appear on the passport label when shipping via a marketplace or third-party platform?
The label or accompanying document must carry the four elements: A, the botanical name; B, your operator code (your RUOP registration number); C, the traceability code (batch number); and D, the country and protected-zone marking where relevant. This comes straight from the plant health Regulation (EU) 2016/2031, which also sets out the registration and record-keeping duties behind those codes.
Elements A to D on a physical label vs a document
A printed label tied to the batch is the normal route for B2B shipments, but the regulation allows the elements to appear on an accompanying document instead. If your marketplace order confirms after the plants are already packed, a document listing the batch and your operator code keeps you compliant without reprinting labels. What you cannot do is send the passport "later by email" once the goods have left.
Who is the responsible operator when a platform takes the order
The marketplace takes the payment; it does not issue passports. You, the registered professional operator who assembled the batch, remain responsible for elements B and C and for keeping the dispatch records. If a platform's paperwork strips out your traceability code, the shipment is non-compliant even though the sale went through their system.
FloraPass generates labels and accompanying documents with all four elements, and pairs them with the inspection records you attach to each batch (https://florapass.eu/features/inspections). Where it falls short: it does not push passports directly into marketplace order feeds, so you still paste the traceability code into the platform's dispatch note yourself.
How do I handle mixed orders containing both passported and exempt plants?
Split the order into two groups at picking: regulated plants that need a plant passport, and exempt items that travel on the delivery note without one. The exempt items must never share a passport or dilute the traceability of the regulated ones. Each passported batch keeps its own passport with elements A to D intact.
One label per batch vs one label per parcel
A passport attaches to the batch, not the parcel. If one order mixes three batches of the same species from different plot codes, you need three passports. If a parcel holds only exempt plants, it needs none.
Worked example: a mixed B2B order of 40 items
Say a buyer orders 30 Photinia (passported, one batch) plus 10 exempt pots. You issue one passport for the Photinia batch, and the delivery note lists all 40 items with your operator code. FloraPass generates the passport at dispatch and keeps the batch-level record attached to the shipment, so the exempt line items never touch the traceability chain (https://florapass.eu/features/shipments).
What changes when a buyer's address falls in a protected zone?
A delivery address inside a protected zone changes two things: the passport must carry the PZ marking in element D, and the plants may only leave your holding if it is free of the relevant quarantine pest. The format of elements A to D is set out in Commission Implementing Regulation (EU) 2019/1709 on the plant passport. FloraPass applies the PZ flag automatically when a postcode matches a protected zone, and blocks dispatch if the batch lacks the corresponding pest-free record.
Checking the delivery postcode against protected zone lists
Run the check at order confirmation, not at packing. A protected-zone order caught at dispatch means a cancelled shipment, a restocked batch, and a customer waiting. Map each consignee postcode to the active zone lists for your relevant pests before you confirm anything. You can test the workflow with Italian demo data at FloraPass.
What to do when the order cannot legally be fulfilled
If your holding is not free of the relevant quarantine pest, you cannot ship into that zone, with or without a passport. Tell the buyer immediately, offer an equivalent batch that qualifies, and log the refusal with its reason. That record is your evidence if the plant health authority later audits the order.
Which records must I keep after dispatch, and for how long?
After dispatch you must keep records that let you trace every batch and every movement of plants, and produce them to the plant-health authority on request. Retention periods are set by national implementation of Regulation (EU) 2016/2031, so check what your Italian authority requires rather than assuming a single EU-wide number.
What a compliant dispatch record contains
For each shipment, record the batch, the traceability code, the operator code (RUOP), the plant passport elements A to D, the dispatch date, the quantity, and the buyer's destination. For protected-zone destinations, keep the specific justification for that movement. The test is simple: from the record alone, the authority must be able to reconstruct where a batch went and which passport covered it.
Paper spreadsheet vs a dedicated register at inspection time
A spreadsheet can satisfy the letter of the requirement, but only if someone updates it for every order, including marketplace sales and cancellations. In practice, gaps appear exactly where volume is highest. FloraPass builds the register automatically from each dispatch, with unlimited records at €79/month, so an inspection request becomes a filtered export rather than an archaeology project. That is honest about its limits too: if your ERP already holds order data, a register is only half the picture, and reconciliation stays your job.
How do returns and cancelled orders affect passport obligations?
Voiding a passport for an order that never shipped
If a customer cancels before dispatch, the passport you already printed is dead stock: mark its record as voided in your register rather than deleting it, so the traceability trail stays intact. The batch keeps its original traceability code and stays available for the next order. Under the national record-keeping rules for registered professional operators, records of passports issued and cancelled must remain auditable for the retention period set out in the Italian Ministry of Health's plant-health pages.
Re-dispatching returned plants with the same traceability code
A returned batch re-enters stock under its original traceability code, not a new one. Before re-dispatch, check whether the plants left a protected zone or were opened from their packaging: if so, re-inspect and re-issue a passport with a new issue date. FloraPass handles this by reopening the batch record and generating the replacement label, but you still make the re-inspection call yourself; no software can inspect a plant for you.
How do I automate passport issuance inside an online shop workflow?
The options sit on three levels. Manual: a Word or PDF template you fill in per order, then print. Dedicated SaaS: a tool that generates passports from your batch data and prints labels directly. ERP integration: passport issuance embedded in your WMS so it fires automatically at picking or dispatch. Fitoware, Feedentity Nursery, Atlas Core Cloud, Plant Pass and Phytia all work in this space; FloraPass is ours.
Comparing the options honestly, including where FloraPass falls short
Judge every tool on the same five criteria: label output (PDF and ZPL for thermal printers, QR encoding the traceability code), export of your register for inspections, automatic protected-zone checks against the buyer's address, batch-level traceability from availability list to dispatch, and API access so your e-commerce platform or ERP can trigger issuance itself. Run against those criteria, FloraPass covers flat-rate unlimited passports, availability lists, shipment dispatch, protected-zone checks and full compliance records at €79/month with no demo or sales call. Where it falls short: there is no native ERP or WMS module, no marketplace plug-in, and no on-premise option. If your picking logic lives in SAP or a custom WMS, you will need the API route below or a manual export step, and a tool like Phytia that sits closer to ERP workflows may fit better.
What an ERP or platform partner needs from a passport API
A usable API does four things: it accepts an order or batch reference and returns a printable passport (PDF or ZPL) without a human opening a dashboard; it validates the delivery address against protected-zone rules before the label prints, not after; it writes the issuance event back to the register so your records stay complete; and it handles cancellation, so a cancelled order voids the passport rather than leaving an orphaned record. If a vendor cannot demonstrate all four against your real order flow, the integration will leak manual work back into your team.
FAQ
Can I put the plant passport information on the delivery note instead of a separate label?
Yes. The regulation allows elements A to D to appear on an accompanying document rather than a physical label, which is useful when a marketplace order confirms after packing. What you cannot do is send the passport "later by email" once the goods have left your holding; the information must travel with the shipment.
Do I need a plant passport for seeds or for plants sold to private consumers in my own country?
The passport obligation applies to plants for planting listed under the Union regime in Commission Implementing Regulation (EU) 2019/2072, and it applies to domestic movements too, not just cross-border sales. Whether seeds or a particular species fall outside the regulated lists depends on the current annexes, so check the lists before assuming an exemption applies.
What happens if I ship to a protected zone without the PZ marking?
The shipment is non-compliant on two counts: the passport lacks the required PZ marking in element D, and you have no evidence the batch is free of the relevant quarantine pest. A plant-health authority can treat the movement as an illegal introduction into the zone, so block dispatch when the batch lacks the pest-free record.
Does my RUOP code have to appear on my website listings?
No. Your listings may state that a batch is passported, but the passport itself is issued at packing, keyed to the batch actually shipped. Element B, your operator code, belongs on the passport label or accompanying document at dispatch. Printing traceability codes on availability lists invites mismatches, because the code must match the batch shipped.