For optimum performance, the EDI translation software should be on the same platform as the business applications. Levels of mapper implementation or integration vary greatly from translator to translator. Communications software can be a module to the translator, a programming tool that enables communication protocols to be written, or a separate application. If you upload a word processing file and the recipient tries to open it in a database program, the result is a mess of characters instead of the expected information. Attempting to do EDI without translation runs a great risk of transmitting data that the intended recipient will not be able to read.
Many organizations use different business applications on their computers.
The translator ensures that the data sent can be converted into a format that the receiving organization can use. There are a few fundamental differences between a customer EDI translator and one that comes from a software company. A custom translator is very rigid and is designed for use with one organizational partner, using limited transaction sets. Most commercial EDI translators are designed for transacting with organizations with a multitude of documents. A customer translator is difficult to update.