Carriers can administer EDI through:
When you’re trying to figure out a solution for EDI, getting a stellar recommendation from a colleague in the transportation industry is fantastic. But be aware: You might actually need a little bit more data before you pull the trigger. Have you thought about which EDI management model is the best fit for your company? We’ll highlight and then review the positives and negatives of all four.
EDI can be a real bear to manage, especially if you’ve chosen a solution that doesn’t play to your company’s strengths. These distinct EDI management models can be broken out into two categories:
you contract with a third party to handle your company’s EDI. It works well for carriers that don’t have the expertise or the headcount required for the self-service models.
On the downside, transportation companies that do EDI as a managed service lose autonomy, which might make it harder to get work done on their timeline or to resolve technical problems that arise with trading partners. This option also tends to be the costliest of the four models.
The first EDI self-service model is custom development. Building your own EDI solution often starts out as a great idea when your company has development capacity. After all, using in-house programmers is a soft cost.
What trips most carriers up is the amount of maintenance and ongoing dev time required by home-grown EDI solutions. Custom development may look straightforward when you’re dealing with one partner and a few connections, but scaling is a real problem.
The next self-service model, on-premise software, has traditionally been used by transportation companies for decades. By bringing on or contracting with highly specialized EDI experts, carriers could build and manage their connections with local installations of EDI software.
Although the acquisition costs for many installed EDI products are lower today, ownership costs could still be relatively high. Usability, for example, is a big deal when you have to train new employees on dense, technical software.
Software as a Service or SaaS, the last self-service model, takes EDI software to the cloud where maintenance and updates are done by the EDI provider. EDI products using a SaaS model can be accessed on the web … from anywhere.
SaaS is generally easier to use and narrower in focus than on-premise solutions. For example, most SaaS EDI products won’t come embedded as a module to your transportation management system. Critics of the SaaS model often prefer owning the rights to EDI software over renting it — so to speak — through a recurring monthly fee.
Well, there you have it. Now that you know a little bit more about each of the four EDI management models, which do you think is right for your company?
I hope I’ve helped you figure it out!
Cut EDI on-boarding time in half with point-and-click, drag-and-drop building tools
Avoid unnecessary errors by customizing business rules to meet your requirements
Confirm partner connections work in minutes before pushing them live
Know immediately when message errors occur and how to fix them
Hotline Freight, a Wisconsin-based LTL, uses Babelway’s visual field mapping to shave months from EDI on-boarding.
Plus, the data interoperability problems that before plagued the company’s exchanges vanished.
– Cory Kucera, IT Administrator, Hotline Freight
Before goods are delivered
After goods are delivered
So what makes Babelway different from other EDI providers? In a word, control. See how far you can go on your own.