Overview
The NIS -New Item Set-up- sheet needs to be filled out with your products' description and pictures. These NIS sheets are then uploaded on Seller Station, reviewed by the content team, and then pushed live at noon.
There are 2 ways to create new products in noon.
- Single SKU creation - create one product at a time.
- Multiple SKU creation - create multiple products at once.
For more information about Single SKU creation. please click here
Downloading the templates
You start by opening the Catalog then go to Partner Catalog tab,, and then click on Create Multiple Products.
This will open up a window where you can search for the full type that you would like to create a product for as following:
You can either manually search and drill down the categories and select a full type, or paste a URL from noon.com to automatically generate the category tree the product is in.
After the category tree is generated, click on Download Template to download.
Understanding and filling out the NIS sheet
When you first open the NIS sheet, it may seem a little daunting so let us break it down for you -
Green fields: mandatory fields, which are essential to the identity of your product and we recommend you to fill these out for better visibility.
Orange fields: optional information which you can provide to further improve your product content
These fields will be populated and will vary depending on the fulltype/subtype combination you would like to create your product into, however the following fields are common for all fulltypes to be filled in -
Partner SKU Unique: It is the unique value/identifier that you will use to identify your product. This value will be used in all sales/invoicing/reporting etc... on seller station.
Brand: The brand of your product. If the brand is not available in the system, you can submit a new brand request. For more information on brand creation please click here
Product Title: Title of your product which the customer will search this product
GTIN: A Global Trade Identification Number (GTIN) which is internationally recognized product identifier and will be used to inbound your product. You will have to update this value as a partner barcode as well. For more information on partner barcode imports, please click here
After these fields are filled in and completed, we recommend the following additional fields to fill out to better improve and enrich your content.
Attribute Key and Attribute Value: You can create any additional fields that you would like to add against your product which may not have been added in the NIS sheet by noon - for example, for a laptop, Attribute Key = RAM and Attribute Value = 1TB
Feature/Bullets: Information that you'd like to highlight as bullet points on your product display page on the noon website should be added as clear & crisp in the Feature/Bullets columns.
Adding your pictures to the NIS:
If your pictures are available on any website, and they respect the image requirements; you can copy the link and paste it in the picture fields of the NIS. Make sure the link address ends with .JPEG to ensure the import successfully goes through.
For more information on image requirements, please click here
Once all the above information and images are uploaded successfully, you will be able to view your products on the catalog page immediately.
Creating product variants in bulk
To create variants, you will need to first define parent <> child relationship between your products in the NIS sheet.
A parent SKU is created first and then you can create multiple children SKUs. All children are grouped together by the parent which is defined as the parent group key.
To elaborate on this, let’s see how we can implement this on the NIS sheet.
The above section of the NIS sheet will help you create variants for your products.
Here you need to first define a Parent Group Key and a Parent SKU. In the example below we have defined this:
Once you have a Parent Group Key and Parent SKU defined, you can use the same Parent Group Key to group multiple children SKU and define them as Child.
And then you need define the variation that each child would signify, this is defined below:
Please note the Parent SKU will be an independent variable and does not need a size variation defined.
All the content will be pulled from the Parent SKU for the children except the Size Variation.
Your final import file should look something like this:
Family, Product Type, Product Subtype, Sizing Standards, Brand + all the other columns --> ONLY on the Parent row (1st row in the example)
Parter SKU Unique, Size Variation --> ONLY on the Child Row(s)
Parent Group Key, Parent Child Variation --> On the Parent and Child rows.
Variant Axis
Currently we only allow variants to be created on ‘Size’ axis.
For variants to be created on Color or other Axis, find more information about Groupings, click here
 |
To define the variants you will need to fill in the Size Variation and Sizing Standard section within the NIS sheet. In this example we have defined the size for the product and its sizing standard |
Handling the error report
Once an import is successfully ingested, SKUs that have valid content and no errors will be created in the catalog page. However, if there are errors in the file or we weren't able to create a SKU for any reason, an error file will be generated.
You can check the status of the report on the imports page (Catalog > Imports > Bulk ZSKU listing)
You will be able to see the report for each individual upload. The status columns gives you and overview of your report.
- Import processes - file was processed by the system.
- Report generated - error report has been generated and is available for you to download.
- Mapping Done/Error/Pending - how many of your products have a unique Seller SKU assigned, how many are still pending and how many have an error that prevents them form getting a Seller SKU.
Under the comments column you will find a summary of all the errors found in your report and the number of times they occur.
These errors should be self explanatory and will be available to export.
When you download the file, move to the right most columns in the file to identify errors at specific line level to know which SKU failed to get created.
Upon fixing the errors, you can reupload the same file for the SKUs to be created or, if the error still persists, a new error file will be generated.
That's it!
Got any more questions?
Contact us on seller@noon.com.