Institutional portal
Where the sector is governed
Verification queues and the block registry. In this prototype, an extension officer signs in here.
Kashmir Bee Information Portal
Kashmir’s honey is credible. Its record-keeping is not.
Farmore Hives is a proposed registry, traceability and advisory platform for apiculture in Kashmir. This page introduces it. The officer’s registry is a separate portal.
Sample record · Ganderbal
Apple blossom honey
HB-2026-0001
- Harvested
- 18 May 2026
- Quantity
- 42.0 kg
- Apiary
- Lar orchard
- Village
- Lar
Open the sample jar
Beekeepers
21
Apiaries
18
Colonies
22
Harvests
10
Demonstration figures for the Ganderbal pilot. Not an official count.
The problem
Open a point to read what the registry is meant to change.
A jar’s claim can’t be checked Origin and lab status live on paper, or nowhere.
A verified record is what makes the claim checkable. The sample jar on this site is a demonstration. A laboratory pass and a real code on a jar are later phases.
Disease outruns the report Thai sacbrood and Varroa move faster than a memo.
A field observation can be recorded now. Alerts and laboratory confirmation are a later phase.
Migration leaves no trail Movement out of the valley is undocumented.
The colony and its movement would sit on one record. That trail is a later phase.
Policy runs on estimates Production is reconstructed after the season.
A department would see the season as it happens, not six months later.
One spine of record. Three ways in.
Field app Works without a signal
This webpage stands in for the Android field app and does not work offline. The offline app is a later delivery.
Beekeeper
Your own record
Apply for the Ganderbal pilot, or sign in to the record that is already yours.
What success looks like
These are the outcomes the proposal is written to produce. They are not published case studies. Open one to read who it is for.
01 A beekeeper’s record becomes an asset.
The basis of a price premium, a subsidy claim, or an insurance case. Scheme eligibility is evidenced instead of argued.
02 A department sees the season as it happens.
Not six months later. Live reporting for the Department and SKUAST is a later phase.
03 A buyer gets a claim that is checkable.
That is what an export market pays for. The sample jar on this site is a demonstration. A laboratory pass and a real code on a jar are later phases.
Who it is for
Beekeeper
A record worth money: colonies, treatments and harvests in one place.
Beekeeper sign in
Extension officer
Assisted registration and a verification queue, instead of a file pile.
Institutional portal
Department and SKUAST The season, from operational data.
Production, species, disease and migration. That reporting is a later phase, so this card does not open a dashboard.
How a record is made
This is the path the prototype can walk today. Later phases stay labelled as later.
-
01
Apply
A beekeeper submits a Ganderbal application, or an officer registers someone. The colony estimate is a rough number.
-
02
An officer verifies the person
Verification is a separate judgement. It can also be sent back with a correction note.
-
03
Sites and colonies stay separate
An officer registers each apiary and each colony when the records exist. The first application does not require every hive.
-
04
Field logs follow verification
Inspection, feeding, treatment, a disease observation, and harvest attach to a colony after the beekeeper is verified.
-
05
A jar page can show a harvest
The sample jar is a demonstration. A laboratory pass and a real code on a jar are later phases.
Example workflows
Each card is an example workflow. These are not quotations, case studies, or claims about a real harvest.
Example workflow
Start with a profile
A keeper applies with a name, a village, and a rough colony count. Individual hives are registered later, one record at a time.
Example workflow
More than one site
A keeper can name one site on the application. Further sites are separate apiary records. Each site is confirmed on its own.
Example workflow
A harvest after a colony exists
Once the person is verified and a colony is registered, a harvest can be recorded. The sample jar shows one demonstration harvest.
Example workflow
A cooperative name, as text
The application can store a cooperative or FPO name. Cooperative accounts are a later phase.
Privacy and verification
What a jar may show
Name and village appear on a jar page only when the beekeeper has agreed. Mobile, email, and the note for the officer stay with the beekeeper and the block officer.
What verification means here
An officer records that they accept the person for this block. That is separate from a confirmed apiary site. It is not a certificate from SKUAST or the Department.
What the statuses mean
- Awaiting verification
- The application is with the block officer.
- Correction requested
- The officer asked for a change. The note stays in the history.
- Verified
- The officer accepted the person. Field logs can begin once a colony exists.
- Site unconfirmed
- The apiary is recorded. Its location is not confirmed yet.
- Site confirmed
- The officer accepted the coordinates for that apiary.