Skip to content

Component Import: Fields and Rules

This guide details the required fields and formatting rules for importing Component data. By using a structured spreadsheet, the import function allows you to create and update components in bulk, streamlining your sourcing and material management workflows.

You can import multiple components at once using a downloadable template, making this feature ideal for product development, sourcing, or materials teams that handle high-volume data. To ensure a successful import, all field values must comply with the validation rules configured in Site Settings.

Quick Check - Before You Start
  • Site Settings includes every Type, Season, Brand, Supplier, Currency, and related list value you plan to use in the file.
  • Price Type is only Buy or Costing as required by the template.
  • Data is cleaned (no stray spaces, consistent number and date formats) before upload.

Fields and Descriptions

Field Name Description
Status The current status of the component (e.g.,Active, Inactive). This must match a value configured in Site Settings.
Component Number A unique identifier for the component.
Description A brief description of the component.
Type The component's type (e.g.,Trim, Fabric). This must match a value configured in Site Settings.
Unit The standard unit of measure (e.g.,Metre, Piece).
Unit Measurement The numerical value for the base unit (e.g.,1.0 for each, 100.0 for metres).
MOQ The Minimum Order Quantity required by the supplier.
MOQ Measurement The numerical value for the MOQ (e.g.,100).
Composition The material composition (e.g.,80% Cotton / 20% Polyester).
Supplier The component's supplier. This must match a supplier already in the system.
Supplier Reference The supplier’s unique ID or reference code for the component.
Lead Time The expected lead time for procurement, in days.
Season The season assigned to the component. This must match a value configured inSite Settings.
Brand The brand the component is associated with. This must match a value configured inSite Settings.
Collection The collection the component belongs to. This must match a value configured inSite Settings.
Story The product story or theme. This must match a value configured inSite Settings.
Colour Code The internal code for the component's colour. This must match a configured colour code.
Colour Description The descriptive name for the component's colour. This must match a configured colour.
Price Type Must be either Buy or Costing.
Currency The currency for the price. This must match a currency configured inSite Settings.
Price The price of the component, based on the selected Price Type.
Costing Price The costing-specific price, if applicable.
Costing Price Currency The currency used for the costing price. This must match a configured currency.
Custom Fields Any optional custom fields that have been configured for your site.
Validation Requirements
  • All fields that use dropdown menus in the interface (e.g., Type, Season, Supplier, Currency) must contain values that exactly match those configured in Site Settings.
  • Any invalid or mismatched entries will cause the import to fail for those rows.

Helpful information

1.Clean Your Data Before Importing: Before you begin, thoroughly clean your spreadsheet data. Remove any leading or trailing spaces, ensure consistent formatting for dates and numbers, and check for any special characters that could cause errors. Using spreadsheet functions like TRIM or CLEAN can help automate this process and prevent common import failures.

2.Import in Small Batches: When dealing with a large number of components, import them in smaller, manageable batches rather than all at once. This approach makes it significantly easier to troubleshoot any errors that may arise. If an issue occurs, you only need to investigate a small subset of data, saving you time and effort.

3.Back-Up Data Before Updating Existing Components: Before you use the import tool to update existing components, it is highly recommended to first export the current data as a backup. This precautionary step ensures that if any mistakes are made during the import process, you can quickly restore the original data and prevent any loss of information.

Troubleshooting

Why do rows fail with validation errors on Type, Supplier, or Currency?

Those columns are validated against Site Settings and master data. Any mismatch fails the row.

Steps to resolve:

  1. Compare each value to the configured lists in Site Settings.
  2. Ensure the supplier already exists in the system before referencing it in the file.
  3. Use the Import Summary to pinpoint the first failing column per row.
The import rejected my Price Type or price columns—what should I verify?

Price Type must be exactly Buy or Costing, and prices must align with the rules for the selected type.

Steps to resolve:

  1. Correct Price Type spelling and casing.
  2. Confirm Currency and Costing Price Currency match configured currencies where used.
  3. Re-import and review the Import Summary for any remaining numeric or format messages.
I am updating many components—how do I avoid bad bulk changes?

Large update files amplify small mistakes across many records.

Steps to resolve:

  1. Export and keep a backup of current component data before running an update import.
  2. Run updates in smaller batches or single-field-focused files.
  3. After each run, read the Import Summary before starting the next batch.