PREFLIGHT CHECK
Check UTF-8 encoding and malformed CSV quoting that can trigger Shopify “Illegal quoting on line” errors before import.
Analysis stays in your browser; the file itself is not sent to BlueprintLab.
| Severity | Row | Column | Issue | Value |
|---|
Live service-side state, account-specific settings, remote server reachability and current master data are not asserted. Always prefer the latest official service information.
Check UTF-8 encoding and malformed CSV quoting that can trigger Shopify “Illegal quoting on line” errors.
Handle,Title,Variant Price blue-shirt,"Blue, Shirt",19.99
If Shopify reports `Illegal quoting on line`, editing product names or prices may do nothing because the problem can be CSV encoding or quote structure rather than product content.
This checker verifies UTF-8 and surfaces parser-level issues such as an unclosed quote, unexpected characters after a closing quote, or a quote appearing in the middle of an unquoted field.
A product title such as `Blue, Shirt` is valid CSV when it is written as `"Blue, Shirt"`. The problem is not the comma itself; it is a broken quoting boundary.
That distinction matters because deleting every comma from descriptions is a common but unnecessary workaround.
CSV fields can contain line breaks inside quotes, so a record number and a physical text-editor line number are not always the same thing. Review the flagged record and the surrounding source lines together.
If the file is not UTF-8, fix the encoding first. Shopify’s own troubleshooting guidance calls out both UTF-8 and missing or stray quotes for this import error.
Fixing one malformed field can reveal another later in the file. Re-run the checker until structural errors are gone, then continue to Shopify’s import preview.
Keep the original CSV unchanged and make fixes in a copy so you can compare exactly what changed.