CSV Import Error Groups for Support

CSV import errors are easier to support when they are grouped by user action instead of listed as raw validation failures. A raw message like “row 183 invalid” tells the user where pain exists but not how to repair the file.

A useful grouping starts with identity errors. These include missing IDs, duplicate IDs, email collisions, or update rows that cannot be matched to existing records. Identity errors should usually block commit because the product cannot safely decide what record is being changed.

The second group is required field gaps. These rows have a missing customer name, SKU, quantity, date, owner, or other required value. The preview should show the count and examples, then let the user choose whether to fill a default, skip affected rows, or return to the spreadsheet.

The third group is format repair. Dates, currency, phone numbers, booleans, and status values often differ by tool or region. The preview can offer transformations, but it should show what will change. For example, “12/04/2026” needs a date interpretation before commit.

The fourth group is ignored data. Extra columns are not always bad, but users should know they will not be imported. A good importer says which columns are ignored and whether they can be mapped manually. Support load drops when the product shows the repair path, not just the failure.

CSV Import Error Groups for Support

// COMMENTS

ON THIS PAGE