The allergen information is visible in the recipe overview but disappears in cooking mode. For a professional kitchen setting where cooking mode is used at the pass, the allergen status should be persistent and visible — not something you have to navigate away from cooking mode to check. A small always-visible allergen indicator in the cooking mode header (showing 'contains: dairy, gluten' or 'no common allergens') would address this for food service use cases.
The version history shows a diff of changes over time for one recipe. I want the ability to open two different recipes side-by-side and compare them — for example, my base carnitas recipe vs a variant I created for a lower-fat version. A side-by-side view with ingredients and method shown in parallel columns, with differences highlighted, would be very useful for deliberate recipe development.
The cook log is currently not accessible via the API — I can write cook log entries via the cooking_log.created webhook but cannot read historical entries. A GET /v2/recipes/{id}/cook-log endpoint would allow me to build external analytics on my cooking patterns — frequency, rating trends, yield accuracy over time. This seems like a straightforward addition given that cook log data already exists and is structured.
When browsing my recipe library I often want to add a recipe to this week's meal plan without opening it first. A single-click 'add to this week' button on the recipe card would save several clicks per recipe. Current flow: open recipe, navigate to meal plan, find the right day, drag recipe in. Proposed flow: hover recipe card, click 'add to week', select day from a small popover. For people who plan 5-7 recipes per week this is a meaningful time saving.
Right now recipe feedback happens outside burrito.ai — in this community, in messages, verbally. There is no way to attach a comment or discussion to a specific recipe within the app. A comment thread on each recipe (visible to the workspace team) would allow feedback to live alongside the recipe. For catering teams or cooking classes this would centralise the conversation that currently happens in Slack or email.
I batch cook every Sunday and about a third of what the app generates does not freeze well. I find out on Wednesday. A freezer flag on generation, or better, a freezer mode that biases the whole recipe towards things that hold up. Underdone eggs, cubed potato instead of shredded, nothing fresh, no soft dairy. The knowledge is all in this community already. It just is not in the app.
Raised this as a bug and it turned out to be one, so this is the broader version. Exclusions should be a hard constraint applied at every point the app suggests an ingredient. Generation, substitution, scaling, the shopping list, all of it. Right now they are applied once at generation and everything downstream forgets. If I have excluded something it is usually because it makes the food inedible to me, not because I mildly prefer otherwise.
I’m a big fan of the recent improvements that you have made to the dashboards, it allows me to do in-depth analytics and generate the reports that I use in my QBRs. It would be even better if we have more filtering options available such as:Company Sign up date Age AccountRight now I need to get this data elsewhere and combine data sets.What do you guys think?
Please add an ability to convert any useful instruction or answer provided by any community member to Article.Actually it is one of trending features of modern communities - to collect community knowledgebase by users instructions which can solve a lot of cases then. It would be nice every article has its own direct link to have an ability to provide it to customers.This ability allows to save moderator's time (he/she does not need to create such articles him-/herself). Also users trust other users more than brand representatives. And also it might be used as an additional engagement approach - user's whose posts become articles feels respected and/or might be promoted.
Hello,Company dashboards would be so much easier to interpret if the same properties when used would ALWAYS have the same color.Example: I have created several dashboards that compare different metrics within different target countries. In each of those dashboards, those countries have different colors assigned automatically and I can’t seem to be able to change that.That makes no sense at all.Thanks,- Raphael
It would be great to have the ability for users like me to award badges to other users! I was recently helped on the community and I would love to give a ‘helpful’ badge to another user! I understand you may not want to give users the ability to award badges but I think it could really increase engagement, and who knows, we might come up with some badges you wouldn’t have thought of! ?
Hi Company,While creating new dashboard and new reports, it can be very beneficial to add team notes to explain why I used certain properties, or timeframes. Can you consider adding a team notes feature so I can include basic background information with reports?I created a short illustration to explain what I mean:Team notes in practice!Thanks,-Josephine
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.