We’ve been doing EDI for a long time. Like many others, I sorta fell into EDI. I was working at GM in the early 90s and “EDI” consisted of flat files exchanged with the MRPII system. Although it was a rudimentary system, I learned quickly about supporting the business via ASNs, electronic pull requests, and many other automotive documents. Since those early days, we have went on to support numerous X12 and EDIFACT implementations. Typically we rely on an outside translator/VAN to route the files, then we handle the complexities of integrating with the ERP system.

Electronic Data Interchange (EDI) means different things to different people. We pride ourselves on cutting through the complexities and focusing on the results. Our goal is to get you saving time and money as soon as possible.

EDI is daunting. EDI used to be implemented because a trading partner was requiring it. If you wanted to be a Walmart vendor, you needed to have EDI. This need was quickly met by using web-based EDI. Unfortunately, this often means that you just doubled your workload. Enter the data in the ERP, then enter it in the website…then hoping your data accuracy was up to par. This week we turned on an EDI system for a customer that received 70+ Walmart orders on the first day. The time savings are immense. What used to be done because it was “required” is now just common sense.

We can help. You might be surprised how quick the payback is on an EDI project.