How bulk listing files work
A bulk listing file is a flat table: one row per product, one column per field, with a header row of field names the marketplace recognises. The upload validates each row and rejects the ones it cannot interpret, reporting an error per row rather than failing the whole file.
For automotive catalogues the file has two layers: the product rows themselves, and the vehicle compatibility rows attached to them.
The columns that matter for car parts
Category-required item specifics vary by part type, but this core set applies across almost every automotive listing.
| Column | Purpose | Common mistake |
|---|---|---|
| Category ID | Places the item in the parts tree | Using a generic or retired category |
| Title | Search text buyers match against | Missing brand or part number |
| Brand | Filter and catalogue matching | Three spellings of one brand |
| MPN | Manufacturer part number | Internal SKU used instead |
| EAN / GTIN | Barcode matching | Number mangled by the spreadsheet |
| Item specifics | Category-required attributes | Left blank, so the row is rejected |
| Quantity / Price | Stock and sell price | Cost price uploaded by mistake |
| Compatibility rows | Vehicle fitment | Model only, no engine or year range |
The errors that reject a file
Almost every failed automotive upload comes down to the same handful of causes. Fixing them at the source file level fixes them for every future run.
- Part numbers auto-formatted into scientific notation, dates or trimmed leading zeros.
- Required item specifics missing for the chosen category.
- Non-UTF-8 characters from a supplier export breaking the row.
- Inconsistent header names, extra blank columns or a stray total row.
- Compatibility referencing vehicles that do not exist in the marketplace's vehicle catalogue.
- Duplicate SKUs across two supplier files creating conflicting rows.
Where spreadsheets stop being enough
A few hundred rows can be hand-corrected. Ten thousand rows with fitment attached cannot: the correction work grows faster than the catalogue, and every supplier price update restarts it.
At that point the job stops being an upload and becomes catalogue management — normalisation rules, brand and category mapping, reference deduplication, validated batching and repeatable price and stock runs.
Having it built and imported for you
CPL PRO is a done-for-you automotive eBay listing and catalogue service — not software, SaaS, an AI tool or a self-service platform. You send the supplier data in Excel or CSV. We clean and structure it, build the listings and import the agreed products into your own eBay account.
FTP stock feeds and price update runs are quoted as project extras, not plans or subscriptions. Every project includes a live editable Excel margin sheet with rebate filters.
Frequently asked questions
What file format does eBay bulk listing use?
Bulk listing files are comma-separated CSV files with a fixed header row of recognised field names. Spreadsheet software can produce them, but the file must be saved as CSV, not as a native workbook.
Why does my bulk upload keep failing?
The most common causes are missing category-required item specifics, invalid category IDs, part numbers reformatted by the spreadsheet into scientific notation or dates, missing brand or MPN values, and inconsistent column headers between the header row and the data.
Can compatibility be uploaded in bulk?
Yes — vehicle compatibility can be supplied in bulk, but it multiplies row volume quickly because each SKU carries one row per vehicle variant it fits. Large catalogues run into hundreds of thousands of compatibility rows.
Do you handle the upload for me?
Yes. CPL PRO cleans the catalogue, builds the listing data and imports the agreed products into your own eBay account. Typical delivery is 3–5 working days after a 1–2 working day planning stage confirmed in writing.