Import many SKUs without breaking search quality. Prepare clean files, map categories, and review before you publish.
Bulk upload is useful when your catalog is already running in Excel or an ERP. It is risky when the spreadsheet is a decade of mixed spellings, empty prices, and categories that only your warehouse staff understand. STUS search and directory filters read what you import. If the file is messy, the marketplace will look messy, and buyers will not stay to decode it.
Prepare the file before you open the importer
Export your working catalog and delete columns nobody needs. Keep SKU, product name, category, subcategory, description, MOQ, unit, lead time, origin, and image URLs if you host photos. Standardise units: kg or carton, not both in the same column with no rule. Split “UAE/KSA” into a single primary origin. Buyers filter by country; mixed cells break those filters.
Map every row to a STUS category that already exists on the platform. Do not invent parallel trees such as “Foods – Snacks – Chips – Promo.” Directory search will not know where to place them. If a SKU truly spans two categories, pick the one a buyer would search first and mention the second use in the description. Duplicate rows with slightly different names create duplicate listings and confuse RFQ comparison.
Import in a test batch, then scale
Upload twenty rows first, not two thousand. Check how names wrap on the product card, whether images load, and whether category filters return the items. Fix the template, then import the rest. A full dump on day one is how catalogs publish with 400 broken image links. Review error rows the importer returns. They are cheaper to correct in Excel than one by one in the live store.
Watch character encoding. Arabic and English names in the same sheet need UTF-8. If Arabic becomes symbols, buyers in KSA and UAE will skip the listing even when the product is right. Keep a separate column for English search titles if your internal names are only in another language. The public title should be the one a procurement officer types.
Quality control after the bulk job finishes
Sort the live catalog by recently added and spot-check high-value SKUs. Confirm MOQ is a number, not “MOQ 10 tons please call.” Confirm photos match the SKU code. Confirm you did not publish internal cost or customer names in the description field. Bulk tools copy whatever is in the cell, including notes you meant only for staff.
Schedule a second pass a week later. Search the directory using the same filters a buyer would use: category, country, and a keyword from your hero product. If bulk items do not appear, the category map is still wrong. Adjust those rows and re-import only the corrections. Bulk add is not a one-click shortcut around catalog discipline. It is a faster way to apply the same discipline to many SKUs.
When the file is clean, bulk upload is one of the highest-leverage hours you will spend on STUS. When the file is dirty, it is the fastest way to look unprofessional at scale. Treat the spreadsheet as a public document, because that is what it becomes after import.
Appoint one person to own the master file. Parallel copies on three laptops guarantee conflicting SKUs. After each successful import, export or download what the platform now holds and archive that snapshot with a date. If a future import goes wrong, you can compare rather than reconstruct from memory.
Images deserve their own mini-project. If the importer wants URLs, host files that will not expire next week. If it wants local files, name them with the SKU so mismatches are obvious. A bulk job that attaches the same hero image to eighty products is worse than no image. Buyers notice identical photos immediately.
Do not mix test rows with live rows. Use a prefix such as TEST- in SKUs for sandbox imports, then delete those products before customers search. Leftover test items have a habit of appearing in RFQs at the worst moment. Cleanup is part of bulk add, not an optional extra.
After a large import, brief the sales team. They should know which SKUs went live, which remain draft, and which prices are public. Nothing undermines a bulk project faster than a salesperson quoting an old Excel file while the marketplace shows something else. Alignment is the last step of the import, even though it happens in a meeting rather than in software.
Keep a change log for bulk jobs: date, row count, who approved the file, and what broke. Six months later nobody remembers why 40 SKUs lost images. The log also helps when you hire a new catalog owner. Bulk add without history becomes folklore, and folklore is how companies re-import the same mistakes. Write it down. The file is not finished until the log exists.
When volume is high, import overnight and review in the morning with fresh eyes. Fatigue is how 200 rows go live with the wrong currency or the wrong unit. Bulk work rewards patience more than speed, even though the tool feels fast. The marketplace will keep those rows until you fix them, so the cheap moment to be careful is before you click confirm.