Name: Master Omnichannel Success: Automate Selling on Marketplaces
Uploaded: 2025-03-25T17:46:08.876Z
Duration: 31 min 28 s
Description: Master Omnichannel Success: Automate Selling on Marketplaces

Transcript for "Master Omnichannel Success: Automate Selling on Marketplaces": Hello, everybody. My name is James Hoxton. I'm a solutions consultant here at Saligo. I Wanna take a moment to welcome everybody to our webinar series today. And I see in the chat we have somebody from Noblesville. I'm actually from Indianapolis, Indiana. So happy to see you, Henry, here. But yeah. So today, we're going to be covering, yeah, automating selling on marketplaces, and what that can look like on Soligo's platform. But, today, before we jump right in, we'll cover a little bit about what Soligo is. Jumping over here. Soligo is an iPaaS platform. What that means is we're an integration platform as a service, and we're going to provide you that user interface for that platform to build and maintain any and all integrations that you may have through one pane of glass. You can see on the right there some of our major logos that are already, having success, you know, integrating on our platform. And on the left, some of the metrics that support that. You know, we're already processing over 40,000,000,000 records per month on our platform. And of those, we're able to to resolve or auto resolve over 762,000,000, errors that may be occurring within those records we're processing. Down here, we're connecting to over 6,000 endpoints or, you know, different applications on our platform. And of those, we have over 250,000 active flows running with and we have 900 partners worldwide and over 5,000 customers that are actively integrating processes on Soligo. And really what this goes to show is that, you know, Zaligo is proven at scale. We're trusted by, the thousands of IT leaders worldwide. And so whether you're integrating a handful of applications or you're managing a global enterprise, Zaligo is gonna deliver you that security, scalability, and automation that your IT team needs. So further backing that up, you know, Zaligo is the number one ranked iPaaS on g two for the past four consecutive quarters. And so when you're evaluating integration platforms, it's very important, to consider third party, validation as an important measure of reliability there. And Soligo consistently tops that chart. Right? Our customers are, saying that we're the number one iPaaS. And this G2 chart is based on real customer feedback. It really does prove the ease of use, scalability, and overall satisfaction that our customers are saying that they have on our platform. But when it comes to marketplace selling and success within you know, selling on those marketplaces and what automations you're going to need to see that success, we'll jump to the next slide here and show some of the examples of automations that we see on Saleum. You can see on the left, you know, some of the major e commerce marketplaces out there that we're going to give you the ability to connect to, as well as the major ERP systems that, you may be needing to tie those marketplaces to. I mean, so some of the the common integrations or automations that we see between these ERPs and marketplaces are gonna be things like syncing your product data out so you have one source of truth for that product data across marketplaces, really allowing your ERP to drive that data and move that across your marketplaces as you see fit. Really then eliminating the need to, you know, have multiple points of contact when you're going to create new products or update product listings. You can do that in one place, and Twilio can automatically update those listings across your marketplaces, as well as product, you know, and inventory data syncing between those systems, you're going to want to be able to pull in orders. So being able to automatically create sales orders in your system, handle refunds, cancellations, or, you know, in turn then payouts. And really, how are you gonna be able to do this on our platform? Right? So we go is going to offer you one centralized platform to leverage whether it's prebuilt integrations, which we'll touch on today, some of our integration apps or templates, as well as new integrations from scratch. So while this subset is some of the more common, you know, integration flows that we see built, this is not everything that that can be built on Sligo's platform. And to further show that here, you know, while this is really drilled into what specifically you may be connecting between that ERP in the marketplace, things like orders, refunds, payouts, you know, products inventory, fulfillment, There may be other systems too that are tying into this process as well. Right? And so if we if we look here, this is how you can see a more holistic view of how Soligo can tie into that order to cash process with marketplaces specifically, but also those other systems that may be tying into that marketplace. It's one thing to be able to sync that product data out to your marketplace, but what if that product data is also originating from a PIM or CMS platform that you're using, like a Jasper or a Salsify? How are you getting that excuse me, data into your ERP to then sync out to those marketplaces? Or, you know, as orders are flowing in, how are you then pick packing and shipping those orders in your ERP? Do you have other three PLs or WMS softwares that are doing some of that process that you need to get those orders out to and get fulfillments back into your ERP? Or even going down the line here, you know, things like return services. If you're handling returns outside of those marketplace platforms, how are those being handling handled? How are you automating those returns back into your ERP? And then all the way down to things like customer service. You know, if you guys are using Zendesk, or just of the world for customer service and and ticketing processes with your customers, how how are those processes being synced back and forth? And so this can sort of give you, you know, an idea, a view of how Zilligo can play a more holistic view and tie all of your systems together that may be touching that order to cash process. But today we'll be focusing mainly on what those, specific flows between your marketplaces and your ERP can look like on Soligo, sort of how those are gonna help you guys see success, in selling on those marketplaces. So now I will stop sharing here and and share my screen out. So switch over to that here. And when I do that, you guys should be seeing Integrator IO. And then so Integrator IO is our homepage or landing page for any and all integrations on Saleo. So this is giving you that one pane of glass for any of the integrations or automations that you may want to build, whether that be like today talking about marketplace integrations or other things like ecommerce, shipping and fulfillment returns. You know, if you guys then are taking that data, pushing that into any data lakes or data warehouses, pushing, data into business intelligence and analytics processes, Sort of how you can see those different integrations work together on our platform and be organized. In my environment here, I'm organizing my marketplace integrations all into one tile. You could organize your integrations as you see fit, as makes sense to your company on on the platform, and you can see that as when we drill into one of the integration apps later. That's really one tile representing an integration between two disparate systems. But as we drill into the marketplace integrations here, you could have one tile represent integrations across many different systems like you see here. And so you can see some of the major marketplaces that you may be wanting to tie to and how we're tying into those and creating flows for each of those individual objects that we would be looking to pass between the systems, in the middle. So putting it through here, you can see, you know, we're we can build out flows separately between, your ERP and Amazon, your ERP and Walmart, Wayfair, TikTok, Shop, etc. I'm really looking to use that ERP as that hub and spoke out to those separate marketplaces. Then the ERP is driving the data and then we're spoking that out to those marketplaces as needed. So when we look at this, you know, talking about building a store on a marketplace, one of the first things that I like to think about is, you know, building those product listings, setting up your store, and and getting those listings over to your marketplace. And so if we think about that as an example, we can take a look at what a flow would look like within Salego. So here using NetSuite as the example ERP and Amazon as the example marketplace, we can show how we're easily able to export item data, do any type of transformation or filtering on that data before we pass it to your your destination system, and then ultimately map that into your marketplace. If I click in here, you can see how we can easily set up an export step between or from NetSuite in this example. We're naming that export, telling it what type of record that we're grabbing. In the case of NetSuite, we're able to use saved searches as well and then you're even able to preview that data. The point being you'd be able to set up this source from your ERP, tell the integration what type of record we're grabbing and then preview the exact fields that you would have to map to a destination system right inside the platform. Then once you have that export step set up, you can see what fields we're pulling from that item record, in this case in NetSuite. You also have additional developer tools available right at your fingertips. You need to add any scripting here either before sending that data or before saving a page, or if you need to do any transformations of that data to say restructure any of those fields or provide an output filter, You could do that and those tools are available to you as well. You'd be able to add additional sources. If we need to add an additional source for item data, maybe not all of the fields that you want to pass to that Amazon seller central item import are a part of your NetSuite item. You could add additional sources to gather fields as you need and then pass those to your destination. As well, you'd be able to add branching here. We can do conditional branching where you can add a condition based on a certain field coming from your ERP, set up a Boolean there, and then set that conditional statement. You can then save this and see how we'd be then be able to even branch different, excuse me, records. That adds an additional step for you to add a destination here. As we go in and we look to add destinations, or export steps, We can use, any of those prebuilt connectors that we have. So we're gonna have a long list of prebuilt connectors to these different applications. You can see that list here, and always search for the different applications that you may be working with. Now Soligo is endpoint agnostic. We also have universal connectors. That means that if you're going through this list and you find that we don't have a name connector for a certain market, marketplace or ERP, you can always utilize universal connectors to tie into any of those endpoints that have an open API or a way to connect. But then within those pre built or named connectors that we do have, you could say click for NetSuite as an example here, say that we want to import records. Then you can even see steps here on the right that are going to allow you to not reinvent the wheel. As you're going through, it's going to pull up any of those available steps from either our marketplace or within your own environment, allowing you to reuse different import or export steps in your environment so that you're not ever reinventing the wheel for processes that maybe you would need to repeat. As well, you can reuse those within your account or within your marker or within the marketplace directly. That makes it very easy to then onboard new marketplaces or create new steps, destination steps as needed without needing to be a developer, go in and know all of that back end coding. Additionally, you'll be able to set up your import step here. So here is where we're telling it essentially how we're sending that data to Amazon. And again, we're going to you could utilize those pre built steps from the marketplace that are gonna set this up for you or then you can configure that further, but giving you those building blocks so that your team, doesn't need to ever reinvent the wheel on those steps that we see as common use cases on the platform. Now additionally then once you have your export step set up, you're exporting exactly what data you want out of your ERP. You provided any additional logic, whether that be scripting, filtering, transformations, and even set up any branching that may be needed. You can then set up your mappings. And the mapping tool is really where you're going in and you're telling it exactly what fields from that ERP we're pulling and how we're mapping those into the marketplace here. And so Celica makes that very easy by, you know, making that very user friendly to see what's mapping where, set up new mappings as you see fit, as well give you the tools that you need to provide any additional business logic into those mappings. So you can define your data type, You can define your field mapping type, so standard field to field mappings, you know, always taking the one field value from your source and pushing that same value to the destination. You can hard code certain values, do lookups into a dynamic search. Say, into your ERP, you need to do a dynamic search for a certain value or field. You can perform those as well. You can do multi field field mappings as well. This allows you to tie into our entire handlebar library and create functions as you need. If you needed to do something like an add or capitalize or compare for certain fields or you needed to do if else logic added right into the field mappings, you can use the handlebar library here, to utilize that as well, perform any additional business logic you need on those mappings. Then moving forward, once you have a flow set up, this is a general high level architecture of a flow. You always have your export, your import, your mappings. You could then schedule these flows out. If you turn the flow on, you can schedule that flow as well. Maybe I'll just switch to another one really fast because I added a branch there. But you can schedule out these flows. Any of your flows could run on the scheduler, you can use a time zone and a frequency. So you can set that time zone and then set your using preset frequencies to run every once either once weekly down to every fifteen minutes, or you could use a crown expression here to get very granular with when you want those flows to run. Could be every five minutes being the quickest, or you could go get get that to run a certain minute, certain hour, certain day of the month if you want to be very granular with when that flow would run. Now, that is an example of how we would build a flow. In that case, taking products, creating Amazon item listings, but really you could look to replicate that same architecture for any of the objects that you'd be looking to automate moving between those systems. Then when we think about importing orders, that's where we have separate flows for importing those orders into the ERP. Here we've seen customers have success by separating out the different selling programs that you might be doing on those marketplaces. So in the case of Amazon, you may be selling merchant fulfilled orders as well as fulfilled by Amazon orders. In the case of Walmart, it may be, Walmart fulfilled or Walmart fulfillment services as well as merchant fulfilled, TikTok fulfilled and merchant fulfilled and so on. And so we've seen our customers have success, importing those records as, the exact record they need. In the case of Amazon taking it for merchant fulfilled and creating, say, a sales order that then needs to be picked, packed, and shipped, fulfilled in your ERP system versus if Amazon is taking care of the fulfillment for you with the FBA program, we could look to just import those in directly as invoices. The point being here that you have the power over exactly what records we're creating into that ERP system and so that we're only creating the records that are needed and never creating you know, anything that maybe would be redundant or not needed to be tracked in that ERP, such as, fulfillment on an order that Amazon's fulfilling for you. But in the case of MFN orders coming in, we'd be able to map in those sales orders, and then really those would be in your ERP and need to be processed. Right? Those need to be picked, packed, and shipped in case of those merchant fulfilled orders. That's where, alluding to, you know, what I had shown previously, we can tie this these marketplace integrations together with some other integrations that you may have in your platform. So this is where we could take those orders, bring those directly into the ERP across different marketplaces. So then there, if I backtrack a second, you could have separate order flows to create those sales orders for MFN Amazon orders, Walmart orders, Wayfair, TikTok, and you're consolidating all of those sales orders into your ERP system. We can then have separate flows to connect that out to any three p l or warehouse management cert systems that you may have to grab those consolidated orders and sync them out to your ERP for fulfillment, as well as bring in any item fulfillment records back into your ERP. We can do that in an automated fashion so that then you're not needing to send CSV files or emails to your 3PL to get order fulfilled. We're automatically sending those over, getting item fulfillments back into your ERP that we can then automatically sync over to the marketplace system. Really then marking those orders as shipped, bringing along tracking numbers so that you're seeing a quick turnaround on those for your customer. It's going to improve that customer experience by really the speed that that order can be processed into the ERP, sent out to the three PL, item fulfillment created, and then ultimately communicated back to that customer where they're seeing that their order has shipped and that their tracking number is there. Now, really once you have orders flowing in, you have items flowing out, you have fulfillments flowing out, you've connected in any three PLs, that's really where we need to think about the transactional side of things. Right? That that order would be at a point where you're ready to invoice it and accept payment from that customer. And so in the case of FBA orders, you may already have open invoices since those have already been fulfilled and we're creating those open invoices right away. In the case of, of MFM, we can build flows on the platform to auto bill orders. So if you need even to have, a flow on the platform to do an ERP to ERP operation, That's a very common thing that we see taking a sales order within an ERP and automatically creating an invoice within that same ERP system, could be done as well. But ultimately, you would need to build those transactions and then we need to get that transaction information from Amazon or Walmart or Wayfair or TikTok's settlement file. That's where I want to backtrack here and show an example of how we solve that with Amazon, but I can dive into our prebuilt integration. And that's really where, it shows a good example of how we're we're settling or we're bringing in those settlement records with Amazon and NetSuite. So here, we're able to then bring in that settlement report or request that settlement report from Amazon automatically. We can tie into any custom records that we may need in your ERP to bring in that information. But ultimately here, we're grabbing that settlement, we're applying any customer payments against open invoices, we're applying any refunds against closed invoices, and then we're creating any journal entry or deposit record that that you may need in your ERP, in this case, NetSuite creating a journal entry. That then allows us to automatically apply those payments and close out those invoices in your ERP as well as track the fees that the mark the different marketplaces may be taking. We can then automatically create that journal entry or deposit record, which is going to speed up the time that your your team is gonna be able to close your books. Alright. We'd be able to automatically, track those fees against against general ledger accounts so that you're more accurately and timely processing these settlements as they're released out to you. Now, this also can show a good view of what, that order to cash process can look like as a whole within those flows. Right? I know my previous example showed across marketplaces there, but this within one tile, shows how you could really automate that order to cash process. Everything from products and pricing syncing out as well as inventory to orders coming in, whether that be FBA or MFN, syncing those fulfillments for the merchant fulfilled orders out, ultimately billing those orders automatically within the ERP, and then processing those settlements coming in. So that then you're really taking that not only the product listing, but also the any of those orders coming in through that whole order to cash process with as little manual effort as possible. Really automating as much of those critical business processes as you can there, so that then you're eliminating any manual effort. You're also speeding up the time that these processes take, to complete. As well, we're also then going to be looking to solve for any errors or check for any problems that may be occurring within these flows. If I backtrack here, Zilligo will also have built in error management. Once you have your integrations up and running, say you have flows up and running for everything from products down to settlements, they're running smoothly. What happens then if a connection ever goes down or if an error ever occurs between your systems? The way I like to look or think about error management on Celica is like a breaker box. You're not going to be staring at the breaker box all day to make sure that there was no circuits tripped. Same idea with Celica. We can notify you of any errors or connections going down so That when these things are up and running, they're running in the background and then you're logging into Silego's platform to solve for any errors or connections down as they occur. If I click into my e commerce integrations here, I can show here. We'll be able to set up those error notifications per flow and port per connection. You can be notified if any specific flows go off or have any errors or if any specific connections go offline. You can also set up those notifications per user. So then that allows you to enable your IT team there where they're only being notified for things that maybe they're responsible for or setting up notifications, you know, per user so that whoever is responsible for a certain, flow or use case can be notified just if those flows go down or have any errors. And then as you as you have any errors occur, you log in to the system. You could see at the highest level if there were any errors down or any connections. And then as you drill into the tile here, you can see we would specify exactly what flow that error occurred on. You can click on that error message and we would then further drill down into what exactly that occurred with that error. Giving you the exact error message, in this case, failed to save a record because we needed to enter values for item number, tax schedule. You can see that error data right inside of the platform and even edit it right inside of here. If you did need to say in this case, since it's a value that's null or empty, if you knew what value needed to be put in there, you could do it right inside of the user interface. Otherwise, you wouldn't be able to assign these errors out to certain users. You could tag these errors. Say if it was, perhaps a user error, like in this case, the customer forgot to put this information in and not necessarily a system error. You can tag it that way and then you can even edit that retry data right inside the UI. You can automatically, so say if you wanted to edit that data, you could hit retry here and it would automatically try to push that record through again. You could obviously also mark these errors as resolved. If you did go in and resolve that within either system and you don't need that record to push through anymore, you'd mark that error resolved, and then we would never try to push that error data through again. Could also view the request data, view any response data, and view those error fields right inside of the error management. As well, Soligo has built in AI error management here. Really what that means is for things that wouldn't require any human intervention, things like rate limit, errors and such from APIs, we're gonna auto retry those that type of data. You're avoiding tedious rate limit errors that you may need to come in and retry for. Those would never be something you would need to come in and retry an error management. It would always be an error that that does require some sort of of human interaction so that you're avoiding coming in and dealing with redundant error data. Then as well, if you do ever run into any errors that you can't solve, you also have resources built into the platform as far as support. You can always click up in the top right, go out to our Help Center, which is gonna be have, all of our help documents. There's lots of material there from our product team, that you can search through. As well, you can always submit a ticket, explain the problem to our support team, they'll reach out to you and work with you to try to solve those those errors. So jumping back here into my slide deck. Yes. So I wanted to highlight an example of one of our customers, PooPuri. They had a very similar use case to what we've gone through today. They saw a lot of rapid growth when they had a viral, marketing campaign. This really, meant that they needed to onboard a cloud based ERP system, and and they chose NetSuite there. And so what they found, success with initially was integrating their ecommerce platform, Shopify with NetSuite. And the amount of success they found, really allowed them to improve that those operations, improve inventory management, the automated processes around the order management, payouts, inventory. And that really allowed that success allowed them to then look to other places they could they could have success with Onslowgo. They onboarded new integrations such as markets like Walmart, FAIR, and BrandWise, and They started using us, to connect into their three PL central, for fulfillment. The result there was, obviously, they optimized those processes, they reduced errors, and, really, they were able to redirect efforts that a lot of their company was doing on manual data entry and keeping up with order processing manually and dedicate those employees to more business strategic initiatives. Now, I will jump over to a QR code here. You can register for our next webinar. This is going to be our Connected Commerce Summit. I'm really covering B2C and B2B commerce. You will be able to check this out on Tuesday, April 29 at 10AM Pacific time, one PM eastern time. And really here, we'll just you'll be able to join top industry experts as, hey, they break down the future of commerce, sharing cutting edge strategies, and revealing how integration and automation can build a future proof business. Now, I believe we'll stop for some q and a, and I can answer any questions that you guys had today. Alright. We have a question here. So, for FBM, does it provide built in integration with three p l services? So I think we covered on that a little bit today. Really, Saligo could provide that bridge to your three p l service. Right? So, as if you're using a three p l provider out there, as long as there is a way to connect, whether that be an open API, an FTP server, a s two servers, any any open way to connect out there, that's where Soligo could tie into tie into that API and really be that bridge. Yeah. So I know we touched a lot on sort of those very critical order to cash processes. But that being said, you know, tying into settlement reports to bring in transactions is something that we see as a very common use case. But also outside of that, we can also tie into really any of those reports that are made available. So, you know, I know, for example, Amazon has APIs for reports for all of the reports they offer. And so I've seen, you know, use cases where other customers look to bring those reports into their ERP for things that are more along the lines of business analytics and intelligence, and so that you can get accurate reporting for things other than maybe just those settlement reports, could be ad related or spend related. Alright. Just reading that question from you, Henry. That's a great question. You know, we could we could certainly provide you more insight, offline here on about exactly, you know, what based on the environment, what the time zones there are. But, ultimately, you'd be able to set up those schedulers as you see fit. So your team's gonna have complete complete power over those. So even if you didn't wanna use, you know, one of the preset frequencies, that's where you could use those Kron expressions to get as granular as you want with when we're running those flows. Well, thank you everybody for your time today. And, yeah, I appreciate you taking the time to to listen to our webinar today, and I hope you guys found value out of this session.