Planning what an order needs

From the order to the oven

“Plan recipes” on an order turns every line into production. A product’s recipes are multiplied by the quantity ordered. An item priced from a recipe is planned at the amount sold. A tiered cake is planned once, whatever the count. Two boxes of macarons and a two-tier cake become shells, ganache, sponge and filling, with amounts already right.

• Product recipes times the quantity ordered
• A tiered cake once, with all its tiers
• Recipe-priced items at the amount sold
• A prompt right after the order is saved

Choosing the day

A week of days opens, each showing the plans it already has. “+” on a day starts a new plan. “Add to this plan” folds the recipes into one that exists, such as Friday’s, where another wedding’s sponge is already listed. Either way the editor opens for you to check the rows and save. Nothing is written until you do.

From a recipe, as scaled

“Plan” on a recipe offers a production plan or an order. The amount goes in as you have it on screen. Scale the brownie to the 30 cm tray first, and the plan gets that tray and that amount. A recipe with sub-recipes asks whether they come along, scaled from the same amount.

When a recipe arrives twice

When what you add meets the same recipe in the same unit, “Merge duplicates?” asks per recipe. One row with the amounts added up, or separate rows. Friday’s 1 kg of vanilla sponge plus a new 800 g becomes 1.8 kg or two batches. A recipe baked in a tin is never merged. Each bake keeps its row.

Common questions