> For the complete documentation index, see [llms.txt](https://docs.foodcore.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foodcore.io/recipes/publishing.md).

# Publishing vs draft

Every recipe in FoodCore has a status: either **Draft** or **Published**. This distinction controls where a recipe appears across the system — and getting it right means you're never accidentally printing labels or building menus from a recipe that isn't finalised yet.

## What draft means

A draft recipe is private. It's saved in FoodCore and fully editable, but it won't show up anywhere outside the Recipes section. Specifically:

* It **does not appear** in the Label Designer's recipe picker.
* It **does not appear** on menus.
* It **does not appear** in the orders section for item selection.
* It **is not included** in any published menu or price list.

Think of draft as your workshop. You can do everything — add ingredients, run costings, check margins, write methods — without anything leaking out to customer-facing parts of the system.

## What published means

A published recipe is live across FoodCore. Once published:

* It **appears in the Label Designer** so you can select it when designing a label.
* It **appears in menus** and can be added to menu sections.
* It **appears in orders** for item selection.
* It **contributes to Business Insights** reporting.

Publishing is not permanent or irreversible. You can unpublish a recipe at any time if you need to take it off the menu or pull it from label printing while you make changes.

## When to keep a recipe as draft

Keep a recipe as a draft when:

* **You're still testing quantities or ratios** — don't publish until the recipe is stable enough to repeat consistently.
* **Ingredient costs are incomplete** — if some ingredients are showing £0.00 because you haven't entered their prices yet, the cost per serving is inaccurate. Don't base pricing or margin decisions on incomplete data.
* **Allergen data is missing** — if any ingredient used in the recipe has a blank allergen status, the recipe's allergen declaration is incomplete. A label printed from this recipe could be wrong. Fix the allergen data first, then publish.
* **The recipe is seasonal or discontinued** — if you're not actively selling something, keeping it as a draft prevents it from cluttering menus and label pickers while preserving all its data for when you bring it back.

## How to publish a recipe

1. Open the recipe from the **Recipes** list.
2. Look for the status toggle in the **top-right area** of the recipe header — it shows the current status (Draft or Published).
3. Click **Publish** (or toggle the status to Published).
4. The recipe is now live across the system.

You don't need to save separately after changing the status — the status change saves immediately.

## How to unpublish a recipe

The process is identical:

1. Open the recipe.
2. Click the status toggle.
3. Select **Draft** (or click Unpublish).

The recipe disappears from menus and the label designer immediately. Any existing labels you've already printed or saved are unaffected — unpublishing doesn't retroactively change anything already in use.

## The label designer and draft recipes

By default, the Label Designer's recipe picker only shows **published** recipes. This is intentional — it prevents you from accidentally designing and printing a label for a recipe with missing allergens or incorrect costs.

If you need to work on a label for a recipe that's still in draft (perhaps to get the design ready before the recipe is finalised), you can temporarily switch the filter in the recipe picker to show drafts as well. Just be careful not to print that label for real until the recipe is published and complete.

## A good publishing workflow

A reliable pattern for new recipes:

1. **Create the recipe as draft** — add all ingredients and quantities.
2. **Check the cost per serving** and set a selling price.
3. **Verify allergen completeness** — make sure no ingredients have missing allergen data.
4. **Recompute** to confirm final costs.
5. **Publish** when you're confident everything is correct.
6. **Generate the label** and check it matches expectations.

This gives you a clear gate before anything goes out to customers.

## What's next

* [Create a recipe](https://docs.foodcore.io/recipes/create-recipe.md)
* [Fix missing data that's blocking you from publishing](https://docs.foodcore.io/recipes/missing-data.md)
* [Generate a label from a published recipe](https://github.com/CharliesGFTreats/foodcore-docs/blob/master/labels/generate-label.md)
* [Add recipes to a menu](https://github.com/CharliesGFTreats/foodcore-docs/blob/master/menus/add-recipe-to-menu.md)
