Chris Reddick (President and CEO at Clarity Ventures) and Ron Halversen (Vice-President of Sales and Marketing at Clarity) finish their discussion about EDIs and what to look for in a developer.

Part 4 of a 4-part series (return to Part 3)

RON: I'm going to have Chris go into the actual hard detail, so I'll do it at the high-level layman's terms. If I'm going to dump an order into a directory and into this SFTP directory, and they pick up this file and they go to process it, this inbound file has a header. "This is an email, this is an order, this is a tracking status, this is a purchase order to replenish stock, this is an 897 acknowledgment that I received your file." This works for tradiational eCommerce as well as B2B buyers groups.  

Whatever it is, it's almost like the header information of each file type, and each file type has a format and that lets the system know what to expect when it engages that file. I know I've probably said that not very technically, but do you want to talk specifically about the types and some of the most common numbers that we use?

what is hipaa

CHRIS: This is something that we can show some different screenshots of some of the workflows, and we'll also reference some sites that have really detailed, comprehensive lists of per-industry workflows. We really recommend that you take a look at this, because what we've found whenever we're working with clients is, a lot of times they just don't know what's possible with X12, especially with automating specific nuances. Here we're showing a standard set of formats, document types.  

One of the things that I wanted to do, Ron, is just walk the audience through a specific example or two, and, to that end, one of the typical workflows is within the retail industry or buying group model. Within the industry, you will typically see things like a price catalog first. You've got to get the catalog itself, and that's going to be an 832—there may be more to this that makes sense in your particular case. Then we'll typically get an order which is an 850, an order change, the 860, We can keep going down this list, but you can see the picture here just shows how this goes.

what is hipaa

CHRIS: Most folks are pretty familiar with the fact that you can basically place an order and then get an order response and maybe even the 856 with the delivery. But the thing that I think is interesting is, a lot of folks don't necessarily know about remittance advice or a sales report or inventory report. These are some additional document types that you can even see that the receiving advice in the inventory report are the same document type in the sales report, but it's used for different things.  
 
That's what we want you to take away from this particular example. And then just to walk through a few more. If you go to the auto industry, that's a similar thing but with different specifics. We're showing the image on the screen here, and you can see that you have this idea of delivery instructions, a daily call off, a shipping notification, receiving advice than an invoice, a credit note, and then payment advice. It’s really powerful to be able to use these in traditional eCommerce and buyers group platforms

what is hipaa

CHRIS: What you'll see is they're the same documents in many cases, like the 810 is used twice in this auto example, but it's got a different set of criteria in the data and that drives a different workflow. So it's not just the different document types, but it's actually the data or the types or flags within the record itself. This can also drive some really powerful workflows to automate the process internally for you.  

There are a myriad of these examples, including many for group buyers. These are just two we wanted you to see. You can see that we can not only take advantage of some document types that you haven't seen before, but also that the same document type itself can be used for multiple phases of the process.  
 
RON: Yeah, and I don't remember how many files, but it surprised me. I always thought it was just orders, status purchase orders, things like that. But the first time I went out to the X12 site and started looking at different file formats—and I'm going to pop the URL up on the screen here—I was surprised at how many different document types there are.  

Even if you don't really know exactly what's available to you, if you just go to this site and just look through the different types and read the different types of documents and what they can do, it'll give you an idea that—and Chris mentioned it before when you started talking about split-shipping and drop shipping and you started getting into some of the little more complex things like purchase groups—EDI I can handle all of that and has for decades. You can just imagine that any of the different types of buying group or online eCommerce, custom bulk purchasing, split-order drop ship, refill inventory counts, multiple warehouse locations—all of that is very easily done. 

We say flat file, so everybody thinks it's simple, but it can still be extremely secure. It can be near real-time. You can set up pingers that auto notify like with a VAN that there's a file, so go pick it up. So now we're only waiting if you seconds. Even though it's flat file and it's file exchange, where normally on most EDI in eCommerce you're setting up and say, “Oh, go scan every five or 15 minutes. And if a file comes in part, process it.” Sometimes there can be a delay of 15 to 30 minutes before something gets processed. 

When you start introducing VANs and things like that, not only do you get additional security, you can start getting the notifications to go pick things up immediately. So it might only be a few-second delay. We call that near real-time. EDI commerce is definitely a powerful option for you.  

