Transcript for "Integrating NetSuite & Shopify B2B":
Hello, everybody. Welcome to the webinar here. We're just gonna give it a minute for everyone to join the call, and, we will get started in just a second. Okay. Let's get started. I think we have critical mass here. Hi, everybody. Welcome to the ins and outs of integrating NetSuite and Shopify b two b. My name is Rico Andrade. I had global partnerships here at Celigo. And in this webinar, we are joined by, one of our partners, Diego Terra, the CEO of Hairball, and Jenny Lawson, our senior solution consultants, who, they will go over, all the details in terms of these, b to b functionality and, some of the things that, we have in store here, with, this legal flows. Just a couple of housekeeping items. First off, this is recorded, so we will send out a copy of this presentation, afterwards. And, secondly, we we this is meant to be an interactive session. So please, ask questions, on, there's a q and a section or add them to the chat, and, we will try to get either as we go, but there's definitely a q and a section at the end. You'll notice too that under the docs tab, there's additional resources that you can point to. We might refer to them throughout the the course of this thing and, some, you know, some elements for you to consider here. But excited to have you here. This is a really big topic that people have been asking for a while, so we switched around, you know, one of our topics of the integration series, and, happy to go in more detail here. So first off, you know, the agenda, we're gonna go over the basics of Shopify b two b, and, what needs to happen there, and then we're gonna talk specifically about the integration use case between Shopify b two b and b and and also how that some of the unique considerations and how that's different from a typical type of Shopify b two c integration. We will share some of the hard earned, practices in these integrations, and then we're actually gonna go into the product and demonstrate some of the things that we've learned on how we resolve what's legal, and then, we'll have a q and a session at the end. For those of you who are new, you know, and, aren't familiar with Celigo, Celigo is, today, one of the largest, most important integration platforms in the world. We have, we're number one on g two for the last six straight quarters. We are, visionaries in the Gartner Magic Quadrant. We have over 5,000 customers. And one of the things that has really stood out over the last, several years is that I we think we've become one of the largest, if not the largest, iPaaS that has, that that that caters to the, you know, ecommerce space, for companies who buy, sell, manufacture, distribute, physical goods. And as a matter of fact, you on the Shopify side alone, we estimate that something like between four to 5% of all Shopify orders last Black Friday, Cyber Monday went through Celigo. And so it's a it's an area that has been really growing for us, and, and and we we we have, you know, quite a bit of experience with these order to cash processes and beyond, and this is where these learnings come from that we're sharing with you today. Before we continue, I do wanna introduce our partner, Herbal, who has a particular set of expertise, in, not just Celigo, but also, in Shopify b two b, integrations in general. So I wanna introduce, Diego, our the founder and CEO, to do a quick introduction. Thank you, Rico. Welcome, everyone. So at Hermo, we are an exclusive Citibolo service partner and experts in NetSuite and Celigo. And, basically, the focus is to help product based companies automate, integrate, and scale faster using Celigo and NetSuite. So last year, we did more than a 150 projects and, almost 90 businesses went live with with Celigo. And, yeah, this year, we've been named an Inc 5,000 honoree. So simply put it this way, I mean, we help this, product brand scale fast with Celigo and NetSuite. Yeah. Thank you, Diego. So lots of, expertise to share here today. So, as you know, you know, this is a part of a much larger, operational story around, ecommerce, and, you know, supply chain logistics manufacturing processes. So, you know, today we're gonna talk about the Shopify b two b, which is where the digital storefronts, fit in on the left side. But clearly, it's it's part of a a much larger story in terms of the processes that need to be automated, across your organization. Particularly as you do the best practice of building the business around the ERP and in this case around, you know, NetSuite, ERP. So, finally, I just wanna you know, for those of you who are new, you know, typically, there's three ways that people typically approach integrations in the NetSuite ecosystem. You know, the first one is the direct integration with, SuiteScript, SweetTalk, Restlet, and so on. Those integrations, you know, they certainly are powerful, but there there's a couple issues with them. They require very technical resources, and they're very static as well. And they don't come with, like, kinda key functionality outside of the box, like, guaranteed data delivery and, error management and data monitoring and so on. Things that are really critical, in terms of any integration. And then when there's a modification that's needed in the future, you're gonna need to kinda relearn exactly what happened and you need a pretty technical resource to do it. So it's hard to scale, you know, it might be great for a one off, you know, with the type of integration that will never change. But in terms of really building a scalable system around NetSuite, it's it's it's not really ideal for that. There's also point to point integrations. And typically speaking, you know, those tend to solve some pretty specific use cases. The challenge with those integrations, while sometimes, you know, it might be, the the the quickness into integrate and the, you know, sometimes maybe cost. The challenges are that, they're not really built for customization and scale. And so, if your processes are exactly as it fits outside of the box, it's a wonderful option. But if you need to customize it to another level, you know, usually, you have to supplement it with another service. And, certainly, that's where, integration platform comes in. You know, that becomes essentially a hub, that comes with a a lot of that functionality, you know, on the net on the, guaranteed data delivery, on the, you know, a low code interface to build and manage those integrations. And in case of Celigo specifically, which we'll show in a little bit more detail, you know, we have some pretty unique features and functionality. One that it's very usable by both very technical or nontechnical functional subject matter experts. But it has, you know, killer features like the AI based error management, which identifies errors, identifies what the resolution of the areas, and automatically executes on the, resolution autonomously without intervention for 95% plus of the use cases. And then, there's very, very specific NetSuite functionality. So it's I don't know if everyone understands that Celigo has some unique technological advantages in terms of how we interface with NetSuite because, most, platforms interface with NetSuite just via the NetSuite APIs. And if you do that, you're limited in terms of what we can do. But Celigo has been building this bundle for the last ten years that has all sorts of functionality directly, you know, between NetSuite and Celigo that allows us to do unique things like full use of the safe search functionality with dynamic lookups and real time triggers and concurrency controls and other, key functionality that is really unique to Celigo and has given us this massive advantage in that ecosystem and help us be the number one global partner for NetSuite. So with that, enough of the introduction. So let's get into the meat of this. Final thing is a quick poll just to understand how many people are actively doing NetSuite integrations, Shopify integrations. Those, currently are probably our most popular integration use cases right now. So excuse me. So, are we sharing the poll? Oh, there we go. Thank you. Okay. 30% on Shopify b two c and yeah. Okay. So majority of folks are actively doing an integration right now. So okay. So, hopefully, there will be some good content, there. So with that, I will step out and pass this on to the experts. So, Jenny, this is all yours. Take it away. Thank you, Rico. Hello, team. Welcome again. Thank you for joining. Before we get into the data flows that we typically see between b two b, Shopify, and NetSuite, let's start with some of the basics. What are the core things you need to know about Shopify b two b? First and foremost, Shopify has been really steadily expanding its capabilities outside of its core offering for the last few few years here, to really support modern b two b sellers, make it really a lot easier for companies to handle some of the complex business to business sales, directly within their platform, versus maybe having to take a manual approach or have to take b two b orders over email. And so when we look at why it's important to integrate some of these new b two b functionalities, is truly critical. What it will allow you to do is unlock some real business value, with these fully typed automated flows. Automating Shopify B2B with NetSuite is gonna allow your company to really achieve some operational efficiency and speed. Data, you'll see, will can move real time, between your two systems, reducing errors, eliminating any kind of rework. And as your company starts to scale with b two b, these integrations are gonna really allow you to grow, and reduce any kind of manual overhead. So, ultimately, it's gonna lead you to better customer wholesale b to b relationships and experiences. And this is all done through personalized catalogs, visibility into product availability, and order status to your wholesale partners, Faster fulfillment, refund process should that occur, for, again, these wholesale brands that you work with. And finally, for your own finance teams, integration is really gonna help streamline the accounting reconciliation, cash flow visibility, and help you close your books, at month end faster. So these are just a few highlights of why it's gonna be critical to automate with the new functions available. Now for Shopify, they traditionally have been very good and offered a full suite of products around b to c. So now that they're doing b to b flows, what does that mean? What are the core differences between b two b functionality and adding on the new b two b flows? And, ultimately, I think it's important to kinda define what the difference is and and why there are gonna be slight differences between the functionality you see. With b to c and b to b businesses, though both are you know, you're selling products online, there are there's inherent differences where with b to c brands, right, ecommerce, you're selling products and services directly to individual customers through your Shopify storefront. So that, again, is all the core Shopify product and what they have focused on on the Shopify end over the last few years. So it's not straightforward, you know, your the end customer is the person buying for themselves, maybe it's a gift. Straightforward, focused on individual purpose, purchases. B two b, on the other hand, business to business, since you said something you'll ask me for anyone. B two b ecommerce and brands, these are businesses selling products or services directly to other businesses, but leveraging the Shopify platform to do so. So those types of customers, not necessarily individual purchases, they're gonna be wholesalers, could be manufacturers, could be distributors, or maybe you're selling to to resellers, retailers, other companies. So when it comes to the integration, really important to understand the difference between the two app offerings. You see here on the right hand side of the table with Shopify b to c, right, Customer records only in terms of your product catalog, very straightforward. You know, you're gonna have a core product offering or price offering. You maybe you have some built in pay later terms, but more more often than not, sorry. You won't have built in pay later terms. More often than not, it's going to be a purchase right then and there. Card is authorized. And lastly, you know, you're gonna have one single user in that instance that would be entering into the Shopify instance, for login. Now with b two b, on the other hand, there's a bunch of new features and functions in Shopify specifically tailored for those wholesale, reseller type businesses. So first and foremost, rather than just having a customer record, new records, exist such as companies, locations, and contacts. Companies kind of being like a parent to different contacts within that organization. Locations being where you're able to ship within that organization. With that, you're also able to set up catalogs with quantity and volume pricing. And that can be set up for unique companies, based off of any kind of predetermined requirements that you have configured, and different types of groups of wholesalers you want to support. B two b also supports payment terms. So things like net 30, net 60, do one receipt once you have actually fulfilled the orders. So big difference between a credit card getting authorized at time of purchase. And lastly, within Shopify b two b, right, you're gonna have multiple contacts structured underneath that same company organization, that you're able to assign different roles and responsibilities. So when you're going to sell to some of your wholesale partners, you have those, contacts clearly defined within Shopify now. So, again, to reiterate, some of the new features that are gonna come out of the box. Right? The new customer, company profiles, markets, awesome for b two b if you are doing international. Dedicated product catalogs, checkout and payment experiences, customer self-service portals, for your wholesale brands. So businesses are gonna be able to manage these multiple locations and accounts and all the permissions quite seamlessly within the Shopify platform. Yeah. And, and all that functionality is is important to note. It's gonna be within the GraphQL APIs, which we'll touch more on that a bit later here. So when we look at the value of these and why we wanna automate each of these things, each of these records between Shopify b two b and NetSuite in particular, we'll start by just thinking about smarter customer profiles. When you are centralizing in NetSuite each of your different customer records and then pushing that data back out to Shopify, you're gonna have a more consistent experience, between those two systems. And it's going to allow you for setting up those unique permissions, order routing, and and make sure both systems are reflecting the same type of source of truth. So it's gonna eliminate things like duplicate data entry, and really empower your sales teams to, have, you you know, all the most accurate up to date information about your wholesale customers. So first, main value point for leveraging the b to b, functionality would be for, of course, the that more seamless flow of customer profile information. Secondly, pricing. Having the right price for the right buyer. This is hugely important. So, you know, with with wholesale, it's never really a one size fits all. Each wholesale company they work with may have different requirements for how they wanna sell. We're talking today, of course, about the Shopify B2B, and offering that online experience for working with your hotel customers. But, you know, you may have some mom and pop shops that like to go over email. Being able to get these types of companies into the b two b experience and leverage that functionality, is gonna be more seamless for your team long term, but make it easier. So the fact that Shopify B2B is such an easy platform for wholesalers, to leverage and place orders. Right? It it's going to really accelerate the sales process and just have that better customer experience. And in particular with the pricing, you know, being able to set up those profiles and price levels, between, again, your NetSuite and your Shopify, it's gonna allow just better visibility into each of, once it's available to your wholesale brands, but allow them to have a single portal to see what is available for them to purchase. So prebuilt, some of these flows to automate pricing logic are gonna be really critical, so that you have the right pie price in the right place at the right time. Flexible controlled order flows. So super important that we're being flexible, allowing for these purchase orders and draft orders, and any kind of approval workflows you want to implement in NetSuite can be supported. So these are a couple more flows that we're gonna be able to see and support, wherein your wholesalers are able to get estimates, you know, get their visibility into fulfillment and then handle, of course, the invoicing process. So no rigid process there. Right? We'll be able to support, all of these great flows per customer. Alright. And then in terms of payment, right, payment is a critical aspect of B2B. Once once you have received these orders and you are are wanting to collect payment from these invoices, again, having this single portal, within Shopify B2B is hugely important, where we're you're able to support things like the terms, credits, and deposits. Really having payment flowing between the two systems is going to allow you to get paid faster and have better visibility into what is outstanding. So hugely important to make sure you're getting paid your way. Alright. And so with that, let's look at some of the common data flows themselves. So integration use cases that we do see between Shopify, B2B, and NetSuite. These can include those company records, managing contacts, and so on and so forth. So let's go to the next slide here. Again, here are those common data flows that we're seeing. Those additional B2B record types here on the right hand side of the slide, companies, locations, contacts, catalogs, price list, draft orders, invoices. And there on the right, we have a handful of the common data flows that we've seen built between Shopify, B2B, and NetSuite. To visualize that, we prepared a a small diagram. Now what we'll mention here is that these are the common b to b data flows that we're seeing. You may have already in use today something like the Shopify integration app with Celigo, or perhaps leveraging one of the Shopify to NetSuite templates from Celigo marketplace where there are a slew of additional data flows built specifically to address the b to c business, so business to customer use cases. These b to b flows would be essentially complimentary around top of some of those flows. Again, it's focused specifically on those these new records, and the workflows required for that seamless wholesale experience. Alright. And so with that, let's shift gears, and I will, hand it off now to Diego to get into further into the weeds, and really talk through some of the best practices for Shopify b two b integration, and then walk through a demo. Alright? Awesome. Thank you, Jenny. Alright. So yeah. I mean, at Herbal, we've done more than two to five b two b projects, from NetSuite to Shopify. So, with more than 20 projects, you get a lot of experience and and, edge cases. But if I need to consolidate the best practices when when defining integration between, NetSuite, and Shopify. The the most important decision, and sometimes we get customers that they are starting with Shopify b two b, so it's easy because they've been operating b two b in NetSuite, and now they need to move the customers to Shopify. But it becomes a little bit challenging when they already have all these entities created in Shopify, and they need to sync them to to NetSuite so the next owner, is assigned to the same company. So now if that's the case, the the most important thing you need to decide is that NetSuite will now become the system of record for a company, a content, and allocation. So all that management will happen within NetSuite. K? So, and then you have different structures in in the company record in NetSuite. You may have companies with contacts, company, with addresses, maybe a company with sub customers, and each sub customer will be a contact. A sub customer may be in an international location and have a different price level. So the first thing you you need to define is the structure of how companies are have been created in the past, in in NetSuite. With that, we can define the the integration and make sure that NetSuite becomes the system of RevAir. The the structure of a company in Shopify is, company, allocation, and customers. Customers belong to the company and to a location. Right? Again, in NetSuite, you have different structures, so you need to accommodate to that. So, again, that's the most important, integration best practice then. The the how you have the data in NetSuite may not match, in Shopify, like, an address, a phone number, a ZIP code, an address one, two. So, some some data cleanup and and some good criteria on the seven searches that define what gets to Shopify. It's it's very important because, I mean, it it will fail. And instead of doing error management, you wanna be proactive in that sense and only push companies that have a a good data structure. Then I mean, the field once you start the integration and all these flows, and I'll do a demo in in five minutes, but, it's important that the flow dependencies make sense. You can't create a location or a contact. We are a company. You can't create a customer if there's no location. So the company, location, contacts, sequences must follow, and then the the each company must have a catalog. So sequencing this is super important, and it's not just creating an an integration and turning on the flow. There needs to be a dependency and a sequence always. And everything that Shopify released in in it's in the GraphQL API, so don't spend time, on the rest API for for nothing related to b to b because you're gonna hit a wall. And, so always, I mean, find the solution on the GraphQL API. On the the next week, the the advanced templates that released in the marketplace are 100% built on GraphQL, so you can use that as a for guidance or for reference. And then, I mean, testing and mapping, the mappings are different from b to c. They have a lot of logic, so I'll show you now in the demo. So how you map, it's it's super important from from a b to b perspective. Common pitfalls we see on the on the Shopify b to b integration, I mean, there are new record types. So, the bundle that you install in in NetSuite will add some customers to the companies. So and adding to the b two c, IA flows, you're gonna now map companies, locations, price list, catalogs, and and and draft orders. So it it involves more flows than the b to c integration. Again, flow dependencies we've talked. And then payments are tricky in a way because you have three types of, of payments in b 2 b. The first one may be that the customer deposits 50 percent of the order when the order gets placed. A second one, and then the 50% of that order gets paid after thirty days in NetSuite. Okay? Maybe the customer doesn't pay anything on checkout because they have Net 30, and that payment is done in NetSuite against an open invoice. Or maybe the customer places an order in, net 15, and after fifteen days, they pay in Shopify. So, again, there are three ways to, pay for an order in b two B. You wanna make sure that the two systems are in sync, and this involves, good flows to make sure that, what the customer sees in the account, it is what it is what it is in reality. Okay. So let's do, demo. Let's share my screen. Okay. So, many of you know Celigo, maybe many of you don't. This is Celigo platform, and this is our integration. This is the Celigo integration app for me to be where, there are some settings where you can define, general preferences for for for the flows, mainly the company locations and contacts flows. But, basically I mean, the the flow groupings are, companies, locations, contacts. K? So, again and they're bidirectional. So you can create the company in NetSuite and push it to Shopify, and that's what we recommend for. But if you already have a lot of the business going on in Shopify and you wanna keep creating companies in Shopify, we also have the flow that, we push companies from Shopify to NetSuite. From a visual perspective, basically, the flow gets companies. It finds some customers' addresses and contacts to build what is gonna be pushed to Shopify. Then this is in GraphQL with a new connector. Find a customer and branch here to, create the company. Okay? And all these are, Shopify settings that you must, do when you create a company or, update the company. In NetSuite I mean, update the company if it already exists. But after you create the company, Shopify will update the company in NetSuite to match the IDs, create the locations, wrappings, and update the main contact. So now it gets the ID that we assigned in Shopify. Then if you have meta fields in in in NetSuite, we'll update the meta fields. So it's a pretty complete flow, from NetSuite to Shopify that takes care of all the different combinations of companies, sub customers, contacts, addresses, and everything involved in in in making next week, talk really well with Shopify. Locations and contacts, again, are part of the company creation. Then we have a standard order flow. Shipments, that is like the the the d two c where if our fulfillment is created, NetSuite will create a a shipment in Shopify. And then we have payments where if there's a Shopify payment, we'll send a webhook to to the flow, and we're gonna look for, open invoices in NetSuite. And if there's an open invoice, we're gonna create a customer payment that is the invoice. And if the customer pays in, NetSuite, we're gonna get the payment, understand the order details, create the payment in Shopify, and update the payment that's sent in NetSuite. So like I said on the pitfalls is the payment flows are super important in in b two b. Then we have returns and refunds. Returns are not part of the b two c, but you can use this flow for Shopify returns, and then refunds, as you know. Catalogs and pricing, we have three different flows. The first one, make sure that, price levels in NetSuite are created as catalogs in Shopify. The second flow assigns the catalog to the company and to the location. K? And the third one updates constantly pricing from NetSuite price levels to Shopify catalogs. And then we add another flow now that Shopify introduced markets to catalogs and companies. We assign the correct market to the company. So this flow could be grouped under catalogs and pricing too. Then, inventory flows, again, pushing from your location in next available inventory to Shopify. And, again, this is an advanced template. You have full control on the logic, and you can create your own custom flows. So, for example, one that is very popular is, getting the meta fields of products in in an order and updating the sales order in that. But, again, Senio gives you the flexibility to, I don't know, tune the order flow to your logic. That's and this is very different from EIA, where now you have access to the hooks. You have access to everything to write your own logic and extend the integration with, custom jobs. Okay? So going back. So, Jenny, I guess, back to you or Rico. Yep. I'll take it. Thank you so much, Diego. Okay. So we have lots of questions coming in. So before that, just wanna summarize a couple of key things here. You know, this these are the general takeaway. Right? So there's a massive advantage of, leveraging the iPaaS, instead of point to point integrations, you know, so that you get the scalability and agility that's possible with b two b. These accelerators that, you know, we we have put in the marketplace are really gonna speed up the the process for the majority of the use cases. And, you know, it the the management of the integration is always underrated. We think that, you know, the management, the long term, TCO of the integration is it should be a first class citizen because ultimately, you're gonna spend more time there than just on the building of the integration itself. So before we go to the questions, just wanna point out a couple quick, upcoming, things and resources. So first off, we have our connected roadshow, going across the nation. We've done our first four. Tomorrow is Dallas. If any of you are in the Dallas Fort Worth area, I am in Dallas right now ahead of, the event tomorrow. We would love to see you. It should be a great, turnout. We got Toronto on September 10 and Atlanta November 5. So whether you are yourself, in those areas or if you have, you know, customers or prospects who are interested in Celigo and wanna meet us in person, you know, please join us, that you could see the link in the box there. Reminder, we did launch the NetSuite integration handbook. It is a complete document in terms of how to build, your practice around NetSuite and how integration strategy fits with any NetSuite strategy, for the long term. It there's some specific information about, where Celigo, fits into that equation, and what makes us unique in that ecosystem, and then some best practices and, like, next step, you know, so you can set a roadmap for where you're gonna wanna go next with the integration. The in and out series continues. So, the next one is on Adobe commerce slash Magento on September 10. We're gonna talk about spreadsheets, you know, Excel, Google Sheets, on October 22. It's actually, like, a huge topic because everyone exports data from NetSuite to Excel, and we don't necessarily need to do that manually. We'll go BigCommerce on November 6, and then we'll talk about, advanced Salesforce integrations. It's a in, extension of the first Salesforce integration webinar that we did, and then, HubSpot in January 21. Actually, it looks like the data is missing there. And then finally, from a resource perspective before we get to q and a, Sweet World is coming up October. I know many of you, are gonna be there. We highly, recommend it for everyone on the NetSuite ecosystem. We will be the diamond sponsors. We'll have the largest booth there, a huge team. We would love to meet everybody in person. So, please let us know if you're coming, and we'll schedule a time to make sure that we talk in person. There is a blog. You can access this from the the docs that kinda summarizes some of the details on this accelerator. We have a webinar on how manufacturers and suppliers can automate drop shaping for scale agility with iPaaS. So that is independent of NetSuite specifically. It's, but it is a common use case for us. And then, if you are just interested in learning more, you know, just go ahead and book a call with us, you know, thirty minutes. We can go over some of the stuff in detail. And, again, the details of that is in the docs. Okay. With that, let's go to q and a. You can sign up right here for the ins and outs series. So, Diego, Jen, you guys probably need to come back on stage. But, alright. So let's start with, if we already have the Celigo NetSuite Shopify integration app, is this a full replacement or an additional integration? Example, does this EDU's DDA integration handle d to c orders? And yeah. I mean, if you wanna move everything to this integration, it could handle it. There's probably additional logic that the Celigo IA already has that it's not in the flow. But if the flow, as it's built, works for you, you can, yeah, migrate it to the the these templates. So, I mean, basically, they can keep the integration app and add additional flows from the template, or they could move the entire integration app into the template if they want additional level of customization. Exactly. Yeah. Okay. Well, that answers it. What about handling one order that ships to multiple separate addresses? How how does legal handle that? So there you have two options. I mean, the flow doesn't handle that out of the box, but you can customize it to or use the monthly ship to feature of NetSuite. Or, I mean, additional logic could be to close the original order and then create suborders, each order for its own address. But you can write the logic in the in the flow. Since you guys built these, built out these GraphQL flows for this, does this mean that we are close to a GraphQL version of the regular order flows in the integration app? And What? So that's definitely something that's top of mind on the Celigo side of the house, for updating the prebuilt integration app option. We are adhering to the timeline, that Shopify has for the deprecation schedule. So I think that the the the drop dead date will be everything with need to be migrated by February, I believe, of next year. And so we'll be continuously rolling out updates to the IA, based off of the schedule they have there. And for that, we we can share, where you can see the releases and updates on the Celigo side, through our help center, as well as in the platform. You can see what's new in the account drop down in the upper right hand corner. So we'll make sure to share that link. K. What if the customer is on net 30 terms but checked out in Shopify using a credit card? Will NetSuite, I think they mean NetSuite integration app, collect payment? As far as I'm told, the answer is no, which is bizarre to me. In in these templates that I showed today, yes. If there's a payment, we will create a customer deposit against the order. So as long as if there's a payment, it doesn't matter the terms of the customer. If there's a payment, we need to book that payment into the GL. So there's gonna be a customer deposit against the the order. The only thing we have yet to figure out with catalog is custom pricing. Price levels work no problem if a customer has a custom price level. This doesn't work. Has anyone figured this out? Yeah. So the the basic level of pricing, it's the price level as you as you mentioned. But if you wanna add group pricing, quantity pricing, or, specific custom pricing per item per customer, it is available in the NetSuite API, so you could create a specific candidate for that company and for that item. So it's possible. Yes. It it it involves, some good NetSuite knowledge and and and some good candidate of knowledge of Shopify and and and and that would flow there. But it is possible. Not too common. If a business does not use contacts, locations, and other fields records, especially with the new e tail channels that come with the b two b template and also don't have data for customers, companies, etcetera, in Shopify, how do we get started syncing up? We can run flows without fields in NetSuite, but we can't fill the fields in NetSuite if we don't have them in Shopify yet. So, I mean, the minimum information you need to create a company in Shopify, it's the company, one address, and one customer, one contact. In NetSuite, the minimum you can have that represents a company, it's a company with an email and an address. So as long as you have that those data in each in the company in NetSuite, you can create the company in Shopify. But, again, to create a company in Shopify, you for as a minimum, you need, the company information and address information and who's the buyer of that company. And, Diego, is that something that your team over at Hairball would be able to give advice and instruction on? Yeah. Definitely. I mean, we've seen many different configurations of companies in NetSuite and how to adapt them to work in Shopify. So yeah. Awesome. So you're a resource here. Yes. Please please leverage, Diego, and his team. Reviewing the customer to company and sub customer to location creation flows, I do not see where meta fields are mapped. I'm familiar with the integration app. So this is not an integration app. This is advanced templates built specifically for Shopify in GraphQL that because it's in GraphQL, now it allows to add the meta fields I mean, custom fields in NetSuite as meta fields in Shopify or meta fields in Shopify as as fields in NetSuite. So so, yeah, you won't see the meta fields in the integration app, the the b two c one. What advantages does GraphQL have versus REST API? The the main advantage I mean, two, performance, first, and the second one is accessibility. Any new feature released by Shopify is gonna be in the GraphQL, and 5% will be on the right API because it's a necessity. But, I mean, everything Shopify is releasing is in GraphQL, and you can access any field in any record. Yeah. To to add on to that, Shopify as an organization, made the business decision to move to GraphQL as their core kind of supported, integration option, and move away from rest. So that is a business decision on their point. And to to Diego's point, really, it might our understanding of why that happened is for performance, that efficiency and data retrieval. With GraphQL, you're essentially requesting the exact fields you need within a single query, and you can do it across multiple objects. So it's it's gonna really prevent overreach, and make those calls that you're making to get data out of that's where you're pushing in and that's where you first see things up, but a lot more efficient. So hopefully, that answers that question too. K. What is the difference between integrating Celigo between NetSuite and Shopify compared to the NetSuite connector? And maybe I can start that one. Generally speaking, the NetSuite connector is very fixed in terms of a couple specific, use cases. And then but if you have to deviate from those use cases and customize them, you know, it's it's not built for that. Whereas, the legal, is a lot more robust in terms of the the extent of the use cases that are coming, out of the box and in terms of the ability to customize and configure, those use cases if you have, you know, modifications. But Diego or Jenny, do you wanna add to that? Yeah. So after billing, more than 200 Shopify integrations, I mean, there there's always for for a good integration, there's always a need for some custom logic, something custom, and and and it's not just about, creating custom flows, but it's about that custom flow may save a lot of hours and a lot of errors. You know? So it it is important to have them. When you work with end to end I mean, point to point integrations that are prebuilt by typical use cases, you lose the flexibility of getting the integration right where you need your company, I mean, to to take value out of integration. So again, if it's basic, flows and the typical ones and and the typical use cases, it it's fine. But but if you really wanna get the integration right to save time and and scale and everything that a good integration gives you, that that's the main difference. And then, error management in the integration, it it is critical. So once the integration goes live, making sure that all the data, you know, is, going back and forth and, and and someone can manage it, an administrator, it's it's critical. So error visibility, it's it's another main a huge difference between the the Monica and and Celigo. Excellent. What is the list price for this integration? So these are templates. So, basically, if you have a Celigo Integrator IO edition that has, you know, the endpoints and the the flows to accommodate it, you can, you know, use the integration without, additional subscription costs. There may be services cost, professional services if you're, you know, leveraging, you know, someone that like hairball. But in terms of subscription, it can go into the, yeah, into your existing subscription. But, if not, you know, it's an it's an additional endpoint, and, you know, might be additional flows depending on, where your capacity is. Anything to add there, you know, Jenny? Or Yeah. I mean, you can leverage the the Shopify endpoint. We create a connection to GraphQL, and then, again, the templates are available in the marketplace. It takes some time to navigate them. And I think if you need an amazing partner, we can also help you with that implementation, but you can take it on your own too. Yeah. So if you already have Shopify, and NetSuite as endpoints, you know, then it's looking at the flow capacity there. When the GraphQL orders integration is built out before the rest is deprecated, will there be a template version of it as well similar to the b two b one? We are really loving the customizability and access to hooks, etcetera. So that that's a yeah. But that's I mean, from San Diego product team may answer that one. I I don't have that. But, but, yeah, I assume yeah. One that, good. Jenny, you wanna take a pass? I you know, I'm afraid I don't have the specific time line. My assumption is yes, but I'm not here to make promises on behalf of the team I'm not on. So well, we can absolutely get back to you on that. We will follow-up. Last year, did I ask this one? Last year, we implemented Shopify b two b already with NetSuite as our master ERPOMS. We developed custom flows in Celigo to manage this. Really interested to learn more how we can benefit from this. Yeah. I mean, happy to review them together and see, what you build and how it compares to what's in the marketplace and how you can leverage these these new templates by scenario. But, I I mean, it takes care of a lot of use cases. It has many implementations using it, so, it's really tight in terms of b to b flows. So happy to review them together. Okay. I think the let's see. Let me know if you have any more questions. I see someone had issues downloading, the ebook. Do we need to put the the link again maybe in the chat there? The NetSuite integration handbook. But we will follow-up afterwards too with these links. Yeah. Frank, we'll we'll, we'll we'll send you the link directly. If anyone else is having issues, let us know. And, yeah, maybe we can if we need to, we can, pull yeah. We'll we'll we'll send you the link directly. Okay. Any other, final questions? Okay. Looks like, we okay. Yeah. There's a new link there in the chat. If you wanna take a look, try that one. But looks like we, haven't gotten through it. So thank you so much, Jenny and Diego for participating in this webinar. Again, if you want to learn more about, you know, this use case and you're looking for, an, a partner to help you navigate and integrate it, you know, certainly, please reach out to Diego at Hairball or reach out to us and, you know, we'll put in touch, or, anything. You know, just reach out to us if you wanna learn more about this integration. Don't forget to register for the next one in the series, and, hopefully, we will see you all in person, either at one of the roadshows, or, at SuiteWorld or beyond. But thank you so much. I hope you all found this valuable, and we'll see you next time.