Approved inputs, finally readable
We rebuilt the product sheet around a single question: can I use this on this crop, at this stage, today? Everything else comes after.
By Nabatic product team
An approval sheet is an administrative document. It is accurate, complete, and just about unusable standing in a field with a phone in your hand.
What the farmer is actually looking for
We watched people search for products in real conditions. The question is never “what are the characteristics of this product.” It is always one of these three:
- Am I allowed to put this on my crop?
- How much do I use?
- Can I still harvest next week?
The official sheet answers all three, but four screens of scrolling and a seven-column table later.
Three answers, before anything else
We turned the sheet upside down. At the top, three lines only, computed for the crop the farmer declared:
Approved on your crop — green, red, or amber when approval exists but for a different use.
Dose for your area — not the rate per hectare, the quantity for the declared plot, in the unit of the container sold in the shop.
Pre-harvest interval — in days, with the resulting date. “21 days” requires mental arithmetic; “not before 25 June” requires none.
Everything else — active ingredient, chemical family, hazard statements, conditions of use — is still there, below, in full.
Filtering by crop changes everything
A product approved on twelve crops shows twelve dose lines. Eleven do not concern the user, and it is in those eleven lines that dosing errors are born.
Since the sheet opens filtered on the crop from the diagnosis, dosing questions in the chat have halved.
What we do not show
We never propose a product that is not approved on the crop concerned, even if it is technically effective, even if the practice is widespread. When no authorised product fits, the app says so and the agronomist takes over.
An input database is only worth something if you can trust what it does not show you.
- #inputs
- #compliance
- #product
