Retail EDI

Gap Analysis is an integral part of any EDI (Electronic Data Interchange) implementation, as well as any replacement to a company's existing software base. Analysts need to identify points where there is a difference between the existing solution and the replacement software.

When it comes to EDI, there are identification codes / qualifiers that are frequently either not present or do not match existing codes already in use with a particular document or perhaps data currently sent that a “Trading Partner” (EDI term for a supplier / customer / etc) is not making use of or perhaps data that a Trading Partner needs that's not currently being sent with your existing solution. Or perhaps it's the other way around and you're the one receiving the data. There's also the issue of which EDI transaction set to use to represent your document and also which EDI standard set to use. If you're located in Europe, you most likely will use the EDIFACT ( United Nations/Electronic Data Interchange For Administration, Commerce and Transport ) standards; in the United States, you'll most likely use X12 standards, but if you are located in either one and your trading partner is in another, you may need to support both standards. And then, there's which version of the standards you will use and if your industry has its own guidelines and/or government regulations, you'll want to investigate that as well. All these are valid questions and need to be addressed.