Style Import Fields and Rules

When Use market pricing layout is enabled, use Additional Markets with Price Type (One Price, Price By Size, Price By Colour) and separate rows for each Price Type (Buy, Sell, RRP, …) category.

Steps to resolve:

1. Read Market pricing import on this page and confirm your site has Use market pricing layout enabled.
2. List markets in Additional Markets using commas or semicolons (for example, Australia, New Zealand). The first market becomes the primary market.
3. Add Sell and RRP on separate rows with the required Colour Code, Colour Description, or Size for your pricing layout.
4. Re-import and review the Import Summary for validation messages.

Most rejections on coded fields mean the value is not an exact match for an active option in Site Settings, or the related Site Settings record was changed after the spreadsheet was prepared.

Steps to resolve:

1. Open the linked Site Settings page for that field (from the table above) and compare spelling, casing, and availability of the option.
2. Update the cell to match the current configuration and re-import.
3. Use the Import Summary to confirm the error category for that row.

Each price type is typically entered on its own row, and Price By Size requires a Size for each price row.

Steps to resolve:

1. Review the Price Type and related columns in the table on this page.
2. Add one row per price type (and per size if using Price By Size).
3. Confirm Currency values match Site Settings and re-run the import if the summary reports structure errors.

The platform blocks size scale changes when the style has Orders or when barcode, keycode, or tuncode associations exist, to protect order and identification data.

Steps to resolve:

1. Read the restriction details in Update Existing Styles through Import.
2. Check the Import Summary for the logged skip reason.
3. Engage your administrator if a scale change is required despite these associations.

Weight data requires Colour Code or Colour Description to be present in the same row. If both colour fields are blank, the weight update step is skipped entirely with no error logged in the Import Summary — the row will show only a style details update message.

Steps to resolve:

1. Add the Colour Code or Colour Description (or both) for the relevant colourway to each row that includes weight data.
2. Re-import the file and check the Import Summary for an eCommerce weight size updated successfully entry per row.

The import requires Size Scale Code and resolves the scale using that code. Disabled size scales are not applied. If several scales share the same Description in Site Settings, only the Code identifies the correct row — ensure the code matches an enabled scale.

Steps to resolve:

1. Open Site Settings › Style › Size Scales and confirm the scale’s Code (not only the description).
2. Ensure the scale is enabled in the list (use the toolbar filter if needed).
3. Copy the Code into the Size Scale Code column exactly and re-import.

Colour-level availability dates require Colour Code or Colour Description in the same row, the same as Weight, Weight Unit, and eCommerce Size Enabled.

Steps to resolve:

1. Add Colour Code or Colour Description for the colourway on each row that includes eCommerce Available From and/or eCommerce Available To.
2. Use dd/MM/yyyy date format (for example, 01/06/2024).
3. Re-import and check the Import Summary for colour available date update messages.

Date columns must use dd/MM/yyyy. Extra spaces around the date are trimmed automatically, but invalid formats (such as 2024-06-01 or 06/01/2024) are rejected.

Steps to resolve:

1. Reformat the cell to dd/MM/yyyy.
2. Leave the cell blank if you do not want to change that date on an existing style.
3. Re-import and review the Import Summary for validation errors on that row.