Field counts Weather and growing days Sales planning

Custom open-field vegetable harvest forecast app

Appfront builds apps that let growers of field vegetables forecast, per plot, when and how much can be harvested. Based on planting data, field counts and the weather, so that sales, labour and transport are planned in time. Not a gut-feeling estimate, but a forecast that learns every week.

What is a harvest forecasting app?

A harvest forecasting app combines what you know about a plot with what is happening outside. The planting date, variety and planting layout are fixed. The counts you take during the season tell you how the crop is doing. The weather, translated into growing days, tells you how quickly it will progress. From these three, you get an expected harvest date and expected quantity per plot, looking ahead week by week.

Without an app, that forecast lives in the head of the grower or crop adviser, and it is often not far off. The problem is that sales, labour planning and transport cannot make use of it. A customer who wants to know what is coming in three weeks gets an estimate over the phone. A forecast that lives in a system can be shared and can later be compared with what was actually harvested.

We build custom because every crop grows differently and every business counts differently. Leek, lettuce, broccoli and cauliflower each have their own relationship between growing days and harvest readiness, and a grower with thirty plots counts differently from a sales organisation with three hundred. The app should follow your crops and your way of counting.

Counting in the field

Enter a count per plot on your phone, with a photo, so the forecast rests on real observations.

Weekly forecast

The expected harvest date and quantity per plot and per crop, added up into a weekly overview for sales.

Learning from the difference

After the harvest, the app compares forecast and reality, per variety and per plot. The next season starts smarter.

How we build your harvest forecasting app

We start with how you forecast today, because that knowledge lives in people's heads and we don't want to lose it. Then we build the app around that knowledge, not alongside it.

1
Mapping crops and counts

Which crops, which varieties, how counting is done and when. We also look at last season's forecasts and how far off they were.

2
Plot and planting data

Plots, planting data, varieties and planting layout in the app, with an integration to your crop registration system if you have one.

3
Building the forecast

Growing days from the weather, field counts and the grower's experience, combined into one forecast per field. We test against a past season before we forecast ahead.

4
Sharing and taking over maintenance

The weekly overview goes to sales, labour planning and transport, in the format they need. After that, we take over maintenance of the app and adjust the forecast each season.

What a harvest forecast app actually does

The components below together make up the forecast. Which ones you need depends on how many crops and fields you track.

Fields and planting records

Field, crop, variety, planting date and area, with the map alongside so a count lands in the right place.

Counts with photos

Enter a count or an assessment per field, with photo and date. Even without signal out in the field.

Weather and growing days

Temperature and rainfall per location, converted into growing days per crop.

Forecast per field and per week

Expected harvest moment and quantity, with a margin and the counts the forecast is based on.

Weekly overview for sales

All fields added up per crop and per week, ready to share with buyers and the sales organisation.

Post-season review

Forecast against actual harvest, per variety and per field, so the forecast gets sharper every season.

Who we build a harvest forecast app for

The app is intended for businesses that have to commit to buyers on what is coming and plan people and transport around it.

Growers with multiple fields

Leeks, cabbage, lettuce or broccoli across dozens of fields that ripen at different times. You want to know each week what is coming.

Grower associations and sales organisations

You combine members' forecasts into an offer for buyers. Each member's forecast needs to arrive in the same format.

Businesses with their own processing

Your cutting plant or packing hall plans around what comes from the field. The forecast is the line's schedule.

Contract growing for industry

You supply a processor that asks for volumes by the week. The forecast determines whether you meet the agreement or have to buy in.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

The app works on your phone in the field and in the browser at the office. If you are mainly interested in recording sprayings and crop operations, see our page on a spray registration app. For the administration of the whole business there is agricultural administration software, and you can read about our approach at building an app.

For the office, with sales, labour and transport aligned to the forecasts, there is our harvest forecast software for open-field vegetables.

If you want to plan picking rounds per row in fruit growing and record the crates per picker, see our picking list app for top fruit.

iOS and Android Offline working in the field Weather data per location Growing-day model per crop Field maps Photos with counts Integration with crop records Export to sales organisation Integration with staff planning Reporting per season

Why Appfront for your harvest forecast app?

A forecast is never exact. The value lies in the margin, in sharing it and in learning from the difference.

The grower's knowledge stays in charge

The app calculates, the grower corrects. A forecast that ignores thirty seasons of experience is not trusted and not used.

Test on last season first

We have the app forecast what you already harvested last year. Only when that matches do we forecast ahead.

Your own code, your own data

The forecast and the history are yours. A package that disappears does not take seasons of counts with it.

Security and privacy in a harvest forecast app

Field and harvest data are commercially sensitive, especially when shared with a sales organisation or a buyer. We build sharing as a deliberate choice per field and per period: you decide who sees which forecast and at what level of detail.

Counts and forecasts are stored per version, so you can look back at what was predicted at any given moment and what it was based on. That is the basis for the post-calculation and for a conversation with a buyer about a deviation.

Frequently asked questions about a harvest forecast app

Questions growers ask before they get started.

An app that predicts, per plot, when and how much can be harvested, based on planting data, counts in the field and the weather. The forecast is totalled per week for sales and compared with reality after the harvest, so it gets better every season.

That depends on the crop, the counts and the weather. We start with a range rather than a single figure and first test the app on a past season. As more seasons are added, the range narrows per variety and per plot.

Usually not more often, but in a more structured way. The counts you do now go into the app with date, plot and photo. Where a count is missing, the app uses growing days. For each crop, we look at the moments when a count adds the most.

Yes, in the format they ask for and at the level of detail you choose. A weekly overview per crop is enough for most sales organisations; the plot level stays with you.

The set-up does, the growth model doesn't. Each crop has its own relationship between growing days and harvest ripeness, and we configure that per crop based on your own seasons. Start with the crop that brings in the most and add the rest afterwards.

Yes. Planting data, varieties and plots are often already in a crop registration system or a GlobalG.A.P. file. We pull them from there rather than re-entering them, and the harvest data can be sent back if you wish.

The forecast adjusts to the growing days, but no model can see a hailstorm or a flood. That is why the grower can override the forecast per plot with a reason, and that correction remains visible in the post-calculation.

Want to make your weekly harvest predictable?

Tell us which crops you grow and how you currently forecast. We'll look at a past season with you and show what a forecast would concretely deliver in your situation.

Edit content