> 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/bulk-importing-of-products/label-info.md).
# Label Info
Label Information helps ensure the correct product information is available for labels, making labelling more consistent and reducing the need for manual updates.
Adding **Label Details** to your product setup in Supply’d provides a central place to store and manage information related to your food products, including ingredients, allergens, nutritional information, ingredient origins, and shelf life. When adding products in bulk, this information is entered into the Label fields in the CSV spreadsheet before it is imported into Supply’d, helping ensure the correct information is available for printing product labels, supporting compliance and traceability, and keeping product data accurate, consistent, and up to date.
{% hint style="success" %}
👉 See the [Adding Products in Bulk](/supplyd-erp/products/bulk-importing-of-products/adding-products-in-bulk.md) document for details on downloading the template and importing the information into Supply’d.
\
👉 See the [Product Info](/supplyd-erp/products/bulk-importing-of-products/product-info.md), [Purchasing Info](/supplyd-erp/products/bulk-importing-of-products/purchasing-info.md), and [Sales Channel Info](/supplyd-erp/products/bulk-importing-of-products/sales-channel-info.md) documents for details on completing the respective information in Supply’d.
\
👉 For details on adding products one at a time, refer to the [Adding a Product](/supplyd-erp/products/adding-products/adding-a-product.md) doc.
{% endhint %}
This document explains the labelling information required in the spreadsheet and provides guidance on completing each field.
***
### Completing the Label Info
{% stepper %}
{% step %}
#### Select the Information
Following the instructions for [Adding Products in Bulk](/supplyd-erp/products/bulk-importing-of-products/adding-products-in-bulk.md), document, tick **Label Info** in the **Fields** section in **Step 3**.
***
{% endstep %}
{% step %}
#### Complete the Sales Channel Info
Complete the template by opening it in a spreadsheet application, such as **Excel** or **Numbers**, and entering the required information. Follow the instructions provided, using the downloaded sample data as a reference when entering your information.
{% hint style="warning" %}
* Follow the column headings carefully.
* Do not change column names.
* Leave **ID** field blank for new records.
* Delete any sample data before importing.
{% endhint %}
{% hint style="success" %}
When updating product info, you can remove any columns from the CSV that you do not need to update. Keeping only the fields you want to change makes the import easier to manage and reduces the risk of unintentionally changing other product information.
For example, if you only want to update **Allergen Information** and **Nutrition Details**, keep the **Product ID**, **Allergen Information**, and **Nutrition Details** columns and remove the other fields from the CSV. Any fields that are removed from the CSV will not be changed during the import.
**Important:** Keep the **ID** column for every product you want to modify. The Product ID identifies the specific existing product that Supply’d should update when the CSV is imported.
{% endhint %}
{% hint style="danger" %}
**Important:** The title row should remain in the document in order for the system to match the columns when imported. You should remove the sample data before importing otherwise the system will create custom customers with the sample data.
{% endhint %}
**Country of Manufacture**
Select the country the product was made in.
**Percentage Australian**
The percentage of this items ingredients that are Australian. Applicable to products made in Australia.
**Ingredients**
Add any ingredients contained in this product. Leave blank if not applicable.
**Allergens - Contains**
Enter any allergens that **are present** in this product, separated by a comma (eg. "dairy, nuts"). Don't include leading statements such as "Contains". Leave blank if not applicable.
{% hint style="warning" %}
Use consistent naming for allergens across all ingredients. For example, if **Egg** is used for one ingredient, avoid using **Eggs** for another. Supply’d treats differently named allergens as separate entries, so inconsistent naming may result in both **Egg** and **Eggs** appearing in the generated allergen field instead of being combined into a single allergen.
{% endhint %}
**Allergens - May Contain**
Enter any allergens that **may be present** in this product, separated by a comma. Don't include leading statements such as "May contain". Leave blank if not applicable.
{% hint style="warning" %}
Use consistent naming for **May Contain** allergens across all ingredients. For example, if **Egg** is used for one ingredient, avoid using **Eggs** for another. Supply’d treats differently named allergens as separate entries, so inconsistent naming may result in both **Egg** and **Eggs** appearing in the generated **May Contain** field instead of being combined into a single allergen.
{% endhint %}
**Storage Type**
The type of storage required - **Ambient**, **Refrigerated** or **Frozen**.
**Recipe Goods Cost**
The total cost of all ingredients used in the recipe to produce this product.
**Recipe Labour Cost**
The cost of labor required to prepare the recipe.
**Recipe Total Cost**
The combined total of goods cost and labor cost. This gives the overall cost to produce the recipe.
**Recipe Size**
The total quantity or volume that the recipe produces (eg. number of units).
This helps in portioning and inventory planning.
**Recipe Expected Yield**
The standard or typical output quantity expected from the recipe.
This is the target amount you plan to produce under normal conditions.
**Recipe Min Yield**
The minimum quantity the recipe is expected to produce.
This accounts for natural variations in production.
**Recipe Max Yield**
The maximum quantity the recipe could produce.
This helps set realistic production limits and expectations.
**Recipe Yield Multiple**
Enter the multiple of units produced per batch. Production runs can only be scheduled in these multiples.
For example: If set to **5**, you can only schedule batches of 5, 10, 15, 20, etc.
* Leave blank to allow any batch size.
* Can be used in combination with **Minimum** and **Maximum Yield**.
{% hint style="success" %}
**Setting Yield for Bakers:** For bakers, it’s best to set the yield so that **1 yield = 1 deck (oven)**. This makes it easier to use **Deck Reports** to plan and track daily production.
{% endhint %}
**Recipe Unit Cost**
The cost to produce a single unit of the recipe.
It is calculated by dividing the **Recipe Total Cost** (ingredients + labor) by the number of units produced (**Recipe Size**).
**Default Smart Planner Method**
Enter the default method to apply when using the [Smart Production Plan](/supplyd-erp/production/smart-production-plan.md).
* **None:** To not set a default method for this product.
* **Made to Order:** Create production runs for each of your current Sales Orders.
* **Net Requirements:** Deduct your current Sales Orders and expiry from inventory throughout the date range, ensuring that stock stays above Min Hold.
* **Suggested:** Utilise your forecast rate of sale, stock expiry, and Min Stock Hold to keep you always in stock.
**Include in Deck Reports**
Whether to include this product in production deck reports. Enter "**Yes**" or "**No**".
{% hint style="info" %}
This field will only show when **Bakers Mode** is enabled in the [Production Settings](/supplyd-erp/settings/production-settings.md#production-defaults) section in your [Production Settings](/supplyd-erp/settings/production-settings.md).
{% endhint %}
{% hint style="success" %}
A **Deck Report** is a planning tool used in bakeries and production environments to organise daily production across ovens (or “decks”).
* The report helps optimise the baking schedule, making it easier to plan production, reduce bottlenecks, and ensure efficient use of resources.
* You can select which products appear on the report for a specific day.
* **1 deck = 1 oven**, so the report shows how many ovens are currently being used.
{% endhint %}
**Production Priority**
The **Production Priority** field is used to indicate the importance or urgency of producing a specific product.
**Nutrition - Servings Per Package**
This is the total number of servings in one full pack of your product.
For example, if a bottle contains 500ml and each serving is 250ml, then **Servings Per Package = 2**.
**Nutrition - Serving Size**
This is the amount of product in a single serving. It should reflect the typical portion someone would consume at one time.
**Nutrition - Remaining Fields**
The remaining fields capture the nutritional values of the product, both per serving and per 100g, as indicated in the field headings.
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.supplyd.co/supplyd-erp/products/bulk-importing-of-products/label-info.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
