The Restaurant Technology Guys Podcast brought to you by Custom Business Solutions · Restaurant Technology Guys Podcast, sponsored by Custom Business Solutions

Empowering Restaurants with Foodini: A Deep Dive into Allergen and Dietary Management

·38 min·2 clips

Dylan cites a 400% increase in food allergy lawsuits and says incidents continue even after staff are notified.

1. The Restaurant Technology Guys podcast focuses on Foodini’s ingredient-level transparency for allergens and dietary needs. 2. Jeremy Julian hosts, Erika is a restaurant-tech operator and Foodini co-founder, and Dylan is an Irish corporate lawyer turned co-founder who brings the consumer celiac perspective. 3. The episode asks how restaurants can document ingredients accurately enough to serve diners with allergies, intolerances, and diet preferences. 4. Erika says she started at Campus Food, then worked at SinglePlatform, Slice, Seated, and Odeko before meeting Dylan. 5. Dylan says he was diagnosed with celiac at age 10 and spent years trying to understand what was in restaurant menu items. 6. The founders describe Foodini as a system that powers ingredient-level transparency across the food ecosystem. 7. Foodini says it works with restaurants and hotels to tag menu data with ingredients, allergens, and dietaries. 8. The platform then powers personalized menus for more than 100 diets and allergens through QR codes and website buttons. 9. Erika says restaurant allergen handling still relies on manual staff training and menu labeling. 10. She says current online-ordering tools often tag only the top eight allergens and miss modifier-level changes. 11. Dylan says the problem affects more than people with the big nine allergens because consumers also ask about strawberry, kiwi, keto, low FODMAP, and food-sensitive diets. 12. He says a report found that 54% of allergy incidents happen after staff have already been notified. 13. He also says food allergy lawsuits have increased by 400% in the last few years. 14. Erika says restaurants often lack documented recipes and product detail, which makes ingredients like the mayo in aioli hard to track. 15. She says Foodini works from the recipe source, breaks recipes into sub-recipes, and keeps the consumer-facing menu from exposing chef recipes. 16. Dylan says the platform keeps consumers in the safety loop while still encouraging them to tell the chef about any allergy. 17. The conversation stays practical and technical, with Jeremy using examples like a twice-baked potato and a binder at lunch service. 18. The tone is interview-driven and operational, with frequent back-and-forth on menus, modifiers, and restaurant workflow. 19. Restaurants evaluating allergen labeling, menu data, or digital menu tools would find it useful. 20. Operators who only serve a narrow menu and ignore dietary transparency may not care as much.

As heard by us

A practical look at ingredients, allergens, and diets through restaurant workflow.

Foodini's pitch stays close to a real restaurant problem: ingredients, allergens, and diets are messy, and the discussion keeps returning to how the tool can help operators, technologists, and consumers without losing that practical focus.

Read the full review in PlayNext →

Why you'd press play

If allergens, ingredients, and diets are keeping your night noisy, this one gives you a calmer map.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from The Restaurant Technology Guys Podcast brought to you by Custom Business Solutions