> 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/adding-products/product-details.md).
# Product Details
Products within Supply'd can be used to buy, sell or produce. There is a large amount of information & functionality you can set to configure the products to be used for their various purposes.
When adding a product to **Supply’d**, the **Product Details** section contains the key information used to identify and manage the product. This includes details such as the product name, SKU, category, description, and product type.
Completing these details accurately helps ensure the product is correctly set up and easy to find, manage, and use throughout Supply’d.
This document explains how to complete the **Product Details** section of the **Add Product** form when adding a new product to Supply’d.
***
### Completing the Product Details Section
{% stepper %}
{% step %}
#### Open the Add Product Form
1. Select **Products** from the main menu to open the **Products** page.
2. Click the **Add +** button in the top right to open the **Add Product** form.
{% hint style="success" %}
👉 The [Adding a Product](/supplyd-erp/products/adding-products/adding-a-product.md) document provides detailed instructions on how to open this form.
{% endhint %}
***
{% endstep %}
{% step %}
#### Complete the Product Details
The details about this product such as name, size, images, description etc.
**Brand**
Select or enter the brand of the product. For example, for **Sungold Full Cream Milk 2L**, the brand is **Sungold**. Select a brand from the suggested options, or type a new brand if it is not already listed. If the product has no brand, you can enter your **business name** instead.
{% hint style="warning" %}
Brand is a required field when selling on Supply'd. It helps identify who makes or supplies the product and ensures it appears correctly in the marketplace.
{% endhint %}
**Name\* \[required field]**
Enter the name of the product. Enter the product name without the brand or size, as these can be entered in separate fields.
For example, for **Sungold Full Cream Milk 2L**, enter **Full Cream Milk** as the product name.
**Size**
Enter the weight or size of a single unit of the product. Leave this field blank if you do not want to specify a size.
For example, for **Sungold Full Cream Milk 2L**, enter **2** as the size and select **Litres** from the drop-down menu. The size will be displayed to customers when purchasing the product.
{% hint style="info" %}
**Size**
These fields determine how items are tracked in Inventory and depends on how you want to manage them. For products you sell, make sure you keep the correct sizing as listed. For items used internally or in production, the requirements may differ depending on use.
For example, if you buy a 15 kg bag of sugar:
* If you want to track it as a single 15 kg bag, enter **15 kg**.
* If you want to track it in 1 kg units, enter **1 kg**.
It’s best to keep this consistent across your inventory, especially if you switch suppliers or use multiple suppliers with different package sizes, to avoid confusion and simplify reporting.
{% endhint %}
{% hint style="success" %}
If you do not need a **Size** (and **Measure**), and you want to keep stock as simple units, leave these fields blank. The system will recognise this and track inventory in units rather than by weight or another measurement type.
This is useful when the measurement is not important, or when the item is too small for weight to be practical.
For example:
* **Cello bags** - Each bag weighs almost 0g, so tracking them by weight adds little value. It is much easier to count them as individual units for selling and production.
* **Sugar decorations for cupcakes or cookies** - These are also very light, and during production you usually count how many decorations are needed rather than weigh them. For example, you may place a specific number on each cupcake or cookie.
{% endhint %}
**SKU**
Enter the SKU of the product. The SKU (Stock Keeping Unit) is a unique identifier used to identify and track the product. Each product must have a unique SKU, and the same SKU cannot be used for multiple products.
{% hint style="success" %}
Supply’d can generate a unique SKU for you. Simply click at the top right of the field.
{% endhint %}
**Category\* \[required]**
Select the category on your supplier profile where you want the product to be grouped. Supply’d allows you to create your own categories, giving you flexibility to organise products in a way that suits your business. Click or type in the field to view available categories.
For example, for **Sungold Full Cream Milk 2L**, you might use **Full Cream Milk** if you mainly distribute milk, or **Milk** if you sell a wider range of products.
**Departments**
Select the appropriate department or departments that the product belongs to. Your available departments may differ from the example, depending on how your business has named and organised them.
{% hint style="info" %}
This field will only appear if you’ve set up optional Departments within your [Locations](/supplyd-erp/settings/locations.md).
👉 Refer to the [Locations](/supplyd-erp/settings/locations.md#departments) section of the [Locations](/supplyd-erp/settings/locations.md) document.
{% endhint %}
**Unit Barcode**
Enter the barcode for one individual unit of the product. Use the barcode on an individual item inside the carton, rather than the carton barcode. This allows customers to scan the item and quickly find it in Supply’d for ordering or reordering.
**Carton Barcode**
Enter the barcode printed on the carton or outer packaging. This is useful when receiving purchase orders, as staff can scan the carton directly without opening it to scan an individual product.
**Product Image**
Upload an image of the product to Supply’d. A square image of at least **640 × 640 px** with a transparent background, such as a **PNG**, is recommended. **JPG** images are also supported.
**Description**
Enter a detailed description of the product to help customers make informed purchasing decisions. Include relevant information such as ingredients, allergens, and other useful product details.
**Tags**
Select from a set of predefined tags that describe the product, such as **Vegan, Vegetarian, Nut-Free**, or **Gluten-Free**. Customers can use these tags to find products that match their preferences. Click the field to view the available tags.
{% hint style="success" %}
👉 You can also add custom tags in the [Product Settings](/supplyd-erp/settings/product-settings.md#product-details) section in your [Product Settings](/supplyd-erp/settings/product-settings.md).
{% endhint %}
**Dimensions (cm)**
Enter the **width, height, and depth** of the carton in centimetres when shipped.
**Weight (kg)**
Enter the weight of the carton in kilograms when shipped.
For example, if **Sungold Full Cream Milk 2L** comes in a crate of 9 and each bottle weighs 2 kg, enter **18**. This information is used by third-party applications such as **Shippit** to provide live shipping quotes.
***
{% endstep %}
{% step %}
#### Complete Remaining Fields
Complete the remainder of the form as outlined in the [Adding a Product](/supplyd-erp/products/adding-products/adding-a-product.md) document.
{% 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/adding-products/product-details.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.
at the top right of the field.
{% endhint %}
