Name: Integrating NetSuite and Amazon
Uploaded: 2025-04-09T18:16:04.458Z
Duration: 1 h 4 s
Description: Integrating NetSuite and Amazon

Transcript for "Integrating NetSuite and Amazon": Okay, everyone. Welcome. We are going to, just wait another minute for folks to join. Thank you, everybody. Excited to see lots of folks here, and, we'll start in a minute or so. We are gonna go ahead and get started. Okay, everybody. Welcome to the webinar on the ins and outs of integrating NetSuite and Amazon. This is gonna be a deep one. This is, the fourth webinar of our ins and outs series of NetSuite, integrations. The next one's gonna be on EDI, but, it's been very popular. So thank you for the hundreds of people who have been joining this on a regular basis. We are recording this, and, we are also taking questions. So please, leave any questions, in the q and a section or in the chat, and we will, go ahead and take that throughout the course of the event. My name is Rico Andrade. I'm the general manager of the commercial segment here at Ziligo, and I'm joined by Brent Creech, who's gonna our solution consultant, who's gonna be going to, disclose in quite a bit of detail. So for those of you who've done this before with us, we are quickly just gonna do some introduction. There's some new folks here that haven't seen this before. But then if you are familiar with Saligo and Saligo, the platform, do stick around because we're gonna be covering, more and more advanced use cases as we go. And we're gonna cover things from MFN and FBA, vendor central, Amazon Pay, and so on, and so what we're seeing, from our customers directly. So let's start with a quick poll just to get a a feel for, the products that, folks are using and when we're, what we're gonna be focusing on. So this is just a partial list of some of the things that we're gonna be talking about. Go ahead and take a second to just share which ones you you might be using or have interest in. Okay. Excellent. Very interesting. Yes. FBA, at the top, vendor central, yeah, seller central is something that's very common for us. So, this helps us shape, what we're gonna be saying. And so please, as usual, it's very important that we are providing information that's helpful for you all. So if you do have feedback, it's helped us a lot, you know, shaped shaped this webinar a lot. So, please continue doing so. So to quickly just go through, we have a ton of, ecommerce customers, retail customers, supply chain manufacturing. I wanna say that we are probably the largest iPaaS at this point that, in in that whole ecommerce product supply chain space. Probably, we we have more than 3,000 customers who are specifically using us for these use cases, so we've seen it all. You know? And so we've definitely seen everything that is on the Amazon side, and this becomes even more important now with all the changes that are happening in the world as people need to adjust. Like, the topics that we're gonna be talking today are, actually, incredibly relevant, for people to be able to navigate these choppy waters. So we do have themes. This is the same themes, from Shopify last week, but it feels even more, the last time we did the webinar, but it feels even more relevant, today, as people are having to adapt their, their whole operations, with, all the tariffs that are going on. But really is you need to be able to create a system, an integration strategy that has flexibility, scalability, and efficiency. And, of course, you know, it it's part of a much larger story. Right? Amazon is a a small piece in a big component of your entire, operations. And so, hopefully, you know, there'll there'll be some additional information or nuggets that you'll learn in terms of, how these specific integrations can fit within these holistic processes. So just as a basic introduction for the folks who haven't been here before, The, there there are several ways to, do Netsu integration that we see, and there's a lot of folks here that, specialize in these direct, sweet script integrations, which, they're really great, but you do need quite a bit of technical resources. And probably one of the biggest disadvantages of them is that you need to, create functionality out of the box. So what happens with data monitoring? What happens if one of the endpoint systems is down? What about, you know, exception handling and so on? These are all things that you have to code directly, and also, when you have to make an update, you kinda have to relearn exactly what you did and and do it all over. So there's a place for, direct integrations. It's usually when it's a very static and simple flow. But once you start doing something that's a bit more scalable, you really wanna move, a little bit beyond there. The next level is, you know, lots of point to point purpose built connectors. These are excellent, to get you up and running. They weren't typically designed for flexibility, robustness, and management as an integration platform. That tends to be the limitation. So oftentimes, if you do get those, either they have to be very, very specific to the the processes that, come out of the box, or you're gonna need to supplement them with additional custom integrations, beyond that. And then, of course, there is the iPaaS option, which, gives you a centralized hub, in a a single system to manage all your integrations. It does have, out of the box functionality for things like air managements, guarantee data delivery, a lot of governance, issues, especially on the Saligo side, you know, concurrency and so on. And and becomes really important when you're talking about the building and the not just the building, but the management of the integrations in the long term. You know? Because you wanna be able to manage these integrations in a way that, don't require purely technical expertise, but also functional expertise, can can, can take care of that. So Soligo uses a combination of these strategies within the NetSuite ecosystem to be able to handle everything. You know? We have the best in class, integration apps, which we'll talk about today, that handle the 80% of the use cases for things like, you know, Amazon Seller Central. They're used by thousands of customers, and it's a fully managed integration with a lot of, built in logic, out of the within the box. And, it really accelerates the development and the management of a lot of these integrations. But it certainly, you know, does not handle all the the the use cases that are necessary. And so to be able to handle all the unit use cases within our ecosystem, we have, integration templates as well, which are prebuilt integrations, but they're not fully managed, but they are fully customizable that allow you to, do certain common use cases. But, of course, you have the full integration platform when you need to customize any, business process, or, integration you need without necessarily needing to go into the code and still having the whole underlying infrastructure that's gonna help you manage these errors and correct these errors and change, and manage them, into the long term. And so for those of you who haven't used Allego within the NetSuite ecosystem as well, there is, we do have a technological advantage in terms of how we interface with NetSuite. We don't just it's not just purely, you know, API based. We have a that, enables us to take make full functionality full use of the safe search functionality, enables us to do dynamic lookups, enables us to do, concurrency controls, and and things like that in a way that, no one else can. So, it's not just that, you know, we have the prebuilt integrations and, you know, certain custom NetSuite specific functionality, and, that we're also NetSuite agnostic. We don't need it doesn't need to be NetSuite. But because we are the giant in the NetSuite ecosystem with over 5,000 customers, we have developed, specific, interface with NetSuite that, enables us to do things that take advantage of NetSuite in ways that other platforms can. So this is all by way of introduction for those of you who haven't, known Soligo yet, but, we're gonna jump into the presentation. And, you know, this is where it all starts. This is the most important business process for any, product based company. It's the order to cash process that takes a customer order all the way through, revenue. And, everything starts here and then expands from there. So I'm gonna pass it on to our expert, Brent, who will take it from here. And, please keep the questions coming. Thank you. Awesome. Thank you, Rico, for the introduction. So it's a pleasure to make everyone's acquaintance here today. By way of introduction, my name is Brent Creech. I'm a solution consultant from the Soligo side. So, really, my role within the organization is to work with our different account management teams as well as account executives and, you know, cross functional teams like marketing and such, to work with our customers, and, you know, prospective customers to define what their integration needs look like and ultimately define, a successful integration solution that meets their requirements. Now I have a lot of experience in in dealing with ecommerce integrations in general, but a large part of that involves marketplace integrations. Probably most prominent in that, most common being Amazon. But also seeing a lot of the other flavors of Amazon integration like Amazon Vendor Central pay, etcetera, like what we had appearing in the poll. So, I will be leading the majority of the, the presentation here today as will be, you know, one part presentation through slides and then, kind of the second half, we'll actually be looking at a demo of the platform exploring some of the different, peaks under the hood, if you will for these specific solutions. And I believe it was Manuel. There was a request to look at the RMA integration a little bit more in-depth. Don't worry, I'll keep that bookmarked and we'll see if we can tackle that later on. But jumping right into things, you know, Rico gave a brief explanation of how important this order to cash process is but I can't stress enough how, how important this is for a product space organization to automate. A lot of the smaller businesses that may come to us to automate this process, they'll consider how much we can automate within this. Right? They may be thinking of just specifically, eliminating the opportunity for order duplication. But we can take things all the way from, you know, product information management, maybe even extending the functionality of NetSuite to act as an omnichannel pin, all the way through settlement reconciliation based on the cadence we receive those settlement reports. And just as Rico alluded to, right, automations are invaluable, in times of uncertainty like what we've seen recently. So it's important to have a reliable accurate solution, that can essentially act as the infrastructure supporting your day to day business so teams can explore more creative ways to cut costs which may even involve, more automation in the future. But moving forward to the next slide here, we wanna talk about some of the more standard use cases before getting into the little a little bit more of the advanced or complex, if you will, a little bit later down the line. So I think one that all of us may be familiar with even if you're not selling through Amazon Seller Central, it's likely that you've purchased a product at some point in your lifetime, through their marketplace. And, this is, believe it or not, one of the most common integration scenarios or conversations that we have, for our different users and customers on a daily, if not hourly basis. Right? And it's important to understand this process in its entirety as Amazon has had this effect on consumer behavior, and expectations where there are unique challenges that businesses face now as people want things at their doorstep, you know, before their head hits their pillow at the end of the night at this point. Right? And a lot of those fulfillment needs or fulfillment requirements for organizations can be cumbersome to deal with and challenging and ultimately supported by integrations and automating these different business processes. Alright. But jumping into things here, I want to take a brief snapshot peek at our Amazon NetSuite integration app. Because we have had so many conversations and solved the problems, challenges between Amazon and NetSuite, so frequently at this point or so many times, we've been able to deploy an out of the box solution that covers a lot of the core order to cash use cases while still allowing for flexibility as a businesses grows to include other pieces of embedded business logic to handle scenarios like advanced reporting based on fees or even, even alternatives to how they choose to manage their inventory with FBA. But the benefit of this piece will will be the fact that this is fully managed. It's easy to to deploy, so there's a faster time to value as a lot of the mappings and, foundational pieces of this integration are already laid out for our users to deploy in their own environments. So you can quickly automate that order to cash selling process. But, less about our specific solution and more about the general processes that we see automated in a frequent, or on a frequent basis, I wanna first touch on the fact that there's two sides of the coins we're selling through Amazon Seller Central. We have the fulfilled by merchant side where, you know, you as the seller would be handling the fulfillment of the orders that are being processed through Amazon, but there's also FBA. But focusing specifically on the FBM side of the coin first, I just wanna, talk about this as while there are less unique challenges to solve due to the fact that, it's it's more in line with your standard ecommerce workflow, it's more comparable to that, I would say. There are still a few unique challenges to Amazon specifically. And apologies in advance because I'll be saying unique challenges or unique requirements a lot as we talk through the different flavors of Amazon to NetSuite integrations. But within this, you can see that we're able to support a lot of the functionality we already talked about in and out of the box fashion, where we can automate things like orders being, brought in from Amazon on a, you know, a frequent cadence so that you have up to date information and you're able to predict what type of, selling frequency, that you need to process through Amazon. But additionally here, while we're taking this all the way from order creation to settlement reconciliation, it's important to consider the additional pieces that may be tied into an integration between Amazon and NetSuite. Because while you may be technically selling through the merchant fulfilled channel, you may still spoke off from NetSuite to handle some type of, three p l relationship who actually handles the shipment of your, your your finished goods. So with this, it's important to have a solution that can be agile or flexible and support not only a point to point connection between Amazon and NetSuite, but also to any, three p l via API or even if you've got a trading partner relationship or exchanging EEI documentation. It's important to have a integration solution that can support those different means. Alright. But talking about the flip side of the coin being FBA, I think this is a fun one and I think this was the highest result as we had seen it on the, the poll for, attendees having experience with FBA or maybe even saw it through it. And this includes a lot of drastically different challenges compared to FBM as Amazon is going to be handling the, the storage and fulfillment of your goods that they're actually selling to or you're selling to customers. So there's gonna be a lot of overlap here like things in terms of, item and and product syncing or bringing in orders. But on that note specifically, we actually see that users choose not to flood their NetSuite environment with with respective, sales orders and item fulfillments that may not be relevant to them because Amazon is handling fulfillment. They choose to skip straight to the point of sales invoice or at least that's the best practice. So that invoice includes all of the typical details you might need like tax information, the actual line items that have been fulfilled so we can decrement inventory as one would expect. Now with this, there again, there's gonna be some overlap for the settlement workflow, getting through reconciliation. But one of the more specific challenges relates to keeping inventory in sync as the source of truth shifts from your own internal warehouse or a separate through deal and instead shifts to Amazon's fulfillment centers. So we see a lot of different strategies to keep inventory in in check or in sync between FBA and NetSuite. But a majority of the, users that we automate this for follow the key workflows that you see here at the bottom of our screen where we're accounting from any inventory adjustments that they may report to us, you know, scenarios where, you know, you you hate to admit it's true, but sometimes the people on the warehouse have run into a bit of stock and damaged it so it's no longer sellable or they've lost something on the warehouse floor or maybe they found it at a different point in time, you know. Hallelujah. But, either way, there are different scenarios that you need to account for that can show up in an inventory adjustment and need to be reflected, to update the available available quantity to sell within next week. Additionally, the inbound shipment process, is is, I shouldn't say cumbersome challenge but it's it's usually a challenge that, businesses come to us looking to solve as there's a lot of different steps involved and you're typically working out of NetSuite, Seller Central, and you really just wanna consolidate the process to one system, which we'll talk about that a little bit more here in a second. Then at the very bottom, Manuel, you can see we have a flow for generating RMAs, specific to the, the FBA side of Amazon selling. This is great because there's really two parts to the return or refund process that we manage with with FBA, where you need to account for the financial portion as it would appear on the settlement as well as the inventory component as it relates back to, the actual return. And it's important here to note that we can also align returns to the damaged or sellable inventory location so that everything's not getting looked back into, sellable goods. You can have a better picture, better insight into what's actually available. So, Manuel, I'll try and make a point to the demo to briefly go through that. But with that, since we're talking about inventory, I wanna make sure we spend some time talking through what that transfer order process looks like. As if you've explored this integration through Soligo in the past, you may be happy to find out that this has actually been completely overhauled in the in the recent, say, year, year and a half, I believe, that this this launched, where instead of creating parent and child transfer orders, we're instead allowing you to kick this process off inside of NetSuite through the creation of transfer order or a transfer order, and then allowing you to manage certain details like the placement plan or selecting your character, still within FBA leveraging as much of the core functionality there, as our users required. But the new solution or the new workflow that we offer even ties things like labels back to the item fulfillments that we generate inside of NetSuite so that you can have a complete tracker traceability for each and every, individual shipment to a separate FBA inventory location that needs to be accounted for. All the way through tracking what's actually been received, through the creation of full or partial item receipts as they're updated by the those receiving teams at the actual fulfillment centers. So that's a, you know, a great little overview. But I think a lot of the, maybe accounting personas or stakeholders in the in the audience today would be curious to learn a little bit more about how the financial components of an Amazon integration functions specific to dealing with settlements. We've heard a lot through our respective conversations that the, reconciliation process for Amazon settlements is cumbersome. It's time consuming. It's challenging to align all the fees, whether they're transactional, non transactional, dealing with an Amazon reserve balance or cost of advertising, etcetera. It all adds up. So we have built out a I'm sorry. It looks like there was a chat here real quick. We all good, guys? Sorry. That was backstage. Yeah. Yes. We're good. We'll we'll we'll take the questions. We'll we'll we'll we'll circle back on the questions, afterwards. Gotcha. Awesome. Okay. Perfect. So talking a little bit about the settlement report, like I said, it's challenging to deal with, but even some of the challenges don't tie just specifically to Amazon. It's more specific to the fact that there may not be a landing spot for all of the data you're looking to pull or pull it off of from that report coming from Amazon. So the the strategy or the route we've taken to solve for this problem is to leverage custom records inside of NetSuite to find new landing spots for those details. So we can even track the settlement fees by SKU, at a transactional level as well as in more of a summary detail so that you're able to build those reports and determine whether or not a product is actually worth selling on Amazon. But also account for and allow for easy mapping for accounting teams to define what transactional or non transactional fees should credit or debit certain accounts, as they hit NetSuite through the creation of a journal entry. More to come there as we will explore that use case or examples of the settlement report custom records once we go through the product demonstration. But, it should act as a a fairly good overview of what we're handling there. But, you know, we talked a lot about Amazon Seller Central to this point, and I wanna make sure we show some love to the other flavors of Amazon and NetSuite integrations that may need to be supported or some of you may be interested in. So with this, some of you may be familiar with Amazon Multichannel Fulfillment. Basically, an offering from Amazon that allows them to act as the third party fulfillment vendor, for any of your your goods to be shipped to their respective customers. So we do have a very similar to our Amazon Seller Central NetSuite offering. We have a fully pre built integration application designed to cover a lot of those core use cases in an out of the box fashion. So if you want to, you know, we talked about building that hub and spoke relationship between, your NetSuite and a three p l for FBM. If you wanted to do something similar from your, your merchant selling channel, your ecommerce platform, you can do just that. And I see that there's a question. So does this require an Amazon warehouse in NetSuite? It doesn't necessarily, although we would likely recommend that you're separating the inventory that you're storing on hand, you know, if you have your own warehouse as well as a your some inventory stored through FCF, or even if we're thinking back to FBA. Ideally, you wanna have virtual inventory locations to track as much detail and granularity as possible. So you can imagine you're you're supporting FBA phone centers a, b, c, d. You would have, fulfillment centers for each or not virtual inventory locations for each. But also, we could lump that all back into one general Amazon FBA inventory, or virtual inventory location depending on what your business requirements look like at that time. But there is a lot of flexibility that we can leverage there. Alright. Another, more common use case that we run into and I think was the second highest hit on the poll was the, the relationship between Amazon Vendor Central and NetSuite for a lot of our sellers. Some of you may or may not be familiar with it. This is more of the relationship where you would be acting as the supplier for Amazon. Right? They're buying your goods to then sell on their marketplace. This is a very similar relationship that others may be familiar with big box retailers where you might even be treating them as a trading partner and you're exchanging EDI transactions. So I will admit that Amazon Vendor Central does have a few different ways to, handle the integration points where, this diagram shows that we're using EDI to do so. It's kind of the well worn path before they had launched the availability or access to their API. But honestly, this is a perfect segue into mentioning the fact that for those of you who aren't familiar, with what Saligo has done in the past year, year and a half regarding our our set of product offerings, we've launched a full fledged, EDI solution called b two b manager for managing not only connections to things like Amazon Vendor Central, but also a long list of the common trading partners out there that you may know may be familiar with like your Walmarts, Targets, Ace Hardware, a few that come to mind. But this allows you to leverage, pre built trading partner connections and also maintain your integrations in a consistent manner whether that be through EDI or through API. There's gonna be a consistent means for maintenance, as it'll all be through one singular pane of glass to look through for integration needs and not needing to manage different vendor relationships with point to point API integrations as well as, maybe a relationship to one of those legacy EDI providers. And if you are familiar with some of the more, legacy EDI providers out there and some of the challenges that we hear on a frequent basis like, unpredictability tied to cost, by volume of kilo character or long times to onboard new trading partners, I highly encourage you to, you know, contact us after the call and we can talk more about how this EDI solution solves some of those challenges and allows you to consolidate your entire integration stack. Alright here. So talking a little bit more about some of the other advanced use cases we wanted to explore. We can transition here where we can talk a little bit about how an iPaaS is able to support a relationship between between some of those prebuilt integrations as the foundation of your order cash automation or whatever solution we're looking at. And then building or leveraging the core platform to spoke off of this and, build more tailored platform flows that's specific to your own business requirements. These are are great because, as I just mentioned, you have full flexibility with what these can can cover. We're only limited by the the boundaries in which the applications we're working with draw for us. So any, you know, any anything or record built out in NetSuite, either native or custom, and any of the APIs or connectivity options offered by Amazon or any flavor of Amazon are fair game to include in a solution, for a platform flow. And while that may sound a little bit more customized and like there's maybe a little bit more attention that needs to be involved in the build process, With a tool like the iPaaS that Soligo provides, there's still a lot of pre built components there that allow you to expedite the time to build a new solution, like some of those templates or pre built connectors or even some of the AI assistants, that are folded in throughout the tool can assist with things like scripting or building out filters, so on and so forth. But, another component related to those the the ease of building, a lot of users don't think about the cost tied to the, the ownership of an integration and with ownership of an integration, there comes maintenance. Right? Sometimes this may involve reaching out to a third party or maybe, you know, this legal as the vendor to, to actually manage an integration and make small changes. But with any solution that you were to build out through Integrator IO, our integration platform, you would have the full capability and access to make these alterations at will. So what this means is as you you grow as a business, you bring on new applications with new challenges and new edits to your business process. We're able to stay agile, and you have that integration strategy as a solution going forward. But we will talk about how, you know, some of these advanced use cases that you see here on the right can relate to your, your Amazon selling relationship. One of which being multi region selling. Right? This can be difficult for a myriad of different reasons there, to name a couple. There's sometimes complex tax considerations or specialized, international programs that need to be accounted for. Maybe the Pan European program where you're selling tire, you're just sending inventory to the fulfillment centers in Germany and it gets dispersed to all of the different countries that you may have marketplaces set up for. So it's important to find a solution or make a consideration, of finding a solution that supports selling through all different types of regions and provides flexibility as well to handle maybe, additional customizations to take care of you order VAT tax as it's folded into the NetSuite invoice or sales order. You even got a template flow which I'll show you here in a second that we can explore a little bit more in-depth. Also, for those of you who maybe doing omnichannel selling or or managing different channels rather than just Amazon specifically, you may be leveraging Amazon Pay as a payment processor or gateway on top of your ecommerce, or merchant selling channel. So with this, while they are very similar in terms of order to cash automation between or, you know, compared from what we've explored with Amazon, what you may be used to or have seen with an ecommerce integration, they do provide a starkly different challenge when it comes to reconciling payments where payment may already exist in NetSuite and so there becomes this cross referencing that needs to take place for what Amazon has actually reported as they have paid to us and what is already been logged inside of NetSuite. And then sometimes there's challenges tied to reconciling the different variances or fees that are still presented at that point, that we have even designed a prebuilt solution for. Again, leveraging some custom records since some of those things don't have traditional landing spots within NetSuite. Another piece here or kind of a more fun and exciting use case that we've seen here recently is the involvement of Amazon buy with Prime. A lot of you may be including a buy with Prime option on top of your merchant channel checkout experience. Some of you may be familiar with, you know, the common ones like Shopify, Magento, BigCommerce, but I I say merchant channel rather than e commerce on purpose. Right? Because there's a new relationship between TikTok shop and Amazon buy with Prime that's added some some even more interesting challenges for reconciling the fees from both TikTok and Amazon as Amazon is still handling the fulfillment and part of the, the payment processing there. But you can see a mock up of what an an example of that workflow may look like where you still need an integration solution to interact with the, the the settlement as well as the, the merchant channel to bring things like your order, and the deposit so that we're keeping inventory in your GL in sync as one would expect or require. The last section or type of advanced use case that I wanted to talk to you before jumping into the demo, Or so relates or or or teases some of the topics we're gonna be covering a bit more in-depth in a part two or a follow-up of Amazon or ins and outs of integrating Amazon and NetSuite, Where I do wanna briefly mention that we are able to work with any flavor of Amazon. Right? So if you're familiar with storing data and Redshift to do advanced reporting or analytics or working with s three or Lambda, those are all options or viable, you know, endpoints, connection points that can be folded into your integration stack or integration strategy as it would exist on our platform. But also for some of those more advanced reports that you're able to pull from Seller Central today, like the Amazon FBA inventory report. We can even work with completely custom records in NetSuite and then define custom workflows to do something like an inventory snapshot comparison where we're creating inventory adjustments after the fact. So even though we have these pre built solutions that act as a foundational layer, you're able to make customizations if that's a specific requirement at that point in time. Alright. Before jumping into the demo here, I see, Rico, you jump back on? Yeah. It might be good for us to take a couple questions. There's a lot of questions coming in, maybe just, before we jump in. So, I think these are related and you kind of answered. How how about transfers to AWD? Transfers to AWD. Right. So, actually, I had a conversation about this on, Monday. So it just requires a separate connection point, where we would be connecting or routing inventory to AWD first before they're actually, storing it and then sending it off to replenish the available inventory for sale at your FBA fulfillment centers. So there's a bit of a different relationship there. The truth of the matter is it wouldn't align perfectly with the pre built solution or workflow that we had talked through. But the beauty of the the integration platform is that we can we can tackle that through custom flows. Can Soligo monitor where inbound inventory is within, in Amazon's DC network? Sorry. Let's look at that question. Monitor inbound inventory within Amazon's DC network. Again, that that likely comes down to just the, the connection methods that Amazon offers. I haven't built out or scoped out that use case personally in the past, but with a little due diligence and review of their documentation, you know, so long as they have the available, you know, options for us to tap in, we should be able to pull that data in similar to any other connection point that we've talked about so far. Okay. The Amazon FBA order flow to NetSuite only syncs orders to NetSuite after the order is fully fulfilled by Amazon. This causes some accounting issues when an order is only partially fulfilled because this will not yet sync to NetSuite. This raises concerns most specifically with month end cutoff orders. Do we have an alternative solution for this? So an alternative solution, again, kinda just comes back to leveraging the core platform. There's not a configuration change you'd be able to make within the prebuilt integration, but by building out a custom workflow that we can likely talk through a little bit more in-depth in a one on one scoping conversation. It's likely we can land on a solution that would work to account for that type of, inventory management. Okay. Last one for now and then let's, keep going. Is there anything that you wanna expand with the NetSuite Amazon RMA integrations? Let's actually let's let's save that for the demo because I wanna we can we can talk about that a little bit more in-depth with the visual example. Okay. Sounds good. And we will, circle back. There are more questions here. We'll circle back after the demo. Perfect. Alright. I'm gonna get one or two things moving around and then we are good to jump in. But, I'll transition this into the product demonstration slide and I get my screen shared to your voice shortly. Alright. We've got a lot of great content that we're going to work through as a part of the demo. We're gonna take a look at that prebuilt solution and what it looks like in NetSuite after you are routing information to and from Amazon as well as a few of those more advanced use cases and how those can all be managed through one platform. Alright. But with that, you all should be able to see my screen now. You know, we should be looking at, for those who are familiar with it, an example of an Integrator IO, home landing page. But for those who aren't familiar, this is an example of what your integration environment could look like in a future state. Right? Where maybe we're we're looking to, you know, put out the burning fire that, you know, the immediate need between Amazon and NetSuite to automate the order to cash process. But then we can begin to spoke off into different areas and solve different problems within departments of your organization who are using different technologies, wanting to do things like business intelligence with reporting and analytics tools or maybe servicing IT service management. Really, the possibilities are endless. At the end of the day, it comes down to if your application has some form of connectivity, it's likely we can tap in and build out whatever solution is needed at that point in time. One second here. Let's actually got logged out of that one, but good news is we can very easily switch over to what we need. We're gonna take a look at an an environment I have that has a lot of Amazon specific integrations. And I think the great place to start is that foundational layer that, that integration between Amazon seller central and NetSuite that we offer in a fully pre built turnkey fashion. So this is the actualized version of that solution where you can see we have different flow groups as we call them that segment the different steps of the typical order to cash process automation. For for those who aren't familiar, flow is an important term to acknowledge or learn as a part of the platform. The best way you can think of it is a category of data moving from one system to another. So a perfect example here, you know, right in front of our face is a Amazon merchant fulfilled order flowing into NetSuite to generate a sales order. Now if you're building this with more of a tailored platform solution, you can fold as much business logic or as many applications for that matter into a data flow. But within the prebuilt integration, usually those follow the cadence of one type of record from point a to point b. But within this, if you are working towards maintaining an integration, you may want to define how the actual values move from one system to another. So it's important to understand, you know, what control or what levers you have to pull on to make for changes as your business encounters new challenges. Right? Maybe you've added a new custom field in NetSuite that is important for a report that your boss is demanding to have his eyes on by Monday and you need to get this fixed without involving a third party. Great news is with Zaligo, you know, you don't have to be a developer or someone from IT to come in and make a type of, of alteration like we're gonna see here in a second. You can be someone from accounting operations wherever within a business so long as you have access to the platform, and that the, kinda the the authentication to do so. Right? The, the different permissions or the levels of permissions that you have, you'll have the ability to make these edits as needed. And this can become as simple and easy as a quick matching exercise where if you just need to align, shipping address information or billing information, it's just, you know, simple one to one transfer. But we can also handle additional scenarios where maybe you need to do dynamic lookups or translations between values, which we'll take a look at a little bit later on. But for the most part, this should just be a point and click interaction where you're choosing the field we're pulling from point a and defining where that needs to live once it makes its way to its destination being NetSuite. So, again, a very important component of maintaining an integration, which you may also be wondering, how will this run? Right? When will I get the data? When I need it to be there? So you are able to define preset frequencies of up to every fifteen fifteen minutes and have control over when it starts, ends, what days of the week this runs. But for something as as important as bringing in orders, it's likely you're gonna wanna have this information on a bit more of a frequent basis. Right? As close to real time as possible. So we can have this run as as fast as up to every five minutes. And then even if you wanted to get more granular than that, you can do so defining the the days of the month this runs, is the week, what hours, etcetera. The last maintenance component that I wanted to touch upon is specific to the prebuilt solution where there's a lot of user friendly settings to make, different business logic changes like how we choose to track shipping amounts, gift track amounts or if maybe you're selling on Amazon FBA and you begin to or you encounter the new requirement of assigning lot or serialized numbers to your invoices as they come from Amazon, you can very easily click a box and choose to handle that as in a first in first out methodology or assignment. Right? So a lot of different bits of business logic that you can easily alter, even being someone who's not a developer or has experience in IT. Alright. So rather than spending the entire time within the integration layer, I actually want to show you some of the results or records that you may be interacting with inside of NetSuite, something you may be more familiar with. Right? So we do have an example of a few of the records tied to this order to cash process. But taking a step back and thinking of the master data that needs to live inside of Amazon before you're actually able to sell orders, right, Would be, managing product information. So I do wanna point out that we've designed this solution to allow you to extract as much pin functionality out of NetSuite as humanly possible. So anything custom or native to any of the item records that you have listed for sale through Amazon, will be available to pull from NetSuite, place wherever you need them to live inside of that Amazon product listing. That includes things like descriptions, images, or even any custom fields that you may have folded in. And even the prebuilt solution will take care of some admin work in NetSuite to store some details like the ASIN number or allow you to control the category in which this product is listed. Or if you're you're dealing with item aliases, you can even have multiple ASINs tracked back to the same core inventory item in NetSuite. But once you have items for sale through Amazon, you can then begin to start accepting orders. Obviously, assuming inventory is in sync at that point. But, with this, once your order was brought into NetSuite, all of the mapping decisions that you had defined previously through the implementation or maintenance of this integration play out as one would expect. So tax detail, order totals, maybe even the assignment of a default customer are all tracked in the way that you had defined. So and all of the bits of information that you would expect to be there, exist in NetSuite. Right? So your your order line items. But as the order is accepted, it's at the point where it has been invoiced, and now you're waiting for that settlement report to be, released to you or made available by Amazon. This is when we can have that settlement section or that settlement workflow kickoff to then create a custom record of each transaction from that report inside of NetSuite. So a lot of those details that didn't previously have that landing spot now do, and you have the the data available to you to report off of. So if we wanted to like that that example I alluded to earlier, if we wanted to look at a breakdown of the fee amount by fee type by SKU to determine whether or not a certain SKU was even worth selling through Amazon Marketplace. You can do exactly that. And then you even have an an audit trail for all of the transactions that exist in NetSuite, tied to that that transaction from the settlement report while also providing a summary level view of this. So if you just wanna view the fees in aggregate, or even the different fee types in aggregate, you can do just that, while also maintaining a kind of a 10,000 foot view over the success of that settlement reports processing. So if there needed to be any specific attention to identify why a refund was unapplied or partially applied or payment the very same, you can do just that through the power of these custom records. Now custom records are great, but admittedly they're non GL impacting. Right? So how does this actually affect your books? That is through the creation of a journal entries. This is kind of the final or capping step where we can align anything like the Amazon reserve balance or cost of advertising, cost of storage, etcetera to credit or debit any of the GL accounts that you may want it to hit. Alright? And it's very easy for accounting teams to manage this as well. You know, if you wanted to keep track of a new fee that, that Jeff Bezos has added to the the long list, you can very simply come in and define the exact fee we're looking for and which account that needs to hit as it would exist on the the next week journal entry. That applies for both non transactional and transactional fees. Really quickly here, I wanna click into the FBA return section. Because while the the settlement report process will handle the refund component of a return and well, I know it's important to talk about what that flow actually looks like. So this is a comprehensive flow that will create both the RMA as well as the item receipt to close out the RMA all in one fell swoop while going back to how you want that inventory to be tracked, allowing you to define different, virtual inventory locations in NetSuite to track both sellable versus damaged returns. So there's a lot of control, and options there. Hopefully, that answers your question, but if not, we can we can circle back. Alright. So that is a good peek into the prebuilt solution. I wanna make sure we have time to go through some or one or two advanced use cases and then circle back for some more questions here. So very quickly, if you are gonna be building out, your own tailored platform flows on our platform, it's important to know what resources are available to you to jump start that building process. So I encourage every new user to explore our integration marketplace where you can see prebuilt resources for not only connections between Amazon and NetSuite, but really any other application, that that we may have a prebuilt connector for. So for some of the different flavors of Amazon like Amazon Pay, s three, Seller Central, or Vendor Central, you can see that we have a lot of these prebuilt templates or even these integration apps that can, lay the foundation for the the the full customization that you may want to make for your eventual solution. So even as an alternative to connecting to Vendor Central via EDI, we have a template here designed to handle those API connections out of the box. Right? And even if we come back to this, you're going to maintain a lot of the same, maintenance or touch points similar to what we were looking at within the integration app. Like, if we wanted to map invoice detail, it's the it's the same user experience from that point. So there's a consistent means in which you're controlling how data moves from one system to another. And, there's less enablement for managing different solutions throughout your your tech stack. Alright. The last thing here that I wanted to touch upon is fact or more of an art of the possible example. Right? I don't have a flow for this, but tying back to that example where we wanted to map to a custom record in NetSuite to keep track of the variance between what we have tracked in in our virtual inventory location and what the actual three p l or Amazon FBA is reporting to us. We can process the details from that report looking at an inventory snapshot at a given point in time, choose to track something like the variance and then have a custom workflow in NetSuite or even another integration flow to create the inventory adjustment in an automated fashion and then, basically mark this record as archived or already attended to so that you can, you know, alternatively manage inventory in a way that makes sense more for your process. But with that, that gets us through what I wanted to cover on the demo today. I'm gonna go ahead and stop sharing screen and actually pass things back over to Rico for a wrap up. Okay. Thank you, Britt. We do have more questions. So let's let me just close out a couple of details, and then, we will, get to the questions. But, yeah, I mean, flexibility, on these dynamic processes are super important, especially, in the times that we have right now. So it's not just about, building the integration and, you know, kinda getting it through, but it's really thinking through about the whole life cycle of the of the integration from start to finish and what do you have to do if you have to adapt your your systems very quickly. Before we get to the q and a, note that our next, webinar is going to be on, EDI, and, NetSuite. So, join in. We also have, give me one second. People wanna see the screen. We also have a connective webinar I mean, commerce summit. This is pretty big. We have a lot of experts. Some of the experts I see here, on this, chat. So Lander, good to see you here. That, they're gonna be speaking about their experience, and, you're gonna learn a lot. You know, there there are some big names we're gonna be talking about, the operations in general. This is virtual, so, do sign up for this. So with that, yeah, let's get to the questions of so first question here. How do you think of timing for FDA receiving processes? Have this integrated today, but seeing issues whereby FDA continues to receive and keep an inbound order open for long for a long period of time. Right. Right. That's a, admittedly, a problem that we've we've solved for a few different times. When we think about the timing, and the challenges tied to the timing of the receiving process with FDA, we look to involve strategies that look at different statuses for the receiving process. Right? So I believe there's three supported through the prebuilt integration like, receiving fully delivered. There's one more that's escaping me. But we can we can likely alter what's currently configured in your integration to ideally close out that, that that inventory, or that that was that transfer order rather to align your inventory better, even though, you know, a a lot of times I hear that the inventory is actually already in stock or available through FBA. So it's it's likely that any discrepancies can be taken care of by the supporting inventory adjustment workflow, or an alternative means through a platform customization like that inventory snapshot comparison record that we had taken a look at. So a few different, means to likely solve that challenge, but it's it's probably worth reaching out to your account manager and getting in touch with someone like myself or maybe even the support team or professional services to explore the options available to you or different configurations, and just kinda have more of a a hands on look at, what's what's currently running and why you may be encountering those issues. So the best practice is to simply work off the final sales invoice. I think this probably goes back to one of the earlier one of the earlier products, Seller Central. Sorry. I'm looking for that question. So the best practice is to work off the sales invoice. I would say that is true for the FBA process. Obviously, with the merchant fulfilled side of Amazon, you want a little bit more control or the ability to create an item fulfillment. Right? But, majority of our our sellers through FBA choose to just bypass order and fulfillment entirely because they're they're truly non relevant records that you don't need to flood your NetSuite with and ultimately can lead to a more optimized integration. We do have a survey coming up if you see Alexia, notes on the chat here. So please, let us know what you think and what we have so far. Another question here. Do we have similar seminars to integrate Amazon with SAP? We don't have anything scheduled at the moment, but we are able to sched to, do Amazon integration with SAP. As you can imagine, these processes are, very similar, between, marketplaces and ERPs, so we can, interface everything. We have done I think in the past, we've done one before. So, it's certainly something that's a possibility in the future even though we don't have anything scheduled yet. But but if that is an integration that you're doing, we'd we'd love to chat and learn more, and, see if, we can help even if there isn't a a webinar dedicated to it. Let me see if there's anything else that we haven't checked. Any final questions? Looks like, that might be it for now unless something comes in the last minute. So thank you so much for everyone who attended. I hope this was beneficial and helpful. Please let us know if there are things you'd like to see differently or, for next time. We will continue. We're gonna be doing EDI and then data warehouse. We're gonna do HubSpot. We're gonna talk about Walmart, and all sorts of other use cases. So please, please let us know. And, hopefully, we will see you either in the next webinar or at the, Connectives Commerce Summit. So, cheers and talk to you all soon.