Skip to content
English
  • There are no suggestions because the search field is empty.

Data Load Sheet (DLS) upload errors: what they mean and how to fix them

If your Data Load Sheet (DLS) upload is rejected, the error message tells you which column has the problem and why. Search this page for your error (Ctrl+F or Cmd+F), fix the value in your file and re-import.

1. Required fields are blank

Error looks like: “[Field] can’t be blank”

These columns must have a value for every row:

  • CatalogueOrder
  • SKU
  • ProductName
  • AgeGroup
  • Gender
  • DisplayWholesale and DisplayRetail
  • WholesalePriceOriginal and WholesalePrice
  • RetailPriceOriginal and RetailPrice
  • AvailableMonths

Fix: Fill in the missing value for each row listed in the error.

2. The value doesn’t match what’s set up in Brandscope

Error looks like: “… does not exist in Brandscope” or “… does not exist for this brand”

Column What it must match
CompanyName The company you selected when uploading
BrandName The brand you selected when uploading
ReleaseName The release you selected when uploading
Brandscope Hierarchy A valid category from the Brandscope hierarchy [link to category list]
SegmentNames A segment already set up for your brand (the error lists the valid segments)
Source A source in your brand’s integration ID source list

Fix: Check spelling and spacing exactly. Make sure the company, brand and release you selected on the upload screen match what’s in the file.

3. The value isn’t one of the allowed options

Error looks like: “… does not exist in Brandscope. Please choose one of the following…” or “… is not valid”

Column Allowed values
AgeGroup Infant, Kid, Youth, Adult, Any
Gender Male, Female, Unisex
State Active, Inactive, Cancelled

Fix: Replace the value with one of the options exactly as shown.

4. Number fields are invalid

Error looks like: “… is not valid. Should be a whole number greater than 0” or “Should be a number greater than 0.0”

  • Whole numbers greater than 0: CatalogueOrder, PackUnits
  • Numbers greater than 0 (decimals allowed): WholesalePriceOriginal, WholesalePrice, RetailPriceOriginal, RetailPrice, DisplayWholesale, DisplayRetail

Fix: Remove currency symbols, letters, spaces and commas, and make sure the value isn’t 0 or negative.

5. Value is too long

Error looks like: “[Field] is too long (maximum is X characters)”

Column Max characters
ProductName 80
SizeBreak 40
DisplayWholesaleRange 20
All other text columns (SKU, ProductCode, Barcode, Collections, Divisions, Categories, ProductTags, ProductDisplayColour, AttributeType, Integration_ID, SalesTip, MarketingSupport) 500

Fix: Shorten the value to fit the limit.

6. Duplicate values

Error What it means Fix
“SKU+Colour should be unique. Another product with this SKU+Colour already exists.” Each SKU and colour code combination can only be used once within a brand. Check whether the product already exists. To update it, use the existing product’s row instead of adding a new one.
“Integration_ID should be unique” Each Integration ID can only be linked to one size break, across all releases. Give each size break its own Integration ID, and don’t reuse IDs from other releases.
“SKU/ProductColourCode/SizeBreak already exists” The same size appears twice for one product. Remove the duplicate size row.
“AvailableMonths must be unique” The same delivery month appears more than once. Remove the duplicate month.

7. Size break rules

A product either has no sizes (one row with a blank size) or sizes (every row has a size). It can’t have both.

  • “This product already has a blank size, cannot add more sizes.” means the product was loaded without sizes. Contact Support if you need to change it to a sized product.
  • “This product already has a size, Sizes cannot be blank for this product.” means the product has sizes, so every row needs a size value.

8. Delivery month not in the release

Error looks like: “AvailableMonths: Delivery month of … does not exist on given Release”

Fix: AvailableMonths must match one of the release’s delivery months. Check the release’s delivery months and correct the value, or contact Support if the release needs another month added.

Still stuck?

Contact Customer Success, Include the error message, the row number(s) and your DLS file.