...
Maintain or expand the ability to document a crop sale
Several common categories of incomes / revenues
Crop sales
Event hosting
Tourism
Consultations
Crafts
A standard flow for adding a new instance of revenue that covers at least the following attributes:
Description (optional)
Date of income (required) [default to day of creation]
Category (required) [selected via tile]
“Is the revenue associated with agriculture?” (required)
“Yes” (default)
, “No”
“Associated with crop(s)?” (optional) [dependent on “Is the revenue associated with agriculture?” being “Yes”]
User should be able to select any number of active of crop plans
Revenue location (optional)
“On farm”, “Off farm”, null
Customer(s) (optional)
Notes (optional)
Ability to easily add several revenues back to back (but not within the same flow)
Saved revenues must correctly attribute revenue categories and crop types
...
Ability to add several revenues in the same flow
Ability to mark a revenue as repeating
Ability to attribute revenues to particular crop(s)
Non-functional Requirements:
...
Question | Answer | Date Answered |
---|---|---|
Should we call money coming into the farm “Revenues” or “Income”? | Revenues |
|
Are there other revenue types we’re not tackling now? Why? | Yes! Per user meeting on . Then there were several that they mentioned, but I think we'll handle them once we add the relevant functionality:
Processed goods: As discussed in the past, we might want to wait on this as there is additional complexity to this. Probably need to add a "processing" task | |
Out of scope
Documenting “CSA boxes” as a revenue source; reasoning is the complexity of documenting new CSA boxes each period. Should likely be implemented as a “template”.