Work · Disk 02
Intake & batch tracking
Deliveries, batches and stock across two facilities during harvest.
- React
- Supabase
- Tablet-first UI
- PDF exports
30 sper delivery at intake
2facilities on one system
0paper logs by week three
Olive oil processor · 5 weeks
ClientOlive oil processor, Messinia
Team size8 people, 2 facilities
Timeline5 weeks
ModulesWeighbridge intake · Batches · Tank stock · Grower statements
ServiceCustom CRMs
Before
- Deliveries logged on paper, typed up weeks later
- Stock known only at season end
- Grower statements took a fortnight
After
- Thirty-second tablet intake at the weighbridge
- Live stock per tank, per facility, from a phone
- Statements generated in one click
The problem
During harvest a regional olive processor receives hundreds of deliveries a week across two facilities. Weights, growers and batches were logged on paper and typed up weeks later, so nobody knew stock levels until the season was over.
What we built
- A tablet intake screen for the weighbridge: grower, weight, variety, timestamp — thirty seconds per delivery.
- Batch tracking from raw olives through pressing to tanks, with yield calculated automatically.
- Live stock per tank per facility, visible to the owner from anywhere.
- End-of-season grower statements generated in one click.
How it went
Live before the harvest started. Weighbridge intake takes thirty seconds a delivery, the owner checks tank stock from his phone, and end-of-season grower statements went out in a day instead of a fortnight.
30 s
per delivery at intake
2
facilities on one system
0
paper logs by week three
Have a similar problem?
Fixed price after a discovery visit. Reply within two working days.
Start a project