Practical guidance
Find duplicate or empty CSV headers
Two columns named SKU are two separate columns. A parser that converts each row into an object too early may overwrite one with the other.
Use column position as well as name
In the example, the first and second SKU columns have different values. Do not choose one by position or discard the other without checking the source. One might be a parent code and the other a variant code.
SKU,SKU,Title
PARENT-08,00081,Canvas bagGive each column a confirmed purpose
- Review the header row in its original order.
- Compare repeated columns across several records.
- Confirm which destination field each source column represents.
- Rename or map deliberately, then review the output schema.
Whitespace can hide a mismatch
SKU and SKU followed by a space look similar in a table. Header trimming can be a useful proposal, but the result still needs a collision check. If trimming creates two identical names, resolve that ambiguity before a schema-specific import.
Worked example
Only after the merchant confirms each column’s meaning
SKU,SKU,Title
PARENT-08,00081,Canvas bagParent code,SKU,Title
PARENT-08,00081,Canvas bagThis generic example is not a Shopify import schema. The confirmed destination template determines which columns are accepted.
What this check cannot establish
Golanto retains duplicate columns by position. It cannot decide the correct business meaning from repeated names alone.
Check your file
Start with a copy. Review changes before downloading your import file.
Open the CSV tool