The journey continues...
Stedi overs 4 pillar features. Buckets, Triggers, Guides, Maps
The buckets and triggers is what hooked me. The guides and maps is what has been saving me. You see, EDI is a confusing btch. And trying to map out my json to those EDI files is a nightmare. Well, would be a nightmare without Stedi. Their UI makes it simple and easy to do. I'm able to now enjoy life again. Smile, laugh, love. All because of what Stedi is doing to shake up the EDI world.
In Stedi We Trust.
DISCLAIMER: I am not affiliated with Stedi in any way. Not financially nor socially, only emotionally because I love their product that much.
*START*VALUE1*10.00*BOB*DOLE*100*ADDRESS*STREET*
Where the double asterisk is where a blank value is.
However, it is a standard. It is knowable. You can get the ANSI X12 standard for whatever industry you're in and implement this.
And let's be clear, you still have to do the dirty work with these guys. You still have to map values to fields, which is the hard part of working with the format. Once you have that, you can knock this together fairly simply.
It's difficult to use the method you're describing to write a transaction like this, particularly when the receiver's system can fall over due to a single character out of place: https://www.verizon.com/business/support/vec/onlinehelp/dam/...
(I'm the CEO of Stedi)
So, you know, Healthcare billing information. It's tedious, but the worst part is the mapping from your own data source to the format. And you don't help with that part.
Unless you can host this locally this seems like a deal breaker in many industries (healthcare, insurance and perhaps others)
Not sure which sweet spot they want to hit with this
