Production traceability
Cultivar connects receiving, production, quality, storage, and shipment records around a traceable batch history.
Interactive no-backend prototypeWorking prototype
Every control below changes local browser state. Use the navigation inside the product, complete the sample workflow, and reset it whenever you want to replay the story.
Use the reset control inside the application to return to the seed scenario.Loading prototype… / Cargando prototipo…
Starting point
In this fictional operation, receiving lots, production sheets, quality checks, storage moves, and shipment lists lived in separate files and paper packets.
A hold could stop a pallet, but understanding every upstream ingredient and downstream allocation required several people and careful cross-checking.
Customer ask
The modeled brief asks for fast two-direction trace, an explicit quality-hold state, a complete recheck record, and linked shipment allocation.
Release must stay a human decision with a reason, owner, and visible history; the interface must never imply certification by itself.
What we designed
The selected batch becomes the spine of the workspace. Ingredient lots sit upstream, process steps and quality checks form the center, and shipment records show downstream exposure.
Recording the sample recheck changes the local hold state and linked shipment language together, demonstrating one record without making a food-safety claim.
Scene by scene
A searchable work list makes current hold and release state explicit.
Status was split between production paperwork and quality follow-up.
Search or select a fictional batch to update the complete trace workspace.
Ingredient lots, process steps, checks, storage, and shipments remain connected.
Teams had to manually reconstruct which records belonged to one batch.
Switch seed-to-shipment or shipment-to-seed and expand individual steps.
Reason, affected quantity, check result, owner, and permitted next actions stay together.
A hold label did not explain the evidence or the release path.
Record a passing recheck, then release the sample batch with confirmation.
Every linked allocation inherits the current batch disposition.
Downstream lists could lag behind a quality decision.
Watch linked shipment state change after the local release workflow.
What the concept connects
All batches, suppliers, checks, quantities, and shipments are fictional. This concept does not certify safety, send a recall, control equipment, or persist a release.
Next application
Grant application reviewBring the people, records, exceptions, existing tools, and decisions. We will help define the smallest complete application worth building.
Discuss your applicationRoasted tomato base