Reproducible Lab Cases

See exactly what the checker does with known CSV failures

Each lab case uses a small downloadable fixture, documents the expected behavior, and explains why repair is safe or blocked.

These are controlled test cases, not customer stories. They are intentionally small fixtures used to make CSVFixLab's behavior reproducible and reviewable.

Safe normalization

Semicolon CSV → comma CSV

A valid three-column semicolon file can be parsed and serialized as comma-separated CSV without changing field values.

Repair blocked

Rows with too few and too many columns

The checker can prove the row width is wrong but cannot invent the missing business field.

Repair blocked

Unclosed quoted field

A missing closing quote can swallow later commas and line breaks, making automatic insertion unsafe.

Confirmation required

Windows-1252 → UTF-8

Auto proves the file is not UTF-8, then waits for the source encoding to be explicitly selected.

Platform blocker

Shopify CSV missing Title

The file is valid generic CSV but fails a basic Shopify product-import header check.

Repair blocked

Duplicate CSV header names

Two columns with the same header make downstream mapping ambiguous, so safe repair does not rename them.

Why publish test fixtures?

A repair tool should make its boundaries visible. A screenshot or marketing claim is difficult to verify, but a tiny CSV fixture lets anyone run the same input through the checker and compare the report.

The cases intentionally cover both outcomes: files that can be normalized without changing business meaning, and files where the tool refuses to guess. That refusal is part of the product behavior, not an unfinished feature.

How to use a case

Open a case page and download its sample CSV.
Open the linked CSVFixLab tool.
Upload the sample without editing it.
Compare the detected structure and issue messages with the case notes.
For repairable cases, download the fixed copy and re-check it.

See Testing methodology for the safety rules used across the toolset.