How to troubleshoot CSV Import Errors

In this article

The Import Portal checks your file and rows before you confirm an import. File problems must be corrected before you can review rows. If only some rows need a correction, you can import the ready records and fix the remaining rows separately.

Start with the section that matches the message you see. Keep your original file until you have checked the import result.

The file must use UTF-8

If the upload says This file cannot be imported. CSV files must use UTF-8 text., save a new copy using UTF-8 CSV.

The current UTF-8 file error

UTF-8 keeps accented letters and special characters readable. Changing the filename extension to .csv does not change its encoding. Check that names look right in your spreadsheet before saving the new copy.

Check the Preview column on the Map fields screen. If accented letters appear garbled (such as Café  instead of Café ), fix the text in your spreadsheet first so characters display correctly, then export a fresh copy using UTF-8 encoding.

Click Choose another to select the corrected file.

Choose a corrected UTF-8 file

A required column is not mapped

In Map fields, look for the Required badge in the YoPrint field column. Skipped means a CSV column has not been assigned to that YoPrint field. Review rows stays disabled while any required field is unmapped. You can map a differently named column header without renaming the header in your file. Mapping every required field enables Review rows, provided no columns have conflicting assignments.

Required mapping and row values by import type

  • Simple Products: Only Title must be mapped to proceed. Brand and Supplier Code are optional in mapping, though their values matter for matching existing products. New products also require a valid price during row validation.
  • Variant Products: Only Title must be mapped to proceed. Brand and Supplier Style Code are optional in mapping, though their values matter for matching existing products. During row validation, new products require a valid price, and variants must have matching ID and label pairs for size, color, or both.
  • Customers: Both Customer Name and Tax Exempt must be mapped.
  • Vendors: Vendor Name.

This example uses item_name  for product names instead of title .

  1. Open the dropdown beside Title.

    Open the required Title field’s column selector

  2. Choose item_name, the column containing the product names.

    Map the item_name CSV column to Title

Check the Preview value to confirm that the correct data is mapped. Our example now shows Café ceramic mug under Title.

  1. Click Review rows.

    Continue after the required column is mapped

Use the same approach for other fields: match names to names, prices to prices, and contact details to their corresponding fields. The current template’s headers match automatically.

A row is missing a required value

A mapped column can still contain an empty cell. In Review rows, a row with a problem shows Needs fix, and the affected field displays the reason. In this example, the blank product title shows The title field is required.

A missing title beside a valid product row

Click 1 need fix to show the affected row. The count changes with your file.

Filter the review to rows that need a correction

Fill the required value in your CSV. For this row, enter Enamel lapel pin in the title  column. Keep the other details on the same row, save the corrected CSV, and upload it again through the same import type.

If you want to import the ready rows first, follow Import ready rows and retry the rest.

A product appears more than once

When two simple-product rows have the same matching identity, the review says This product appears more than once. Keep one row for each product. YoPrint flags both rows because it cannot guess which row has the intended details. You cannot delete rows inside the Import Portal.

Two rows with the same product identity

Check Brand, Title and Supplier Code together. In this file, both rows describe the same Embroidered patch with supplier code MT-PATCH-01. Keep one complete row for that product and remove the duplicate row from your file. If the rows represent two distinct products, give each product a distinct Title or Supplier Code in your CSV before uploading. Matching normalizes letter case and spacing, and setting an identity that matches another saved product updates that product instead.

For a variant file, keep one row for each size and color combination within a product. Different sizes or colors belong on separate rows. See the variant template columns when checking those values.

Save the corrected file as UTF-8 CSV and upload it again. If all rows in your file need a correction, or match existing products while Skip existing products is enabled, the portal says Nothing can be imported. Click Back to review to return to the review screen and inspect the row errors. From there, you can click Cancel and select Discard import to exit without importing.

No rows are ready while both products are duplicates

Import ready rows and retry the rest

You can import ready rows while leaving rows that need a correction for later. Review the import and skip counts before confirming.

  1. Click Review.

    Review a file with one ready product and one row needing a fix

  2. Click Download skipped rows CSV to keep a file containing the rows that will be left out.

    Download the rows that need a correction

Save skipped rows before confirming

Click Download skipped rows CSV on this confirmation screen before confirming the import. In this preflight-skipped result, the final completion screen offers only Download original, which contains the full unseparated file. The downloaded skipped rows CSV contains the mapped review data without error descriptions, so note the specific error messages in the review before continuing.

  1. Click Import 1 simple product. The button’s count reflects the records ready to import.

    Import the valid product while skipping the row with no title

Partial import completed shows how many records imported and how many did not. Read Records not imported for the row and its issue. Check the Status and Issue columns to distinguish intentional skips from validation errors:

  • Rows marked Already exists were skipped intentionally because matching records exist in YoPrint.
  • Rows marked Needs review (or displaying a validation error such as The title field is required.) failed validation and must be corrected before reimporting.

In this example, Linen pencil pouch imported, while the pin row still needs a title.

The partial result lists the skipped row and its issue

Correct the skipped rows in the downloaded file, then save it as UTF-8 CSV. Upload that corrected file through the same import type and check its mappings. Use only the remaining rows so you do not repeat products or customers that already imported.

  1. Click Review after checking the corrected rows. The pin now has its title and is ready to create.

    Review the corrected Enamel lapel pin row

  2. Click Import 1 simple product to confirm the corrected row.

    Confirm the corrected product

Import complete confirms that the remaining record imported.

The corrected product imported successfully

Click Done to close the summary dialog. Close or switch away from the Import Portal tab to return to YoPrint (or click Back to YoPrint at the top right of the portal). Above the Products table in YoPrint, click Refresh to display your imported products.

Customers with a matching name are marked Already exists and skipped. Products can update an existing match or be skipped with Skip existing products. Read the result and intended action before importing again. See Import Customers Using CSV or Edit Products Using CSV for those choices.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.