PREFLIGHT CHECK
Read a Mercari Shops product_import_result CSV and group common import errors by row.
🔒 Analysis runs in your browser. The CSV file itself is not uploaded to BlueprintLab.
| Severity | Row | Column | Issue | Value |
|---|
The tool does not claim to verify live service-side master data, account-specific state, or network reachability that cannot be established reliably in-browser. The service’s own validation remains authoritative.
Read a Mercari Shops product_import_result CSV and group common import errors by row.
商品名,エラー内容 サンプル商品,商品名が130文字を超えています
After a Mercari Shops bulk import, `product_import_result` can contain several different failure messages at once. This analyzer groups those messages into useful buckets such as product-name length, description length, half-width spaces, brand IDs, shipping fields, and images.
The goal is not just to count failed rows. It is to show which causes are repeated so you can choose the fastest fix.
The analyzer looks for columns named like error, reason, message, or result. If none are found, it scans all cells for typical failure wording.
That makes it more resilient to result-file layout changes than a parser that assumes the error is always in one fixed column.
If the same half-width-space issue appears on 100 rows, fixing the CSV-generation process is faster than editing 100 products individually. If only one row exceeds the product-name limit, that is a row-specific correction.
This tool classifies error text. It does not prove that a brand ID or shipping code exists in the current Mercari Shops master; verify live master values separately.
Do not treat the result CSV as the file to re-upload. Use it to understand the cause, fix the original product CSV, preflight the corrected file, then upload again and inspect the next result.
That “read result → fix source → rerun” loop is much easier to manage when the failure list is large.