Chris Reddick (President and CEO at Clarity Ventures) and Ron Halversen (Vice-President of Sales and Marketing at Clarity) begin their discussion about the best way to handle multi-warehouse scenarios for eCommerce businesses.

Part 1 of a 4-part series

RON: Good morning, Chris. How are you doing this morning? 
 
CHRIS: Hi, Ron. Doing great. How about yourself? 
 
RON: Very well. It's webinar Tuesday. 
 
CHRIS: Looking forward to this one. For everyone who's watching, this one's going to be really interesting, because we're going to be going into multi-warehouse implementation for buying groups. This is really something that can apply to a lot of different scenarios.

what is hipaa

CHRIS: If you think about buying in groups and how they have drop shipping, typically you're going to be fulfilling from different distribution centers. Of course, you may have a direct fulfillment model where you are directly fulfilling and may have multiple locations. All of this has to be coordinated, right, Ron? And so we're going to talk about that in detail today.

what is hipaa

RON: Yeah, sounds good. So let's kick off by defining what buying group multi-warehouse is and why it's so important to buying groups. And I know we lightly touched on this—at least the definition—we lightly talked about it in a previous webinar chapter about inventory management. Specifically where we really talked about why buying groups come to you, typically because they're buying in large quantities, whether that's a large quantity of buyers like at a Costco, or whether they're buying in bulk, again like at Costco.  

One of the things that was so important in the inventory management that we talked about is never running out of inventory in the notification options for inventory and things like that. And that is especially true now, when we're talking about multi-warehouse location, because now the coordination of inventory isn't just potentially one inventory account. It can be dozens of locations, and there could be shipping implications as far as local and intermodal shipping and cost of shipping and low inventory counts and things like that. So this one's really exciting.  

Let's go ahead and dive in a little bit with some of the common scenarios. Chris, why don't you just tell us some of the different places that multi-warehouse eCommerce applies, and then we can dive in technically on how a platform should be able to handle and address this, both from a technical perspective and from a UI/UX perspective for the buyers on the site.

CHRIS: Absolutely. Ron. And one of the fundamental thoughts is that these different multi-warehouse scenarios, as we're calling them, can apply to a lot of different situations. You could consider it from a functional perspective within the application. You can consider it to be a multi-warehouse situation, even though it's the same facility. There may be reasons for that, and you'll see that a lot with different ERPs and systems that are capable of handling routing and transfers of inventory within a single location. But some of them may not have that, and it may make sense for you to consider this multi-warehouse capability even within a single location. 
 
With that caveat aside, in addition to being able to take advantage of some functionality that may not literally match the description of multi-warehouse, we also want to consider a [literal] multi-warehouse. You may have a situation as a purchase group where there is some form of dropship, or there may be distribution centers that are all over the world or geographically optimized for lead-time optimization. 
 
So with this type of model and any variance thereof, it's really, really important to be able to capture inventory information and be able to present to the end-users what the lead times are, what the inventory is, and is there any other information that we need to capture and present to the buyers whenever they're on the site or in an omnichannel environment. They're using a device like a mobile ERP app, tablet application, et cetera. Maybe it's a PunchOut catalog system that they are purchasing from you as the binder. The key question here is, “Do you have the ability to tie all of these different aspects of your fulfillment and your inventory together?”  

The list goes on. Let's say that you have a multi-locations scenario. A lot of different buying groups and group purchasing organizations will have multiple locations. They may sell different things that are substantially different. They may also have a situation where they're working with another vendor and those other vendors have an area in their distribution center for the buying group and on and on and on. So we just need to be able to manage all of this.  

what is hipaa

CHRIS: Ron, one of the things that's always interesting about this is a lot of buyers groups tend to have some of the most complex scenarios. And I think this is because, l logistically it makes sense, you've got a lot of different participants, so you're going to have split payments and split shipping as almost a guarantee. But then you also tend toward having drop shipping. So you could have fulfillment from multiple locations, from multiple different drop shippers, and this is going to add up to be almost like a Cartesian explosion of different variables going on here. Because you also want to optimize the pricing and the inventory and making sure to fill a container.  

This is really what we're dealing with. We're dealing with all of these things at once. And this is the reality of optimizing for these group purchases, we've got to be able to understand in real-time—with the data and the integrations between the systems—we have to be able to understand and present that to the user, as well as to the vendors, in an accurate way that is reliable and credible so that the user can make a sound decision when they're purchasing. [It also has to be] based on accurate fulfillment timelines, accurate inventory and pricing data, et cetera. 

RON: Yeah, that makes sense. Matter of fact, I want to give a real-world example that just really expounds upon the complexity that can happen in just a simple scenario of buying a product on a group buying platform. One of our clients supplied and sold railroad ties. Most of the time when they sold these railroad ties—and they sold them in bulk—it was to construction companies and landscape companies that were doing things like—I think the last time when I was talking to them about this, they had a client that was building and won the bid to build one of the football stadiums. And I don't remember if he's NFL or was just high school stadium, but they needed like 70,000 railroad ties.  

Well, if you've ever seen a railroad tie, these things aren't light, right? They're not small. They're not light. And I can't even imagine with gas prices today what it would cost to ship 70,000 railroad ties. But anyway, this scenario was, our client had 11 different distribution centers across the US where they would house these railroad ties and stock them. 
 
But let's say, for example, someone in Salt Lake City is building a new stadium and they need 70,000 railroad ties. But right now the shipment hasn't come into Denver. So there's only 10,000 in Denver, and that's the closest facility, the closest distribution center, and there's 10,000 there. The next closest is in Seattle. And there's a couple hundred thousand up there.  

So is it cheaper, potentially, instead of getting 10,000 from Denver and then the rest from Seattle, to just order them from Seattle because they're coming on a train? Like you and I've seen in so many of our scenarios, we talk about having to fill a container or fill a truck before shipping, because it's a flat rate per truck. Well, potentially it could be cheaper.  

But on the other hand, what if that construction crew has a date that they need to hit and they can't wait that extra four days to get all of them from Seattle? They need to ship the 10,000 from Denver because they can get those here in time to start so it doesn't delay the project. And the cost of delaying a multi-million-dollar project is much more than the extra few thousand to ship those in. So we may not even be in control of this scenario that requires them to ship from different locations. 

But how easy do we make it for that crew in Salt Lake to see how many units are available in each of the 11 locations? How easy do we make it to estimate delivery times and shipping costs?  You think about all that, and based on the volume that people mostly buy from them, who didn't notify Denver that they were running low on stock so they could reorder or potentially transfer some? Maybe the ship came in, offloaded them in Seattle, and then, because gas was so expensive, they said, “Hey, let's just not ship them down to Denver. If they need some, we'll ship down, but let's not.” And they let them run low, and now, all of sudden, this caused a problem for their clients.  

It can become very complex. You basically want to allow your buying group platform to provide the capability to allow your vendors to not mess up. Because the goal of your vendors and you together is to support and make it easy for your buyers if you're a buying group. And if you mess that up, you could potentially lose your buyers. Especially when they're buying in bulk like that, you definitely don't want to lose a client. Any additional comments on this before we move on to the next one? 
 
CHRIS: I think that's perfect. Thank you. 

Continue to Part 2 to find out more about integrating data with multiple warehouses.