Zipli

Zipli is a B2B food-surplus platform that connects professional kitchens with redistribution hubs across Finland, turning food that would otherwise be thrown away into logged, matched, and delivered donations. We came in as a technical and UX partner to help the Zipli team get the product built and usable for the people actually doing the work.

The problem. The people who generate the data — cooks, kitchen porters, hub staff — are on their feet during a shift, not at a desk. Any system that asked them to fill in forms or learn a new tool was going to be ignored, no matter how good the reporting on the back end looked. Meanwhile restaurants had no real-time view of what they wasted or why, and redistribution hubs were coordinating donations by phone call and spreadsheet.

What we did. We worked alongside the Zipli team on the technical build and the UX for the people on the floor: logging a batch of surplus food had to take seconds, work one-handed on a phone, and need no training. We spent time understanding where friction actually killed adoption for kitchen and hub staff, then helped implement the matching and delivery flow so it runs quietly in the background — kitchen teams log, the system matches and notifies the right hub, and management gets a portfolio-wide view without anyone doing extra admin.

What shipped. A mobile-first logging flow that takes under 30 seconds, a matching system that connects surplus to the nearest suitable recipient, and a dashboard giving restaurant groups and hubs real-time visibility into waste trends and impact — with kitchen teams reporting fast adoption and hubs cutting coordination time by roughly 70%.

Visit getzipli.com →