Sergiy, the problem with that approach is that it works for synonyms but not for typos in the correct character string. For example:

ABC Movres

A.B.C Movers

Authentic British Cars Movers

Authentic British Car Movers

Authntic British Cars Movers

Auth. Brit. Car Movers

Auth Br Car Moevrs

I was about to say you can't anticipate typos, but if you are willing to pay the price in disk space, it's possible to generate a routine that will generate the typo patterns I handle with StringsClose. Obviously, the larger the string, the more rows of acceptable combinations will be produced. But with some limitations on what is considered acceptable, it might be workable.

There would need to be additional synonym capability to associate the 'ABC Movers' with 'Authentic British Car Movers' so you could handle typos against the longer string and against abbreviated strings such as 'Auth Br Car Movres'. There is no taking some of the manual work out of it, and it will always be imperfect. Some edge case you didn't anticipate will always slip through the cracks. But when it's running, it's probably going to be the fastest of many imperfect solutions.