Ins and Outs of Integrating Shopify and NetSuite

In today’s webinar, we will talk about the “Ins and Outs of Integrating Shopify and NetSuite”. And my name is Ebru and I’m a product marketing manager at Celigo. And I’m here today with Mannan, who is our senior solutions consultant, and he specializes on e-commerce integration. So I will start the webinar with a short presentation. And then Mannan will do a live demonstration of Shopify, NetSuite integration. So if you have any questions during the webinar, you can submit them through the chat window, and we will be taking questions at the end of the session. Okay, so let’s get started here. So, yeah, Celigo is an iPaaS integration-Platform-as-a-Service company. On our platform, one can connect any application with any other application to automate key business processes. For example, you can easily integrate Shopify with a 3PL provider to automate your fulfillment processes once an order is received. Or you can even think of integrating Shopify with HubSpot for marketing automation to target your existing customers with new offerings. So these are all some examples on what you can do on the platform. And we’ll talk more about this later. Some background on the company. So we’ve been around for nearly a decade and we are actually the largest NetSuite partner. And if you’ve been in the NetSuite ecosystems, so you probably have heard of us before. And we’ve also been in the Gartner Magic Quadrant for a couple of years now and we read G2 iPaaS leader. And here are some examples of our existing customers. We have a lot of expertise in e-commerce integration. So we have helped basically thousands of customers with automating their order to cash business processes. And aside from Shopify, Amazon, eBay, Walmart, Zendesk, 3PL, EDI, are the other most popular integrations we see amongst our e-commerce customers. And then what makes the platform unique is it is built for both business and technical users. So this means if you’re someone without any coding experience, you can still build and manage integrations through the intuitive user interface. Okay, so yeah, when it comes to e-commerce platforms, so we see more and more of our customers are moving to Shopify. It is easy to use and also provides all the advanced functionality any e-commerce business needs. But so if you have Shopify, and if you have NetSuite as your ERP or an accounting system, and these two systems are not connected with each other, it means you’re still manually entering and downloading and uploading data between the two application. And obviously, this is a really source-intensive, slow, and error-prone process. And not having real-time visibility into customer orders, transactions, and [messages?] can lead to backlogs in bookkeeping, errors in accounting, and this can result in poor financial planning. And then when [inaudible] is not currently updated across systems with every fulfillment, you can easily run out of stock and you can delay procurement and also even end up selling out of stock items to your customers. And last, not having real-time visibility into your orders can cause delays and errors in fulfillment and returns processing, and all of this can easily lead to lost revenue and poor customer experience. So integration is a must when you have Shopify and NetSuite. So selling off I-Pass, it’s standardized how applications are integrated across an organization and it creates repeatable processes to move data between different applications. So our I-Pass plus firm is called Integrator.io and it provides all the tools needed to build and manage your integration. So it comes with pre-built connectors and templates which help to get you quickly started and then development turnaround time on the platform is very fast when you compare it to building API integrations from scratch through coding. And data delivery between the connected systems is always guaranteed, so meaning no data is ever lost. And also the platform provides easy-to-use dashboards and features for monitoring, troubleshooting, and managing your integration. So on top of the platform, we have our integration apps. So these are basically task applications. These are built and they are running on the platform. So here Shopify, Amazon, Returnly, ShipStation, Zendesk are some examples of our existing integration apps, and our platform is actually the only I-Pass that offers integration apps. So these are prebuilt out-of-the-box integrations covering popular use cases and all the essential flow. And these can be easily configured and deployed without any coding. And then they are fully managed, meaning for example, for the Shopify-NetSuite integration app, we’ll make sure that the app is always up to date to support the latest versions of both Shopify and NetSuite. And so because these integration apps are built on our platform, all the features of the platform I mentioned earlier apply actually to these apps. So the integrations they can and be easily customized and expanded to match the changing needs of your business. And today we’re going to focus on the Shopify NetSuite integration app. So we talked about what happens when there’s no integration between Shopify and NetSuite. And then here’s how Celigo’s NetSuite Shopify integration app helps. So this app basically syncs data, as you see here in the flow diagram, such as customer, order, fulfillment, product, billing, refunds, cancellation, inventory data between Shopify and NetSuite. And so how this helps, at first having real-time visibility into Shopify orders and transactions eliminate accounting errors and helps with reliable financial forecasting and resource planning. And then syncing orders leads to faster customer delivery and syncing refunds, cancellations, helps with fast and accurate processing and just all positively impact your customers’ experience. And centrally managing the listings across multiple Shopify stores from NetSuite and the ability to automatically update products basically ensures listings are always up-to-date and reflect latest descriptions, pricing information, and save businesses a lot of time by not having to manually go through the update process. And updating the fulfillment information from NetSuite to Shopify on the other hand provides customers with a real-time visibility into their orders better. And so for inventory, keeping inventory levels up-to-date between them helps maintains healthy inventory levels through accurate forecasting and inventory planning. And then the last thing I didn’t mention here is we also have an addon for this app for payouts reconciliation. And that basically helps eliminate manual reconciliation processes by automatically downloading payouts reports from Shopify and identifying any payment discrepancies and unsettled amounts. And of course, on top of all of these, any custom flows for your specific business use case can be added on top of these, leveraging the iPaaS. So now, here I will hand it to Mannan so he can walk us through the products and show us a live presentation. So let me hand it off to him. Okay [Manard?], now you’re the presenter. [silence] Mannan. We can’t– Alright. Let me know when you can see my screen. Yes. We can see your screen. Thank you. Awesome. Alright. So thanks everyone for joining in. I think it would give a brilliant lead up to where I need to get started. And I did want to talk about this integration app that we have in place. I think a lot of you all may have seen glimpses of it in the past. But on the whole, we’re going to be talking about the different record types that we will be able to sync along with the direction and the overall frequency for the same. So before we do get started, I do want to share that I did mark up a quick order on the Shopify side to something that we can use to talk through and view between the two systems. Created this a couple of minutes ago, and we will be seeing how this transaction flows into NetSuite. From there we will dive into the integration and look at the different configuration related options and the different features that it can offer you. All right. So starting out, we had an order in Shopify 1076. It contains a single product out to you, has a genetic discount, has shipping on it, and then there’s something going on for tax out to you. We’ve got a customer record set up as well. And we will now take this back into NetSuite. So jumping back on the NetSuite side, we will see that we’ve got another order 1076. We’ll scroll down, we’ll see this item out. There’s the item out here, we’ll go into shipping. We’ll see that there’s another item out here as well. Come back into billing, we’ll see that there’s some billing information, and then we let the billing open for invoicing and deposits at a later stage. And also, there’s going to be an [e-till?] tab available out here where we give you a little bit more information on the Shopify transactions. So you will be able to see the Shopify discount code, the Shopify order number, the transaction IDs. And if there was any risk rating, we will be able to display that out here as well. As part of the next step, so you can go ahead and fulfill this transaction within NetSuite and we’ll be able to see that information flow back over to Shopify. So again, just starting out with a quick, more action-heavy approach. And then we’ll definitely switch into talking about how the integration actually processes this information. All right, let’s go and enter in a tracking number. And let’s go ahead and hit save. All right, so I’m just going to quickly trigger something on the integration. So we can come back to it once we have the right opportunity to do so. All right, so in about 15 or 20 minutes, we will circle back to see the fulfillment record pass over to Shopify. It’s actually done more or less instantly as soon as I click that button, but I do want to spend more time talking through the rest of this integration. So we will actually start out with the product data, where you’ve got a NetSuite item, which contains all your information, for example, the product title, the description, the product tags, images, and any other important information, like the weight or the vendor or the product type. And at that point of time, we can take the NetSuite item and send it over to Shopify. If there happens to be any change on the NetSuite item, for example, the product title may change, or the the description or say even the price. We do have the ability to push those updates over to Shopify as well. Now there are different product types in NetSuite. So for example, you may have something which is set up as a parent, child relationship. Also called as a matrix item within NetSuite. So in that case, we will be able to push the matrix item from NetSuite to Shopify with the same hierarchy that you’re looking for. So it would, for example, be a t-shirt with a parent set as the t-shirt and then the child option would be the size and the variations or the colors as well. Let’s quickly jump into NetSuite and take a look at the item. So again, just set up a random item called 9911. It’s a generic [fan?]. And we’ve got some pricing information, as well as some sales descriptions set up for it. Again, this description is set up in HTML using a rich text to field on the NetSuite side. And Shopify understands the same language, so it was very easy to push that over with some formatting as well. We did have some price levels that I’m working with as well, so on the Shopify side, I’m sending the list price out. And along with that, there’s going to be a couple of more additional fields for the Shopify side where we are controlling the product visibility and if we needed to set the product type or the tags or the weight, we could do that as well. I’ll jump into Shopify to just give a quick example of the same product. You’ll see that it’s again, the same [fan?] with some basic information out here. We’ve got image, we’ve got pricing, and I believe there should be weight and inventory as well. So we’ve got weight out here and inventory. We will circle back to inventory in just a moment. But once this product is going to be set up, it’s available for customers to purchase if there is quantity available. Now in this case, my item does have inventory but let’s go back into the integration and talk about how we will be managing inventory. Now these inventory items in NetSuite could have different configurations and use cases. On the whole, we do take inventory quantity available against a NetSuite item and send it over to Shopify. If you’ve got a NetSuite kit item, we will send the lowest available quantity across the kit components over to Shopify. These processes or these up flows will be add update features. So let’s say you’re listing the product for the very first time, you will have the option of sending the inventory or creating the inventory. And then as the quantities change within NetSuite for various reasons, let’s say you receive items, you sell items, you dispose of certain items. Let’s say something got damaged– and again as long as the inventory quantity available at a specific NetSuite location changes, we will push that over to Shopify as well. The process for that is, again, pretty straightforward. You have the option of choosing the NetSuite locations where we should source the inventory from. And we will gather the data from NetSuite by leveraging a native tool called as a saved search. That save search helps us qualify the items and then send them over to Shopify. With the correct formatting that it’s expecting as well. We did cover quick couple of things on the inventory side of things and the product. And the key thing to remember is that when we are sending information out from NetSuite to Shopify, all the data is again going to be housed within NetSuite. However if there is certain data that you feel that you would prefer is controlled directly within Shopify, you do have the option of making those configuration changes as well. So on the right, as I click into the button out here, you will see that there is a section called as edit mapping. And as I click into this, you’ll see that we give a quick list of fields that are mapped between NetSuite and Shopify. And at that point of time, I have the ability to control what information is truly being sent out from the NetSuite item over to Shopify. So let’s say, for example, we’ve got the product title, you will see that this information is locked away. So we do not want users to change this. But let’s say that there is something like the tags, or the product body, or the description, and we do not want to send that over to Shopify since the merchandizing or the marketing team will prefer to handle this themselves, we simply click on the delete button out here and it’s gone. Right. Similarly, if you want to add more options, it’s pretty easy to do so. We can click on the drop-down and see a bunch of fields coming out from my NetSuite account. Likewise, if you’re looking for fields on the Shopify side, we can click on the drop-down again and see all the different options coming up. If somebody is using custom fields on the Shopify side, also known as meta fields, our integration handles those as well. Again, that’s on a parent level as well as on the child level. So we will simply ask you again through the same process to pick the saved search that you want to use. We do start out by creating a saved search for you. And then you have the option of choosing the currency and then the corresponding price level that should be sent out as the default price and currency on the Shopify site. Coming into the meta field options, you do have the option of defining the namespace, the key, and then the NetSuite field where the data comes from. All right. Okay, so I think this is now a good point to go and talk about the order right now. This might seem to have a lot more flows or options to load an order in. However, this also contains a couple of more options, for example, bringing customer data, as well as sending customer data from NetSuite to Shopify, and sending NetSuite orders to Shopify. The one that we will focus on today is bringing a Shopify order to NetSuite. And the process of doing that would be to again have a Shopify order in a particular state. So let’s say for example it has been fulfilled or not, in this case, that’s it’s been captured and is ready to be fulfilled. The integration will then go ahead and pull that into NetSuite, allowing you to capture your next steps, for example, fulfillment, billing, and then the deposit stage. However, if you do have certain scenarios where you authorize the card on order creation and would prefer to charge the card after you ship the order, the integration can definitely work with that as well. All of these things would be more or less configurable within the integration and do not require more than a few clicks to get to that option. If you have certain scenarios where you do both, let’s say you have a B2B and B2C scenario, we can definitely work with that as well as I click through the next few options, I do want to focus on this button on the top right which says configure order. And as I click into this, we will note that there’s another pop up coming in which talks about the different configuration related options that may come in. These are simply the different components a sales order might have. For example, shipping, payment, discount, tax, etc. And you’ll notice that we actually prefer to use drop downs and check boxes wherever possible and then pair it up with a text box where needed. As you hover over to the right, you’ll actually see what the field help text looks like as well. And again we try to give you a basic understanding for what that field might be asking you to do, and for anything more detailed, we’ve got extensive documentation on a knowledge basis. Coming back into this section, we’ll see again shipping information. So let’s say for example on the Shopify site, I have something called as free shipping. I can point that out to [inaudible] on the NetSuite side. As I click into the drop down, you’ll see the different shipping options set up on my NetSuite account. Again, these would likely be different from what you have on yours. And if you are looking to set up more options, you can go ahead and add them in [inaudible]. So let’s say a customer sees standard shipping. You can point that over to FedEx Ground. Let’s say they see expedited. You can add that over to FedEx Overnight for examples. Right, this is simply a one is to one logic, but if you do have any more parameters to consider, we can definitely work with those by adding in more advanced logic to this. Likewise, you’ll notice there’s similar table for payment and discounts as well. We do have a couple of unique ways of bringing in discounts to NetSuite and also tax. I think this is one of the unique offerings of our integration where we do help you reconcile the tax amounts between Shopify and NetSuite by overriding what NetSuite calculated in terms of the tax rate. We will still expect NetSuite to calculate the tax code. However, if NetSuite fails to do so, you can provide a generic tax code that should be used for situations where NetSuite said that the order should be nontaxable, however, Shopify actually had tax against the order. So in that case, we would use that generic tax code that you provide. In my case I provided the 12909, and then add the correct tax rate from the Shopify transaction. For the folks who have GST or VAT for their transactions, we do have the option of deducting that tax before loading the order into NetSuite, and then you can have NetSuite reapply the taxes and bring it up to the right amount. There are a few more settings, but I think we may have been able to accomplish the objective [inaudible] demonstrating the user interface. I do want to switch in and show something as we call the field mappings for the order flow as well. Again, this data is coming from Shopify to NetSuite. And we will be able to see the different elements that are already set up as part of the integration when you install this, as well as some of the options that you can easily modify as you go along the way. So let’s say, for example, we’ve got some basic information that the integration needs in order to be more effective for you, and then you’ll see other information that your transactions should ideally contain. Going back to the previous example where we looked at the product information, you can add in more mappings of your own. So for example if I want to pull in let’s say note from Shopify, I can take the note and pass it over to the memo field within NetSuite. And these are all as you noted type aheads as well. We do have another option of mapping within NetSuite. It’s called as the NetSuite Assistant, and it’s typically used for importing data within NetSuite where we will [actually?] pull up on NetSuite transaction form. Or also you can view this as you configure your other internet suite. Again, the goal is to make sure that you don’t have to navigate through too many windows. I can just demonstrate what this process would look like again. So let’s say, for example, we’ve got the Shopify note field, and we want to point it say the memo field out to you. Do note that as I make my next click, this field out here will get populated. So I’m going to quickly click into the memo field on the NetSuite form, and you’ll see memo will set up out to you. And as I’m done, I simply hit save and close. What if I want to save my [current?] progress and continue, I click on the save button out here. All right. In terms of some other elements that I would love to talk about is customer management. So as long as the email address between the Shopify transaction and the customer and the NetSuite customer record are the same, we will reuse the same customer record for you. If you would prefer to not do that and make some changes, it’s definitely configurable on how you apply those. Let’s say, for example, you’ve got the same customer across different Shopify account altogether or different natural subsidies, I do have the option of adding additional logic or identification parameters for the customer. The order flow again will not stall if there’s no customer in NetSuite. We will still charge through. We’ll create the shell or the skeletal record for the customer, and then go ahead and create the rest of the order. And then there’s a dedicated customer flow right here, which is going to go ahead and bring in the rest of the information from the customer record in Shopify, things like the customer tanks, the customer address, and any other fields that might have been set up out there. As part of the integration, we do support the ability to edit transactions within Shopify. Again, Shopify recently provided support for this. And if you want to edit a transaction within Shopify, we would be able to pull those edits down into NetSuite as well. I do want to put in those small caveat that your NetSuite transaction should have ideally not been [inaudible] by that stage, or have been sent over to the shipping service because that might cause you a little bit more process-related troubles. Again, no issues between Shopify and NetSuite on a PR integration level at that stage, until you then try to fulfill the transaction. As part of the other process, we do bring in some transactional information into the NetSuite auto. This could be things like the transaction ID, the authorization code, the captured amount, or the authorized amount, as well as the payment gateway that was used. This information is housed into a custom record on the NetSuite sales order and is something that I would typically DMS preferable but not critical. So if you feel at some point of time that the information might be a little sensitive for the sales or for your NetSuite reps or your service reps, you can definitely turn those flows off. And the process of turning a flow on or off is again, pretty simple. Think of this as a giant switchboard with multiple regulators. Certain flows can just go on or off, whereas certain flows can be scheduled as well. The auto transaction is coming in from Shopify to NetSuite. And [other?] creation are going to be real time. You do have the option of batching them up for various use cases as well. So let’s say for example if you prefer that you get your transactions every 30 or 60 minutes in that case you can definitely control that. Now, just to show you how we can turn a flow off. Again, just we’ll click on the button out here which is on and again clicking on that will give you a popup asking you to confirm if you want to turn that flow off and we will click on yes and the flow has gone off. Let’s say that we want to control the schedule for a particular flow, you can click on the three dots towards the end again and click on the schedule button and we’ll give you a popup to select your time zone. So let’s say that I am in Pacific but let’s say that you want it on this every 30 minutes, you can select the flow to run every 30 minutes. By default, we run this every day but if you would prefer to choose that a particular flow runs between 7:00 AM and say 5:00 PM you can definitely make that work as well. Again, that’s probably not right for the flow in question but I just do want to show you how to set up these schedules. It’s again definitely configurable by the user. We want you to control these options, we want you to own these as you move forward and make changes as your business processes evolve as well. All right. We’ve spoken about bringing an order from NetSuite– sorry, from Shopify into NetSuite and in the same case if you have certain older customers or other processes which are loading data or sales orders into NetSuite for you and you prefer to see them in Shopify as well you can send those transactions from NetSuite to Shopify. Again, the key thing out here is that the system which captures or takes the order should be responsible in some way for the payment authorization of the capture, and in the same way if the customer record needs to be found it would be running off the email address as well. Okay. We’ve spoken quite a bit about orders and customers and I think now is a good point for us to go back and talk about this fulfillment piece that we had bypassed earlier. I did create a shipment in NetSuite against a particular transaction and I did go into the integration and quickly triggered this flow off as well. So this information should now be in Shopify. All I need to do is go back within Shopify and take a look and we will see that the order status should have ideally changed from unfulfilled to fulfilled and it should have a tracking number as well. And that’s changed and we will also see a tracking number out here. Again, this is not an actual tracking number but you might see that it still has a hyperlink and that’s because I kind of gamed Shopify into thinking that this is a UPS transaction by putting 1Z at the beginning of it. And similarly, as your customers get their email, Shopify will translate the shipping carrier and they can do a one-click link as well. If you happen to be using certain unique shipping carriers which may not be within Shopify’s definition, the integration definitely supports you sending in customized carry out as well as tracking URLs to Shopify. It’s pretty neat to have at that stage especially when you have LTL shipments for B2B or larger scale buyers. All right. Coming back into the integration, the next step out here would be to cycle down to the billing event. And depending on what your NetSuite systems and your processes are. We do have the option of creating a billing record in NetSuite for you. So again, if you prefer to bill by creating a cash sale within NetSuite, by all means. If you prefer to bill NetSuite using an invoice, again, you’ve got the option. If you prefer to do both, you can definitely run through those as well. Again, the key differentiator is the presence of a payment method on the NetSuite sales order, again, from what I’ve understood. And if there is a payment method defined NetSuite will not typically allow you to create an invoice against it, but the default process would be to proceed by creating a cash sale. So you do have the option of running both configurations in again, for the B to C as well as B to C– sorry, B to B environment that you might be running out of the same Shopify store. If you happen to choose the invoice billing mechanism within NetSuite, you do have the additional option of getting customer deposits created. And natively whenever the NetSuite invoice process is triggered, we will go ahead and apply the customer deposit through that particular invoice as well. All right, and again in those B to B scenarios where you captured or rather would prefer to capture funds within NetSuite, you’ll have the option of going back to Shopify and letting Shopify know that the billing events were completed. Otherwise, Shopify will always think that it’s in a pending state. So that does cover quite a bit on the billing side of things. I do want to talk about an image at next step that talks about how you can reconcile or post these transactions in NetSuite. Let me actually just find something for you. So we’ve got a customer deposit and as we pull it up, we notice that the status of this customer deposit is not deposited. Now, in this case, that’s how we had set it up at least within my integration and most of the merchants as well. And when Shopify or your payment processor releases a report either on a daily or a weekly basis, we will be able to take this deposit and put it against a specific account of your choosing. That process is accomplished through a unique add-on within the integration called the payout add-on where we can go ahead and deposit the sale customer deposit and at the same time we will create, well again, the NetSuite deposit records. So these are slightly different in terms of it. The names are awfully similar but it will create a NetSuite deposit record. NetSuite deposit records typically allow you to go ahead and define cashback as well, so if there were any fees against a transaction. So let’s say that this transaction was for 16.85 in this case and you’ve got, say, about 80 cents in fees. At that point in time, you will go back into NetSuite and create a deposit for an aggregated list of transactions, however, this particular line will read as 16.85 and then the cashback against it to reconcile the fees would be the 80 cents. So you will see the 16.05 against that effectively. However, it will all be aggregated across the entire payout report. Again, this does take away a lot of hassle of figuring out which of these transactions went through, were paid out, had a data variance in terms of the tax or whatever else or let’s say Shopify paid you less for a transaction than it should have for some reason or if there are any disputes as well. All right. So yeah, I mean I think so far we’ve spoken about the genetic catalog managements sending in information from NetSuite to Shopify for your product data, images, inventory, price, etc. Then we spoke about the order to cash to process and actually doing the recognition for that through the payout process. And I think the next thing that we should talk about is the less than ideal part where somebody might request for a refund or a cancellation. The one thing that I do want to talk about is that these flows are designed to be bi-directional so both of them, the refund as well as the cancellation. So you can actually trigger them from either of the two systems. So let’s say that somebody calls in and says, “Hey, can you please cancel my order?” You say, “Sure thing.” Go ahead and cancel it in NetSuite. We go back out to Shopify and cancel it as well. If you’ve got an app connected to Shopify which takes care of this in some ways and it happens to cancel the Shopify order, we will come back into NetSuite and cancel that for you as well. If your customers are asking to cancel a particular item out of say 5 or 10 of them on the Shopify order, you might want to leverage Shopify order editing. Again, that’s pretty much why the feature in Shopify was developed and released and in that case, we’d expect that you make the changes within Shopify, handle the payment changes, and then once you do that we will come back into NetSuite and update the NetSuite transaction. If there was a customer deposit created and the Shopify order was now edited to a lower amount, we will create a customer refund against it for that balance amount. If there was an additional transaction on the Shopify side which increased the amount of the transaction, we will go and create another customer deposit for you as well. All right. Again, that’s the cancellation aspect and kind of did bleed into the refund process. So again if Shopify does happen to trigger a refund, we will create an process on the NetSuite side. So again depending on how you eventually build the NetSuite order through cash sale or an invoice, we will create a cash refund or a combination of a credit memo and a customer refund to close it out. And these processes could also be originated from NetSuite. So if you want to create the refund within NetSuite again as a credit memo or as a cash sale, that’s perfectly okay and we will go a cash refund. That’s perfectly okay and we will go ahead and push that out over to Shopify for you. All right. So yeah, I mean there’s a lot of content. There’s a lot of use cases that can be configured. I may not have covered every single configuration of this within this session today but if there any unique questions or unique use cases that you need help with, please do feel free to reach out through the chat or even reach out through our support lines. I’m quickly going to talk about a few more things that you might eventually see at some stage. Again, one of the more common ones is external fulfilment, where you’ve got an external shipping app or the third party logistics system that handles the shipping for you. At that point of time we will let the app provide the tracking number in that suite, and then we will pass it over to Shopify for you. If you happen to use any recurring orders or subscription management apps on the Shopify side, we’ve definitely worked with those in the past, as well. If you’ve got any returns management apps that automate the return, and receipt, and refund processes for you, we can definitely work with those, as well. Again, some of these might require us– given that those were external apps, as well, we might have to move outside of this app, as well, and leverage features within the larger platform that this entire creation is built on. Again, I always like to say that almost everything is possible. Quick couple of things that I’d like to talk about now is just some basic user management, where you do have the option of defining the different users who can use and access your integration account. you’d see that– let’s say that I’m the owner of this account, but I’ve setup one of my co-workers as a monitor, and then yet another one of my accounts is managed. So the different side here is I have one account, but I access it from different places. So I might want to give myself the ability to make changes, no matter where I’m logged in from, however my co-worker, who’s not a technical resource, shouldn’t be able to go in and click a button which might change or break my integration. So you do have the option of providing view-only access to different people within your organization, ideal when you’ve got folks who are on a need-to-know or a information-only. And the advantage of that still is that each of these users can now setup their own notifications, if something were to go wrong. So let’s say, for example, John wants to know when an order did not hit next week. He can go in and click on the dropdown menu and then see the corresponding flow. Again, that’s probably somewhere down here. And then he can choose also to be notified, if a connection happens, to go offline. So you do have a little bit more control out there. Each user can setup their own notification preferences, and the emails will need to go to their specific email address that they use to create their integrator IO account. You can have an endless number of users added to an integration. Again, we always err on the side of caution out there. Don’t put too many cooks into the kitchen. Yeah, I think that’s pretty much it. Everybody, this is probably a good time to take questions, if we have any, but that’s all from my side. Okay. Great. I actually have a few more slides before we wrap it up, and this should give our audience enough time. If they have any questions, please type them in the chat window. So let me see. Am I sharing my screen here? No Let’s see. [silence] okay, yeah. So yeah, before wrapping it up, I just wanted to give an example of a customer case study. So Enviolo is a European a bicycle component manufacturer and as a part of their brand experience, they were offering after-sales service parts to bike repair shops via Shopify, so that their customers could easily repair, replace their bicycle components. And then their problem was that their back-office ERP was not connected to Shopify and their staff had to manually process each single incoming order. So this month, they need to create a profile in NetSuite, one in Shopify, and then manually copy paste order information between the two applications for fulfillment. And this process creates a slow error-prone fulfillment process and also degrades the customer experience. And in addition to that, they also didn’t have visibility into the availability of parts. And this often caused them to revisit orders and go back to the customer, sometimes do cancellation. So as a solution, they implemented our Shopify, NetSuite integration app, and then they start sinking in the key information. And with this, as a result, they were able to achieve past a current real-time order processing and they gained visibility into inventory levels, all leading to better customer experience. And they were also able to free up their stuff from doing manual order processing work and they were able to focus on more important tasks. And so if you’re interested to learn more details about how Angular leveraged our integration app, we actually recently did a webinar with them and also a case study, and you can access all of this information on our website on their resources. And just to– yeah, finally, I also would like to mention that with Celigo’s iPaaS, in addition, to integrating Shopify and NetSuite, you can automate your whole order to cash business process end to end by integrating marketplaces such as Amazon, Walmart, 3PL providers for fulfilment, point of sale solutions for your storefronts, customer support applications, payment gateways, and CRM, and more. And, yeah, so we also have another last webinar in this series coming up for Amazon. So if you’re also selling on Amazon, please register for the webinar on our website. And then I believe this brings us, yes, to the end of this webinar. So yes, thank you Mannan for the excellent walkthrough of the product. And let me see here. So, Mannan, there’s a question for you. So we have several Shopify stores configured to NetSuite, is it possible to copy the settings of one Shopify store and to another one and do the minor changes? So we don’t offer that at this point of time. It’s scheduled somewhere for the end of the year. But again, if you’ve set up one, the other one will take almost no time to configure. Okay, there’s another question here. So if an item is canceled in NetSuite on the order. Do they need to process a credit back to the customer through Shopify? Or if they cancel the item in NetSuite, will the cash sale be generated and then the customer will only be charged for the items fulfilled shipped? Do you have any information on that? Yeah, I mean, I think that’s going a little bit deeper into the process. Ideally I’d like to say that if you have charged the card in Shopify, you should make sure that there’s a NetSuite cash sale against it as well. If you have only authorized, you will then make the change on the Shopify order to make sure that Shopify knows that there’s a change. I do not believe Shopify considers partial cancellations for one of the items. You do have to do it to edit on the order. Okay. Let me see. We have actually a bunch of questions here. So another question is as long as the order goes through Shopify, the payment capture, payment application, and reconciliation will be handled through this app even if the order payment originates with Amazon, Apple Pay, Stripe, etc? So again as long as Shopify triggers that information, it’s got an order accepted and created, we can definitely bring it down into NetSuite. Most of these payment gateways are directly integrated into Shopify so you will not have to go much out of your way to reconcile or rather view the payment method on the Shopify site. That’s only if you absolutely need to. Most people that we worked with in the past just want to know whether it was credit card or PayPal or Amazon Pay, etc. Okay. So another question is do I need technical stuff to maintain the integration app? I can take that one. So our platform it is built to be used by both business and technical users, and as I mentioned before, so we have an intuitive user interface, and our dashboards are easy to use. So no, you don’t have to have technical stuff, and in fact we have many customers who are e-commerce business managers that also manage the integrations themselves. So we’re out of time here. I will just include one more question, and then for all other questions please reach out to us off line, and we’ll get back to you. So can I integrate multiple Shopify stores and update product information from NetSuite? Is that something you can answer? Yes, definitely. So if you do have multiple stores integrated via NetSuite account, you’ll still be able to control the data within the same NetSuite item. Again, do remember that if it happens to be regional specific information, you’d probably have to create a second field in NetSuite to send the data out to Shopify. Okay, great. Yeah, we are already past our time, and we’ll be ending our presentation here. So thank you everyone for joining us today. And as I mentioned, please reach out to us with any further questions. Also visit our website at celigo.com. Thank you.