Lab Case · Blocked

Rows with too few and too many CSV fields

The checker can identify the exact structural mismatch but cannot know what missing or extra business data was intended.

Reproducible fixture
Issue: row widthOutcome: repair blockedHeader width: 3

Fixture

name,price,sku
Blue Shirt,19.99,SKU-001
Red Shirt,24.50
Green Shirt,15.00,SKU-003,EXTRA

Expected evidence

RowExpectedFoundMeaning
332One field is absent or a separator is missing.
434An extra delimiter/value exists, or quoting is wrong.

Why CSVFixLab refuses to fill the row

The second data row does not say which field is missing. Even if sku looks like the obvious choice to a human, a generic repair engine cannot safely assume that without source-system knowledge. The fourth row has the opposite problem: deleting EXTRA would also be an unsupported business-data decision.

Run the fixture

Confirm both mismatched rows are listed.

Check nearby quote errors

A malformed quote can produce width mismatches as a secondary symptom.

Correct from source data

Use the originating database or spreadsheet to determine the intended values.

Re-run the checker

The corrected file should have the same field count on every non-empty row.

Decision: diagnosis is safe; automatic reconstruction is not.

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.

Manual example using the explicitly defined synthetic schema: add SKU-002 and remove the deliberately inserted EXTRA field. This is not an automatic inference.

Worker mode: repair. 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-833Nocolumn-count (record 3): Expected 3 columns but found 2. / column-count (record 4): Expected 3 columns but found 4.
Corrected example · rechecked with Auto33YesNo issues detected by these checks

Corrected fixture

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

Download corrected example · Download complete measured reports

Fixture identity and test scope

Original SHA-256: 5d0e6b2a1998bfc1eab47f847a20885e64e6300953d0a8f0460b8b47c413ebe2

Corrected SHA-256: 725aa897245627e021efb309404747b94804a2ed696069d5c293cd74abdea141

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.