There is a fast way to define strings (names, product types, error numbers etc.) as non-translatables. This procedure doesn't deal with glossaries but with a text file that has been assigned to collect your non-translatables. You can use this file either for generic non-translatables (like SI units) or if the speed of adding non-translatables is important.
Note that non-translatables in this file will be treated as such in all your projects, in all your languages. If you translate in several languages, this can have disadvantages. In that case, you're advised to use non-translatables glossaries.