Projects and Price Books

Projects organize the culinary work. Price Books organize the purchasing reality behind that work.

What belongs in a project

Create a project when recipes and menus belong to a specific event, client, restaurant, venue, course, or production plan. A project can hold existing or newly created recipes and menus without removing them from your broader library.

Deleting a project does not automatically delete its source recipes and menus from the library.

What a Price Book controls

A Price Book contains the context used by costs, sourcing, suppliers, and shopping:

• city, region, country, and postal context;
• currency;
• vendors and products;
• active ingredient matches and price history;
• the price search location and radius used by sourcing.

The same recipe can therefore cost differently for two locations without creating two unrelated technical sheets.

Changing city or currency creates a new Price Book revision, because those change which market the prices belong to. Adjusting the search location or radius does not: it only changes where the next search looks, so your existing prices stay valid.

Reusing recipes

Recipes are reusable culinary assets. Add the same recipe to more than one project, then open it from the project whose Price Book you want to use. Ingredient quantities stay the same while matched prices and totals follow the active context.

Reusing menus

Menus are copied when you move them into another project. This protects the original menu while allowing the destination project to change its courses, dishes, and prices independently.

Switching context safely

Pages such as Products & Vendors, Costs, and Sourcing include a Price Book selector. Before importing or saving prices:

1. confirm the Price Book name;
2. confirm its location and currency;
3. perform the import, match, or sourcing search;
4. reopen one recipe to verify the expected cost.

Switching Price Books changes which catalog and prices you see. It does not convert or copy every supplier price into the other book.

Recommended structure

• Use the default Price Book for general library work.
• Use one project Price Book per real purchasing market.
• Reuse a Price Book only when location, currency, suppliers, and purchasing terms are genuinely shared.
• Name projects by client/location and service date when you manage many events.

Next: Products, vendors, and prices.