Harvest Manager
The cost of a pound. Measured, not estimated.
Every input that touched the batch lands against the batch. So a harvest gives you a number, not a weight.
Most farm software ends at the scale. You log a weight, and the question everyone actually cares about — what did that pound cost me? — goes back to a spreadsheet somebody maintains by hand and nobody quite trusts.
Digital Cultivation tracks seed, media, nutrients, packaging, labor hours and energy against the cycle that consumed them. When the batch is harvested, the cost per pound is already there. It is then benchmarked against the live USDA terminal-market price for that crop on that day, and the COGS journal posts straight into the general ledger.
No re-keying. No shadow spreadsheet. No arguing at the end of the quarter about what a pound of basil actually cost to grow.
Questions
The things people actually ask.
How does the platform know what a batch cost?
Seed lots, grow media, nutrients and packaging are consumed against the cycle as they are used. Labor is attributed by time on task, and energy by metered kWh. When the batch is harvested, those inputs are already associated with it, so the cost per pound is a sum rather than an estimate.
What is the margin compared against?
The live USDA terminal-market price for that crop, pulled through the Market Prices module — so the margin reflects what buyers are actually paying on the day you harvested, not a figure typed in months ago.
Does this replace our accounting system?
It does not have to. The COGS journal posts into Digital Cultivation's own general ledger, and exports in a QuickBooks-ready format if you want your books to stay where they are.
See Harvest Manager on a real farm.
We'll walk an order all the way through to its margin — on live farm data, not a slide.