Check shape
Count columns, find ragged rows, and confirm quoting before changing field mapping.
Bean Jar Labs
CSV Import Error Decoder
Use this quick guide when a CRM, marketplace, finance system, inventory tool, or internal dashboard rejects a CSV with a vague import error. It explains what the error usually means, what to inspect first, and when to run a local precheck before another upload attempt.
Check headers
Trim whitespace, remove duplicates, and make required columns explicit.
Check types
Look for text in number/date columns and blanks in likely required fields.
Common CSV import errors
What the message usually means
Rows do not match the header width.
The importer expected each row to have the same number of cells as the header. Common causes are broken quoting, stray commas, truncated exports, or rows copied from a spreadsheet with hidden delimiters.
Two or more headers normalize to the same field.
Duplicate headers can make a mapper overwrite values or reject the file. Look for repeated names, casing-only differences, and leading or trailing spaces.
A mostly typed column contains a conflicting value.
A numeric column can fail because of currency symbols, thousands separators, blanks, text placeholders, or date formats that changed partway through the export.
A key import column is empty in at least one row.
Required IDs, emails, SKUs, dates, amounts, names, and foreign keys often need a quick profile before upload. A blank can be valid only if the destination system explicitly allows it.
The visible header is not the actual header.
Import mappers often treat id, id, and id
as different fields. Trim before mapping.
The export changed since the last successful import.
Added, removed, renamed, or reordered columns can break repeat imports even when the file looks similar at a glance.
Fast triage checklist
Before another upload attempt
- Save a sanitized sample with the header and enough rows to reproduce the issue.
- Count the header cells and compare every row to that count.
- Trim headers and check for duplicates after lowercasing.
- Profile likely required fields for blanks.
- Profile numeric, boolean, and date columns for conflicting text values.
- Document the exact import error and the destination system that produced it.
Specific fixes
Jump to the detailed error page
Local first
Run the browser precheck before sending files anywhere.
The Bean Jar Labs precheck runs in the browser and can generate a short findings report from a sanitized sample. It is designed to help you decide whether the file needs a quick checklist, a tracker template, the audit kit, or a done-for-you audit.
Use sanitized samples only. Do not send sensitive personal, health, financial, credential, regulated, or confidential data until handling and scope are explicitly confirmed.
Destination-specific