Custom batch registration app for the field and the shed
The trail of a batch rarely breaks in the office. It breaks at lifting, when two crates stand side by side, or at grading, when one batch splits into sizes that then go their separate ways. That is where it is decided whether you can still trace back where something came from in three years' time.
Where traceability fails in practice
A plant passport carries a traceability code that gives every batch of plants a unique code, alongside the botanical name, the company's phytosanitary registration number and the country code of origin. That code is only worth something if it survives the handling the batch goes through.
Traceability data must be kept for at least three years. In flower bulb growing, that is more than one cycle: a batch being delivered now was planted in a season that most people no longer remember exactly.
Then there is the naming. The rule is one cultivar, one name: a bulb crop may only be traded under a single name. Nobody in the field works with that name. There, a batch is known by the number on the crate or by the bed it stands in, and the translation to the official name happens later, from memory.
The fields and batches themselves must also be registered with the inspection service, with deadlines that are strictly enforced. What has happened in the field determines what should be in that registration, and that is precisely the information that takes longest to reach the office.
How we build this
The core is the handling of the batch. Planting, lifting, grading, storing and delivering are each a moment when the trail can break or be secured.
A code on the crate or the bed opens the right batch, with its name and history attached.
What was done, when and where, even without a connection. The field rarely has coverage, and the shed doesn't always either.
When grading, a batch falls apart; when topping up, something is added. Both must be recorded as lineage, not as a new batch.
Anything that stands out during the work goes into the file with a photo, instead of disappearing in a chat message.
What the app actually does
Registration at the batch carries the whole thing. What else you need depends on the size of your business and how many extra hands join during the season.
Scanning at the crate and bed
A code opens the batch without searching through a list. That is the difference between registering and not registering while you work.
Lineage when splitting
Grading turns one batch into several. The app records where each new batch came from, so the trail stays intact.
Works without signal
Fields, sheds and cold stores rarely have coverage. The app works locally and syncs as soon as there is a connection.
Observation with photo
Disease, an abnormal stand or a problem at lifting: a photo with location and time is quicker than a description.
Keep the name in view
The official cultivar name is shown with the lot, even if everyone in the field uses a number. That saves translating afterwards.
Works with gloves on
Large buttons and few fields. Anything that takes three precise taps won't happen on a lifting day.
Who we build for
Who does the recording differs per company. Four situations.
Crop workers
They are in the field and the first to see what deviates, but they have no time for a form with twenty fields.
Packhouse staff
During grading and packing, a lot splits into several. What isn't recorded there can't be reconstructed later.
Farm managers
They would rather see what's going on during the season than at the end, when the application has already been submitted.
Seasonal workers
Someone who joins for a few weeks must understand the recording in five minutes, or they won't do it.
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
Crops are added, operations differ per farm and inspection requirements shift. Operations, fields and codes should be configurable rather than fixed in the app.
Why Appfront
The trail breaks at grading
That's where one lot splits into several. We build the lineage first, because without it the rest of the file is decoration.
Scanning is the difference between doing it and not
Anyone who has to search for a lot in a list does it at the end of the day. Anyone who scans does it immediately.
In the field the number counts, in trade the name
We show both with the same lot, so nobody has to translate in their head.
Three years back is more than one season
The retention period spans several rounds. What isn't recorded now can no longer be traced at all.
Security and privacy
What is recorded in the field says something about your cultivation plan and about selections that don't have a name yet. That is commercially sensitive information, especially when seasonal workers are involved. We set access per role, show an employee only the lots they work on, and log who views what. Data stored locally on the device is encrypted and can be wiped remotely if a phone is lost.
For this topic, reliability at the moment of recording is the point. A lineage filled in after the fact because a question came up is no longer traceability. We record operations immutably with time, location and person, even when synchronisation happens later, and make a correction a visible correction alongside the original entry. How we handle security ourselves is described in our information security policy.
Frequently asked questions about on-site lot registration
Because the operation takes place at the crate and in the bed, often with gloves on and without signal. What is only filled in in the evening is a recollection.
Then one lot splits into several sizes. For each new lot, the app records where it comes from, so the trail back to the field stays intact.
Yes. Fields, packhouses and cold stores rarely have coverage. The app works locally and synchronises as soon as there is a connection again, keeping the original time.
Traceability data must be kept for at least three years. In bulb growing that spans multiple seasons, so an employee's memory isn't enough.
In the lot administration, where cultivar names, field registration and plant passport data come together. We describe that on our page about KAVB software.
That is a design requirement, not an afterthought. Scanning instead of searching, large buttons and few fields, so someone understands it within five minutes. See our approach to building an app.
Does your batch code survive sorting?
Take one batch that was sorted last season and trace back, per size, which original batch it came from. If that isn't recorded anywhere, your traceability is a reconstruction. We build this as a standalone app and as part of a broader app development project.