Practical guidance
Review a CSV repair before exporting
The useful outcome is a file whose changes you understand. A lower issue count by itself does not prove that the product data is right.
Start with a preserved original
- Upload a copy and confirm the platform and create/update mode.
- Read structural errors before cell-level findings.
- Review the original value, proposed value, affected row, and rule source.
- Accept only changes supported by the source data. Use undo if the result is wrong.
- Revalidate, then download the import file and both reports.
Separate three types of work
A deterministic proposal has a narrow, explainable rule, such as normalizing an accepted boolean spelling. A review-required change may alter meaning. Missing information needs a merchant-supplied answer. Bulk acceptance should include only explicitly eligible proposals; it should never fill unknown prices or stock.
Keep the reports beside the file
The change report records applied edits. The unresolved-issues report records what still needs attention. Spreadsheet reports are for human review, while the machine-import file preserves the catalog values required by the importer. Keep all three with the original for comparison.
What this check cannot establish
Passing the checks implemented in Golanto does not mean a marketplace has approved the file. Store state, category rules, media availability, and account permissions can still affect import results.
Check your file
Start with a copy. Review changes before downloading your import file.
Open the CSV tool