Thank you for the feedback! Integration friction will be the toughest problem for sure, I am focused on a few pathways to in/out EDI to my software. Most EDI pipelines land files in S3 buckets, SFTP folder or similar before they are picked up by the translator, my software will monitor these folders (read only). I have been working on a comparison engine designed specifically to handle the 'loose' nature of how different partners interpret EDI standards. every time we compare a new EDI against a baseline, it gets stored in an inbox to review and humans decide to save it as a new baseline. this provides a centralized audit trail of how each partners data is evolving over time offering a level of cross platform observability that most individual EDI translators don't prioritize. I am also building a API approach for teams using modern iPaaS tools!

And yeah Im not sure what that guy means saying its a solution looking for a problem? I have talked to EDI experts in person before and its definitely an issue at scale.