eBay Item Specifics in CSV Bulk Uploads: Category Templates That Actually Pass

8 min readPipeSheets Team

If your eBay bulk upload rejects listings for missing item specifics, the cause is almost always a mismatch between your spreadsheet and the category template you downloaded from Seller Hub Reports. Item specifics live in columns prefixed with C: (like C:Brand or C:Type), and those columns are generated for one specific category. When a required specific is blank, or you paste rows built for one category into a template for another, eBay refuses to post the listing. This guide covers how the C: convention works, which specifics are required versus recommended, how CustomLabel matches listings on revisions, and how to clean the file before you upload.

Why do item specifics columns differ for every eBay category?

Seller Hub Reports does not give you one universal listing template. When you go to the Reports tab, choose Upload, and download a create-listings template, you pick a category first. eBay then builds the file with item-specifics columns matched to that exact category. A trading-card template exposes columns like C:Grade and C:Card Condition; a men's clothing template exposes C:Brand, C:Size, C:Color, and C:Type instead. Everything else in the template stays the same across categories, but the C: columns change.

This is the single most common reason bulk uploads fail. Sellers download a template for one category, build a large sheet, then reuse the same column layout for products in a different category. The C: headers no longer match what eBay expects for the new category's Category ID, so required specifics come back missing even though the cells look filled in. The Category column must contain the numeric leaf (final) category ID, never an intermediate parent category, and the C: columns have to belong to that same leaf.

How the C: column prefix works for item specifics

In Seller Hub Reports templates, any item specific is expressed as a column whose header starts with C: followed by the specific's name. The value in that cell becomes the value of the specific. You can add a specific that is not in the downloaded template simply by inserting a new column and naming it C: plus the specific name. This is the same format Seller Hub uses internally, so it imports cleanly.

C:Brand      -> the item's Brand specific
C:Type       -> the item's Type specific
C:Size       -> the item's Size specific
C:Color      -> the item's Color specific
C:Department -> the item's Department specific

Two rules trip people up. First, the name after C: must match eBay's specific name for that category exactly, including spelling and spacing, or eBay treats it as a custom specific rather than the required one it was looking for. Second, if a specific genuinely does not apply to your product, do not leave it blank when it is required. Enter Does Not Apply, or for a brandless product enter Unbranded. A blank required specific is a failure; an explicit Does Not Apply passes.

Required vs recommended item specifics, and what fails

eBay splits item specifics into two groups. Required specifics are mandatory for the category. Common ones include Brand, Type, Size, Color, and Model, but the exact set is defined per category. If a required specific is missing, the listing does not post. In the Seller Hub interface the missing fields get flagged in red; in a bulk upload the row fails and the upload report tells you which specific was missing on which row.

Recommended specifics are optional for posting but strongly affect discoverability. eBay derives them from buyer search and filter behavior, so a listing that fills in the recommended specifics surfaces in more filtered searches than one that only clears the required minimum. Missing recommended specifics will not block your upload, but they quietly suppress how often the listing appears when buyers narrow results by attribute. Treat required specifics as a pass/fail gate and recommended specifics as a visibility lever.

Required item specifics are category-specific and change over time. Always download a fresh template for the exact category you are listing in rather than reusing an old file. A template pulled months ago may be missing specifics eBay has since made required, and every row built on it will fail.

The core columns beyond item specifics

Item specifics get the blame, but a few structural columns cause just as many rejections. Knowing what each expects saves a round of trial and error.

The columns that decide whether a bulk row is accepted:

Action: the first column. It accepts Add (create a new listing), Revise (update an existing one), Relist, End, Delete, and AddOrRevise. Blank or misspelled Action values fail the row.
Category: the numeric leaf Category ID. It must be a final category, not an intermediate parent, and it must match the C: columns in the file.
CustomLabel: your SKU. Optional to include, but this is how eBay identifies which listing to revise, so it is effectively required for any update workflow.
Title: the listing title, capped at 80 characters. Longer titles are rejected.
PicURL: image URLs. Up to 12 images per listing, separated by a pipe character.
C: columns: the item specifics, matched to the category, as described above.

How CustomLabel (SKU) matches listings for revisions

Bulk edit and full upload are two different jobs. A full Add upload creates listings from scratch. A Revise upload changes fields on listings that already exist, and eBay has to know which live listing each row refers to. It matches on the eBay Item ID or, more conveniently, on CustomLabel, your SKU. If your SKUs are inconsistent between the original upload and the revision file, eBay either cannot find the listing or updates the wrong one.

