Fix bulk upload rows that were skipped or dropped
Read the reasons behind Duplicate, Failed and Dropped rows, download the error report, correct the rows and upload them again.
When a bulk upload finishes, the Results panel shows how many parts were added and how many were not. Rows that did not go in are counted as Duplicates, Failed or Dropped, and every one of them is listed with a reason you can read.
This page covers reading those reasons, downloading the report of rows that did not go in, correcting them, and running them again. Nothing you already gained is lost — the parts counted as Added are in your Inventory and stay there.
Rows are not repaired inside GridX Connect. You correct them in your spreadsheet and run a new upload containing only those rows. And there is one group you should not try to fix: rows skipped as duplicates are parts you already stock, and re-running them will skip them again.
> [!WARNING] > On a Used file, leave the Brand column empty. Used parts can only be listed as OEM. If a row in a Used file carries a brand name, GridX Connect reads it as an aftermarket part, and the row fails every time you upload it. This is the single most common reason a row fails. Clear the Brand column — or set it to the vehicle make — and the row goes through.
> [!NOTE] > You do not have to stay on the page to keep your results. A finished job reopens on the Results panel when you return to Bulk Upload, and every past job is kept in the Recent Jobs list with its error report.
Before you start
- A finished bulk upload. A running job returns to the Processing step; a finished one opens on Results.
- The spreadsheet you uploaded, or the error report from that job.
- The correct OE Number or Manufacturer Part Number for each row you want to correct, plus the Vehicle Make.
- Room left under your plan's SKU limit, since re-uploaded rows are added as new parts.
- The same condition in mind — New or Used — because a corrected file is a fresh upload with its own whole-file condition.
Steps
1. Open Bulk Upload from the left sidebar. A finished job opens on the Results panel showing "Upload complete". 2. Read the Added count first. Those parts are already in your Inventory and need nothing further here. 3. Click View details on the issues chip to see each Failed and Dropped part with its reason. 4. Click Export CSV to download the rows that did not go in. The file is named {filename}_errors.csv. 5. Open that file and read the reason on each row. The reason tells you which of the fixes below applies — do not apply the same fix to every row. 6. Correct the rows: - Wrong number — replace casting marks and stamped numbers with the OE Number or Manufacturer Part Number. - Missing vehicle — fill in the Vehicle Make. - Used row that failed — clear the Brand column. Do not add a brand to a Used file. 7. Delete any rows that were skipped as duplicates. Those parts are already in your Inventory and will be skipped again. 8. Save the corrected rows as CSV or Excel (.xlsx), 10MB or smaller. 9. Click New Upload to return to Step 1. Pick the condition again, add the corrected file, and click Start Processing. 10. On the new Results panel, check the Added count, and repeat for anything still listed under View details.
What each result means
| Result | What it means | What to do | |---|---|---| | Added | The part was placed in your Inventory. | Nothing. Click View Inventory to see it. | | Duplicates | The part number matched a part you already stock, so it was skipped rather than added twice. | Remove the row. To change an existing part, use Bulk Update. | | Failed | The row could not be processed. On a Used file this is almost always a Brand that should not be there. | Read its reason. If it mentions Used and OEM, clear the Brand column and upload the row again. | | Dropped | The part could not be verified or found. | Correct the part number and fill in the Vehicle Make, then upload the row again. |
Failed rows: Used parts must be OEM
Nearly every failed row comes from the same thing: a Brand on a Used row.
GridX Connect works out the part type for you from what is in the row. A brand name that is not the vehicle make marks the part as aftermarket — and a used part can only be listed as OEM. The two cannot both be true, so the row fails. Re-uploading it unchanged fails again, every time.
The message on the row says so directly:
> Used parts can only be listed as OEM. The Brand on this row was read as an aftermarket brand. Clear the Brand column (or set it to the vehicle make) to list this part as used OEM.
The fix: clear the Brand column on that row, or set it to the vehicle make, and upload it again. Leave the Vehicle Make filled in — that column is fine and helps the match.
If you genuinely need to list a branded aftermarket part, upload it in a New file instead. Condition is a whole-file setting, so branded aftermarket parts and used OEM parts belong in separate uploads.
If a failed row's message is not about Used and OEM, upload the row again; if the same row keeps failing, contact support with the part number.
Dropped rows: the part could not be verified or found
Dropped rows carry a reason such as "Unable to find product information for this part number" or "Could not identify the product for this part number". Both point at the same thing: the details supplied were not enough to identify the part with confidence.
The most common cause is the wrong number. Use the OE Number or the Manufacturer Part Number. Casting marks and stamped numbers look like part numbers but return the wrong part, so a row built on one is likely to be dropped.
The second cause is the vehicle. Fill in the Vehicle Make on every row — it is checked when your file is processed and it is what makes a match accurate. If the make was not recognised, the reason usually names it and often suggests the correct spelling, for example when "PEGEUOT" should be "Peugeot". Correct the spelling and re-upload.
A brand that is not a real vehicle make can also land in the Vehicle Make column by mistake. If the reason says the make looks like a parts brand, move that value to the Brand column — and remember that on a Used file the Brand column should be empty.
Duplicates: parts you already stock
A duplicate is a row that matches a part you already hold — the same part number, with the same brand and the same condition. GridX Connect skips it. The part is not added a second time, and Bulk Upload does not change the part that is already there.
Duplicates are counted but not listed row by row, so to see which ones matched, compare your file against your Inventory.
If every row in your file matched, nothing new is added. That is not an error to fix in the file — it means the list you uploaded is stock you already hold. To add parts, upload a file with part numbers you do not already stock.
If what you actually wanted was to change the price or quantity of those existing parts, Bulk Upload is not the tool. Bulk Update is the separate feature that changes the price and stock of parts you already have.
Jobs that stopped early
A whole job can end without every row going in — but that is not shown as a separate status. A finished job opens on the Results panel headed Upload complete whether every row went in or not; the shortfall shows only in the Duplicate, Failed and Dropped counts and under View details. Two endings look different:
- A job that could not finish at all shows Job processing failed — open Results to see the issues and any partial output.
- If you click Cancel Job while it runs, the page returns to Step 1 with Job cancelled successfully.
Two things stop a job that is otherwise healthy. Reaching your plan's SKU limit stops it and opens the upgrade prompt, because Bulk Upload uses the same SKU limit as adding parts one at a time. A billing limit does the same for a different reason — a monthly spending limit reached, a plan quota reached, or a suspended account — and opens the matching prompt. Clear the billing issue from the prompt or in Plan & billing, then upload the remaining rows again.
Finding a job and its report later
The Recent Jobs list on the Bulk Upload page holds your past jobs, each with the filename, date, parts added, errors and percent. Hover a job to download either the file you uploaded or its error report, so you can come back to a job days later and still get the exact rows that did not go in. The list refreshes while a job is running.
On the Results panel, Export CSV gives you the rows that did not go in. That report is the right starting point for your corrected file.
> [!TIP] > Correct the rows in a copy of the downloaded error report rather than in your original list. You keep the reasons next to each row while you work, and the rows that already went in cannot be uploaded again by accident.
After the corrected rows go in
Parts added by any bulk upload land in your Inventory. They are not on eBay — publishing is a separate step you do from Inventory, where you open the part, add at least one photo, and publish it.
If your corrected parts came in without pictures, the Results panel points you to it: "Items missing images? Use PartSnap in Inventory." Open the part in Inventory and add photos there, or include image links in the Image URLs column of the Advanced template next time.
If something goes wrong
| On-screen text | Why it appears | Fix | |---|---|---| | "Used parts can only be listed as OEM. The Brand on this row was read as an aftermarket brand." | A row in a Used file carried a brand name, which marks the part as aftermarket. Used parts can only be OEM. | Clear the Brand column on that row, or set it to the vehicle make, and upload it again. To list a branded aftermarket part, use a New file instead. | | "Unable to find product information for this part number" | A row was dropped because no details were found for that part number. | Use the correct OE or Manufacturer Part Number and fill in the Vehicle Make, then upload that row again. | | "Could not identify the product for this part number" | A row was dropped because the part's details could not be confirmed. | Check the part number and the Vehicle Make, then upload that row again. | | "The vehicle make in this row is not recognized" | The Vehicle Make column holds something GridX Connect does not recognise as a car maker. | Use the maker's normal name. If the reason suggests a spelling, use that. If the value is really a parts brand, move it to the Brand column. | | "An unexpected error occurred while processing this part number" | The row could not be processed on this run. | Upload the row again; if it keeps failing, contact support. | | "Job processing failed" | The job could not finish. | Open Results to see the issues and any partial output, then upload the affected rows again or contact support. | | "Connection error. Please refresh the page to continue." | The live connection to the job dropped. | Refresh the page. Your job keeps running and reopens at the right step. | | "Too many requests. Please wait a moment and try again." | Requests came in faster than allowed. | Wait a short moment and try again. | | "Access denied. Please check your account permissions or contact support." | Your account does not have access for this action. | Confirm your plan includes Bulk Upload and your account is in good standing, or contact support. | | "Please select a condition above before processing" | No condition was chosen for the corrected file. | Pick New or Used at the top of Step 1, then click Start Processing. |
Start Processing is greyed out on the corrected file. The button stays off until you have both added a file and picked a condition. A re-upload is a new job, so the condition has to be chosen again even if it is the same as last time.
Your corrected rows failed again. If the file is Used, check the Brand column is empty on every row — a brand on a used row fails every time, no matter how many times you upload it.
Your corrected rows were dropped again. Check the part number is the OE or Manufacturer Part Number rather than a casting mark, and that the Vehicle Make is filled in and spelled the way the maker spells it. If both are right and the row still drops, contact support with the part number and the reason shown.