How bulk create jobs run and report results

Learn how a bulk create job is queued, processed row by row, and reported back to you by email.

1. The bulk create job flow (a CSV plus an optional assets ZIP, submitted with a mandatory job name) is asynchronous: files are uploaded, the job is queued, and a background worker processes it.

2. The user can watch the job in the jobs list; statuses move from initialized through ongoing (with automatic retries shown as retrying) to completed or failed.

3. Unlike the transactional bulk edit, rows are processed independently: invalid rows are collected as failures while valid rows still create their SKUs, and the job still ends completed with success and failure counts.

4. When it finishes, the requesting user - and only that user, unlike bulk-edit emails which go to all catalogue managers - receives an email summarising counts with an attached spreadsheet listing every row's SKU name, status and error message.