> 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/product-types/product-types-overview.md).

# Product Types Overview

Product types in Supply’d help you organise, manage, and filter products more efficiently, making it easier to track and streamline your inventory.

**Product Types** in Supply’d are a powerful way to categorise and manage your products. By assigning types, you can group similar items, filter product lists, and apply settings or rules more efficiently. This helps streamline inventory management, simplifies reporting, and ensures greater accuracy across your product catalogue. **Product Types** are selected when [Adding a Product](/supplyd-erp/products/adding-products/adding-a-product.md).

<figure><img src="https://2965503026-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDaPYJDB89ny0x7wcMedb%2Fuploads%2FryM0fQ35EvijtcxSJ9Mc%2FProduct%20Type%20Drop%20Down.jpg?alt=media&amp;token=8f812d9d-7494-4859-8243-0857abc810da" alt="" width="563"><figcaption></figcaption></figure>

**Standard**

The most common product type. It is a single product with no advanced traits.

👉 See [#standard](#standard "mention") below for more details.

**Bundled**

A bundle of multiple products within one parent product. An additional section, **Bundled Items**, will show when this is selected.

👉  The [#bundled](#bundled "mention") section explains this a little more.

**Recipe**

A product that is made up of a number ingredients produced at the time of sale, eg. a burger at a restaurant. An additional section, **Recipe Items**, will show when this is selected.

👉 See the [#recipe](#recipe "mention") section below.

**Shipping Carton**

A shipping carton used during the packing stage, such as a bread tray, bread crate, produce crate, carton or box.

👉 See [#shipping-carton](#shipping-carton "mention") below.

**Carton Container**

A pallet, trolley, stillage, etc that shipping cartons may be packed into for shipping.

👉 See [#carton-container](#carton-container "mention") for more details.

**Gift Note/Card**

A gift note/card that can be configured to be automatically generated and printed. An additional section, **Gift Note/Card Settings**, will show when this is selected.

👉 See [#gift-note-card](#gift-note-card "mention") for guidance on this Product Type.

**Production**

A product that can be manufactured using the production module. When "Production" is selected, additional sections will appear.&#x20;

👉 Learn more in the [#production-product](#production-product "mention") section below.

**Breakdown**

Separates one input into multiple trackable products, such as processing oilseeds into oil and oilseed cake.

👉 Refer to the [#breakdown-product](#breakdown-product "mention") section for more information.

**R\&D**

A Research and Development product that functions similarly to a **Production Product**, but remains excluded from other areas of Supply’d and is primarily available within the **Production** module while under development.

👉 Find out more about this Product Type under [#r-and-d-product](#r-and-d-product "mention").

**Labelling Details**

The **Labelling Details** section is available for **Standard**, **Bundled**, **Recipe**, **Production** and **Breakdown** Product Types and contains the information required for accurate product labels.

👉 For a brief overview, see [#labelling-details](#labelling-details "mention").

{% hint style="success" %}
The same product may be assigned a different Product Type depending on how your business prepares, sells and tracks it. The examples in this document are provided for guidance only and do not prescribe how a product must be configured.

For example, a burger prepared when ordered in a café may be set up as a **Recipe Product**, while a burger made in advance by a ready-to-eat meal company may be better suited as a **Production Product**. Choose the Product Type that best matches your business processes and inventory requirements.
{% endhint %}

***

### Standard

A **Standard** product type refers to a regular, standalone product that you buy and use or sell as-is. It is not made up of other products (like a bundle) and isn’t something you produce (like a production item).

In Supply’d, a Standard Product can be:

* Purchased and sold directly to customers.
* Purchased and used in production, such as food ingredients or packaging.
* Purchased for internal use only, like cleaning supplies.

In general, any item that you want to keep in inventory and that doesn’t require changes or assembly can be classified as a Standard Product. If you do not need to track the inventory, purchasing or usage of items such as cleaning supplies, you do not need to add them as products in Supply’d.

{% hint style="success" %}
👉 For full details on completing this, see the [Adding Products](/supplyd-erp/products/adding-products.md) documentation.
{% endhint %}

***

### Bundled

In Supply’d, a **Bundled Product** combines multiple products into a single package or offer. Each component remains a separate inventory item, while the bundle is sold and displayed as a single line item on the order. Bundles are most commonly used for retail products and are generally assembled at the time of sale. During fulfilment, the individual items within the bundle can be picked, packed and assigned to specific inventory batches.

For example, a gift hamper assembled when an order is placed would typically be set up as a **Bundled Product**. If the hamper is assembled in advance, either a Bundled or Production Product may be suitable. However, use a **Production Product** if you need to track the finished hamper as a separate inventory item.

**Why Use Bundled Items?**

1. **Simplified Sales**
   * Bundles appear as one line item in a sales order, making order entry quick and customer-friendly.
   * For example, instead of entering Pasta, Pasta Sauce and Parmesan Cheese separately, you can sell them as a "Italian Dinner Bundle".<br>
2. **Flexible Pricing**
   * Set a fixed price for the whole bundle (eg. “Italian Dinner Bundle – $25”)
   * Great for discounts, promotions, and upselling.<br>
3. **Order Management**
   * Bundles keep orders tidy by showing as one product.
   * You can expand the bundle in the system to see the individual components if needed.

**Examples:**

\
**Unicorn Bundle** – 1 Pink Chocolate Unicorn + 1 White Chocolate Unicorn + 1 Blue Chocolate Unicorn.

**Gift Hamper** – Assorted Chocolates + Biscuits + Tea + Jam.

**Italian Dinner Bundle** – Pasta + Pasta Sauce + Parmesan Cheese.

{% hint style="success" %}
👉 For full details on creating and managing a Bundled Product see the [Bundled Products](/supplyd-erp/products/product-types/bundled-products.md) documents.
{% endhint %}

***

### Recipe

A **Recipe Product** is made from multiple components, such as ingredients or other items. When the finished product is sold, Supply’d automatically deducts the required quantity of each component from inventory.

Unlike **Bundled Products**, the individual items within a **Recipe Product** cannot be picked, packed or assigned to specific batches. When the Recipe Product is sold, Supply’d automatically reduces the inventory of these items using **FIFO** (first in, first out) or **FEFO** (first expired, first out), depending on your inventory settings.

This makes Recipe Products ideal for cafés and restaurants, where staff prepare items at the point of sale without creating production runs or managing picking, packing and batch assignments. For example, a café burger would typically be set up as a Recipe Product.

**Key Features**

1. **Defined Components (Ingredients)**
   * A Recipe Product has a list of items (with specific quantities) that make up the final product.
   * For example, a “Burger” recipe might include a bun, patty, lettuce, onion, tomato and sauce.<br>
2. **Automatic Inventory Deduction**
   * When you sell a Recipe Product, Supply’d automatically deducts the right amounts of each ingredient from stock.
   * This keeps inventory levels accurate without manual adjustments.<br>
3. **Cost Tracking**
   * The cost of the Recipe Product is calculated from the costs of its components.
   * This helps with pricing, profit analysis, and cost control.<br>
4. **Flexibility**
   * Recipe Products can be used in sales orders or bundled with other items.
   * Great for cafes or restaurants who need to manage raw materials and finished goods.

**For Example:**

Burger:

* 1 × 50g Burger Bun
* 1 × 86g Beef Patty
* 50g Lettuce
* 20g tomato
* 15g onion
* 7ml Tomato Sauce

{% hint style="success" %}
👉 For a full step-by-step guide on how to add and configure a Recipe Product, refer to the [Recipe Products](/supplyd-erp/products/product-types/recipe-products.md) documents.
{% endhint %}

***

### Shipping Carton

**Shipping Carton** product type is used to represent the packaging materials (like trays, boxes, crates or cartons) used to ship customer orders.

Key points about Shipping Cartons:

* They're not sold to customers but are part of the fulfilment process.
* Can be assigned in [Adding Products](/supplyd-erp/products/adding-products.md#fulfilment-rules) to determine how products are packed for picking and dispatch.
* You can track their stock levels to ensure you don’t run out of packaging.
* Useful for planning and managing dispatch operations efficiently.

Use this type to keep control over the materials that help get your products out the door.&#x20;

***

### Carton Container

A **Carton Container** is a larger transport unit used to hold one or more shipping cartons during staging, transport, and delivery. Common examples include pallets, trolleys, stillages, roll cages, and dollies.

Key points:

* Holds one or more shipping cartons.
* Used to consolidate cartons for easier handling and transport.
* Typically moved through the warehouse and loaded onto delivery vehicles.
* Can represent reusable equipment such as trolleys or pallets.
* Can be used in [Adding Products](/supplyd-erp/products/adding-products.md#fulfilment-rules) to determine the appropriate transport container based on the shipment size or volume.

***

### Gift Note/Card

**Gift Card/Note** product type is used for items like gift cards, gift notes, or messages that can be added to a customer's order.&#x20;

These products:

* Can still be added to orders like any other product.
* Are helpful for personalised customer experiences or promotions.

{% hint style="success" %}
👉 Refer to the [Gift Notes & Cards](/supplyd-erp/products/product-types/gift-notes-and-cards.md) for more details.
{% endhint %}

***

### Production Product

A **Production Product** is a product that can be manufactured within Supply’d using the **Production Module**. This is typically used for items you make in-house from raw materials or components (for example, baking bread, blending coffee, or assembling a kit).

A **Production Product** is typically used when products are made in advance, often in batches, rather than prepared at the point of sale. It allows you to track the ingredients, stages, labour, costs and inventory batches involved in creating the finished product.

For example, a pizza prepared when ordered in a café would usually be a **Recipe Product**. However, pizzas manufactured in bulk for wholesale or supermarket sale would generally be **Production Products** because they are produced in advance and require batch and cost tracking.

Production Products can combine multiple inputs into one finished product or convert a single input into another product, such as processing seeds into oil.

{% hint style="info" %}
An oil producer processing seeds into oil only may use a **Production Product**, as one input becomes one finished product. If the process produces both oil, meal, husk etc., a [#breakdown-product](#breakdown-product "mention") may be more suitable because one input creates multiple outputs.
{% endhint %}

When you select **Production** as the product type, additional sections and settings will appear. These allow you to:

* **Define the Bill of Materials (BOM)** - List all ingredients or components required to produce the item.
* **Set Production Steps** - Outline the processes or stages involved in making the product.
* **Track Costs** - Capture both material and labor costs to calculate accurate production expenses.
* **Manage Inventory Movements** - Automatically deduct raw materials from stock and add the finished product into inventory once production is completed.

This setup ensures accurate stock control, clear visibility of production costs, and smooth management of internally manufactured products.

{% hint style="success" %}
👉 For a full step-by-step guide on how to add and configure a Production Product, refer to the [Adding a Production Product](/supplyd-erp/production/adding-a-production-product.md) documentation.
{% endhint %}

***

### Breakdown Product

A **Breakdown** Product Type separates a single input into several usable output products that can each be tracked individually in Supply’d. For example, an oil producer may process oilseeds into oil and oilseed cake. This differs from a standard **Production Recipe**, which combines multiple ingredients to create one product.

Here's a few examples where this feature may be useful :&#x20;

**Butcher**&#x20;

* **Input** - 1 whole animal carcass.
* **Output** - Various cuts (eg. steaks, mince, bones, fat).
* **Why it’s useful** - Allows accurate tracking of yield and component inventory.

**Oil Producer**

* **Input** - Bulk seeds or raw oil.
* **Output** - Refined oil, meal, husk, waste.
* **Why it’s useful** - Splits raw input into sellable products and by-products.

{% hint style="info" %}
If an oil producer processes seeds into both oil, meal, husk etc, a **Breakdown Product** may be suitable because one input creates multiple outputs. If the process produces oil only, a [#production-product](#production-product "mention") may be more appropriate because one input becomes one finished product.
{% endhint %}

{% hint style="success" %}
👉 The [Creating a Breakdown Product](/supplyd-erp/production/creating-a-breakdown-product.md) document takes you through the process of adding a **Breakdown Product**.
{% endhint %}

***

### R\&D Product

An **R\&D Product** is a **Research and Development Product** used to develop and test products before they are ready to become standard products. R\&D Products function similarly to **Production Products** and can be used with the **Production Module** to test recipes, production processes, costs, and finished products while keeping them separate from your regular products.

When you select **R\&D** as the product type, you can:

* **Define the Bill of Materials (BOM)** - Add the ingredients or components required to produce the product.
* **Set Production Steps** - Define the stages and processes involved in producing the product.
* **Track Costs** - Track material and labour costs to review production costs and margins during development.
* **Perform Production Runs** - Produce and test the R\&D Product through the normal production process.
* **Manage Produced Inventory** - Once a Production Run is completed, the finished R\&D Product will appear in inventory where its stock can be managed.
* **Submit for Approval** - When development is complete, submit the R\&D Product for approval before creating it as a standard product, if approval is required.

R\&D Products remain separate from your regular products while under development, allowing you to test and refine them without making them available to customers. They only become visible once approved and configured for the appropriate sales channels.

{% hint style="success" %}
👉 See the [R\&D Products](/supplyd-erp/products/product-types/r-and-d-products.md) documentation for more information.
{% endhint %}

***

## Labelling Details

The **Labelling Details** section appears when you select **Standard, Bundled, Recipe, Production**, or **Breakdown** product types. It captures all information needed for accurate product labelling, especially for food items.

**Key Information Included:**

1. **Ingredients** – Lists all ingredients, including allergens. For Recipe or Production items, this can be auto-populated from components.
2. **Nutrition Information** – Displays values like calories, fat, protein, and sugar for regulatory compliance and customer transparency. This can also be automatically populated from the components of Recipe and Production products.
3. **Storage Type** – Indicates recommended storage conditions (e.g., refrigerated, frozen, ambient).
4. **Additional Details** – Can include serving suggestions, preparation instructions, or warnings.

{% hint style="success" %}
👉 For full details on adding the labelling details information, see the [Labelling Details](/supplyd-erp/products/adding-products/labelling-details/labelling-details.md) document.
{% endhint %}


---

# 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/product-types/product-types-overview.md?ask=<question>&goal=<user_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.
