This blog post is the third part of a series highlighting the best practices for EDI-as-a-Service in planning and evaluation.
As past entries in this series pointed out, determining if EDI-as-a-Service is right for your business, and which provider solution makes the most sense, requires some careful consideration. Two very important caveats are to be sure to choose a solution based on requirements instead of provider capabilities, and approach your selection with a broadened view of total cost of ownership (TCO).
Pick EDI-as-a-Service for Requirements, Not Provider Capabilities
When EDI-as-a-Service offerings initially became available, “on-network translation” were the provided capabilities which hosted on Value Added Networks (VANs). Data format flexibility was minimal due to limited EDI translation options, where direct integration with enterprise applications and data resources could be offered, but came with a large price tag for the customization. Continue reading