eBay Rejected Your CSV Upload? Template Lines, UPC Damage and Encoding, Explained

Last updated: August 2026 · By the CSVUndo team · 9 min read · Applies to Seller Hub Reports uploads and legacy File Exchange files · Not affiliated with or endorsed by eBay

eBay’s own File Exchange instructions address the zeros head-on: when a field value contains leading zeros, change the cell format to Text — otherwise the zeros are removed from cells in Number or General format the moment the file is saved as CSV.

Why does eBay say it couldn’t identify my template?

Seller Hub Reports — the bulk-upload system that took over when eBay retired File Exchange in mid-2021 — generates every template it will later accept. There are five — create new listings by category, edit price and quantity, relist unsold listings, add tracking, create drafts — each downloading as an Excel workbook (the default) or as a CSV that eBay describes as the option for advanced sellers. Whichever you pick, the rows above your data are structural: the #INFO row at the top “is to remain on the file” — eBay says so explicitly — and the first real cell is a metadata header along the lines of Action(SiteID=US|Country=US|Currency=USD|Version=1193|CC=UTF-8). The Version number changes over time — keep whatever your downloaded template contains, never a value copied from an article — and the legacy File Exchange manual warned that changing the metadata values can cause upload errors.

Alter that first line — or let a program alter it for you — and the upload page responds: “We couldn’t identify your template. Make sure you haven’t changed the first line of the template you downloaded.” The maddening part is that sellers hit this without knowingly touching anything. A re-save can prepend an invisible UTF-8 byte order mark — sellers using Excel on a Mac report the bytes surfacing as  in front of #INFO — a detour through Word plants hidden characters, and saving in a format that is not a true CSV changes the file wholesale; threads about the same upload page also quote a “selected file format is incompatible” rejection. The reliable escape: download a fresh template for your own eBay site (headers and required fields differ by site), paste your data rows into it, and leave everything above the headers alone.

Why did my UPCs become 8.85E+11 — and why does eBay call the UPC missing?

In Excel’s default General format, any number of 12 or more digits is displayed in scientific notation. A UPC is exactly 12 digits — eBay’s create-listings help caps P:UPC at 12 characters and P:EAN at 13 — so every single barcode qualifies. Open the CSV by double-click, save it, and the display string is what gets written: 885909560622 leaves the file as 8.85909E+11. To eBay that cell no longer holds a product identifier at all, so in a category that requires one the row fails. Tools that submit through eBay’s API report it as Error: Required field, UPC, is missing. (21919301) — or the EAN variant; if you upload through Seller Hub alone, the results file may phrase the same failure differently.

eBay’s field table labels P:UPC as “Type: Integer”, which reads like an instruction to format the column as a number in Excel. It is not — it describes what eBay expects to receive, and in Excel the cell must be Text or the value will not survive a save. A second trap sits nearby: eBay’s template guide genuinely does say to format one column as Number with zero decimal places — but that advice is for the Item number column, eBay’s read-only 12-digit listing IDs, which never begin with a zero. Applied to a UPC or EAN column, Number format quietly deletes the leading zeros instead. Two columns, two opposite rules.

One case where a barcode-less cell is legitimate: eBay’s documented value for items with no product identifier is Does not apply, typed without quotes — and on a variation listing, each child row without a barcode carries it.

Where did the leading zeros in my UPCs and EANs go?

The same double-click that causes the notation is what removes the zeros. A CSV has no way to declare “this column is text”, so Excel guesses; a cell made only of digits becomes a number, and to a number parser 0085674858930 and 85674858930 are equal. The zero is discarded before the sheet finishes opening, and the next save writes the shortened code into the file for good. EAN columns suffer worst, because the EAN-13 form of any UPC-A is the same 12 digits with an extra 0 in front — an entire column of values engineered to begin with zero. The general mechanics, and the Excel-side prevention, are in the leading-zeros guide; the bolded File Exchange sentence near the top of this page is eBay’s own statement of the same rule.

How do I repair a damaged eBay file in the browser?

Repair the raw file instead of fighting cell formats. The scientific notation fixer expands cells like 8.85909E+11 back to plain digits in the columns you choose, and the leading-zeros fixer left-pads shortened codes back to a standard width — 12 for UPC, 13 for EAN. Both read the file as bytes and run entirely on your device; nothing is uploaded anywhere.

