1.
Bale Count Entry for All Baling Types
When recording baling activities on crop-share fields, the system only allows me to enter acres baled unless the baling is linked to a harvest event (such as hay). For straw baling, since the crop was already harvested earlier, I cannot record number of bales produced.
On our farm, we track both acres baled and bale counts for hay, straw, and silage. Bale counts are important for our yield tracking, inventory, custom work, and crop-share calculations.
It would be helpful if the baling activity allowed bale count input for all materials, not just hay tied to harvest.
2.
Equipment Cost Tracking Should Support “Per Bale” Rates
For our operation, baling costs are tracked on a per bale basis, not per hour. Currently, the system only supports hourly cost tracking.
Our operators often don’t record or track machine hours, but bale counts are always logged, so hourly tracking doesn’t line up with how we manage costs.
Adding the option to track equipment costs per bale would make cost allocation more accurate for our workflow.
Guest
