CSV import should be flexible before commit

Whether SaaS CSV import should accept messy files into preview but keep commit strict.

CSV import seems simple until real users upload files from spreadsheets, CRMs, marketplaces, and regional tools. I think the product should be flexible in preview: detect headers, suggest mappings, group warnings, and show sample rows. But the final commit should stay strict about identity, required fields, and destructive updates. Does that split reduce support load, or does it make the import UI too complex for a small SaaS?