May this product be used here, on this crop, against this pest?
Authorisations are national and sit in a separate register per country. FairGrow retrieves those registers, hangs them on EPPO codes and answers the question you actually ask. No estimate, no model, only what the register says.
An authorisation is national, always
A product authorised in the Netherlands is not thereby authorised in Belgium or Germany. Not even if the active substance is approved at European level, because that approval covers the substance and the authorisation covers the product on a crop against an organism. So in FairGrow the register hangs off the country of your plot, not off the language your app happens to be in.
From question to verdict
Crop and target organism
Both as EPPO codes, so the question means the same thing in every country. If your plot is already in FairGrow, your own crops are a shortcut and the country is filled in for you.
Even a product that is not listed
You may deliberately pick a product that does not appear in the list for that combination. That is exactly when the check earns its keep: it tells you why it is not there, instead of quietly leaving it out.
Looking across the border
For growers with plots in more than one country: the same question, side by side, per register. Useful for seeing that a product you are used to has a different status just over the border.
What determines the answer
The outcome comes only from fields of the national register. There is no estimate in it, no model and no derived value. This is the order in which the rules are worked through.
Withdrawn or expired
If the product has been withdrawn, or the expiry date has passed, it is not authorised. Withdrawn products are never deleted here, only set to that status, so you can still look up and account for a spraying from three seasons ago.
No use block on this crop
If your crop appears nowhere in the use blocks of this product, it is not authorised for you. What helps then is seeing the crop entry alongside: in ornamentals your species often travels inside a collective entry under a quite different name.
On the crop, but not in the same block
The most important rule, and the easiest to get wrong. Crop and pest have to sit together in one use block. If they sit in different blocks, that product is not authorised for that combination, however familiar it feels.
Expiry within ninety days
Authorised, but with conditions. You see the product with the date beside it, so you can plan instead of discovering halfway through the season that your stock is no longer allowed.
Emergency authorisation
An exemption under article 53 also produces the outcome “authorised with conditions”. Those conditions are rarely trivial, so they sit alongside the verdict and not in a footnote.
And otherwise: authorised
If none of the above applies, the product is authorised for that combination. You see the dose, the pre-harvest interval and the conditions of use exactly as the register supplies them, with a link to the legal instructions for use.
What decides the answer, and what only adds context
Imitating a register you cannot fully retrieve is worse than saying plainly that you do not know. So the verdict comes from the national register alone, and everything else we show sits beside it, with its source. That separation must not quietly slip with a later extension.
- The verdict, the dose, the pre-harvest interval and the conditions of use come only from the national register, as the register publishes them. We do not estimate or model them
- Reference data from other sources, such as EPPO codes and the EU approval of active substances, is shown alongside with its source. It never changes the verdict
- Where FairGrow shows risk signals or published action thresholds, they are marked as such, carry their source and have no influence on whether a product is authorised
- No environmental indicator of our own: that dataset is licensed, and rebuilding it ourselves would produce invented numbers. We refer you to the official source per country
- The product label always prevails, and nothing here replaces a crop protection adviser
- For countries whose data we cannot retrieve reliably we show what we do know and refer you onward for the rest
Raw data is the truth
Canonical rows are never edited by hand. A correction goes into a separate overrides table and is applied while reading. That way the correction survives the next import, instead of quietly vanishing at the following synchronisation.
Being able to look five years back
Withdrawn products are never hard deleted. A grower has to be able to look up a spraying from three seasons ago, and the retention period is five years. So there is a status on it, and no waste bin.
A mass withdrawal is usually a broken source
If a synchronisation run would withdraw more than a tenth of a whole country, it refuses itself, logs “partial” and leaves the old rows standing. A register quietly emptying out is the kind of fault you only discover once someone has made a wrong decision.
Anyone may read it
This is public government data, so reading is public. Only writing sits behind a lock, and that runs through the same coordination mechanism the rest of the platform uses.
Per country, and different in every one
Every member state keeps its own authorisations, in its own format, at its own rhythm, with its own way of grouping crops. There is no European button that fetches all twenty-seven. What we do is open them up one at a time and normalise them to the same model: product, active substance, use.
The Belgian register is the furthest along and has a page of its own, with the nightly feed from Fytoweb and the mapping onto EPPO codes. Read there what one country looks like close up: the Belgian plant protection register in FairGrow.
Working with codes rather than names is the precondition for doing this across borders. How that works is on the page about EPPO codes. And what you have to record about a spraying you carried out is under crop records.
What growers ask us
Does FairGrow block me if I enter something that is not allowed?
No. You get a warning with the expected and the entered value, and you can record why you are going ahead anyway. Blocking drives you to paper, and then there is no file at all. Warning plus a justification actually produces a stronger file.
Do I see the dose as well?
Yes. Since August 2026 the maximum dose is shown and also checked. That is a deliberate reversal of an earlier choice: by holding the dose back, people put the label next to the screen and retyped it, and that is not safer. The liability is handled with a clear notice, not avoided by leaving the data out.
My app is in French. Which register applies?
The one for the country where your plot lies. Language is presentation, country is regulation. A Walloon plot falls under Fytoweb even in a German-language app, and a Dutch plot under the Ctgb even in a French-language app. The country is derived once from the coordinates of your plot and then stored.
Why is my country not there yet?
Because we only add a country once we can retrieve the data reliably and repeatably. A half-loaded register that looks complete is more dangerous than no register. For those countries we show what we do know and point you to the official entry.
Can I see what was allowed last season?
Yes. Withdrawn authorisations stay in place with the withdrawal date and the use-up period beside them. And a check you had run at the time stays stored exactly as it read then, even if the register says something else today.
Ask the question for your own plot
Put your plot into FairGrow, pick your crop and your pest, and you see what is authorised for that combination in your country. With the dose, the pre-harvest interval and a link to the legal instructions for use.
Create your account → Go to crop records →