The table below explains each of the fields that can be imported and how they should be used:
|SKU||Each product should be assigned a unique SKU. These are particularly important when integrating with sales channels, but also for searching for products, importing inventory or updating products via an import.
|Name||Enter the product name in this column. Ensure that variants are given the exact same name - option columns must be used to assign the distinguishing details such as color or size.||Yes|
|Brand||Every product must be assigned a brand. The import will fail if no existing brand can be matched. However, it is possible to create new brands as part of the product import.||Yes|
Every product must be assigned to at least one category. The import will fail if no existing category can be matched. However, it is possible to create new top-level categories as part of the product import.
Note that these categories can be manually moved after the import if it should be a sub-category of another.
Enter "Yes" in the spreadsheet to set the product as stock tracked, or "No" to set the product as non-stock tracked.
If this column is included but left blank the products will be set as non-stock tracked.
If products are created with the incorrect status, they can be changed in batch from the product list. Products with stock in the system cannot be set to non-stock tracked.
Set the product to 'Live' or 'Archived'. If this field is not included the product will be set to Live.
Any products with stock which are assigned a status of 'Archived' will be set to 'Discontinued'.
|Long description||This will populate the long description on the product record. It is populated most effectively by importing the text written within html tags.|
This will populate the long description on the product record. It is populated most effectively by importing the text written within html tags.
|Weight||These fields are used to assign measurements to products. The unit settings for these fields can be set via Settings > Products/Inventory > Inventory settings.|
|Barcode||The product's barcode.|
|Collection||Enter the name of the collection the product belongs to. It is possible to create new collections at the point of import.|
|Tax class||Enter the product tax code, e.g. T20 or T2.
(Not applicable in the US)
|Taxable item||Specify whether the product is taxable or not by entering "Yes" or "No".
|Sell code||Enter the sales account (nominal) code, e.g. 4000.|
|Buy code||Enter the purchase account (nominal) code, e.g. 5000.|
|Stock code||Enter the stock account (nominal) code, e.g. 1001 (used when cost of sales accounting is on).|
|Supplier||Assign a vendor (supplier) to the product - one per import. Importing with a different name will not remove previously assigned vendors (suppliers).|
These four fields are used to assign a default warehouse location to products. Where standard warehouse locations is activated the inventory will be automatically moved by importing this information.
Note: The locations must already exist in order to be assigned - they cannot be created by the import.
|Reorder level||Define the minimum inventory level for products. If inventory falls below the quantity defined then the item will be listed on the low inventory report.|
|Reorder qty||If items must be purchased from vendors (suppliers) in batches, use this field to record the quantity.|
This column is used to create the item as a bundle of other products.
A bundle product requires its own row on the import file with the SKUs of the items (or components) within the bundle listed in this field. The component SKUs will need to either already exist in Brightpearl or be listed (and therefore created) before the bundle line in the import file.
Component SKUs must be listed in this field as "SKU:quantity to be bundled" and separated by a comma, e.g SKU001:2,SKU002:1,SKU003:1.
Note: If no quantities are entered, a value of 1 is assumed
|Reporting season||A product can belong to multiple categories and seasons within Brightpearl. These fields allow you to choose a single category that you always use for reporting on the product.|
|Primary vendor/supplier||Sets the primary vendor (supplier) against your product records. Assigning a primary vendor (supplier) to a product will also adopt them as a regular supplier.|
|UPC||Include these fields to record UPC, EAN and ISBN codes.|
Include price list fields to add the price for a product. Price list fields are always titled "Price (CODE)" where "code" is the price list code.
Prices should always be entered at net (excluding tax).
Remember to import using 4 dp if your products need it!
Note: price breaks can only be imported through the price list import.
Options such as "color" or "size" will each need to be added in order to assign the option values to product variants.
Note: the options must already exist in the system (though missing option values can be created using the import).
Any existing custom fields can be added to a data map. When including custom fields they will always be titled "PCF_EXAMPLE".
When importing data for Yes/No custom field types, enter the digit 1 in your file to represent 'Yes' or the digit 0 to represent 'No'.