> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/supplyd-erp/products/managing-products/printing-recipe-sheets.md).
# Printing Recipe Sheets
Printing Recipe Sheets provides a quick and convenient way to access recipe information, ensuring staff have accurate ingredients, quantities, and preparation details when needed.
**Supply’d** allows you to generate and print **Recipe Sheets** directly from a product’s page. Recipe Sheets provide a convenient way to view and present recipe information, including ingredients and preparation details, for reference or use during production.
{% hint style="success" %}
**What is a Recipe Sheet?**
A **Recipe Sheet** is a document that provides detailed information about a recipe in a clear, organised format. It can include key details such as ingredients, quantities, and preparation instructions recorded in Supply’d.
\
Recipe Sheets are only available for products with a Product Type of **Production** or **Recipe**.
{% endhint %}
This document explains how to print a **Recipe Sheet** from a product's page.
***
### Printing a Recipe Sheet
{% stepper %}
{% step %}
#### Select the Product
1. Select **Products** from the main menu to view your list of products.
2. Select the product you want to print a **Recipe Sheet** for.
{% hint style="success" %}
Use the search feature in the top right to quickly find the product you are looking for.\
{% endhint %}
***
{% endstep %}
{% step %}
#### Select Download > Recipe Sheet
Click the 3 dots in the top right, then select **Download > Recipe Sheet**.
The **Print Recipe Sheet** form will open, allowing you to select your options for printing **Recipe Sheets** for the selected product.
{% hint style="success" %}
To open or close the **Customisation** section on this form, click the small arrow to the right of the section, as circled in red above.
{% endhint %}
Complete the fields following the guidelines below:
***
{% endstep %}
{% step %}
#### Template
**Template\* \[required field]**
Select the template to use when generating the **Product Recipe**. Choose a **Custom** template if you have created your own recipe template, or select a **System** template provided by Supply’d.
The available **System** templates are **Product Recipe** and **Product Recipe Costing**.
{% hint style="success" %}
👉 See the [Templates](/supplyd-erp/settings/templates.md) document for details on creating custom templates.
{% endhint %}
***
{% endstep %}
{% step %}
#### Customisation
Complete this section if you want to customise the appearance of your **Recipe Sheet**, such as using a different font or adding a logo (see note below).
**Font\* \[required field]**
Select the font you want to use for the text.
**Logo**
Select the logo you want to display on the recipe sheet. Leave the field set to **None** if you do not want to include a logo on the sheet.
{% hint style="warning" %}
**Note -** This setting only applies to templates that utilise the {{logo\_image}} tag.
{% endhint %}
***
{% endstep %}
{% step %}
#### Click Print
Click to generate the **Recipe Sheet** for printing or downloading.
The **Product Recipe Costing** sheet provides a detailed breakdown of the costs associated with producing the product, including ingredient and labour costs.
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.supplyd.co/supplyd-erp/products/managing-products/printing-recipe-sheets.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
to generate the **Recipe Sheet** for printing or downloading.
