> 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/product-info.md). # Product Info Product Information helps ensure products are created accurately and consistently, making it easier to maintain your product catalogue and reducing manual data entry. When adding products in bulk, product information is entered into the **CSV** spreadsheet before it is imported into Supply’d. The **Product Information** fields contain the basic details about each product, including its name, description, SKU, category, and tags. This information helps identify, classify, and organise products within Supply’d, making it easier to manage inventory, track items, search for products, and support accurate reporting. Completing the product information accurately ensures products are created consistently and correctly in your product catalogue. {% 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 [Purchasing Info](/supplyd-erp/products/bulk-importing-of-products/purchasing-info.md), [Label Info](/supplyd-erp/products/bulk-importing-of-products/label-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 product information required in the spreadsheet and provides guidance on completing each field. *** ### Completing the Product 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 **Product Info** in the **Fields** section in **Step 3**.
*** {% endstep %} {% step %} #### Complete the Product 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 the **Price** and **Category**, keep the **Product ID**, **Price**, and **Category** 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 %}
**Id** The **ID** is the unique identifier of a product in Supply’d. * **For existing products:** Enter the product’s ID to update it. * **For new products:** Leave this tab blank so Supply’d can assign a new ID automatically. This ensures Supply’d correctly matches updates to existing products while preventing conflicts for new products by letting the system generate a unique ID.
**SKU** Enter the SKU of the product. This should be a unique identifier for the product. The same SKU cannot be used on multiple products. The SKU is used to match products when updating so it is strongly recommended not to leave blank.
**Brand** Enter the brand or the manufacturer of the product. In the example of : Full Cream Milk 2lt, the brand would be "Sungold". The brand is optional if you do not sell the product.
**Name** Add the product name. As the brand and size can be entered in alternative field you would enter it without the extra details. For example if you have a Sungold Full Cream Milk 2lt you would simply enter the name as "Full Cream Milk".
**Size** Add the unit size of the product to be used in conjunction with the **Size Measure** field. For example, with our product Sungold Full Cream Milk 2lt we would define the size as "2".
**Size Measure** Enter the unit size measurement of the product to be used in conjunction with the **Size Unit** field. For example with our product Sungold Full Cream Milk 2lt we would define the size measure as "Litres" or "l". Possible values are: * "Grams" or "g" * "Kilograms" or "kg" * "Millilitres" or "ml" * "Litres" or "l" * "Ounces" or "oz" * "Pounds" or "lb" Any alternative measures will be ignored.
{% hint style="info" %} **Size & Size Measure** 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 **Size 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 %}
**Barcode** Enter the barcode of the product. This should be the barcode of an individual item in the carton. This allows customers to scan an item to find it quickly in Supply'd for ordering or re-ordering.
**Carton Barcode** Add the barcode on the carton of this product (if different to the unit barcode).
**Description** Enter a detailed description of the product. This is useful to give customers extra information to assist them with making their purchasing decisions. For example, you may include any allergen information and/or ingredients as well as descriptive details of the product.
**Category** Add the category on your supplier profile that you would like this product to sit under. Supply'd is flexible with categories to allow you to define your own so you can group your products in any way you choose. For example, with our product **Sungold Full Cream Milk 2lt**, if you are a milk distributor you may opt to have a **Full Cream Milk**"category, or if you sell lots of other products not just milk you may opt to have the category as simply **Milk**.
**Tags** Enter any tags that suit the product, separated by a comma. Supply’d provides a set of predefined tags used to classify and match specific product attributes, such as whether a product is vegan, vegetarian, nut-free, or gluten-free. These tags help customers filter and search for products more effectively. For example, customers can use tags to find all vegan products that match a specific search query. Available options are: * Biodegradeable * Compostable * Gluten Free * Vegan * Vegetarian * Dairy Free * Nut Free * Egg Free
{% hint style="success" %} 👉 You can also add custom tags in the [Product Editing](https://help.supplyd.co/configuring-supplyd/settings/product-settings#product-editing) section in your [Product Settings](https://help.supplyd.co/configuring-supplyd/settings/product-settings). {% endhint %}
**Width** Enter the width of the carton in centimetres when shipped.
**Height** Add the height of the carton in centimetres when shipped.
**Depth** Enter the depth of the carton in centimetres when shipped.
**Weight (kg)** Enter the weight of the carton in kilograms when shipped. For example, if a product weighs 500 g on its own, but weighs 1 kg once the required shipping packaging is included, the weight entered should be **1**.
{% hint style="success" %} For our example product, **Sungold Full Cream Milk 2L**, each bottle weighs 2 kg and is shipped in a crate of 9. The crate weighs 1kg. The total shipping weight is therefore **19 kg**, so **19** would be entered as the product weight. {% endhint %}
This weight is used by third-party applications such as **Shippit** to provide accurate live shipping quotes. It should account for the product plus any packaging or shipping materials included in the shipment.
**Type** Enter the type of product this is. Options are:
* Breakdown * Bundled * Carton Container * Gift Note/Card * Production * Recipe * Shipping Carton * Standard
{% hint style="success" %} 👉 For more details on **Product Types**, refer to the [Product Types Overview](/supplyd-erp/products/product-types/product-types-overview.md) document. {% endhint %}
**Sell Product** Whether or not you sell this product. Enter **Yes** or **No**.
**Price** Enter the default sell price for this product, including tax.
**Sale Price** If this product is on sale, enter the sale price here. Leave blank for no sale price.
**Tax Type** If tax, such as GST, is applicable to this product when selling, enter the tax type, eg. "GST". Leave blank if tax does not apply.
**Unit Rrp** Enter the recommended retail price (RRP), including taxes, for a stockist to sell one unit of this product.
**Avg Unit Cost** Add the average cost for one unit of the product.
**Pack In Carton** Whether or not this item should be packed in a shipping carton when shipped. Enter **Yes** or **No:** * **Yes**: The item would be packed in an aggregated shipping carton during packing. * **No:** The item would ship as is with no additional cartons.
**Version Of** This field links a new product to an existing one when you're creating an updated version (like a recipe or packaging change). It helps you track changes while keeping the product history clear.
**Is Discontinued** Whether this item is discontinued. Enter **Yes** if the product is discontinued.
**Notes** Add any desired notes about this product - for internal reference only.
**Departments** Enter the department(s) this product belongs to. {% hint style="info" %} This field will only appear if you’ve set up optional Departments within your [Locations](/supplyd-erp/settings/locations.md). {% endhint %}
**Custom - Ambient Shelf Life** This is an example of a custom field. The shelf life of this product.
**Custom - Ticket Name** Another example of a custom field. The name that will appear on the shelf ticket for this item.
{% hint style="success" %} Custom fields are additional fields you can create for yourself, and they may differ from those in our example above. 👉 See the [Product Settings](/supplyd-erp/settings/product-settings.md#custom-fields) section of the [Product Settings](/supplyd-erp/settings/product-settings.md) document for details on how to add these. {% endhint %}
{% 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/product-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.