Name: Integrating NetSuite and EDI
Uploaded: 2025-06-04T18:16:08.496Z
Duration: 1 h 1 min 16 s
Description: Integrating NetSuite and EDI

Transcript for "Integrating NetSuite and EDI": Hi, everybody. We're just gonna give it a few seconds here for folks to log in, and then we'll get started. Okay. Let's go ahead and get started. Looks like we're getting critical mass here. So, welcome to the ins and outs of integrating NetSuite and EDI, the sixth webinar in our series our deep series of NetSuite integration. My name is Rico Andrade. I am the general manager of commercial here at Celigo, responsible for the channel, and alliances team. And, we're gonna be joined today by Chris Beidelman, our director of solution architecture, and Tim Heater, solution consultant. And we're gonna go into all the details of EDI and, and how interfaces with NetSuite. Just a couple housekeeping items today. This session is being recorded, so we are going to send a recording afterwards in the presentation. It is also intended to be an interactive session, so please, feel free to ask questions. There's a q and a session. There's a chat. So, welcome to, you know, ask questions over there. We'd love to hear where people are calling in from and, you know, but but we're gonna get to hopefully, we'll we'll have time to get through everything today. But, quick overview of the agenda, you know, we're gonna do just a very quick introduction, and then I'm gonna pass off to the experts, who are truly deep experts, in this particular topic. Once we pass it on, you know, we're gonna start with some of the basics of EDI. This may be a bit of EDI one zero one for, some of you folks, but we're gonna quickly get into the the details, in in in, quite a bit of depth. So please stick around, from that context, and, you know, we'll we'll we'll provide a pretty good overview. We'll talk about the standard and advanced use cases, you know, some of the things that we see, some of the gotchas, you know, common things that you should have, be thinking about. And then we're gonna show you actually how this, interfaces on our platform so you get a sense of, you know, how some of these issues might be resolved, in practice. As always, a lot of the themes, for this session is flexibility, scalability, and efficiency. These are all things that are so important today, particularly around, you know, when in agility is so important, in this day and age, you know, as people are having to, you know, move their operations and supply chains and adapt very quickly and, maximize, their efficiency. And so, those are gonna be key components in terms of what what we, you know, put together today. And this session is gonna be a little bit different from the previous ones for those of you who've been part of these webinars previously. I usually spend a little bit more time in the beginning kind of, as an overview in terms of how, Celigo, actually approaches integration. With EDI, you know, there is a a totally different approach that we're gonna talk about, you know, because we launched our own product with the b to b EDI manager. This is in response to some of the big challenges that, you know, we hear from, the monolithic vendors, in terms of control, customer service, you know, time to projects. And so as you're gonna see, it provides you with a lot more of a typical, what looks like an application to application, experience, but it's more of a, you know, you're you can connect your training partners that way. And, you'll note that we're actively looking for partners too who are, wanting to expand their EDI practices and and maybe, you know, have a little bit more control of their own destiny with the EDI services. So we're gonna talk a little bit about that. But as always, you know, why is it that, we are talking about this? And part of the reason, you know, we keep, coming back to some of these subjects is that, you know, Celigo not only is one of the now leading, players, in the iPaaS space. We just, you know, we're we're number one on g two, you know, going on to six quarters now. We last week, we were named visionary in the Gartner Magic Quadrant. But, we also have an incredible foothold with thousands of customers, in the ecommerce, commerce, retail, wholesale distribution, supply chain manufacturing, anyone anything with products, you know, that we've really found a strong foothold, for those organizations. And so we've developed a wealth of expertise that, you know, we're we're aiming to share in these, you know, long, detailed webinars that, a lot of you have been joining us month to month. So we're gonna go through that. And at the end, we'll show you some additional resources including, the rest of the series that we've scheduled for the rest of the year and what we're gonna go over. So with that, I want to first to go ahead and jump into, the main, event. And, before we do that, I wanna get just a quick sense of who is in the audience here, so that it's gonna set us up for a conversation with Chris Vitaman. So we're gonna run a quick poll, and just to understand where everyone is at. So So you could take a couple more seconds here, on the polls. Very questions, being, you know, how familiar you with EDI. Very familiar already using, somewhat familiar, and I'm, you know, I'm here to learn more. Fairly mixed. Looks that looks like there's a good number of you who are very familiar. Some of you somewhat familiar, a good number just wanna learn more. So you're in a good place here, to be able to do that. So, and more votes coming in. So okay. So let's get you learning more then. I will stop sharing this. And, let me go back to the presentation and pass it on to Chris. Thank you, Chris. You bet. Thanks, Rico. Good afternoon. Good evening for some of you. My name is Chris Beidleman. I'm the director of solution architects here at Celigo, part of our professional services group, and I've been at Celigo for, I think, actually, just hit my fourteen years here. So I've been at the company quite a long time, but certainly been doing supply chain and EDI for many more decades than I care to admit. So today, I wanna just kinda give you sort of an overview of of EDI and and sort of where Celigo fits into that network. Now what we're seeing and with, obviously, Celigo being iPaaS and and connecting to lots of different types of business applications in there, and b two b just being one of those, many different integrations, we're seeing a a shift from maybe traditional EDI providers because they're sort of one trick ponies. They can handle EDI, but a lot of trading partners are now starting to migrate towards API integrations. For example, Amazon Vendor Central now has SP APIs to do the transactions rather than the EDI. So it really does fit for an iPaaS to be able to handle all the different any type of integrations you may have, both for your b to b partners as well as your b to c. And so today, of course, we're gonna focus on that b to b ecosystem. And what we like to also sort of emphasize here is, you know, obviously, we have NetSuite in the middle here because we like to have NetSuite as that sort of hub. You have the information on the inventory, on the orders, the allocations, all those types of things that occur because, let's face it, most people are multichannel. Or if you're a buyer, you you have a lot of network of different vendors. So we're gonna kinda talk about all those different sort of aspects of that. And, you know, as Rico mentioned, we have launched a product called b two b manager, but we've been doing EDI for good ten years now, and have a lot of different trading partners we commonly integrate with. And, Tim, when he comes on to to demo, we're digging that a bit more. But our network of trading partners that we're enabled is growing all the time. Every two weeks, we're launching more and more of them, on as needed basis and the most common ones. So we're really pleased about the adoption and growth that we've been seeing. So let's take a step back and just kind of talk about EDI and sort of the the basics here. So what is EDI? Well, let me let me just kinda take it down to sort of the basics. This is electronic data interchange. It's essentially the business documents that trading partners exchange, purchase orders, invoices, and such. And this is a technology that's been around since the seventies, but it was sort of adopted and ratified in the eighties. So we're talking 40 year old technology that was based on a mainframe format, and it's still utilized today. And and you kinda go, wow. Why are we still using it? Well, it's the adoption is pretty there and still sort of the lowest common denominator. So it is something that, is used by literally thousands of different trading partners out there, and it's not going anywhere. So who utilizes it, as I mentioned, is a lot of the different companies out there. Anyone who's doing a lot of the back end trading, buying, selling, of of goods in the b two b world still utilizing this. And so it's used a lot in retail. We all see it in health care and logistics companies too. So they're still utilizing this technology. And there are some standards out there. Here in North America, we use what's called a n c x 12. So x 12 is is the standard, and most of the rest of the world, including Europe and Australia, uses edifact, which is a similar thing. It was a ratified, format, by the UN. And, though, some some of the ones in Europe still utilize x 12, but that doesn't really necessarily matter. But it's still a machine based language, and, I wanna kind of in a way, actually, I wanna scare you because this is what EDI looks like. On the left is the x 12 and edit facts on the right. Unlike maybe JSON or XML you've seen before, you can kinda read it and kinda understand sort of human readable exactly what these fields are. But if you look at these, you it just looks like a bunch of numbers and symbols out there. And each segment, which is the lines, designate a different position. If you see an asterisk, that's a column deliminator. So it is really hard to be able to distinguish what is this document seeing if you look at it in raw EDI format. So this is not human readable. It's his only machine. So that's sort of where, this legal comes in and our ability to to be able to turn this, gobbly goop into something that can be utilized by other other systems. So, again, this is where iPaaS really does shine in its ability to be able to connect any to any including EDI. So let's get into a little bit about how and why and what happens with EDI. So as I mentioned before, this is really just business documents passing to to trading partners. So either you're a buyer persona, you're buying goods from your different suppliers, You send out a purchase order saying I wanna buy this. They receive it. They tell you they can, ship it out. Then they'll pick back and ship it either through common carrier or maybe a less than a truckload or LTL shipment on a pallet and and send it back, and then we exchange these datas. Well, you know, in in EDI world, well, this is handled can be handled, still manually. You can still get emailed the the purchase order. And if you only get one or two orders a month, this still might be the most cost effective, approach. But what we're seeing also is because of the provenance of a lot of orders coming through, people wanna be able to process this and automate this and kinda take the hands off and and let the the machines or the automation handle at least the order intake and and be able to do that exchange. So this is where, you know, the so they go and and helps to be able to automate this and and be able to deal with the EDI so you don't have to see all that ugly stuff I just showed you on the previous screen. So this is really what we're talking about. It's just automating these business processes that you might be familiar with. Now as I mentioned, there's different personas or roles that you may have in this trading when when we're talking to you about trading partners. So trading partner, you're either a seller, meaning you have goods that a maybe a large box retailer wants. You're you're selling to Macy's or Amazon, Vendor Central, or Best Buy to be able to sell them your goods. They buy it from you at wholesale, and then they're able to resell them, on their web stores or in their in store, like a Walmart or Costco. So that's the one scenario. And you're gonna be shipping to, you know, either a distribution center or to directly to a store or possibly, they may have your goods on their website. So target.com. You're gonna get a order from Target to drop ship it directly to that customer, on on their behalf. So there's different relationships you have as a seller. And so within EDI handles all these different scenarios, but as we'll get into, each one has its own unique, problems associated with it. But on the other hand, you might be a buyer. So now you are the one sending out from NetSuite the purchase order. You create the purchase orders. You send them out, and they're the ones that are gonna be, shipping either your goods to your stores or to you. So, again, it's just the direction of what we call the inbound or outbound purchase orders. And so just the direction is important on how the EDI flows. So I mean, we're asking about that or even, you know, if you're trying to evaluate what is the direction things need to flow, then that's important. And then the other major component of what we commonly see is, either you're if you are a supplier, maybe you're having a third party logistics company actually be your warehouse, and so they're shipping it out. Or you're multinational, and so you have different warehouses that can fulfill these orders or drop ship them. And so they have a whole different set of different types of DEI transactions that might go on, with with a third party logistics. And even within the logistics world, there's a whole of different thing if you're, you know, managing carriers and and sending out orders and this whole 200 series of of different transaction types. So, again, within the world the EDI world, there's lots of different transactions. And, again, business documents that can be exchanged between trading partners. So it just depends on where you fit. Alright. So why does EDI matter? Well, you know, again, there's lots of different, things why this integration is important. As I mentioned, you can now parse and translate that EDI into usable formats for lots of different systems. We'll be able to syndicate it out to where it needs to go. You can also speed up the order intake of these orders. So now you don't have to wait for the PO, have somebody type it in to NetSuite and and create the sales order. We can automatically do that for you. And then, also, as we all know, if you have humans entering orders, errors can occur. So now, you know, we eliminate a lot of those errors and can also include different business rules depending on the type of order, what is the item, or which warehouse it might actually need to be, fulfilled from. So a lot of those business logics can be built into these sort of the integrations and and remove some of the human interactions that might need to be reviewed prior to, know what are being placed or dropped to the warehouse. So those are kind of things. Also, the the inventory accuracy, you know, if you're getting inventory updates from your vendors or you need to provide those, to to your trading partners, you know, we wanna be able to make sure that inventory is accurate. So at least you're getting in that information, and there's different EDI documents that can help improve that visibility. The next point is around the data availability. It is now able to see it through dashboards or your orders and see if there's some fast moving products that are coming in that you need to be able to either reorder sooner or basically shut them off so you don't have any back orders. So it's all very important. I mean, in this day and age where supply chain is now not instead about weeks, it's about days or hours, two day shipping, same day shipping so that accuracy and the data visibility is incredibly important. But also the alerts associated with that, if, say, an FTP server you're using goes down, you need to know that that's down or you're not receiving orders that you normally think you would or the warehouse isn't getting stuff shipped as quickly as they should. So at least now gives you ability to get these proactive alerts if you do, you know, these different types of integrations You really see what is going on in your supply chain. So lots of opportunities for improvement and, streamlining your your your operations and and hopefully, making people more effective and be able to, you know, see and and react quicker to to different customer demands. And if you wanna grow your business, then this is a way you do scale scalability is by these type of integrations. And then a lot of trading partners at the last point here is they have scorecards. You know? Are you meeting your SLAs? Are you, able to respond? I mean, there's things like Target requires that they they expect to have that advance shipping notice sent within an hour after the, truck leaves the dock, and they won't have that invoice too, or they're gonna hit you with chargebacks because you're not meeting your SLA. So there's type those type of things where it's very important as you as a as a trading partner to be able to also, meet those demands and be able to, deliver. Alright. So, Tim's gonna get in much more of the details around Celigo b two b manager, but this is a new product we recently released to fit the demand. As I mentioned, we've been doing EDI for a long time, but it was a lot more labor intensive, a lot of scripting involved than others. But now we've been able to have a product release as part of our Integrator IO platform, which is a add on feature to be able to handle this interaction between your trading partners and EDI. And if you're familiar with Celigo Integrator IO, it's the same user interface. It's the same, technology and mappings that you're familiar with. The only thing different is it's EI. So there are some nuances that I'll get into a little bit, but this is, you know, really where we're able to, help with the different type of transactions, business documents you need to translate and be able to move back and forth within your ERP and also your trading partners. So, in in the world of EDI, you might hear different terms or numbers. X twelve utilizes these document types of eight fifty as a purchase order, eight fifty six as a little van shipping notice, or in the NetSuite world design fulfillment. Those those are the type of documents that we have to kinda translate the way those things are structured, the the layouts, and be able to fit that into the business processes that, you know, you're used to for the order of cash within NetSuite. Or if you're on a buyer side, you're gonna be procure to pay. So to be able to, you know, send out the purchase order, get the receipt, item receipt, and then be able to, obviously, pay pay the invoices that you have. So, again, it's very familiar type of transact transactions, but you just kinda get used to the different number. And, again, there's hundreds of these different types. But these are the most common ones that we enable within it, and this is more of your cash type of things or for pure pay, type of transactions that you're probably very familiar with. On the logistics side, though, if you're dealing with a warehouse, you're gonna have different numbers. You're you're dealing with what's called 900 series. So $9.40 is a shipping order that they may have. Now three pills, a lot of them can support multiple different formats. They may have, EDI capabilities. They may have API. And, of course, legal, that's certainly our preference, but, some only deal with the the DDI. So here's a different type document types that we would have to exchange with them as far as outbound orders for 09:40 and a $9.45 for the shipping when it actually goes out. Or if you have inbound stock, that's gonna replenish them. They're doing a 09:43 and a 09:44. And then and then that's where we're all you know, those those are your inbound shipments or a transfer order. So you're transferring order from one warehouse to another. So we'll send them a 09:43 saying here we're we're sending these in. And once they receive it, they're gonna send you a $9.44, which becomes the I fulfillment in NetSuite. So, again, there's a lot of translations that go along that, we're able to have you know, we have existing templates that can, do that heavy heavy lift for you. But you just kinda put it into business, terms, then it does make a lot of sense, even though you just gotta start getting used to all these crazy numbers you'll see. Now there are some considerations to deal with with EDI, and this is what kinda makes EDI hard. This first point, even though EDI x 12 is a standard, every trading partner has their own adoption of that standard. They have different mapping specifications. They they might have different versions, that you they utilize. I mean, there's there's you might hear a term of version forty ten. Well, this was released in the nineties or early two thousand, and it's still being utilized. But, you know, there's new versions that do come out. And so there is that differences that we see. Even if we've done Costco over and over again, we see different, because of the type of, items or commodities that you sell, there might be differences in way the EDI is translated in because they're using different fields out of the standard. And so it is tricky. EDI is no never ever, just plug and play. It's not washering page every single time. Each one is unique depending on the requirements and and what they need. Because they may have you different use cases, and they have you sending through a third party, or they may have you shipping in different ways. And you need a a way to be able to to be able to onboard these trading partners quickly, and so that's where we hope that, you know, a lot of the Tim's gonna show you, you know, some of the abilities for us to be able to either clone or or have the utilize these flows over and over and then work by exception as far as the mappings and and we utilize as much as you can within the platform itself. So you're able to onboard training partners much quicker. You know, we're talking weeks instead of months that it might take, like, today with your traditional, EDI providers. Alright. So, real quick, there are different protocols associated with the way, EDI providers communicate. So in you have a choice of either doing direct or peer to peer type integrations with your trading partners. So as I mentioned, maybe NetSuite is your hub, and then you're connecting to all your different trading partners either through FTP or a s two. And, again, that FTP service is gonna be, hosted by either your one of the trading partners, that you're gonna extend or or a s two is is a very common and and reliable and secure protocol that a lot of the trading partners require that that type of interaction. So we do have a a Celigo does have a AS two connector. But as you start getting more and more, if you have twenty, thirty different trading partners, trying to do these point to point integrations is pretty daunting. So in comes the VAN or the value added network, you know, these have been around a long, long time. Think think of it as like the post office. So these are different post offices of the different VAN providers that you can plug into and be able to simply have an address. So your address is this ISA ID that you're identified as as you two different trading partners, and this inter this, interchange actually then knows how to route that through it. So you just send everything through the van, and then you can then it gets routed based on the address of who is the sender or receiver of that EDI message, and then it shows up in their mailbox. And they pick it up and process it. Well, we still need to also have a band connector now that we've released to be able to also, be able to plug into that interchange, because that is that. Oops. I forgot. Sorry. We have to hit this slide here about interchanges for EDI. So there are, like, these three different methods that are utilized today, and you will see those certainly able to provide the release for that. I won't go through all these because I know we're gonna share some of these, but there are, different things to consider when you're doing EDI. I mean, there's lots of little things that can trip you up as far as that, just the identifiers that they use or different way to deliver or the carrier, all these other little details that do trip you up in the trading part that might reject your your transaction. And so, attention to detail is is incredibly important. You know, we we there's gonna have a specification as far as how they're utilizing that. It's a second bullet point or understanding what how they're connecting. If they have a choice, you know, definitely go FTP. That's that's quick and easy. AS two is harder. The hand's even harder. So if you can go go to FTP, you know, certainly encourage you that. But there are other considerations that they have. As I mentioned, there's lots of different variations that they're gonna be shipping you multiple POs on the same file that need to be broken up in a different sales order in NetSuite. So that's something else that needs to be considered. Or if you have to ship to multiple locations, you know, they you get an order from Costco and they said, okay. I need to ship to five different distribution centers. Well, of course, in NetSuite, that's gonna be five different sales orders because you can only have one ship to address. So there's lots of different things that need to occur, technically, that can also trip you up as you're going along. But on the flip side, you know, even with the NetSuite, there are some challenges that we have to, face as far as the way the structure is. So, for example, EDI bulk shipping. There's a lot of information on that van shipping notice or the item fulfillment that out of box NetSuite doesn't have that kind of level of detail that we need to have, and and Tim will show you a little bit about that, about some of the customizations that we need to do in NetSuite to be able to have that information so that we can pull it out of NetSuite and then be able to properly send that ASM to them. And then, vendors also have different ways that they will order items too. They may reference a UPC code or a g 10 code or some other codes that's different from your SKU number that you have in in NetSuite. So we've got a lot of cross references that usually have to be within, NetSuite for us to be able to do that. And, also, you're going to measure, you know, they may order in cases. They may order in each of this, but you can only sell by case if you're doing b two b. So that translation, again, needs to be in NetSuite for us to be able to make that proper translation of knowing how many units are actually being picked, packed, and shipped. Because if you got order for 24, they come in cases of 12, but you gotta tell the warehouse and you gotta ship two cases. Again, those kind of translations need to kinda go through your whole supply chain. So there's a lot of of details that we need to know and and be able to help. But like I said, those those are sort of what we have. As I said, I mentioned a lot of these already. I won't go into them. But the advanced shipping notice, as I mentioned, is really the hardest thing that we do, and and can get tricky as far as the different levels and hierarchy that we call about the shipment. We have to tell them about the order, and then you have to talk about the pack. And is it palletized? How big is the pallet? How many items are in the pallet, what's the weight of the pallet, etcetera, etcetera. So there's a lot of information that goes into, just creating the advanced shipments. So all the transactions is the one that always takes the longest. And like I said, there's a lot of other different, things that might occur if, like, say, eight eight sixty, which is a purchase order change order, might be a canceled, and I had an item change an item, change the shipping window that they want. So there's how do you react to that? And so those are the kind of things that we have we have to build within the integrations to understand, you know, how how best to handle those type of situations. And then if you're doing serial numbers or lot tracking is at last but the point, those are the one that can really be sort of challenging to to not get through. So, finally, and sort of leading up to Tim giving you this demo, you know, it's legal to enable this transactions that go through all these different data flows that we are. There's tons and tons of different things you could have. Maybe only two. You just do the order and performance, but there's tons of other interactions that happen within your supply chain that all have EDI that, Celigo can certainly enable, for you, and and we certainly hope that you can, do that. So I think, you know, we're gonna hand him over to Tim here. And, but at first, I think we're gonna do one more poll associated with, you know, kinda understanding, you know, what is your current, EDI situation and and solutions. So, like I say, we'll go ahead and stop sharing right now and allow Tim to be able to come on stage here. And, Tim will introduce himself, but, we'll put the poll out there. The votes are coming in. As I mentioned before, you know, we we work with a lot of people that already have EDI. They have lots of different EDI providers there. And, Tim actually filled in his own instruction, will say he used to come from a former EDI, the solution provider here. And so it looks like a lot of people have services. Alright. So there some people are using so they go, well, thank you. Thank you for coming out today. Alright, Tim. I'm gonna hand the ball to you. Alrighty. Alrighty, everybody. Pleasure to meet everyone. My name is Tim Heater. Been with Celigo a little over three and a half years now. As Chris had mentioned, I did come from, TrueCommerce. I I started there, many, many years ago, it feels like. But, started as front frontline support, worked my way up to NetSuite implementation lead, and found my way over here to Saligo for greener pastures trying to get away from EDI. So here I am on a webinar to explain to EDI on our platform. But to get into how to tie all of this together, what's Celigo has done for our offering, we are now evolving what we used to have, into a more user friendly and more exposed EDI solution. So first and foremost on the platform, what we have in our marketplace for our NetSuite customers is we do have a template, for b to b flows. So if I take a look at this just to show, it does come with the nine nine seven. So the functional acknowledgment, the invoice, the ASN, the eight fifty five, and eight sixty, and eight fifty. So this should cover most use cases. Obviously, it won't cover everything. But these are gonna be the primary ones that people are usually looking for a solution. Now one of the things that we, upgraded drastically on platform for EDI was to provide a dashboard to show, customers the data that's actually moving back forth through the platform. So prior to b two b manager, you would just have running flows and completed flows, which wouldn't show you really much EDI information at all. But now what we've added is a EDI tab here to show you the EDI activity. So we have document numbers, the document types, the functional acknowledgment status, whether it's been accepted, rejected, or if it's in progress, if we're ready waiting for a response, and also the x 12 file type. The file type's called out, because I believe July, we are going to be upgrading the platform once again to now support Edifact. So Edifact will be coming on platform. And you can also see we have the inbound, outbound direction type, the date time it was processed, and then the ISA GS information for the trading partner in your relationship. So you know who transmitted and received whichever document it is you're looking for. So case in point, if I take one of these document numbers, let's say you have some kind of discrepancy with a training partner, you could plug it into the search and it will give you that document number, based on your activity. K? Now if I go back to the home screen, like I said, when we, built this out, these are going to visually look like a flow. And the benefit here for existing customers is these aren't counted against you as a flow. So as you can see, we've broken this apart to multiple different trading partners. We have Costco, Ace Hardware, Walmart, so on and so forth. So what we can do is clone these flows, once we have an established trading partner, build a new, trading partner category out, and then bring them over to these different trading partners. So maybe one of them doesn't need all the same documents as the other. So So you can pick and choose which flows you're going to begin with. So if I look at, for example, Ace Hardware with this eight fifty, what we can see is we have a connection that is labeled. So this is one of the other features that we've added for b two b manager is is we now have labeled connector connections for these trading partners as they are added to the platform. So what we've done, additionally, is as customers are onboarding and bringing in new trading partner relationships that maybe we have not seen, What we are doing with the product team is we are adding EDI trading partners to this list. So this is something that we are offering to any customer, to get a project started. There's no charge for this. You give us the EDI spec sheet. We will build out the connector for you and get this added in. So this list has been evolving rapidly. I believe when we first, put this live to our customer base, we are looking at approximately 12 trading partners. I think we're well over a 30 now. So this list is growing. And you do have the option of AS two or FTP with these connections, with the labeled connector at least. Okay? So what does the connector actually do for you on our platform? So first and foremost, what it does when we go to this, step to pull the raw EDI data, we'll establish our connection just like any other connector. And then if we look here, the file type is locked to the EDI x 12. So that way, you can't make any mistake there. And then the EDI profile, this is something a one time configuration for each training partner. You'll build out the EDI profile for that partner. And really what this is is the envelope information for EDI. So the actual ISA, the trading partner information, the qualifier, is it in production or test? That is all able to be controlled right here on the screen. And again, like I said, it's a one time configuration so you don't have to set this up for each document type. Now the other thing that we added to b two b was the functional acknowledgment. So before, b two b manager, we would have to actually build a flow step and send the nine nine seven, which was just adding time to getting people implemented. Now there's a listener that we can just say, get the functional acknowledgments and send them as the eight fifty, for example, comes in. So when we build out the connector, what it really does is this EDI parsing definition. So on platform, we can't natively read the EDI raw as it is here. So we're we're taking this raw EDI data and then we're parsing it through this rule definition. And ultimately, what that's going to do for us is then kick out a JSON file that we can then map and parse however we need. Now the benefit here is even though we are building this rule definition file, if you need to update it, for example, if the trading partner says we're changing the, the value for the b e g o five, that it's now going to be a max length of, let's say, 15, I can now make that change. If, they say, for example, we're gonna add the 0 6, then I can come into this file, paste that value in. And if I remove this date two, I now have a b e g o six. So I can very quickly make changes rapidly without having to rely on some kind of support system where, you know, the email goes in, it may take a day or two to get a response. I can now, on the fly, come in and make these changes. So that is the key differentiator of how we're doing this on platform and how we're giving you the access to manage EDI directly on platform. Right? So the second layer to this is a transformation. So what we do here is just try to clean up the data a little bit and make it more friendly to the mapping step at the end. So what you can see instead of one large JSON payload, we're now gonna break it apart into a transactions array. So I can see the purchase order ID. We're calling out the field that we've created for this and all the different values that we're now adding in. So, again, this is just to clean it up, make it a little more friendly for the mapping stuff. Okay? Just like any of our other integrations, when I go to NetSuite, again, we're still doing standard imports. We're right back to, if you're familiar with the platform, how we really do things with every other, data flow. So we're picking our record type. What are we doing? We're adding, creating a sales order, and that would essentially be it for the eight fifty. We wanna generate new sales orders when the eight fifty comes in. And then the mapping step here, as you can see, we're selecting on the left the JSON field. So this is the raw EDI on the left. And then on the right hand side, my NetSuite fields. So as I wanna add more data in, I can select and my drop down window will appear referencing everything on the input. I can choose anything I want. And then on the right hand side when I click, I now have all my NetSuite fields listed. And then I could put anything I wanted there. And now I've got the wait field going to my Etail parent order ID. Alright. Now the other thing to call out is we also have kept the error management. We've improved this, from what it used to be on the legacy, before b two b. So initially before, we would just kinda tell you that something has gone wrong, that the file has failed to parse, and that wouldn't really tell you much when you're trying to troubleshoot. But now as you can see here, we actually call out the segment and the element and what is happening and why is it failing. So I can see the ISA control number, the group control number, the identification code, the document type. This is for an eight sixty four, and the BEG failed in position one. So it's saying that it's missing on line four. So this is calling out immediately why did this fail to parse, what happened. That way I can troubleshoot. And if it is something that I need to reach out to my training partner for, I now can see at a glance. Is this an error from them, or was this something that I messed up in my mapping spec? And just to take one step back here. So now if we are to do, an outbound document, for example, the eight fifty six, the more complicated document, we can see here there's multiple steps involved. So what we're doing is a safe search to pull the item fulfillment record, and we're isolating which ones we want for ACE hardware with this specific search. And then that's going to give us, the data that we need to send to ACE hardware for the eight fifty six. Now you can see here we have bill billing details and then the package, fulfillment packaging details. And I'll get to that in a second in NetSuite. So, once we get here, everything that we looked at on the eight fifty is now reversed. So we're pulling JSON data out of NetSuite, obviously, not raw EDI. And then if I go to this, Ace Hardware, EDI profile, that is set up right there just from the eight fifty step, and then I go to the EDI generator. So my sample flow from or my sample sample data from NetSuite is right here on the top right. It's going to run through this rule definition once again, and then this is kicking out the raw EDI on the bottom. So everything is the same from the eight fifty, but now we're just reversing the set of instructions. So initially, we're getting raw EDI, push it to JSON. But now for outbound data, we're getting our JSON payload and converting that into raw EDI. And once again, this file is not locked down. This is not something, locked away that you cannot edit. So you can feel free to change this whenever you need. And again, this would be your specific file. So if, let's say, I had a company that had the same trading partner as you, if I make a change on my profile, it does not affect you as that is tied to your profile. So you each every customer will have their own unique, mapping spec with at least a starting point with the connectors. So how do we tile that in with NetSuite? So, really, what we like to do, is with our, bundle with the Celigo bundle, there is the known problem where when you go to the packages tab with NetSuite, this doesn't really tell you much. With some trading partners, you can get away with this, that this is sufficient. Maybe you're only doing, pure carton, packing, which is great. But in the event where maybe you have palletized shipments, maybe you have mixed cartons, something along those lines, then we need to dive in a little bit deeper and figure out how we're going to get that information. So what we have done here is if I go to the ASN package contents tab, what we have here is the information is broken out for the item in the package. So you can see on this line, we have the order line ID that it's referring to, the quantity of the item, the item unit to measure, the tracking number for that package. And if you do have palletized shipments, it also can have the pallet SSCC here. Now if you needed more packages, for example, this can be broken out into multiple packages, multiple pallets. But this is how we've gotten around the limitation of not being able to see what items are in what box within NetSuite. And, of course, this information, if, you have a three p l, for example, you would then be able to take the three p l payload and generate these records to make sure all that information is sourced through on the item fulfillment. So that way when it goes to the training partner, everything's ready to go. Okay. Now in a nutshell, this is truly the, the platform and how we are doing it. We are still, adding more features as we go. The three p l, is another feature that people, do utilize, so we're building these out as they come through. So, again, if you're looking at expanding, it's not just the eight fifty, eight 50 six, eight 10. All the documents are supported, within, the EDI spec sheet. So as long as we get the spec sheet from you, the customer, we can build these connectors out. And and again, the, last thing to cover would be the error management from NetSuite. Sorry. I forgot to mention this. So if we look here, error management, that you're used to on the platform before has remained the same. So in this example, we have a lookup that has failed, for the NetSuite record, just to go through in case that nobody's aware of this. But if you needed to make a change, for example, let's say the unit price is not 0, it should have been a hundred. I can then change that value here, hit save and retry, and that will push that back into NetSuite. So you're not stuck with an integration where the the record has failed and there's nothing you can do. You can you can still, just like any other data flow on our platform, make any edits that you need to to repush into your system. And Rico, I believe that's what I've got here today. Okay. Thank you so much, Tim. Yep. We got a few minutes here. So we will get into q and a. Oh, actually, one last thing here. I'm wondering, Chris, do we wanna cover this or should we just jump into the, the q and a? Why don't we jump into q and a, and then we can circle back on this in terms of, you know, how to actually approach these projects? Before we do, just a couple quick, resources that, are going to help you, through this process. First off, remember, you know, we are actively looking for partners for b to b manager, you know, especially for customers and partners who are having frustrations with, you know, the traditional solutions, and wanting to have folks have a little bit more control. This is a great option for everyone. We launched a new NetSuite ebook. I'm also gonna put this link here. It's also available in the docs tab. I recommend everyone go in and click it. It is deep deep in terms of everything you wanna know about NetSuite integration. You know, the importance of building your tech stack, your business processes, around NetSuite, you know, given that it's the master data record for, financials and customer data and, you know, products and from and the importance to have an integration strategy which to go with it and all the options for integrating and, how Celigo approaches it and, you know, the multiple business processes all the way through AI. So do take a look. It's an incredible resource for folks who are just trying to understand more on, how to build the NetSuite strategy and how to, get more of their, NetSuite, practice. Next is, we released the, the the rest of the calendar for this integration series. So, you know, we've already done basically introduction to platform. We've done Salesforce, Shopify, Amazon, three p l e d I. Those are all available via recordings. But next up is data warehouses next month, then we do with Magento, Adobe Commerce. We'll go into HubSpot. We'll go ahead and talk about spreadsheets, you know, Excel and Google spreadsheets, super common use case, and then, advanced, Salesforce use cases like, you know, CPQ and so on, not for profits that, we've been requested to go deeper in the conversation. If you also wanna learn more, there's advanced, introductory and advanced legal use cases. Next one, we have, data as a service, displaying real world API use cases. Those are very helpful. And the, I I do see there's a question, Naoia, in terms of links of the password. If you click on that link that I just put here, the Celigo registration link, and you scroll down, you have access to all the the reported ones. Not the not the saligo.com/webinar, but the the previous link, which is I'll post it again. So right here. If you go on this link that I just shared in the chat and you scroll down, you'll have access to all the recorded ones. And then finally, for those of you, around the country, there we actually have a roadshow going on right now. We have a lot of customers and partners who are missing this because they are in Salt Lake City right now talking about Celigo. We've been to New York. We've been Chicago. But next up, the roadshow, we do Hyderabad, India in a couple weeks here on June 17. We, go to Dallas in August. We're gonna go to Toronto, and then we finish the year in Miami. So, if you are near any of those, if you have employees near those locations or if you have, you know, customers or partners that are interested in diving deeper into legal, come come meet us in person. Okay. So if you have any questions, please drop them in the chat, and let's see here. Okay. First question. Can a b two b manager handle SDQ scenarios with large retailers? So, SDQ is storage is free quantity. So what that means is, as I mentioned earlier, a retailer might ask you to say, I'm gonna order a hundred items, but I want 20 of those to go to these five different stores, and they'll they'll just distinguish which store numbers that those might go to. So long answer short is, yes. We can support that. The challenge is how do you want to support that? I've had situations where they want us, to break those up into five different sales orders so they can be shipped to different areas, or if somebody wanted them all to stay on the same sales order in custom fields, but then the item of the filaments would would have a different type of ship to locations when they send it to the three p l. So there's lots of different ways to handle that, type of integration, but, yes, we can certainly parse it and and bring it out, but it's really how do you wanna handle those. So, that's where I say it makes every situation might be different, but it can be supported. Do you charge per kilo characters or kilobytes? So we we do not, charge that way. So the the way that the pricing model works with b two b manager is we look at it holistically. How many trading partners do you need and how many EDI documents, unique documents, are being processed across your trading partners. So what that means, for example, is the eight fifty, the eight fifty six, the eight ten, the eight forty six, the eight fifty five. So our our baseline, our starter package comes with three trading partners, five EDI document types. You are not charged, for example, an eight fifty per trading partner. It is that you are able to process the eight fifty regardless of how many trading partners you, add to the platform. So each trading partner you add to the platform is 25,000 transactions per month per partner. So for example, the the starter package then would be 75,000 transactions per month across all your partners. So it's a pool of transactions that you're building as you add more training partners to your business. And certainly provide some stability of your cost too. So that's that's very important point, Tim. Yep. Yeah. So it's very predictable and you're you're not gonna get dinged, for example, in the holidays. You know, orders generally go up. There's no change at all to our pricing model for that. I think you may have covered some of this. Can you work with my my WMS for ASNs instead of NetSuite? Yes and no. I mean, a lot of three pills I shouldn't say a lot. Several three pills can actually handle those ASMs on your behalf. We've done those type of integrations. So we'll send them the order, but they'll send out the ASM to the trading partners, and then we'll just pull any of the shipping information back in the NetSuite that you need to know. So, I guess, you know, the answer is yes. We've gone in both those scenarios before, so, it certainly can be supported. Can you clarify that EDI is a single endpoint within this legal environment? So the the endpoint alright. So so with our standard pricing structure, you you're correct. You have endpoints and flows. With b two b manager, we don't look at it that way. So each trading partner is, like I said on the other question, is a trading partner. That that's truly how we're looking at it. It is not counted as an endpoint. So for example, if you, have access to the platform right now, you would see your allotment of endpoints and flows. When you add b to b manager, it would be separated from that. So you would have how many trading partners do you have access to and how many EDI document types are you using. So even though, the b two b manager, EDI processing looks like a flow, it is not counted as a flow against you. So you would still be able to manage and build however many flows you wanted not relating to process, EDI processing. And, also, again, the EDI trading partners are not an endpoint. So we're not tacking on you need to buy more endpoints to support partners. So if you already have a network connector, you're you're fine. You're just adding trading partners at that point. Does Celigo support a direct integration between three p l and Celigo using nine forty and nine forty five? Yes. Yeah. So the the nine forty and nine forty five are supported. There's also the nine forty three, nine 40 four. And again, depending on how there there's really no, issue in how you would process that data. For example, some customers choose to utilize the NetSuite sales order, for the nine forty. Some of them choose to use an unpacked, unfulfilled item fulfillment record. So whatever use case makes the most sense for your business. But, yes, we can definitely support those documents. Yep. The only trick I've seen is if as I mentioned before, if if your trading partner is ordering in each is, but the warehouse needs no cases case size, we have to do that conversion when we send it the $9.40 to them. So, those are, you know, some of the gotchas I talked about earlier. But, yes, they can easily be supported. Okay. I probably have only time for one or more two more questions here. Do you have any integrations in place for UCC label generation, Summit IT, or similar, or built in support? Yeah. That's a a tricky question. So what what we are working towards having a, integrated solutions part of our platform for, label generation. So this is the g s one label that goes on the packages or on the pallets itself. We do have a partner who has actually built this integration to bartender that that is offering that type of integration. What we've also found, though, is a lot of three pills that they're utilizing that are able to generate those GS one labels because every vendor has a different layout. And that's not necessarily something that we used to we do want to maintain, but we do wanna partner, with somebody like a bartender or nice labels for somebody that does that for a living. And so that is sort of direction we're going. So, stay tuned for more information on that, but we do have alternatives for you, if you do that. And, certainly within NetSuite, those same solutions are also available as a plug in if you are using NetSuite as warehouse. And I believe the partner you're referring to is probably Dave Charlene, from Altura here who just commented, on the label. But, we are at time. So thank you, everyone. Hopefully, please let us know if this was helpful. We do have a survey that went out there. Appreciate it. Sign up for the rest of the integration series. Do take a look at the ebook, and, hopefully, we will see you, in the the near future. Let us know if you, have a need for b to b manager as well. Thank you so much.