The current PIM import process automatically strips trailing space characters from all fields before validating the import. This causes frustrating behavior when a category is named (accidentally or otherwise) with a trailing space character in it.

The import validation strips the space characters from the file, which causes the import to fail with the "Category Name not found" error. The PIM admin then has no good way of identifying that the trailing space character is what is causing the issue since the error does not specify which category is the one not found.

In order to avoid this, I would propose two potential solutions:

A) Improve the category import validation to specify which category name is the one not found

B) Add a system setting for the import process to accept trailing space characters as-is and not automatically remove them from the file before performing the validation