Reusable/shared recipe stages (when edited the changes apply to all recipes using them)

Ideas & feature requests
1

Creation of “Fermentation and Conditioning Profiles” feature that allows a user to build multiple fermentation profiles that encompass all the “post wort creation” recipe stages.

-A recipe could then utilize these fermentation profiles.
-Multiple recipes could utilize the same fermentation profile.
-Editing at the Fermentation Profile level could update the planned batches and all new batches to utilize this new version of the profile. Similar in function to the way batches utilize recipes.

2

Thanks for the suggestion, Tait. This sounds very interesting - we love the idea of reusing information like this.

What would you want to define in a fermentation/conditioning profile? What information would be stored and how would it be “used” by Breww?

3

Thanks Luke.

Most of the things I’d like to include in a fermentation/conditioning profile I’d also like to be able to do as outlined in the logic based recipe stages feature request that I posted about here.

The difference is that it would be nice to create these “fermentation profiles”, utilize one profile across multiple recipes, edit the profile and have it update all future batches of the recipes that utilize that profile (in much the same way as you already utilize recipe changes to apply to planned batches of that recipe).

This would be much more efficient that having to build each recipe from scratch or copy recipe stages from other recipes. That said, it’d be great, when creating a recipe, to utilize an existing “ferm profile” or “modify an existing profile” thereby creating an alternate/new version of the profile.

I’m not sure quite what you mean by “what information would be stored” but as far as how the info would be “used” by Breww, its along the same lines as the other feature request: Once created, applied to a recipe, and a batch of that recipe is initiated, Breww would prompt the user to perform the checks, take actions or whatever is required as defined by the “fermentation profile”.

1 Like
4

Thanks for the extra info, Tait.

Am I correct in saying that:

  1. You’d like some additional features on receipt stages, and these are covered by Logic based option for "Edit Timing" of actions in Recipe Stages (but may be used in this request too)?
  2. You’d like to have “Reusable recipe stages” that can be built once and then shared across multiple recipes? When you edit the reusable stage, all recipes containing it will have the changes applied?

Thank you.

5

Correct on both fronts Luke.

1 Like
6

Perfect, thanks for confirming. I’ve updated the title of the feature request to make this clear. Hopefully this can pick up some more votes as it would be a great feature.

1 Like
7

I can see how shared recipe templates could be incredibly valuable for brewers to exchange knowledge while adapting processes to their specific equipment. Let me clarify and expand on your idea to make it more precise.

Improved Recipe Sharing System Concept

A shareable recipe template system could work by:

  1. Creating a base template with standard brewing stages (mash, lauter, boil, fermentation, etc.)
  2. Adding customizable parameters for each brewer’s specific equipment and preferences
  3. Implementing a code-based sharing system similar to Breww’s reporting link-codes

The key distinction would be that unlike the current shared stages (which propagate changes to all recipes using them), these templates would serve as starting points that each brewer could then customize without affecting the original.

For example, a “Traditional Pilsner Template” might include:

  • Standard mashing schedule framework
  • Typical hop addition timing points
  • Fermentation temperature profiles
  • Expected gravity targets
  • Common QC checkpoints

But each brewer could then adjust:

  • Specific mash temperatures for their system
  • Water chemistry adjustments
  • Equipment-specific flow rates
  • Facility-specific procedures

Would this align with what you’re envisioning? The sharing mechanism could generate a unique code that, when imported, would create a new recipe instance based on the template but independent from the original.

1 Like
8

Thanks for the comments, Robert and apologies for the delay in getting back to you.

It didn’t, but I do really like the suggestions, so we can certainly look to include some of these ideas when we get to this project. This is why the community can work so well, as everyone can get involved with ideas and help shape them before they go into development, so thank you for the comments :pray:

You can already create a recipe that uses another beer’s recipe as a starting point. To do this, go to the “base” recipe and duplicate it. Once it has been duplicated, you can edit which beer it is associated with to move it to another beer. This process can work well within a single account, but doesn’t work across accounts, like your “share code” version would.

I love the idea of people being able to help others with “base” recipe sharing across accounts, just like we have with Raw data explorer reports :+1:

1 Like