operacion y costos
Cost per block: how to do it right without a giant ERP
A 3-step methodology to calculate real cost per block every week, without waiting on the annual ERP close.
May 08, 2026 · 7 min · AgroSynapse team
If you still decide which block to renew using last year's close, this is the next-60-days guide.
The problem isn't the ERP, it's the cycle
Most ERPs used by fruit growers work. What doesn't work is when they deliver the numbers. A typical per-block close lands between March and April, when the season is already over and there is nothing left to adjust.
Getting out of the annual cycle does not require replacing the ERP. It requires building a small operational pipeline that runs in parallel, week by week, on the same data the ERP eventually reconciles.
The 3-step methodology
Pick the allocation unit
The block is the minimum operational unit. Every work order, wage and input is allocated to one or more blocks, with a written rule for shared costs (admin, supervision, central irrigation).
Capture at the source
Data enters when the operation runs: the crew finishes a task and clocks it; crop-protection leaves the warehouse and is allocated; the pump reports kWh per block. The supplier invoice reconciles later — it isn't the source.
Close and publish weekly
A fixed day, a fixed owner, a standardized report to 4 people (GM, field lead, agronomist, controller). The team stops debating whether the number is right and starts debating what to do with it.
What the weekly report looks like
The report has to show:
| Block | Content |
|---|---|
| Unit cost | Per kilo for each block. |
| Comparison | Variance vs. last week and vs. budget. |
| Ranking | Top 3 most profitable blocks and top 3 most expensive. |
| Drill-down | Which line items explain each variance (labor, inputs, services). |
What about the ERP?
The ERP remains the accounting authority and the system of record for formal closes. The difference is that it is no longer the bottleneck for decisions. When the annual ERP close arrives, it brings no surprises — it only confirms what the operation already knew 11 months earlier.
The mistakes we see most often
Next steps
To try this methodology without replacing your ERP, AgroSynapse's Cost per block module already runs half of this pipeline in production: capture at source, weekly close and line-item drill-down, with cost per kilo for each block. The per-hectare and per-plant cut doesn't exist yet — for now, hectares only work as a prorating driver for shared costs, not as their own cost unit. The PDF guide walks through each step in detail with downloadable Excel templates and two real cases of operations that moved from annual to weekly close per block.