eBay File Exchange Errors: Why Your Bulk Listings Fail (And How to Fix Them)
You uploaded a CSV to eBay File Exchange or the Seller Hub bulk listings tool, waited for the response, and got back a report with a wall of red. Half the rows failed. The error column says things like "Required Item Specifics missing" without telling you which item specifics, or "Invalid Action" without telling you what's wrong with the action. The good news: every error in a File Exchange report has a fixable cause once you know what to look for.
How eBay Validates Your Upload
When you submit a bulk file, eBay runs each row through a sequence of checks: file format and encoding first, then the Action column to decide what eBay should do with that row, then per-row validation against the category's required fields, and finally the marketplace-specific rules (US vs UK vs DE, etc.). A single row can fail at any stage, and the error report only tells you about the first failure it hits. Fix one error and you may surface a second one the next time you upload.
Where to find your error report
In File Exchange, go to the File Management Center and download the response report for your upload. In Seller Hub, navigate to Listings > Reports and download the error summary. Both reports use the same row reference — the row number from your original upload — but the column layout differs slightly. The response file lists each row's status ("Success," "Failure," or "Warning") and the error message that triggered the failure.
Action Codes: The Source of Half Your Errors
Every row in a File Exchange upload requires an Action value in the first column. The action tells eBay what to do with that row: list a new item, update an existing one, end a listing, or relist a sold-out item. Using the wrong action — or omitting it — is the most common single cause of upload failures.
Valid action codes:
- Add — Create a new listing. CustomLabel/SKU should be unique; reusing an existing SKU will fail.
- Revise — Update an existing live listing. Requires either ItemID or CustomLabel that matches a current listing.
- Relist — Re-list a sold or ended item. Requires the original ItemID.
- End — End an active listing early. Only needs Action and ItemID (or CustomLabel).
- Verify — Dry-run validation. Returns the same errors as Add but doesn't actually list.
- VerifyAdd — Same as Verify; used by older File Exchange templates.
Error: "Invalid Action" or "Action not recognized"
This usually means a typo or trailing whitespace in the Action column. eBay is case-sensitive about action codes in some templates. "add" or " Add " (with a space) won't match. Trim whitespace from every cell in the Action column and verify the casing matches the template documentation.
Error: "CustomLabel already exists" or "Duplicate SKU"
You used Action=Add on a row where the CustomLabel matches an existing listing. Either change the CustomLabel to something unique, or switch the Action to Revise if you meant to update the existing listing.
Required Item Specifics: The Moving Target
eBay's required Item Specifics change per category and per marketplace, and they update them with no warning. A CSV that uploaded cleanly last month may fail today because eBay added a new required specific (like Department or Type) to your category. The fix is always the same: add the missing column with valid values.
Error: "Required Item Specifics missing"
The error report should list which specifics are missing, but sometimes it just says "required item specifics missing." If you don't see a specific name, look up your category in eBay's Item Specifics Lookup tool. The current requirements are listed there for every leaf category. Common required specifics include Brand, MPN (Manufacturer Part Number), Type, Department, Size, Color, Material, and Style.
Error: "Item Specific value not recommended"
This is a warning, not a hard failure — but it suppresses your listing from filtered search. eBay maintains a recommended values list for many specifics (Color, Material, etc.). Using "Light Blue" when eBay expects "Blue" will list the item but bury it in search results. Stick to the recommended values when possible.
Error: "Brand value 'Unbranded' requires MPN value 'Does Not Apply'"
eBay enforces conditional rules across Item Specifics. If you set Brand to "Unbranded," the MPN field must be exactly "Does Not Apply." Leaving MPN blank, putting a real part number, or using a variant like "N/A" or "None" will fail. The reverse is also true for some categories: setting MPN to "Does Not Apply" forces Brand to be Unbranded or Generic.
Category and Variation Errors
Error: "Invalid Category ID" or "Category is no longer leaf"
eBay periodically reorganizes its category tree. A category ID that worked previously may have been split into subcategories, making the parent ID invalid for listings. You can only list under leaf categories (the most specific level). Use eBay's Category ID Lookup or the Sell Your Item form to find the current leaf category, then update PrimaryCategory and SecondaryCategory in your CSV.
Error: "Variation Specifics inconsistent across variations"
Multi-variation listings use a parent row plus child rows. eBay requires the Variation Specifics columns (like Size and Color) to be consistent: every child row must specify every variation specific defined on the parent. If your parent says variations vary by Size and Color, every child must have a Size and a Color value. Missing values in even one child row fails the whole listing.
Variation vs Item Specifics confusion
Item Specifics describe the listing as a whole (Brand, Department). Variation Specifics describe what varies between SKUs (Size, Color). Putting a varying attribute in Item Specifics — or putting a constant attribute in Variation Specifics — breaks the listing. If every variant is the same brand, Brand goes in Item Specifics. If sizes differ, Size goes in Variation Specifics.
Wrong structure:
Action,CustomLabel,Title,*ItemColor,*ItemSize
Add,PARENT-001,Cotton T-Shirt,Blue,Small
Add,CHILD-001,,Blue,Small
Add,CHILD-002,,Blue,Medium
Right structure (parent declares variations, children specify values):
Action,CustomLabel,Title,Relationship,RelationshipDetails
Add,PARENT-001,Cotton T-Shirt,,"Size=Small;Medium;Large|Color=Blue;Red"
Add,CHILD-001,,Variation,Size=Small|Color=Blue
Add,CHILD-002,,Variation,Size=Medium|Color=BluePhoto and URL Errors
Error: "Picture URL must use HTTPS"
eBay requires all picture URLs to use HTTPS. Any http:// URL in the PicURL column will fail. If you're hosting images on your own server, set up SSL. If you're using a CDN, verify it supports HTTPS and update the URLs.
Error: "Too many pictures"
eBay allows up to 24 pictures per listing for most categories, 12 for some. Separate URLs in the PicURL column with the pipe character (|) — not commas, not semicolons. Going over the limit will reject the listing.
Error: "Image could not be downloaded"
eBay tried to fetch the image URL and got a 404, a redirect, or a non-image response. Common causes: URLs that point to a viewer page instead of the raw image file (image-hosting services do this), Google Drive or Dropbox "sharing" links that require authentication, or URLs with query strings that have since expired. Use direct CDN URLs that return image bytes when fetched.
GTIN, UPC, EAN, and ISBN Errors
Error: "Invalid UPC" or "GTIN checksum failed"
UPCs, EANs, and ISBNs all have checksum digits. eBay validates the checksum on every product identifier. If you typed a 12-digit UPC and got the last digit wrong, eBay rejects the listing. Common sources of bad GTINs: scanning a barcode and missing a digit, copying from a vendor catalog that has typos, or storing UPCs as numbers in Excel (which strips leading zeros).
Excel gotcha: UPCs starting with 0 (like 012345678905) get converted to numbers by Excel, dropping the leading zero. Always format UPC columns as Text before opening the file, or import as CSV with explicit string types.
Error: "Product Identifier required"
For most categories, eBay requires a Brand + MPN + GTIN combination, or the explicit "Does Not Apply" values for items that genuinely have no GTIN (handmade goods, certain vintage items). Leaving these fields blank fails the listing. Setting any of them to "N/A," "None," or empty when eBay expects "Does Not Apply" also fails.
Encoding and Character Errors
eBay expects CSV files in UTF-8 without a BOM (byte order mark). Files saved from older Excel versions or systems set to other regional encodings often contain characters that look fine in your spreadsheet but break the upload. The classic symptoms: accented characters appear garbled in the error report, rows that look identical succeed and fail, or the first row fails when row 1 is just the header.
Characters that frequently cause failures:
- Smart quotes (' and ") — replace with straight quotes
- Em-dashes (—) — replace with hyphens
- Ellipsis character (…) — replace with three periods
- Non-breaking spaces — invisible but break parsing
- Trademark/registered symbols in titles (™ ® ©) — disallowed in many categories
Step-by-Step: Fixing Your File Before Re-Upload
Step 1: Fix encoding first
Open the file in a text editor (not Excel) and verify the encoding is UTF-8 without BOM. In VS Code, the encoding is shown in the bottom-right status bar. Re-save if needed. This fixes a surprising number of "the file looks fine but won't upload" cases.
Step 2: Verify the Action column
Every row needs a valid Action value. Trim whitespace from the Action column. Check the casing matches eBay's documentation for your template version.
Step 3: Check category and required specifics
Look up each unique category ID in your file. Confirm it's still a leaf category. Pull the current required Item Specifics for each category and verify your CSV has columns for all of them. This is the single highest-yield step for fixing upload errors.
Step 4: Validate GTIN checksums
UPC checksums use a simple modulo-10 formula. If you have access to a spreadsheet formula or a small script, validate every UPC/EAN before upload. For files with leading-zero UPCs, ensure they're stored as text strings, not numbers.
Step 5: Sanitize titles and descriptions
Run a find-and-replace pass on titles and descriptions to convert smart quotes, em-dashes, and ellipsis characters to ASCII. Strip trademark symbols where the category doesn't allow them.
PipeSheets can do most of this in one pass. Upload your eBay file, run a cleanup pipeline that normalizes encoding, trims whitespace, replaces smart characters, and standardizes empty values — and download a File Exchange–ready CSV. See the eBay Bulk Upload CSV Helper for an eBay-specific preset.
Preventing Future Failures
If you upload eBay files regularly, build a cleanup pipeline once and run it every time. The same vendor or source system tends to produce the same set of issues, so a pipeline that fixes them on one file will fix them on the next. Re-run eBay's Verify action on a sample after each cleanup to catch new requirements before you upload the full batch.
Quick prevention checklist:
- Use the latest File Exchange template — eBay updates them with new fields
- Save CSVs as UTF-8 (without BOM), not regular CSV
- Format identifier columns (UPC, MPN, ISBN) as text to preserve leading zeros
- Run Verify on a single row before uploading the full file
- Keep a log of which errors you hit and which fixes worked
Try the automated solution
PipeSheets can fix these issues automatically. Clean your first file free.
Clean Your CSV