Seller tool
Validate your NIS file before Noon rejects it
Upload your NIS workbook and get a row-by-row report of structural problems, missing required fields, duplicate SKUs, and risky image URLs — before the import does.
Why NIS files fail
Most NIS rejections are boring: a renamed header, a blank required cell, the same SKU on two rows, an image URL that returns a 404. Each one costs you an import cycle and a day of waiting.
The NIS Validator maps your workbook against the official template structure, flags missing or mislabeled columns, duplicate SKUs, empty required fields, and image URLs that will not survive upload.
What you get
A structured report grouped by severity: errors that will block the import, and warnings worth reviewing. Every finding names the row, the SKU, the field, and what to change.
The validator also exports a starter file: a clean, correctly structured NIS template pre-mapped from your data, so your next upload starts from a known-good base.
Part of a pre-upload routine
Sellers who validate before every import catch problems in minutes instead of discovering them in a rejection email. Pair it with the Bulk Issue Fixer when the file also needs content fixes.
Frequently asked questions
Template hygiene
Most structural failures come from spreadsheet habits, not product problems: sorting one column without the others, dragging a formula across SKUs, or “cleaning up” headers into nicer names. The importer does not care about nice names — it matches the template exactly.
Protect yourself with a simple rule: never edit the template_data sheet directly. Do your edits in a working copy, then paste values — not formulas, not formatting — into a fresh official template before upload.
When validation passes but the import still fails
A clean validation means the file is structurally sound — it cannot promise that Noon’s business rules will accept every row. Category policies, brand authorizations, and manual content review all live outside any spreadsheet check.
When that happens, read the import report row by row: fix exactly what it names, change nothing else, and re-upload only the failed rows. Resist the urge to “improve” unrelated columns in the same pass.
Reading the report: errors vs. warnings
Errors will block or corrupt the import: missing SKUs, duplicates, broken structure, dead image URLs. Fix every error — there is no “probably fine” error. Warnings deserve human eyes: an unusual category path, a very short title, a brand you have not sold before. Warnings are where experienced sellers earn their keep; the tool points, you decide.
Validator + fixer: the intended pair
Use the validator first for structure, then the Bulk Issue Fixer for content. Structure problems poison content work — there is no point perfecting Arabic titles in a file whose headers the importer will not recognize. Validate, then fix, then validate once more before upload. Two minutes of re-validation has saved many sellers from a wasted import cycle.
Make validation a habit, not an event
The sellers with the cleanest catalogs validate the most often — not because their files are worse, but because they catch drift early. Add the validator to your definition of “done”: no file is upload-ready until it has a clean report attached. Thirty seconds of discipline per file compounds into a catalog that rarely surprises you.
Which NIS template version does it check?
It checks against the standard NIS Create/Update template structure (template_data sheet). Always compare with the latest template from Seller Lab.
Does it fix the errors for me?
It reports every issue precisely; structural fixes you apply in your spreadsheet. Content fixes (category, brand, Arabic titles) belong in the Bulk Issue Fixer.
Is my file uploaded anywhere?
No — validation runs entirely in your browser.
Runs in your browser. No sign-in, no API key. Your files never leave your device.