01Outcome
Proof that matching could work
A feasibility prototype and a live direction at regiobiomatch.de — showing that bioregional menu planning can be guided by data, not guesswork.
Web App · 2024
Match regional organic menus to what farms actually have in season.
RegioBioMatch is a digital matching service for community catering — connecting bio producers, processors, and large kitchens so menus are planned around what is actually available in the region.
Funded as a technical feasibility study, the platform links two data worlds: regional product supply and canteen recipes, then suggests menus an algorithm can stand behind.
01Outcome
A feasibility prototype and a live direction at regiobiomatch.de — showing that bioregional menu planning can be guided by data, not guesswork.
02Project context
Community kitchens in Heilbronn and Hohenlohe want more bioregional food on the plate. Small producer structures, limited processing, and fragmented logistics mean nobody shares one view of what is available and what is needed.
RegioBioMatch was funded as a technical feasibility study to test whether a digital service could match canteen menus with regional organic supply.
03My role
I joined as designer without a formal backlog — only workshop boards, domain experts, and loosely structured research scattered across documents and calls.
My job was to synthesize that chaos into testable flows: journeys for producers, processors, and canteen planners, then wireframes and prototypes the team could react to.
04Menu matching
Kitchens plan menus around what the algorithm can actually match — registering a canteen, composing recipes, and seeing which regional bio products fit each dish based on seasonality, quantity, and certification.
There were no tickets — just Miro boards, stakeholder calls, and pages of unstructured notes about producers, processors, and canteen planners. I translated that noise into the first end-to-end flows: register a kitchen, plan a menu, and see which regional bio products the algorithm could match to each recipe.
Menu planning — matching canteen recipes to regional bio availability.
05Product catalog
Producers and wholesalers expose what they have in a searchable catalog — so kitchens can understand regional inventory before committing to a menu, and suppliers gain planning security from clearer demand.
Producers and wholesalers needed a place to expose what they actually have — quantities, certifications, ripeness, seasonality. The catalog view makes that inventory legible so kitchens can search, filter, and understand what the region can deliver before they commit to a menu.
Product catalog — regional bio inventory for producers and processors.
06Reflection
The hardest part was not the UI — it was finding the right model inside noisy research. Once the three actor types and the two-database logic clicked, the interface followed.