When receiving the emailed batch import report, it shows errors on certain line numbers. These line numbers never match the line numbers on my spreadsheet. Today's import included about 2600 excel rows, but the report comes back with errors in rows 12000+. I have 4 failed products and have no idea which they are with only "Line 12102-12113: can't be blank". I had other failed items, but was able to find them using additional info given, such as the image URL. Why don't the lines correspond to my spreadsheet? Is there a method to the madness of this numbering system? Please help. Thanks =)
The formatting of the CSV spreadsheet has to match (exactly) to the formatting listed here:
Unless your CSV matches up with the exact column names and accepted values, as outlined in the page above, you will get errors.
If you're working from an export which was generated by another platform, I'd recommend using an app like Excelify, to import the data. The app automatically figures out the formatting of your CSV file and then sorts out the import for you.
Best of luck! :)
Did you ever get a response? I have same exact problem. I don't understand how this can happen if I'm using Shopify's exported file! I just realized that the file that exports from Shopify doesn't even include the column Inventory Qty! I had to add it, SMH. We should be able to export the Shopify file into Excel and make the changes, save it as a .csv file and import it back without issues. There's always a cost and a push to use yet another app! Getting support in chat is a joke, they have ZERO clue and then after 2 hours chatting with no results, they let you know there's a "technical team" they have to forward your issue to who will get back to you by email (never does). What a joke and ripoff of our money. This isn't a free service and we deserve to have immediate support of our issues.
I was just facing the same issue and I might have found a solution for those who might still struggle with this problem in the future.
Shopify's references to the line numbers never match the actual row numbers in our CSVs so basically what you need to do is the following:
This way you can find what products are causing errors when importing.
*Not my solution, just decided to pass it forward*