FRD Sample
KisanMarket Functional Requirements
A functional requirements document sample describing modules, permissions, fields, and rules for the MVP.
Functional requirements
| ID | Module | Requirement | Acceptance criteria |
|---|---|---|---|
| FR-01 | Browse | Users can filter listings by crop, category, state, district, price, and grade. | Filtered results update without page refresh and clear action resets filters. |
| FR-02 | Listing | Each listing shows crop, variety, farmer, district, price, quantity, grade, trust tags, views, and minimum order. | Missing optional tags do not break the card layout. |
| FR-03 | Buyer | Buyers can open a listing and submit structured enquiry details. | Quantity, delivery city, and contact method are validated before submission. |
| FR-04 | Farmer | Farmers can create and manage crop listings. | New listings enter pending review if admin approval is enabled. |
| FR-05 | Admin | Admins can approve, reject, flag, and audit listings. | Every admin action stores timestamp and reviewer identity. |
Core data fields
- Listing: crop, variety, category, price per kg, available quantity, minimum order, grade, tags.
- Location: state, district, village or market area, pickup or dispatch notes.
- Farmer: name, verification status, phone verification, farm profile, listing history.
Business rules
- Price and quantity must be positive numeric values.
- Verified labels can only be assigned by admin or verification workflow.
- Buyer enquiry must include intent quantity above the listing minimum order.