Lab Case · Safe

A semicolon CSV that can be safely normalized

The values are already correct; only the serialization format differs from a comma-separated destination.

Reproducible fixture
Issue: delimiterOutcome: repair allowedBusiness values changed: no

Fixture

name;price;sku
Blue Shirt;19.99;SKU-001
Red Shirt;24.50;SKU-002

What this case isolates

Every non-empty row contains three fields and the same semicolon separator. There are no broken quotes, duplicate headers, or width mismatches. That means the parser can identify the table without deciding what any value is supposed to mean.

Upload the fixture

The delimiter tool should identify semicolon-separated structure.

Review row width

The header and both data rows should all parse to three columns.

Download safe repair

The tool can re-serialize the same fields with commas and UTF-8 output.

Re-check the output

The corrected copy should parse as a comma-separated three-column CSV.

Why the repair is safe

The operation changes separators between already identified fields. It does not infer a price, SKU, product name, or missing value. Proper CSV serialization also quotes a field automatically if it contains a comma, so this is safer than raw Find & Replace.

What would make the same job unsafe?

If one row had a different width or an unclosed quoted field, the parser could no longer prove all field boundaries. CSVFixLab would then block repair instead of treating the delimiter as the only problem.

Decision: safe structural normalization. The original file should still be kept as a backup.

Lab fixture maintained with the CSVFixLab test suite.

Measured worker results

Executed 2026-10-11 using the CSVFixLab worker handler and the downloadable fixture bytes. These are controlled synthetic tests. No customer file or live Shopify import was used.

Automatic normalization. Parsed fields must be identical before and after serialization.

Worker mode: delimiter. The table records the worker's serialization decision. Diagnosis-only tool pages do not offer a repair download button.

On a small screen, scroll the table horizontally to read every column.

RunData recordsColumnsWorker permits serializationReported issues
Original fixture · utf-823Yesdelimiter: The file can be re-serialized using commas if your destination requires comma-separated CSV.
Corrected example · rechecked with Auto23YesNo issues detected by these checks

Corrected fixture

name,price,sku
Blue Shirt,19.99,SKU-001
Red Shirt,24.50,SKU-002

Download corrected example · Download complete measured reports

Fixture identity and test scope

Original SHA-256: 80ff86f2848e440ce8ff25df96a9699607075bb27870a1ff6e12fb509b958744

Corrected SHA-256: b69deebfddf7de4214190a0cfa1817252fa9e4bd0e10689e2fe2bbc7f5295c1a

Node v24.19.0; actual worker handler with File-compatible byte input; no Shopify live import. Record numbers refer to parsed CSV records, including the header, rather than physical lines. The test checks reported errors and, for automatic conversions, equality of the parsed field values. It does not establish compatibility with every importer.