Currently, in the new collection's admin, when the user tries to import a product sheet with a single product ID that does not exist in the account's catalog, the process fails as a whole without either indicating which line/productID has failed or even responding with an assertive message of the origin cause of the issue in the import attempt.

1. Go to an account's /admin/collections/{id}/ and click the import button.

2. Choose the .XLS format and try importing a single line of a productID that currently is not present in the user's catalog .

3. An unspecific error message will be prompted to the user, something like: "Error. Your file was not imported. Try to import this file again"

This process should either point out where the failure has occurred and/or process the other lines and not interrupt the whole attempt.

(Ex: If I try to import 1000 lines and only 1 line is faulty (does not exist) I will not be able to import anything and without even knowing the reason why).

Option A) Check through roughly if all the productIDs in the sheet really do exist. Option B) Use the legacy collections module Option C) Use the API insertion