Having Problems Importing? Ask Yourself These Questions:
1.) Is my file using the proper format for cells and columns?
Start with a sample import file if you're not sure. See Getting Started for help getting a sample import file.
2.) Do I have at least a title column, handle column, and one field column, and are all columns populated with data?
All are required for the import to run.
3.) Am I providing the proper handles for my products and are they properly formatted?
Many problems with imports revolve around bad handles. Make sure you're feeding the import good handles to work from.
When initially importing your products into Shopify, Shopify will allow you to import handles with special characters or incorrect formatting and will fix them during their import. Custom Fields does not alter handles on import into the app. This can cause confusion because it will appear like the app is not working correctly. In fact, your handles are bad. Here is an example:
Handle in your original CSV: Alcohol-y-Salud-Pública-en-
Handle stored in Shopify: alcohol-y-salud-
If you took your original CSV and added Custom Field data to it and tried to import it, Custom Fields would reject the bad handles and nothing would be imported.
To fix this problem, export all your products from Shopify and use the corrected handles Shopify assigned, not the handles you have in your original CSV. Import that file into Custom Fields and your data will no longer be rejected and will import as expected.
In general, just make sure you read and follow the rules of handles at all times.
See https://help.shopify.com/themes/customization/collections/special-characters-in-handles for more information. Note, Shopify does allow underscores in handles, although their documentation does not say so.
For detailed information about what characters are allowed and exactly how other characters are handled, see https://stackoverflow.com/questions/37667623/what-characters-are-allowed-in-shopify-product-handles
4.) Could my CSV file have encoding issues?
Make sure your file encoding on your CSV is set to UTF-8. Other formats may import but with increased import times. UTF-8 with BOM produces a file not found error when attempting to import.
5.) Am I trying to import odd characters?
Use only characters in the UTF-8 character set. Support for characters in other sets is untested. Some customers have had good results importing data in other languages besides English.
6.) Are there issues with commas and quotes in my file?
A common problem is that a file will have a single row with a comma or quote in the wrong spot. We recommend using csvlint.io to test your file for issues like these. Sometimes their tool can correct the problem for you and provide a fixed CSV file, but it's not a perfect tool and the corrections sometimes need to be made by hand.
7.) Are you moving data from one store to another? For example, from a live store to a development store?
If so, it's generally simpler to remove the ID column as IDs tend to change when importing products from a different store. Also, you must define all fields that you want to import. For example, if you have a field for related prod
Also, you must define all fields that you want to import. For example, if you have a field for related products in your first store, you must define that field with the same name, type and machine name in the second store.
8.) Do I have extra columns in my CSV?
If you're getting the error "Row count does not match header count." check that the headers in your file (title, ID, customfields["your field"]) are all labelled. If a column does not have both a label and data, remove it from your CSV.