Skip to content

Style Import Fields and Rules

The Fields and Rules section defines the structure and validation requirements for importing Style data. The import function enables users to add or update styles in bulk using structured templates, making it easier to set up and modify styles on a large scale.

The Style Import tool helps product teams, merchandisers, and data administrators add or update styles quickly. Each field must follow specific rules, especially those that rely on values configured in Site Settings. By managing these fields through the import template, teams can standardise how styles are identified and categorised, improve data consistency across the catalogue, and ensure that key metadata aligns with configured options for reporting and eCommerce.

Quick Check - Before You Start
  • Download the latest import template from the Style Import page
  • Verify all dropdown field values match your Site Settings configuration (Type, Brand, Season, etc.)
  • For multi-price styles, prepare separate rows per price type in your template
  • Confirm Size Scale values match Site Settings > Style > Size Scales

Style Import Template

Fields and Descriptions

Field Description
Preview Image URL The web address (URL) of an image that appears as a preview when a link to a webpage is shared.
Status Current status of the style (e.g., Draft, Approved, Cancelled). Must match values in Site Settings.
Style Number A unique identifier for the style.
Description Style description.
Type Style type. Ensure that it matches your configuration in Site Settings › Style › Type.
Sub Type Sub-category of the style. Must match Site Settings.
Size Scale Size scale used for the style. Ensure that it matches your configuration in Site Settings › Style › Size Scales. Note: When updating existing styles, the Size Scale cannot be changed if the style has associated Orders or if barcode, keycode, or tuncode are associated with the style.
Composition Fabric or material composition.
Department Linked department. Ensure that it matches your configuration in Site Settings › Order › Department.
Category Product category. Ensure that it matches your configuration in Site Settings › Style › Category.
Sub Category Further product classification. Must match in Site Settings › Style › Category › Sub Category.
Collection Seasonal or thematic grouping. Ensure that it matches your configuration in Site Settings › Style › Collection.
Cost Centre Linked financial cost centre. Ensure that it matches your configuration in Site Settings › Company › Cost Centre.
Designer Assigned designer. Must match staff records in Site Settings › Company › Staff.
Brand Brand name. Ensure that it matches your configuration in Site Settings › Style › Brand.
Gender Intended target gender. Ensure that it matches your configuration in Site Settings › Style › Gender.
Story Product story or narrative. Ensure that it matches your configuration in Site Settings › Style › Story.
Season Assigned season. Ensure that it matches your configuration in Site Settings › Style › Season.
Licence Licensing classification. Ensure that it matches your configuration in Site Settings › Style › Licence.
Tariff Tariff classification for export/import. Ensure that it matches your configuration in Site Settings › Style › Tariff.
Additional Markets Specifies which markets each style applies to. Enter multiple market values separated by commas or semicolons.
Agent Sales or sourcing agent. Ensure that it matches your configuration in Site Settings › Company › Suppliers.
Factory Linked factory. Must match existing factory records in Site Settings › Company › Suppliers.
Design Number Internal design reference number.
Colour Code Code used for colour identification. Ensure that it matches your configuration in Site Settings › Style › Colour.
Colour Description Colour description. Must match defined options.
Colour Tags Colourway tags applied to each colour. Enter multiple values separated by commas or semicolons. Must match Site Settings › Company › Tags.
Drop Product drop or release phase for the colourway. Must match Site Settings › Style › Drop. Ensure Drop is enabled in Site Settings › Style › General Settings › User Interface Layout.
Size Size value. Must match sizes from the selected size scale.
Size Enabled Use Yes to enable or No to disable a size.
eCommerce Size Enabled Use Yes or No to control size visibility in B2B.
Price Type Pricing structure. Must be One Price or Price By Size. If using Price By Size, the Size column must also be filled in for each price entry.
Price Type (Buy, Sell, RRP, Alt RRP, Alt RRP 2, eCommerce) Each price type should be listed as a separate row.
Currency Currency code. Ensure that it matches your configuration in Site Settings › Company › Currency. Alt RRP prices should have different currencies.
Price Price value.
eCommerce Status Set to Draft or Published.
eCommerce Short Description Title for eCommerce display.
eCommerce Collection Grouping used in B2B store.
eCommerce Long Description Full product description for eCommerce.
Tags Product tags. Ensure that it matches your configuration in Site Settings › Company › Tags.
Weight Unit Accepted units: Gram or Kg.
Weight Numeric weight of the product.
Custom Fields Custom-configured fields in the platform. Ensure that it matches your configuration in Site Settings › Style › Custom Fields. Leave blank if unused.

Troubleshooting

A field value is rejected even though it looks correct—what should I verify?

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.
How do I structure prices when a style has several price types (RRP, Alt RRP, eCommerce, etc.)?

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.
Why can I not change Size Scale on an existing style via import?

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.

Tip

  • Always validate your data against Site Settings before importing—all field values must match configured values.
  • For multi-select fields such as tags or custom fields, use commas (,) or semicolons (;) to separate values in the template.
  • For multi-price styles (e.g., with Alt RRP or eCommerce price), enter each price type as a separate row in your import file.
  • Download the import summary after upload to check for errors or confirm successful processing.