This is where dirty spreadsheets do real damage. A SKU stored as SKU-00123 in one export and 123 in another (Excel silently dropped the leading zeros and the prefix on paste) will not match. Trailing whitespace after a SKU, smart quotes pasted from a document, or an inconsistent case will all break the match. When you revise, you also do not need to resend every column, only the ones you are changing plus the matching CustomLabel, so keeping SKUs clean and stable is what makes revision uploads reliable.

On a Revise, image handling is limited. eBay hosts pictures from the URLs you supply on the original Add, so changing a PicURL on a later Revise does not reliably swap the hosted image. If you need different photos, plan to end and relist rather than counting on a PicURL revision to take.

Before and after: fixing an item-specifics file

Here is a typical broken export. The seller merged two category batches into one sheet, so the C: headers do not match a single category, Brand is blank where it is required, a SKU lost its leading zeros, and the header casing is inconsistent. eBay returns missing-required-specific errors on every row.

Before (fails: blank required Brand, mismatched C: columns, mangled SKU)

Action,Category,CustomLabel,Title,c:brand,C:Grade,C:Size
Add,11450,123,Vintage Wool Sweater Large, ,,L
Add,11450,124,Cotton Tee Medium,Hanes,,M

Problems:
- Category 11450 is clothing, but C:Grade belongs to a card category
- Row 1 Brand is blank (required for clothing)
- CustomLabel 123 was 00123 before Excel dropped the zeros
- Header is c:brand (lowercase c) instead of C:Brand

After (passes: consistent C: columns for the category, required specifics filled)

Action,Category,CustomLabel,Title,C:Brand,C:Size,C:Color
Add,11450,00123,Vintage Wool Sweater Large,Unbranded,L,Gray
Add,11450,00124,Cotton Tee Medium,Hanes,M,White

Fixes:
- Dropped C:Grade; kept only specifics valid for category 11450
- Filled Brand: Unbranded for the no-name sweater, Hanes for the tee
- Restored 00123 / 00124 as text so SKUs match on revision
- Normalized headers to the exact C:Name casing eBay expects

A pre-upload checklist for item specifics

Run through this before you upload to Seller Hub Reports:

Download a fresh category template for the exact leaf category you are listing in, one category batch per file.
Confirm every C: header matches eBay's specific name for that category exactly, including capital C and correct spelling.
Fill every required specific; use Does Not Apply or Unbranded rather than leaving a required cell blank.
Add as many recommended specifics as apply, since they drive search filter visibility.
Verify the Category column holds a numeric leaf Category ID, not a parent category name.
Check that CustomLabel (SKU) values are intact, with no dropped leading zeros, no trailing spaces, and consistent formatting across Add and Revise files.
Confirm titles are at or under 80 characters and PicURL images use the pipe separator, up to 12 per listing.
Set the Action column correctly: Add for new, Revise for updates keyed on CustomLabel.

Cleaning the file so specifics match every time

Most item-specifics failures are formatting problems that happen before eBay ever sees the file: leading zeros stripped from SKUs, whitespace clinging to values, inconsistent header casing, and stray null placeholders like N/A sitting in required cells. Excel is often the culprit, since opening and resaving a CSV silently mangles SKUs and dates. Fixing these by hand across hundreds of rows is slow and error-prone.

This is the cleaning stage where PipeSheets helps. You upload the export, run a pipeline, and preview the before and after with detected column types before you download. Trim whitespace clears trailing spaces off SKUs and specific values. Normalize headers fixes casing so c:brand becomes the C:Brand eBay expects. Standardize nulls turns N/A and blank placeholders into true empty cells so you can spot which required specifics still need a value. Find and replace, with regex if needed, rewrites a Category column or renames a specific across every row at once. Because PipeSheets exports CSV without the leading-zero and date mangling Excel introduces, your CustomLabel SKUs stay intact and continue matching on revision uploads.

PipeSheets does not build the eBay template or map columns to a category for you; that mapping is yours to get right against the category you downloaded. What it does is guarantee the underlying data is clean, consistently formatted, and free of the whitespace, encoding, and null noise that turns a valid item-specifics layout into a wall of rejection errors. Get the C: columns matched to the right category, fill the required specifics, keep your SKUs stable, and the upload passes.