To list your products in bulk, you must add your products pictures and description to the NIS (New Item Set-up sheet) which you can access on your Seller Lab account. Once done with filling the NIS, you'll have to upload it to Seller Lab, your products' information will be reviewed by the content team, and then pushed live on noon.
There are two ways to create new products on noon:
- Single SKU creation: allows you to list one product at a time.
- Multiple SKU creation: allows you to upload and list multiple products in one go.
Learn more about Single SKU creation, here.
Downloading the templates
In Catalog, click Partner Catalog, then Create Multiple Products.
A pop-up window will appear where you can search for the full type, product type, and product sub-type of the item you want to create. You can either browse the categories manually and select the appropriate full type, or simply paste the URL from noon.com to automatically generate the category tree the product is in.
Once you select the category, use the search bar option to find your brand, as shown in the screenshot. Next, download the bulk content upload template in either English or English+Arabic language, depending on your needs. If you need more information about the language requirements, please refer to this article.
Note: You can select "with instruction" option to download a sheet that shows clear
instruction on how to fill in the details.
Understanding and filling out the NIS sheet
When you first open the NIS sheet, it may seem a little overwhelming , so let us break it down for you.
The downloaded Excel file includes a tab with detailed instructions on how to fill out the sheet, as shown in the screenshot below.
b. English Template:
The English template only needs the details for the SKUs to be filled in English, as shown in the screenshot below.
c. English+Arabic Template:
The English+Arabic template requires you to fill in the content in both English and Arabic languages. You will find several fields marked with the letters "EN" and "AR." Filling out content in both languages increases product visibility.
Let's go through what each color and field in the NIS sheet represents to help you better understand how to fill it out.
Red fields: The cells with the red border are mandatory fields, which are essential to be filled to make sure the item goes live.
Green fields: The cells with the green border are important fields which helps the customer to identify and discover your item.
Plain fields: The cells without any border color optional information which you can provide to further improve your product content.
Grey colored fields: The cells which are totally grey colored are attributes that are not required to be filled for that specific category you downloaded the content export for.
The fields will vary depending on the fulltype/subtype combination you choose to create your product. However, the following fields are common for all fulltypes:
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 Lab.
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. At least one image URL is a Mandatory requirement for the upload to be successful.
For more information on image requirements, please click here
Once all the above information and images are successfully updated in the sheet save the file as CSV,TSV or XLS> Go back to Seller Lab> Click on Next option in the NIS import option and upload the file. Once uploaded click on confirm as shown in the screenshot below.
Once the file is upload it will be visible under Catalog>Imports> NIS and bulk imports section as shown in the screenshot.
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. It also shows the type of text you need to fill in the given cell for the attribute in the top row.
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.
And then you will select the Noon size from the dropdown in the next column. This will help to make your product more discoverable by the customer in case they set up a filter on the search preference. The noon size can be selected as a best approximation to the international sizing standards which best suits the size variation mentioned in the sheet.
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)
Partner SKU Unique, Size Variation --> ONLY on the Child Row(s)
Parent Group Key, Parent Child Variation --> On the Parent and Child rows.
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.
Got any more questions?
Contact us on firstname.lastname@example.org.