Last updated 15/11/2017
Fashion products require a few extra fields to store their sizes. We've created a separate template for fashion products to give you an idea of what is required.
If you sell both fashion and simple products, then you will be able to import both in the same spreadsheet - you will just omit the irrelevant fields for the simple products.
Before importing fashion products, it may be worth reviewing Creating a Product, Product Codes, and Importing Simple Products before starting. These articles will give you the background to Cin7's product structure.
Here are a few pointers for creating your import spreadsheet. The easiest way to understand the below principles is to make some test imports with a small amount of data.
Each fashion product requires a different Style Code. The Style Code is a unique code for each Product. This means that you can have multiple products with the same name, but with different Style Codes - useful for recurring staple products such as plain t-shirts. If this applies to you then remember to 'Group by Style Code' when importing.
Style codes are also used for simple products, but we have left them out of the Simple Product Import for the sake of simplicity. We create the stlye code automatically based on a code when the style code column is not included in the spreadsheet.
Stock Control Method
Remember that fashion products are stored using the 'batch' stock control method in the system. This means that in the stock control column in the spreadsheet, you must enter 'Batch' against each fashion product.
All fashion products require a Size Range. This is explained in more detail in Creating Fashion Products. It is not necessary for the size range to have been created before import - the system will create them for you upon import. This does mean however that you should create a row for every product in the possible range of sizes. For instance if you intend to sell S - XL but don't currently have any XL in stock, your product spreadsheet should still include the XL size.
The size column will contain the sizes of each row, and can be as simple as "S", "M" or "L".
Each size in your system will have a unique code, and there will only ever be one size code per row. We find it best to build size codes in a logical way, e.g. "RGB1-Red-M". Ideally it will incorporate the 'size' - see above.
We really appreciate your feedback.