The next one we're going to look at, we'll talk about the notification system. And I just briefly touched on that, but I want you to dive in, Chris, to the different types of notifications and why we would need notifications? I mean, if I dump a file off and at least one notification that it was received, is there really anything else that I need to know?

what is hipaa

CHRIS: Good question. One of the interesting things here is that you can see that this industry has evolved just this space overall. And it's really become capable of doing literally most if not everything that you see with other API formats. And although it's not mechanically true that a car can become an airplane in the same way EDI isn't going to become an API. You know, there are certain limitations, but I guess you can put wings on to a car, can't you? If you need to.  

The big thing I would say without getting into super, super-detailed edge cases would be being able to get mechanical acknowledgment of the documents sent and receipt of documents. If you've sent something and it's been received, then you're a recipient of a document. This allows this real-time lightweight communication like a PUB/SUB (publish and) or a service bus. Mechanically within the organization or eCommerce platform, these acknowledgments around purchase order acknowledgment, a shipment notice, possibly a warehouse transfer notification, things like that, where this is going to be driven off of different events so you can have an event-driven workflow that's going to occur.  
 
By properly setting this up with the notifications, you can basically allow the computer systems, whether it's a VAN or if it's an AS2 or whatever mechanism is going to allow this communication to happen within the EDI network, then you're able to allow your systems to follow these rules and take advantage of these different notifications to communicate with each other where it would otherwise be people physically communicating in some form right.  

There can be an order placed online for a store that is in the southeast region of the country. But the item is only available in the warehouse, that's in the northwest part of the country. And so there needs to be a transfer, and maybe it's a weekly transfer that occurs. That's just part of the fulfillment network that, hey, if anything needs to go from northwest to southeast every week, we're going to do that, especially if it's a large order or associated with a buyers group.
 
And so someone places this order online, and little do they know that all they're seeing is the lead time saying their item will be in the store in a week. But what happens behind the scenes? Well, the order gets credited to the store that’s close to the person that's buying online. They're going to pick it up in the store and that store gets the credit within the accounting system. But there's also a transfer of the inventory, possibly from the warehouse that's in the northwest down to the warehouse that's in the southeast.  

And let's say for whatever reason, that person cancels their order after the item has already been transferred. Okay, well, now what are you going to do? You have all these systems playing together. And so you really want to take advantage of notifications because we need to account for the fact that the northwest warehouse transferred the inventory to the southeast warehouse. So now it's in the inventory in the southeast warehouse.  

We also have an order cancelation, so we need to deal with that, and we need to make sure that the store that was getting credit for the order doesn't get credit for it. And on and on we go. The notifications can really be seen as sort of an automation if we're watching them properly and executing against them properly, they're like essentially a eCommerce workflow that we can fire off from these notifications.  
 
I would just say whenever you're looking for a vendor and you're considering your options, make sure that you look for someone who has experience in your particular area. And if you're going to be leveraging some specific details like you're going to be working with EDI, with an eCommerce, for example, or the health care industry, HIPAA websites, for example, it really does make sense to work with someone who has done this and been there and done that before in your particular space. And they can bring in these different capabilities and experiences from successfully implementing what is possible with EDI.  

Don't be afraid to consider really looking at it as well as a long-term investment. A lot of times what we see with clients, even those looking for a group buying platform, is they will just halfway get started into something like EDI thinking that it's just this one thing that we need and then they'll still be using it five-to-ten years later. We really want to encourage you to look at it as a potential long-term investment, even if that doesn't end up being the case, look at it as an investment that might go for five-to-ten years, and make sure that you put the planning in upfront so that you can execute really well. And just be aware of some of the potential opportunities and potential risks going into it.  

I think that's a great segue into our next talks, as we're going to be helping really get into the weeds on those in some of our next discussions. So with that, that's it for me.  
 
RON: For the audience, thanks again for attending today. If you enjoyed today's webinar, please smash that like button, subscribe to the channel. As a reminder, this EDI Buying Group webinar today was number three in a series of 12 webinars about buying groups. So make sure to check the channel, check the playlists for buying groups in all the other chapters.  
 
I'll also try to directly link to all the other videos in this series in the description. So look down in description below for the URLs that Chris talked about, the different formats, the different websites, and then at the very bottom of the description, all the other chapters. So thanks again.  
 
CHRIS: Thanks, Ron.  
 
RON: Appreciate ya. Thanks, Chris.  
 
CHRIS: Thanks, everyone. Bye for now.