One cultivar, one name Batch down to the code Closing deadlines monitored

Custom cultivar registration and phytosanitary compliance software

The internationally accepted naming rule is: one cultivar, one name. A bulb crop may only be traded under a single name. That sounds simple until you open a set of records in which the same lot has a working name at cultivation, a registered name at inspection and a trade name with the customer.

Appfront
Live

Where registration comes together

The KAVB is the international registration authority for tulips, hyacinths and many special bulb crops. All new introductions of these crops, from the Netherlands and every other country, are described and recorded there. Each year that amounts to well over a hundred new tulips, plus around three hundred and fifty new cultivars of other crops.

To register a new cultivar you need thirty healthy, well-flowering bulbs of a single size, together with a completed registration form and a digital photo. The submission is planted in autumn and assessed in spring for distinctness, uniformity and stability. A whole growing season therefore lies between submission and registration, during which the lot simply carries on growing.

On top of that come the obligations towards the inspection service. Growers are legally required to register their fields and lots, and the closing deadlines are strictly enforced: reporting late results in a reminder with costs that rise by the day. Lots of more than fifty ares are treated as commercial product and are therefore inspected.

On the phytosanitary side, everything hinges on the plant passport. It carries four mandatory elements: the botanical name, the company's official phytosanitary registration number, the lot's traceability code and the country code of origin. The registration number is nine digits, preceded by NL and a hyphen. Traceability data must be kept for at least three years.

How we build this

The lot is at the core. A lot has a name, a field, an inspection status and a traceability code, and those four must belong together at every moment.

1
Names in one place

Working name, registered cultivar name and trade name side by side, with one of them marked as the name under which the lot is traded.

2
Linking lots and fields

What is where, in which size and with what area, so that reporting to the inspection service is a printout rather than a form-filling exercise.

3
Carrying the code along

The traceability code stays with the lot through every operation: lifting, grading, storing and delivering.

4
Monitoring deadlines

Closing dates are strictly enforced. The system warns you in advance, not on the day itself.

What the software actually does

The lot administration carries the whole. What else you need depends on your role: breeding, growing, trading or all three.

Cultivar register

Registered names, submissions still in progress and working names for anything that doesn't have a name yet, without them getting mixed up.

Tracking a submission

A submission runs through an autumn and a spring. While it is in progress, the lot should have a status rather than an assumption.

Lot and field registration

Everything the inspection service asks for comes from your own records, including the area that determines whether something counts as commercial product.

Plant passport data

Botanical name, registration number, traceability code and country code, built from what has already been recorded.

Traceability going back three years

From a delivered lot back to the field and the parent lot, even when two seasons have passed since that delivery.

Deadline monitoring

Closing dates and inspection moments with an advance warning, so that a missed date doesn't turn into a reminder notice.

Who we build for

Who works with this differs per company. Four situations.

Flower bulb growers

For them, cultivation, inspection and delivery come together in the same lot, with different records for each track.

Breeders

They work with numbers for years before a name exists, and need to make that transition without gaps.

Trading houses

They buy lots from multiple growers and must be able to demonstrate the origin right back to the lot they delivered from.

Exporters

For them, the phytosanitary file is not paperwork but the condition for being allowed to deliver.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

Registration rules get revised, crops are added and inspection requirements shift. Crops, fields and deadlines should be configurable rather than hard-coded.

Cultivar register with name history Lot and plot records Traceability codes per lot Integration with your inspection service portal Plant passport data from your records Deadline monitoring with advance warnings Roles for cultivation, inspection and sales History per lot across multiple seasons Export for registration and delivery Audit trail on every change

Why Appfront

One cultivar, one name is an administrative requirement

The rule is clear, but it falls apart on working names and trade names. We build names as one register with one trade name.

The code has to survive processing

Lifting, sorting and repackaging are precisely the moments when traceability breaks. That is where we lock in the trail.

Deadlines cost money, not excuses

Closing dates are strictly enforced. A warning a week in advance is cheaper than a reminder fee.

We don't inspect or register

The assessment stays with the inspection service and the registration authority. We make sure your own records match what you submit.

Security and privacy

Your lot data says something about your cultivation plan, your customers and your selections that are not yet registered. That last point is commercially sensitive: a new cultivar is years of work before it has a name. We set access per role, keep ongoing selections separate from what is ready for trade, and log every access. Integrations run through secure connections to your existing software.

For this subject, reliability at the moment of recording is the point. A lot origin that was changed after a complaint is no longer traceability. We record processing steps and links between lots immutably, with timestamp and person, and turn a correction into a visible correction alongside the original entry. How we handle security ourselves is described in our information security policy.

Frequently asked questions about cultivar registration and lot records

That a bulb crop may only be traded under a single name. In your records this clashes with working names during cultivation and trade names towards the customer, and that is exactly where mistakes arise.

Thirty healthy, well-flowering bulbs of one size, with a completed registration form and a digital photo. They are planted in autumn and assessed in spring for distinctness, uniformity and stability.

Four mandatory elements: the botanical name, the company's official phytosanitary registration number, the traceability code of the lot and the country code of origin. The registration number is nine digits, preceded by NL and a hyphen.

At least three years. In practice that means that for a delivery from two seasons ago, you must still be able to trace back to the lot and the plot.

Closing dates are strictly enforced. Registering late results in a reminder, with costs that rise per day up to a maximum per reminder.

That is a separate scheme with its own audit file. We have a separate page on GlobalG.A.P. cultivation records for that.

Can you trace a delivery from last season back to the plot?

Take one delivered lot from two seasons ago and work backwards: traceability code, lot, plot, parent lot. If the trail breaks during sorting, it will break there during a phytosanitary query too. We build this as a standalone application and as part of a broader software development project.

Edit content