Build Recipes have been replaced by Variants

[!note] This feature has been retired. Build Recipes are no longer part of BidCraft. The same job they did — keeping your install doctrine consistent across many services — is now handled directly on each service through a simpler concept called Variants.

If you're reading this from an old bookmark, here's the short version of what changed and where to go.

What replaced Build Recipes

Two pieces of the workflow Build Recipes used to handle now live in different places:

• Sharing materials and tasks across similar services → use Variants on the service detail page. Pick a parent service, hit Create variant, and a deep copy is made with your existing materials and tasks. The variant gets a small badge row showing what's different (size, material, pattern, or any other qualifier you add). Each variant can be edited independently after the copy.
• Setting your go-to product for a slot once and having every service use it → use favorite-for-role on your materials library. Tag any product as a favorite for one or more material roles and Biddy uses it automatically wherever that role appears.

Together these two features cover what Build Recipes did, with less indirection. The install doctrine lives on the service that needs it, the product preferences live on the library, and Biddy ties them together.

Where to go next

• Building your service catalog — covers Variants, the Create Variant modal, and modifier badges in full
• Service materials and favorite-for-roles — how roles + favorites replace the recipe defaulting layer
• Your materials library — where you tag favorites
• How job type templates work — the proposal-level layer (unchanged)