...
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:
Name / Description / Item / Whatever (requiredCustomer (Required)
Date of revenue (required) [default to day of creation and shown]
Category Type (required) [selected via tile on previous screen and not shown on creation]
“Is the revenue associated with agricultureagricultural activities?” (required)
“Yes” (default), “No”
“Would you like to associate this revenue with crop(s)any crops?” (optional) [multi-select]
User should be able to select any number of active of crop plans
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
...
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 |
|
Should the attributes of revenues be defined at the “template” level or the “instance” level? If defined at the “template”, can users overwrite at the instance? Are there some of each? | Kevin’s proposal (to be debated) Defined by revenue type:
Defined at creation:
Duncan Brain + Joyce Sato-Reinhold + Sayaka Ono + David Trapp | |
What attributes should be shown for each revenue type? (e.g. Crop sales, Event hosting, Tourism, Consultations, Crafts) | Crop sales: Shown:
Assumed, and therefor not shown:
All others (including custom): Shown:
Assumed, and therefor not shown:
|
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”.
...