Previous jobs and progress
Every generate or upload creates a job (also called a set). CodeBulk stores the codes, splits them into batches and imports them into Shopify in the background, so you can leave the page while a job runs.
The Previous jobs table
Section titled “The Previous jobs table”| Column | Meaning |
|---|---|
| Discount ID / Title | The discount the codes are for, and the job’s title |
| Requested | How many codes the job asked for |
| Imported | How many are on the discount in Shopify |
| Failed | How many Shopify didn’t accept |
| Status | Where the job is (below) |
| Actions | Download, Klaviyo, email QR embed, delete |
The table shows 5 jobs per page, and refreshes every 5 seconds while a job is running.
Statuses
Section titled “Statuses”| Status | Meaning |
|---|---|
| Importing N% | The job is running |
| Complete | Every batch has been sent to Shopify |
| Failed | The job stopped with an error |
| Aborted | You stopped the job |
| Deleting… | The set’s codes are being removed from Shopify |
| Deleted | The set’s codes have been removed |
Why Imported can be lower than Requested
Section titled “Why Imported can be lower than Requested”Shopify rejects a code that already exists anywhere in your store, and on rare occasions a batch fails because of a network problem. CodeBulk retries temporary errors up to 3 times before it counts a batch as failed. See Why some codes failed to import.