1. Drop the CSV onto the tool, or paste the rows straight in.
2. Scientific notation is found and expanded for you — not by a blanket search-and-replace, but only where a cell passes a shape test, so a genuine part number like 2E5 is left alone. Leading-zero padding is the repair you choose columns for. On the scientific-notation page the column table starts closed, so tick Restore leading zeros first to open it, then tick P:UPC or P:EAN and confirm the width — only you know a code is meant to be 12 or 13 digits wide. (The leading-zeros fixer opens that table for you, if padding is all you need.)
3. Untick “Add UTF-8 BOM” before you download. It ships ticked because Excel needs the byte order mark to show accents correctly — but eBay does not, and a BOM sitting in front of the #INFO row is one of the things that triggers “We couldn’t identify your template.”
4. Click Repair & Download. The delimiter and column layout are preserved, so the file goes back to eBay otherwise untouched.

Be honest about the limits. Expansion restores only the digits Excel actually saved — 8.85909E+11 becomes 885909000000, with zeros where the mantissa ran out — and Excel keeps at most 15 significant digits, so anything truncated past that point is no longer in the file and must be re-exported from your source system. Padding only happens in columns you tick. A header naming a standard-width code such as UPC 12 or EAN 13 is pre-ticked at that width, provided no value in the column still starts with a zero — one that does proves Excel never stripped it; any other digit-only column is offered unticked with the width pre-filled from its longest value, so check that number before you tick it. On size: the tools warn well before the ceiling and refuse above 250 MB on a capable Chrome or Edge machine; Safari, Firefox and lower-memory devices get a lower ceiling. Processing runs off the main thread, so the tab stays responsive and you can Cancel — comfortably beyond an eBay file, since eBay staff have said on the community boards that Seller Hub Reports kept File Exchange’s limits of 14.9 MB and 150,000 lines.

Which delimiters, quotes and line breaks will eBay accept?

eBay’s format rules are strict CSV with a few of its own. Text qualifiers must be plain quotation marks (") — the curly “smart quotes” Word substitutes are not qualifiers, just characters in your data — any field containing a comma or semicolon must be wrapped in quotes, and a literal quote inside a field is written doubled, as in "Clarence ""Lumpy"" Rutherford". Line breaks inside a cell are forbidden outright: eBay’s instructions say fields cannot contain new lines, line feeds or carriage returns, and that formatting belongs in HTML <br> and <p> tags inside the Description instead. A pasted description with a real line break splits its row mid-field — the anatomy of that failure is in the line-breaks guide.

Line endings matter too. Files prepared on Linux or in a Mac terminal need Windows-style CRLF endings — eBay’s manual literally tells sellers to run unix2dos before uploading. And if the file has ended up with the wrong separator entirely (legacy File Exchange accepted comma-, semicolon- and tab-delimited files; those were its rules, not necessarily Seller Hub’s today), the delimiter converter re-serializes it with quoting handled correctly — never with find-and-replace in a text editor, because real commas and semicolons live inside titles and descriptions. A final quirk worth knowing: a lone hyphen (-) in a cell is eBay’s marker for a deliberately empty value.

Why did item titles upload with é instead of é?

The template declares its own answer: the Action header ends in CC=UTF-8. But Excel’s plain “CSV (Comma delimited)” save writes the legacy Windows codepage — Windows-1252 on most machines — and an 80-character eBay title has plenty of room for the é, ™ or curly apostrophe that exposes the mismatch. Plain-ASCII titles survive either encoding, which is why the fault hides until your first accented listing. When wrong bytes do reach eBay, tools that submit through its API report error 20400 — “Invalid request encoding. Please use utf-8 encoding and eliminate any non utf-8 encoding in request content.” — while what the official docs don’t cover, sellers report from experience: accented characters corrupting on upload, and jobs dying over an added byte order mark. The safe universal recipe is UTF-8 without a BOM, CRLF line endings.

Diagnose before guessing: the encoding checker reads the file’s actual bytes and names the real encoding, which regularly contradicts the save dialog. If the damage is already baked in — Café sitting in your titles — re-encoding cannot help, because the wrong characters are now the data. The broken characters fixer reverses the common mojibake patterns, and the mojibake guide explains how one é became two wrong characters in the first place.

Why does eBay say the upload is complete when rows failed?

“Your upload is complete” is a statement about the file, not your listings. eBay’s own help for the upload templates is blunt: even though the upload may be completed, you must check the results report to make sure no rows failed. Processing usually takes under 15 minutes, and the per-row verdicts — including every missing-UPC and invalid-value failure described above — exist only in that downloadable results file. A drafts upload answers “Your listing is complete.” instead. Sellers also report a harsher outcome: a job that never finishes and shows as “Abandoned”, which community posts associate with a stray byte order mark or an invalid line — the template faults from the top of this page, surfacing one step later. Whatever the banner says, the habit that catches everything is the same: download the results report after every upload and read it.

Frequently asked questions