BigCommerce CSV Import Errors

Empty files, invalid UTF-8, malformed quoting, inconsistent column counts, and duplicate headers can block the precheck. A byte-order mark or mixed record endings produces a format warning; the tool can offer a reviewed formatting copy without changing business values.

Missing, reordered, duplicated, or unknown fields must be compared with a recent export from the destination store because store and export configurations can differ.

A blank imported value can mean clear, ignore, or invalid depending on the field and importer behavior. Review blank business values instead of filling them automatically.

Missing or duplicate SKUs reduce matching confidence. Keep product and variant SKUs unique and verify how existing catalog records are identified.

Variant and image rows need a valid parent product and a coherent order. Orphaned or interleaved rows can attach data to the wrong product.

Keep option names consistent inside one product and keep each option-value combination unique. Do not guess a replacement for a conflicting variant.

For example, Price uses a dot-decimal value such as 29.00, Current Stock uses an integer such as 12, and the supported Is Visible format uses uppercase TRUE or FALSE. Check Type and Inventory Tracking against the supported values; store-dependent category or custom-field differences remain review items.

Image references should be valid public HTTP(S) URLs when the importer must fetch them. A syntax check cannot prove that a remote image is reachable.

Category paths depend on the destination store. Differences from the baseline need review after the category tree is prepared.

Compare custom-field names with the destination baseline. Missing fields can remove intended data, while private data may belong in metafields instead.