WEBVTT - Amazon Opens Logistics Network to Everyone

0:00:00.150 --> 0:00:10.100
<v Speaker 1>Hi everyone, this is Lee Klaskow and we're Talking Transports.

0:00:10.240 --> 0:00:13.740
<v Speaker 1>Welcome to Bloomberg Intelligence Talking Transports podcast. I'm your host,

0:00:13.780 --> 0:00:17.840
<v Speaker 1>Lee Klaskow, Senior Freight Transportation Logistics Analyst at Bloomberg Intelligence,

0:00:18.360 --> 0:00:21.810
<v Speaker 1>Bloomberg's in-house research arm. Before we dive in, quick favor,

0:00:21.989 --> 0:00:25.130
<v Speaker 1>if you enjoy the podcast, please subscribe, rate, and review,

0:00:25.590 --> 0:00:28.130
<v Speaker 1>and share it with a friend. Your support helps us

0:00:28.250 --> 0:00:32.490
<v Speaker 1>continue bringing you conversations with leaders shaping the future of

0:00:32.570 --> 0:00:35.809
<v Speaker 1>transportation and logistics. And if you'd like to connect, you

0:00:35.850 --> 0:00:38.510
<v Speaker 1>can always find me on the Bloomberg terminal on LinkedIn

0:00:38.570 --> 0:00:41.610
<v Speaker 1>or on X at Logistics Lee. Today, we're coming to

0:00:41.650 --> 0:00:45.960
<v Speaker 1>you from Bloomberg's global headquarters in New York City. Few

0:00:46.060 --> 0:00:49.640
<v Speaker 1>companies have had a bigger impact on transportation and logistics

0:00:49.979 --> 0:00:52.940
<v Speaker 1>over the past decade than Amazon. What began as an

0:00:53.020 --> 0:00:56.650
<v Speaker 1>effort to deliver packages to customers faster and has grown

0:00:56.710 --> 0:01:00.350
<v Speaker 1>into one of the world's most sophisticated supply chain networks.

0:01:00.750 --> 0:01:04.270
<v Speaker 1>And now Amazon is making those capabilities available to businesses

0:01:04.330 --> 0:01:09.320
<v Speaker 1>beyond its own marketplace through Amazon Supply Chain Services. Joining

0:01:09.420 --> 0:01:12.700
<v Speaker 1>us in the Bloomberg studio is Peter Larson, head of

0:01:12.880 --> 0:01:18.160
<v Speaker 1>Amazon Supply Chain Services. Today, we'll discuss Amazon's long-term logistics strategy,

0:01:18.360 --> 0:01:22.740
<v Speaker 1>where it sees the biggest growth opportunities across transportation, warehousing,

0:01:22.819 --> 0:01:27.020
<v Speaker 1>and supply chain services, how AI is transforming logistics, and

0:01:27.060 --> 0:01:31.430
<v Speaker 1>how Amazon positions itself alongside many of the industry's legacy

0:01:31.490 --> 0:01:35.310
<v Speaker 1>transportation providers. Peter, welcome to Talking Transports. It's great to

0:01:35.350 --> 0:01:36.090
<v Speaker 1>have you here in New York.

0:01:36.490 --> 0:01:38.450
<v Speaker 2>Thanks very much, Lee. I am happy to be here.

0:01:39.390 --> 0:01:42.319
<v Speaker 1>So, you know, what is Amazon Supply Chain Services and

0:01:42.380 --> 0:01:45.020
<v Speaker 1>kind of what are the problems you're trying to solve?

0:01:46.020 --> 0:01:52.520
<v Speaker 2>Well, we, as you may know, Amazon's a technology company, fundamentally.

0:01:53.610 --> 0:01:56.730
<v Speaker 2>that just happened to build one of the world's most

0:01:57.140 --> 0:02:01.960
<v Speaker 2>sophisticated supply chains. And we first built it for ourselves.

0:02:02.260 --> 0:02:05.020
<v Speaker 2>And then we opened it up to the sellers who

0:02:05.060 --> 0:02:08.680
<v Speaker 2>sell on Amazon. And we proved it at scale. We've

0:02:08.700 --> 0:02:11.300
<v Speaker 2>got hundreds of thousands of Amazon sellers using it. And

0:02:11.360 --> 0:02:14.000
<v Speaker 2>so just recently this year, we opened it up so

0:02:14.040 --> 0:02:17.000
<v Speaker 2>that any business of any type can use it. It's

0:02:17.020 --> 0:02:19.540
<v Speaker 2>a little bit like the playbook we ran with AWS

0:02:19.580 --> 0:02:22.000
<v Speaker 2>a number of years ago. Build it for ourselves and

0:02:22.020 --> 0:02:23.620
<v Speaker 2>then open it up for everybody to use.

0:02:24.460 --> 0:02:27.919
<v Speaker 1>And at what point was the decision made, you know,

0:02:28.580 --> 0:02:30.680
<v Speaker 1>whether it's we have the scale or we have the

0:02:30.740 --> 0:02:34.090
<v Speaker 1>ability to say, let's open it up to third parties

0:02:34.320 --> 0:02:35.840
<v Speaker 1>outside of your marketplace?

0:02:36.030 --> 0:02:43.010
<v Speaker 2>Yeah. Well, there were a couple interesting inflections in the journey. Actually,

0:02:43.090 --> 0:02:46.550
<v Speaker 2>a number of interesting points in the journey. But, you know,

0:02:46.630 --> 0:02:48.850
<v Speaker 2>I'll tell you where a lot of this got started

0:02:48.930 --> 0:02:53.810
<v Speaker 2>is that Amazon's been building its own fulfillment centers for,

0:02:53.900 --> 0:02:56.239
<v Speaker 2>you know, since we got going, really. Right. But it

0:02:56.280 --> 0:03:01.620
<v Speaker 2>was in sort of 2013, the holiday season, where, you know,

0:03:01.639 --> 0:03:04.900
<v Speaker 2>we were using a lot of third party transportation companies

0:03:05.020 --> 0:03:08.710
<v Speaker 2>for the last mile delivery. And one of those companies

0:03:08.750 --> 0:03:11.669
<v Speaker 2>just fell over from unexpected demand. And that meant that

0:03:12.010 --> 0:03:14.610
<v Speaker 2>we shipped a lot of packages late to prime members.

0:03:15.210 --> 0:03:17.049
<v Speaker 2>So at that point we decided, well, you know what,

0:03:17.910 --> 0:03:21.510
<v Speaker 2>in addition to the fulfillment centers, we need to build

0:03:21.630 --> 0:03:24.600
<v Speaker 2>our middle mile and last mile transportation networks as well.

0:03:24.660 --> 0:03:29.179
<v Speaker 2>So we set off doing that. Once we got that

0:03:29.220 --> 0:03:32.880
<v Speaker 2>up and running for ourselves, you know, a big part

0:03:32.900 --> 0:03:37.190
<v Speaker 2>of the amazon.com business is third-party sellers. And so we

0:03:37.370 --> 0:03:42.560
<v Speaker 2>opened up that logistics network to our Sellers, otherwise known

0:03:42.740 --> 0:03:47.460
<v Speaker 2>as FBA or Fulfillment by Amazon, that took off. Sellers

0:03:47.500 --> 0:03:50.250
<v Speaker 2>were really able to grow their businesses using that service.

0:03:50.280 --> 0:03:52.670
<v Speaker 2>And that service is where they store their inventory in

0:03:52.710 --> 0:03:54.650
<v Speaker 2>our warehouses and we pick back and ship it on

0:03:54.670 --> 0:03:58.470
<v Speaker 2>their behalf for their orders on Amazon. Those same sellers

0:03:58.570 --> 0:04:01.790
<v Speaker 2>then turned to us and said, listen, we already have

0:04:01.810 --> 0:04:05.980
<v Speaker 2>your inventory in the Amazon network for our Amazon sales.

0:04:07.190 --> 0:04:09.990
<v Speaker 2>How about you just let us use that same inventory

0:04:10.050 --> 0:04:13.410
<v Speaker 2>for our off Amazon channels as well? So we open

0:04:13.450 --> 0:04:15.790
<v Speaker 2>it up to our Amazon sellers for their off Amazon,

0:04:15.830 --> 0:04:19.029
<v Speaker 2>whether they sell it on their own direct to consumer

0:04:19.070 --> 0:04:24.349
<v Speaker 2>sites or another retailer outside of Amazon. Once we did that,

0:04:24.490 --> 0:04:27.530
<v Speaker 2>we had hundreds and thousands of those sellers using our

0:04:27.550 --> 0:04:32.080
<v Speaker 2>supply chain services for their off Amazon volume. We decided, well, heck,

0:04:32.120 --> 0:04:34.920
<v Speaker 2>why not open it up actually to any business of

0:04:35.040 --> 0:04:38.730
<v Speaker 2>any sort? And so now we're offering it for ourselves,

0:04:38.810 --> 0:04:42.130
<v Speaker 2>for Amazon sellers, as well as for any company out there.

0:04:42.650 --> 0:04:45.090
<v Speaker 1>So Amazon supply chain services, we're just going to call

0:04:45.110 --> 0:04:48.550
<v Speaker 1>it ASCS going forward because we only have 40 minutes.

0:04:48.650 --> 0:04:49.469
<v Speaker 2>Yes.

0:04:50.070 --> 0:04:51.550
<v Speaker 1>So, because I'm sure we're going to say it a lot,

0:04:51.570 --> 0:04:53.750
<v Speaker 1>you know, outside of fulfillment, you know, a lot of

0:04:53.810 --> 0:04:56.850
<v Speaker 1>folks that are listening, they know that, you know, they

0:04:56.870 --> 0:04:59.350
<v Speaker 1>get an Amazon package on their doorstep. They know that

0:04:59.410 --> 0:05:02.210
<v Speaker 1>part of the delivery, but you guys are offering more

0:05:02.270 --> 0:05:05.710
<v Speaker 1>services beyond just the final mile. Uh, can you just

0:05:05.730 --> 0:05:07.930
<v Speaker 1>talk about, you know, what markets you're in?

0:05:08.290 --> 0:05:11.300
<v Speaker 2>Yeah. Let me set it up at a high level.

0:05:11.440 --> 0:05:15.660
<v Speaker 2>So we've built, um, an end to end supply chain, really.

0:05:15.720 --> 0:05:19.099
<v Speaker 2>So all the way from pick it up from the

0:05:19.140 --> 0:05:23.250
<v Speaker 2>manufacturer in China, put it on a boat over the ocean,

0:05:23.670 --> 0:05:27.670
<v Speaker 2>get it through customs, pick it up outside of customs, uh,

0:05:27.730 --> 0:05:32.350
<v Speaker 2>with a, um, with a freight truck. Take it from

0:05:32.410 --> 0:05:35.470
<v Speaker 2>that point either to a customer's warehouse or to one

0:05:35.490 --> 0:05:38.870
<v Speaker 2>of our warehouses. Once it's in our warehouses, you got

0:05:38.930 --> 0:05:42.289
<v Speaker 2>two options. If it's a consumer order, we can pick

0:05:42.330 --> 0:05:45.450
<v Speaker 2>back and ship that on your behalf. If it happens

0:05:45.529 --> 0:05:48.890
<v Speaker 2>to be you want to distribute your pallets to other

0:05:48.970 --> 0:05:54.970
<v Speaker 2>downstream retailers or partners, we can pick and pack essentially

0:05:55.170 --> 0:05:56.380
<v Speaker 2>pallets for you as well.

0:05:56.390 --> 0:05:56.630
<v Speaker 1>Mm-hmm.

0:05:57.520 --> 0:06:01.160
<v Speaker 2>And then the last option is if you want to

0:06:01.560 --> 0:06:04.120
<v Speaker 2>get it over the ocean, for example, put it on

0:06:04.160 --> 0:06:06.880
<v Speaker 2>our freight trucks and send it to one of your warehouses,

0:06:07.260 --> 0:06:09.560
<v Speaker 2>you can easily do that. And then if you want

0:06:09.580 --> 0:06:13.490
<v Speaker 2>to hire our parcel shipping to go to your warehouse

0:06:13.550 --> 0:06:16.610
<v Speaker 2>to pick up the good that you need sent to

0:06:16.670 --> 0:06:19.750
<v Speaker 2>your end customer, we can do that as well. So

0:06:19.770 --> 0:06:25.450
<v Speaker 2>we've got multimodal freight, air, ground, rail, and ocean shipping.

0:06:26.190 --> 0:06:29.530
<v Speaker 2>We've got distribution and fulfillment, and we've got parcel shipping.

0:06:29.990 --> 0:06:32.450
<v Speaker 1>And so you do truckload, less than truckload. You have

0:06:32.570 --> 0:06:35.370
<v Speaker 1>freight brokers and freight forwarders and all that.

0:06:35.690 --> 0:06:37.830
<v Speaker 2>We got it. We got it all. You know, I mean,

0:06:37.850 --> 0:06:39.570
<v Speaker 2>of course, we have a lot of work left to do,

0:06:39.710 --> 0:06:43.420
<v Speaker 2>but many people don't know, for example, that we're one

0:06:43.460 --> 0:06:51.080
<v Speaker 2>of the largest freight forwarders that ships containers from China

0:06:51.260 --> 0:06:55.450
<v Speaker 2>over to North America and Europe. Right. Little known fact,

0:06:55.490 --> 0:06:58.650
<v Speaker 2>we are one of the largest freight forwarders in the world. Also,

0:06:58.790 --> 0:07:02.409
<v Speaker 2>little known fact, we have a well-established air cargo network

0:07:02.450 --> 0:07:08.440
<v Speaker 2>as well, both domestically in the States, but also increasingly

0:07:08.600 --> 0:07:12.360
<v Speaker 2>from outside the States into the States. So, for example,

0:07:12.800 --> 0:07:17.200
<v Speaker 2>we run a lot of lanes from Latin America to

0:07:17.240 --> 0:07:21.590
<v Speaker 2>the U.S. for goods, for example, for Mother's Day, for

0:07:21.650 --> 0:07:26.990
<v Speaker 2>flowers or for Valentine's Day flowers. cherries from Chile, things

0:07:27.030 --> 0:07:29.770
<v Speaker 2>that are created outside the U.S. but have to get

0:07:30.010 --> 0:07:34.090
<v Speaker 2>in really quickly because they're perishable, we use our air

0:07:34.130 --> 0:07:35.010
<v Speaker 2>cargo network for that.

0:07:35.390 --> 0:07:38.869
<v Speaker 1>And what's the value proposition you guys provide to third-party

0:07:39.420 --> 0:07:42.100
<v Speaker 1>shippers that are outside your network? Like, why would, if

0:07:42.130 --> 0:07:46.740
<v Speaker 1>I'm a shipper, why would I use Amazon versus DSV

0:07:46.820 --> 0:07:50.500
<v Speaker 1>as a freight forwarder or J.B. Hunt in trucking or C.H.

0:07:50.520 --> 0:07:53.810
<v Speaker 1>Robinson in the brokerage business or you know, recently there's

0:07:53.830 --> 0:07:55.680
<v Speaker 1>been a lot of news about you guys entering the

0:07:55.800 --> 0:07:59.160
<v Speaker 1>LTL market. Uh, so every time there's an announcement hits the,

0:07:59.200 --> 0:08:02.000
<v Speaker 1>the tape, the old, the LTL stocks get, uh, get

0:08:02.040 --> 0:08:05.260
<v Speaker 1>hit pretty hard. Um, so, you know, what, what's when you,

0:08:05.320 --> 0:08:10.540
<v Speaker 1>when you guys are selling your services outside of your own, um, marketplace, what,

0:08:10.580 --> 0:08:11.800
<v Speaker 1>what is that value proposition?

0:08:12.720 --> 0:08:15.730
<v Speaker 2>Well, I think, um, the first thing that we talk

0:08:15.790 --> 0:08:20.070
<v Speaker 2>about with customers is the benefit of having that end

0:08:20.090 --> 0:08:23.240
<v Speaker 2>to end network. Um, A lot of our customers have

0:08:23.260 --> 0:08:27.340
<v Speaker 2>built up their supply chains over years, and they've got

0:08:27.800 --> 0:08:31.220
<v Speaker 2>five or 10 different fragmented firms that they're working with.

0:08:32.220 --> 0:08:36.120
<v Speaker 2>And what that means is you've got missed handoffs and

0:08:36.340 --> 0:08:38.949
<v Speaker 2>visibility gaps in your supply chain. And, you know, it's

0:08:39.020 --> 0:08:43.809
<v Speaker 2>such a connected system. Any sort of a visibility gap

0:08:44.170 --> 0:08:47.090
<v Speaker 2>or when there's a problem, any sort of finger pointing

0:08:47.110 --> 0:08:50.709
<v Speaker 2>is can really have an impact to our customer supply chain.

0:08:50.770 --> 0:08:54.429
<v Speaker 2>So the first thing that we're providing is really an

0:08:54.630 --> 0:08:59.780
<v Speaker 2>end to end system that provides visibility throughout. Second thing

0:08:59.840 --> 0:09:03.420
<v Speaker 2>is that, you know, any disruption that hits in the world,

0:09:03.480 --> 0:09:08.390
<v Speaker 2>you can be pretty sure that it's hitting Amazon at

0:09:08.450 --> 0:09:12.309
<v Speaker 2>that same time. So we have built our network over

0:09:12.350 --> 0:09:15.790
<v Speaker 2>the years to be resilient and Anything that happens, whether

0:09:15.809 --> 0:09:22.100
<v Speaker 2>it's weather or a political issue or sort of a war,

0:09:22.660 --> 0:09:25.720
<v Speaker 2>what have you, we have to deal with it for ourselves.

0:09:25.780 --> 0:09:28.570
<v Speaker 2>And therefore, you get the benefit of our decades of

0:09:28.620 --> 0:09:33.550
<v Speaker 2>work to proactively adjust to those disruptions so that they

0:09:33.570 --> 0:09:36.050
<v Speaker 2>don't affect your end customer. Third thing that we talk

0:09:36.090 --> 0:09:39.670
<v Speaker 2>about is, you know, we build for a peak that

0:09:39.690 --> 0:09:43.860
<v Speaker 2>is higher than I dare say most others peaks are.

0:09:44.640 --> 0:09:50.410
<v Speaker 2>So we're investing a considerable amount in our supply chain

0:09:50.530 --> 0:09:53.490
<v Speaker 2>every year. And we do that because we've got the

0:09:53.510 --> 0:09:58.810
<v Speaker 2>volume from Amazon.com to support that. So if you have

0:09:58.890 --> 0:10:02.550
<v Speaker 2>demand spikes here, unlikely to outstrip our capacity. And at

0:10:02.620 --> 0:10:05.020
<v Speaker 2>any given point, just because we build for a very

0:10:05.080 --> 0:10:09.420
<v Speaker 2>large peak. And then additionally, we've got over a million robots,

0:10:09.480 --> 0:10:14.380
<v Speaker 2>for example, in our facilities around the world. It's a

0:10:14.420 --> 0:10:17.459
<v Speaker 2>lot of investment and, you know, a lot of time

0:10:17.500 --> 0:10:22.340
<v Speaker 2>that goes into that deployment. Our ASCS customers get the

0:10:22.400 --> 0:10:25.640
<v Speaker 2>benefit of all that investment we're making for Amazon. It

0:10:25.660 --> 0:10:28.500
<v Speaker 2>just flows downstream to them and they get it, you know,

0:10:29.059 --> 0:10:31.180
<v Speaker 2>effectively at a marginal cost. Right.

0:10:31.320 --> 0:10:34.160
<v Speaker 1>And obviously, you know, Amazon's a tech company, but you're

0:10:34.200 --> 0:10:38.160
<v Speaker 1>obviously a retailer as well. You know, I get it

0:10:38.200 --> 0:10:41.140
<v Speaker 1>probably either a box or an envelope from Amazon every

0:10:41.179 --> 0:10:41.959
<v Speaker 1>day at my house.

0:10:42.160 --> 0:10:42.599
<v Speaker 2>Thank you, sir.

0:10:43.400 --> 0:10:46.640
<v Speaker 1>You can thank my family. They're the ones that are

0:10:46.660 --> 0:10:47.620
<v Speaker 1>doing most of the buying.

0:10:47.990 --> 0:10:49.910
<v Speaker 2>We're in the same boat in my house, believe me.

0:10:50.690 --> 0:10:55.670
<v Speaker 1>But, you know, we love the convenience. But that being

0:10:55.710 --> 0:10:59.330
<v Speaker 1>that said, are there certain markets where it's tough for

0:10:59.370 --> 0:11:02.730
<v Speaker 1>you to enter? Because I would imagine a competitor like

0:11:02.770 --> 0:11:05.470
<v Speaker 1>a Walmart, for example, might not want to leverage you

0:11:05.530 --> 0:11:09.240
<v Speaker 1>for their LTL freight because, you know, you're competitors. They

0:11:09.280 --> 0:11:10.460
<v Speaker 1>don't want to necessarily.

0:11:10.160 --> 0:11:10.780
<v Speaker 2>Give you the business.

0:11:11.340 --> 0:11:15.670
<v Speaker 1>Are there markets like that where you're having problems? kind

0:11:15.710 --> 0:11:18.770
<v Speaker 1>of getting more of a footing because of that competitive

0:11:18.809 --> 0:11:20.510
<v Speaker 1>nature with other shippers?

0:11:21.390 --> 0:11:25.750
<v Speaker 2>Well, I'm not sure we see a ton of that

0:11:25.880 --> 0:11:31.620
<v Speaker 2>per se. Like we do, for example, distribute packages based

0:11:32.900 --> 0:11:38.500
<v Speaker 2>off of Walmart orders or TikTok orders or Sheen orders,

0:11:38.830 --> 0:11:41.070
<v Speaker 2>you know, pretty much name any marketplace in the book.

0:11:41.170 --> 0:11:44.540
<v Speaker 2>And if you use Amazon supply chain services, we can

0:11:44.620 --> 0:11:49.630
<v Speaker 2>fulfill for those marketplaces. You know, I will say that

0:11:49.650 --> 0:11:52.770
<v Speaker 2>there are certain segments of customers that we're still chipping

0:11:52.790 --> 0:12:00.100
<v Speaker 2>away at. You know, Amazon does really well at goods

0:12:00.380 --> 0:12:05.460
<v Speaker 2>that sell on Amazon. Now, the good news there is

0:12:05.480 --> 0:12:08.819
<v Speaker 2>that we've got over 400 million SKUs on Amazon. So

0:12:08.840 --> 0:12:12.329
<v Speaker 2>that basket of goods we sell is actually very broad, much,

0:12:12.410 --> 0:12:15.870
<v Speaker 2>much broader than most people think, but it's not everything.

0:12:16.340 --> 0:12:19.960
<v Speaker 2>And so you might get some customers who are, um,

0:12:20.160 --> 0:12:25.959
<v Speaker 2>interested in specialized services, for example, cold chain with GLP

0:12:26.340 --> 0:12:30.560
<v Speaker 2>right now, booming for obvious reasons. You know, we're, we're,

0:12:30.660 --> 0:12:31.920
<v Speaker 2>you know, we do a lot of that work in

0:12:31.940 --> 0:12:34.620
<v Speaker 2>our grocery business and our pharmacy business, but in our

0:12:34.640 --> 0:12:38.300
<v Speaker 2>sort of core mainline logistics network, we're still working on

0:12:38.360 --> 0:12:42.690
<v Speaker 2>things like, uh, cold chain, transportation. Those are, you know,

0:12:42.750 --> 0:12:45.490
<v Speaker 2>those are some examples of places we're still working at

0:12:45.550 --> 0:12:45.990
<v Speaker 2>to try to.

0:12:46.270 --> 0:12:49.230
<v Speaker 1>And in the same, like, frenemies vein, you know, obviously,

0:12:49.670 --> 0:12:52.510
<v Speaker 1>given your size, you're a huge purchaser of transportation, even

0:12:52.530 --> 0:12:54.670
<v Speaker 1>though you're doing a lot of stuff in-house. You know,

0:12:54.910 --> 0:12:58.820
<v Speaker 1>how do you view companies like DHL or DSV or C.H.

0:12:58.840 --> 0:13:02.059
<v Speaker 1>Robinson or EPS or J.B. Hunt, for that matter, you know,

0:13:02.179 --> 0:13:05.760
<v Speaker 1>as competitors, partners, both? Like, how does that relationship work?

0:13:05.780 --> 0:13:08.959
<v Speaker 1>Because because we've seen UPS kind of glide down their

0:13:08.980 --> 0:13:12.240
<v Speaker 1>exposure to Amazon over the years. Um, you know, how

0:13:12.260 --> 0:13:13.859
<v Speaker 1>do you see that relationship going?

0:13:13.900 --> 0:13:17.850
<v Speaker 2>Yeah, we, we, you know, um, the, the logistics market

0:13:17.950 --> 0:13:22.210
<v Speaker 2>needless to say is, is, is giant and it's growing.

0:13:22.270 --> 0:13:26.050
<v Speaker 2>And so, you know, we don't really see it as

0:13:26.130 --> 0:13:28.550
<v Speaker 2>a zero sum game where, you know, we're trying to

0:13:28.730 --> 0:13:33.270
<v Speaker 2>add new capabilities, uh, for customers rather than sort of

0:13:33.690 --> 0:13:37.440
<v Speaker 2>take share away from competitors. Um, One of the things

0:13:37.480 --> 0:13:40.900
<v Speaker 2>that Amazon.com has driven is what I like to think

0:13:40.940 --> 0:13:47.020
<v Speaker 2>of as a secular change in speed expectations. And so,

0:13:47.040 --> 0:13:49.530
<v Speaker 2>you know, because we have the prime program and we've

0:13:49.550 --> 0:13:53.930
<v Speaker 2>just been getting faster and faster and more reliable each

0:13:54.010 --> 0:13:57.050
<v Speaker 2>year on those last mile shipments, we've had to build

0:13:57.110 --> 0:14:01.080
<v Speaker 2>our entire network around that speed and certainty. That then

0:14:01.140 --> 0:14:05.520
<v Speaker 2>increases expectations of Customers who shop outside of Amazon, they're like, well,

0:14:05.540 --> 0:14:07.250
<v Speaker 2>why can't I get it in one or two days?

0:14:07.520 --> 0:14:09.430
<v Speaker 2>And why doesn't it arrive when you say it will,

0:14:09.850 --> 0:14:12.329
<v Speaker 2>just like I do on Amazon? That's a part of

0:14:12.390 --> 0:14:15.550
<v Speaker 2>the logistics market segment that we're really helping to drive,

0:14:15.590 --> 0:14:17.050
<v Speaker 2>which we think raises all boats.

0:14:18.110 --> 0:14:21.130
<v Speaker 1>So, you know, in transportation, the stuff that you guys do,

0:14:21.410 --> 0:14:23.640
<v Speaker 1>you tend to have like an asset light or a

0:14:23.680 --> 0:14:26.300
<v Speaker 1>non-asset model where you use a lot of third party

0:14:26.320 --> 0:14:31.550
<v Speaker 1>capacity to do the movement of freight. are there any

0:14:31.610 --> 0:14:35.230
<v Speaker 1>markets where maybe that model doesn't necessarily work if you

0:14:35.570 --> 0:14:40.170
<v Speaker 1>truly want to be more of a competitor? Like the

0:14:40.290 --> 0:14:44.230
<v Speaker 1>LTL space, for example, you know, cross-stock facilities are very

0:14:44.270 --> 0:14:48.030
<v Speaker 1>important for LTL. They need to be strategically placed across

0:14:48.370 --> 0:14:51.820
<v Speaker 1>the country. You know, you guys, from what I understand,

0:14:51.890 --> 0:14:54.119
<v Speaker 1>and please correct me if I'm wrong, you guys are

0:14:54.140 --> 0:14:56.860
<v Speaker 1>doing most of the movements like from your fulfillment centers

0:14:57.700 --> 0:15:00.540
<v Speaker 1>when you're consolidating freight. So can you talk about like

0:15:00.940 --> 0:15:04.640
<v Speaker 1>You know, does Amazon have plans maybe to take more

0:15:04.660 --> 0:15:08.320
<v Speaker 1>of an asset-based approach to any of these modes of transportation?

0:15:09.160 --> 0:15:11.880
<v Speaker 2>Well, I think it's a mix, honestly, Lee. You know,

0:15:11.940 --> 0:15:13.740
<v Speaker 2>if you look at any one of our modes, we

0:15:13.780 --> 0:15:19.120
<v Speaker 2>have a mix of owned assets and third-party assets. And

0:15:19.140 --> 0:15:22.820
<v Speaker 2>that goes across the, you know, across the chain. The

0:15:22.860 --> 0:15:27.370
<v Speaker 2>truth of the matter is at our scale, it's very,

0:15:27.450 --> 0:15:34.040
<v Speaker 2>very hard to... own 100% of the assets yourself. It's

0:15:34.060 --> 0:15:37.550
<v Speaker 2>just too hard to execute on that. And then similarly,

0:15:38.630 --> 0:15:41.350
<v Speaker 2>you don't want to be all third party because then

0:15:41.410 --> 0:15:45.870
<v Speaker 2>you lose a sense of ownership and control over the

0:15:45.890 --> 0:15:48.990
<v Speaker 2>customer experience, which is really important to us. So across

0:15:49.030 --> 0:15:53.890
<v Speaker 2>the board, really, it's a mix for us. The thing

0:15:53.930 --> 0:16:00.580
<v Speaker 2>we do is we use technology to make... Ourselves and

0:16:00.620 --> 0:16:05.580
<v Speaker 2>our customers relatively agnostic on whether it's a first party

0:16:05.720 --> 0:16:10.870
<v Speaker 2>asset or a third party asset. Our network operators, in fact,

0:16:11.630 --> 0:16:14.310
<v Speaker 2>usually don't even know if it's our asset or a

0:16:14.330 --> 0:16:17.810
<v Speaker 2>third party asset because they're using the same set of

0:16:18.050 --> 0:16:22.200
<v Speaker 2>technology tools to run the network. And that works pretty

0:16:22.220 --> 0:16:22.600
<v Speaker 2>well for us.

0:16:23.110 --> 0:16:27.140
<v Speaker 1>And so for ASCS, where do you see the greatest opportunities?

0:16:27.240 --> 0:16:30.080
<v Speaker 1>Is it the domestic transportation market here in the U.S.

0:16:30.220 --> 0:16:33.480
<v Speaker 1>or is it outside of the U.S.? Well.

0:16:35.190 --> 0:16:38.990
<v Speaker 2>So first off, ASCS is growing really, really well, I think.

0:16:39.310 --> 0:16:43.130
<v Speaker 2>And the thing that I've sort of learned over the

0:16:43.170 --> 0:16:47.200
<v Speaker 2>past few months here is that, you know, there's not

0:16:47.240 --> 0:16:51.060
<v Speaker 2>a demand, you know, there's plenty of demand. Folks are

0:16:51.640 --> 0:16:56.650
<v Speaker 2>really interested in having sort of an alternative out there

0:16:56.690 --> 0:17:00.609
<v Speaker 2>with an end to end supply chain for them to

0:17:00.650 --> 0:17:04.450
<v Speaker 2>be able to use. They just like the competitive dynamic

0:17:05.320 --> 0:17:08.870
<v Speaker 2>in the market. They also just like the customer obsession

0:17:08.910 --> 0:17:11.590
<v Speaker 2>that Amazon brings to it. Like we've been doing it

0:17:11.630 --> 0:17:14.609
<v Speaker 2>for ourselves for years and they like our attention to

0:17:14.650 --> 0:17:18.130
<v Speaker 2>detail and our high bar there. I will say that

0:17:18.210 --> 0:17:21.650
<v Speaker 2>the sort of the non-U.S. market is a huge area

0:17:21.670 --> 0:17:25.950
<v Speaker 2>of opportunity. You know, there are some things that we've

0:17:26.010 --> 0:17:29.389
<v Speaker 2>had time to mature in the States that that are

0:17:29.410 --> 0:17:31.780
<v Speaker 2>a little bit less mature, uh, if you go outside

0:17:31.820 --> 0:17:38.980
<v Speaker 2>the States, for example, that end to end visibility and, uh, disruption, uh, management, um,

0:17:39.740 --> 0:17:42.700
<v Speaker 2>those things we've got pretty well tuned here in the States.

0:17:42.740 --> 0:17:44.640
<v Speaker 2>And as you go outside the States, we have some

0:17:44.820 --> 0:17:49.470
<v Speaker 2>really nice opportunity for improvement there. Uh, we also, uh,

0:17:49.530 --> 0:17:52.450
<v Speaker 2>just because outside the, you know, outside the States, most

0:17:52.530 --> 0:17:55.659
<v Speaker 2>countries just aren't as large. And so it's, definitionally a

0:17:55.680 --> 0:18:00.800
<v Speaker 2>little bit more fragmented outside the US. So our technology binding,

0:18:00.859 --> 0:18:03.240
<v Speaker 2>so to speak, can really play a good role in

0:18:03.780 --> 0:18:06.200
<v Speaker 2>getting rid of the fragmentation a lot of customers have

0:18:06.220 --> 0:18:08.359
<v Speaker 2>to deal with on a daily basis and just making

0:18:08.400 --> 0:18:11.459
<v Speaker 2>it look like one easy to use network. Here's one

0:18:11.510 --> 0:18:15.150
<v Speaker 2>quick example. Over in the EU, for example, as a customer,

0:18:15.210 --> 0:18:17.290
<v Speaker 2>you can store your inventory in one of our warehouses,

0:18:17.330 --> 0:18:21.590
<v Speaker 2>let's say in Germany, but you can actually fulfill across 20,

0:18:21.590 --> 0:18:25.879
<v Speaker 2>I think it's 27, 26 EU states from that one

0:18:25.960 --> 0:18:29.300
<v Speaker 2>pool of inventory in Germany. And that's seamless to the

0:18:29.359 --> 0:18:31.720
<v Speaker 2>end customer. You don't have to have your inventory in

0:18:31.720 --> 0:18:34.200
<v Speaker 2>26 different spots. You can have it in one. Gotcha.

0:18:34.540 --> 0:18:37.100
<v Speaker 1>And so looking here in the domestic market, where do

0:18:37.119 --> 0:18:42.200
<v Speaker 1>you guys see the most growth for ASCS? Is it

0:18:42.220 --> 0:18:44.420
<v Speaker 1>the LTL side? Is it the freight brokerage side? Is

0:18:44.460 --> 0:18:45.159
<v Speaker 1>it forwarding?

0:18:45.220 --> 0:18:46.000
<v Speaker 2>Is it fulfillment?

0:18:46.380 --> 0:18:49.070
<v Speaker 1>Where is the growth for the organization?

0:18:49.090 --> 0:18:52.740
<v Speaker 2>Yeah. Well... I'll tell you, all of the modes are

0:18:52.780 --> 0:18:57.700
<v Speaker 2>growing very nicely. I'll say that our partial shipping business

0:18:58.070 --> 0:19:01.130
<v Speaker 2>is cooking with gas, as one of my former bosses

0:19:01.190 --> 0:19:04.690
<v Speaker 2>used to say. That's growing really, really quickly. And I

0:19:04.770 --> 0:19:09.609
<v Speaker 2>think it's because the same last mile network that does

0:19:09.750 --> 0:19:14.369
<v Speaker 2>the delivery to end customers for Amazon is now doing

0:19:14.410 --> 0:19:16.830
<v Speaker 2>it for business of all shapes and sizes. So you

0:19:16.869 --> 0:19:21.639
<v Speaker 2>get the same speed, same delivery. same resilience. You get

0:19:21.680 --> 0:19:23.639
<v Speaker 2>the little maps that show up on your phone that

0:19:23.660 --> 0:19:26.260
<v Speaker 2>show where it is. I think those are.

0:19:26.780 --> 0:19:29.330
<v Speaker 1>And your cost to serve is lower than the legacy players.

0:19:29.430 --> 0:19:32.449
<v Speaker 2>Cost to serve is strong as well. We like to

0:19:32.490 --> 0:19:34.910
<v Speaker 2>think of it as we deliver the most value per

0:19:36.030 --> 0:19:40.370
<v Speaker 2>dollar spent. You know, we are unlikely to ever be

0:19:40.430 --> 0:19:44.060
<v Speaker 2>the sort of the cheapest alternative out there. That's just

0:19:44.119 --> 0:19:46.260
<v Speaker 2>not how we think about it. We want to provide

0:19:46.619 --> 0:19:50.380
<v Speaker 2>the most services per dollar of anybody else. Um, So

0:19:50.480 --> 0:19:52.700
<v Speaker 2>you don't really use us if you want like the

0:19:52.760 --> 0:19:55.700
<v Speaker 2>cheapest and the slowest. You use us if you want

0:19:55.920 --> 0:19:59.770
<v Speaker 2>the best service, which then can hopefully grow your overall business. Because,

0:20:00.410 --> 0:20:02.230
<v Speaker 2>you know, we said Amazon, if there's one thing we've

0:20:02.250 --> 0:20:04.270
<v Speaker 2>learned over the past 25 years or so is that

0:20:04.290 --> 0:20:07.450
<v Speaker 2>supply chain is actually a growth driver, not just a

0:20:07.470 --> 0:20:07.860
<v Speaker 2>cost center.

0:20:08.650 --> 0:20:11.680
<v Speaker 1>And so, you know, obviously within Amazon's DNA, you're a

0:20:11.700 --> 0:20:16.780
<v Speaker 1>technology company that happens to do other things and do

0:20:16.820 --> 0:20:20.340
<v Speaker 1>them quite well. There's been a huge conversation about how

0:20:20.480 --> 0:20:23.619
<v Speaker 1>AI is going to be disrupting the supply chain and

0:20:23.869 --> 0:20:27.130
<v Speaker 1>logistics industries. Can you talk about, you know, how Amazon

0:20:27.170 --> 0:20:31.050
<v Speaker 1>is using AI within its supply chain and kind of

0:20:31.109 --> 0:20:33.530
<v Speaker 1>where you see the benefits and where you see that

0:20:33.570 --> 0:20:34.369
<v Speaker 1>going going forward?

0:20:34.800 --> 0:20:38.220
<v Speaker 2>Yeah, we've been using AI for a number of years,

0:20:38.260 --> 0:20:42.400
<v Speaker 2>of course, beginning really with machine learning. And now it's

0:20:43.380 --> 0:20:48.899
<v Speaker 2>moving as quickly as I've ever seen any technology transition

0:20:48.980 --> 0:20:53.750
<v Speaker 2>into large language model and agents. The things that have

0:20:53.770 --> 0:20:56.050
<v Speaker 2>been working for a number of years for us with

0:20:56.090 --> 0:21:02.160
<v Speaker 2>regards to AI, the first is disruption management. which is

0:21:03.100 --> 0:21:06.710
<v Speaker 2>something happens in the world and we need to reroute

0:21:06.750 --> 0:21:12.530
<v Speaker 2>our network. All that's been happening automatically for a number

0:21:12.570 --> 0:21:18.270
<v Speaker 2>of years. Second thing, a place where we have a

0:21:18.350 --> 0:21:23.139
<v Speaker 2>heavy use of AI is in inventory placement. We have

0:21:23.180 --> 0:21:25.960
<v Speaker 2>over 400 million SKUs, as I said a little bit earlier,

0:21:26.160 --> 0:21:36.030
<v Speaker 2>for sale on Amazon.com. And we have to forecast placement

0:21:36.070 --> 0:21:43.650
<v Speaker 2>for that inventory on an almost real-time basis. And that

0:21:43.690 --> 0:21:49.720
<v Speaker 2>really matters these days, particularly for our ASCS customers, because

0:21:49.740 --> 0:21:53.179
<v Speaker 2>they're not just selling on Amazon. They're also selling on

0:21:53.220 --> 0:21:57.040
<v Speaker 2>marketplaces like TikTok, for example. And they can have real

0:21:57.300 --> 0:22:01.010
<v Speaker 2>demand spikes on TikTok. And they need to make sure

0:22:01.030 --> 0:22:03.909
<v Speaker 2>that their inventory is in the right warehouse to fulfill

0:22:03.950 --> 0:22:12.350
<v Speaker 2>that demand. Our AI inventory placement algorithms are behind a

0:22:12.369 --> 0:22:15.510
<v Speaker 2>lot of that placement for us. I think that the trend,

0:22:15.530 --> 0:22:21.360
<v Speaker 2>of course, along with everybody, is to move to not

0:22:21.480 --> 0:22:27.820
<v Speaker 2>only detection and monitoring, but then following on to action.

0:22:29.710 --> 0:22:34.950
<v Speaker 2>If I am using AI to figure out where inventory

0:22:34.990 --> 0:22:36.650
<v Speaker 2>needs to be in the network and I don't have

0:22:36.730 --> 0:22:40.580
<v Speaker 2>enough in a particular location, right now a human being

0:22:40.619 --> 0:22:43.619
<v Speaker 2>has to step in and make that inventory transfer. Very,

0:22:43.660 --> 0:22:47.860
<v Speaker 2>very shortly, agents are going to be making that inventory transfer.

0:22:48.480 --> 0:22:50.479
<v Speaker 2>And the human beings are going to be more focused

0:22:50.580 --> 0:22:52.800
<v Speaker 2>on strategy and scenario planning.

0:22:52.820 --> 0:22:58.240
<v Speaker 1>Okay. And as leading ASCS in your seat, is there

0:22:58.280 --> 0:23:01.920
<v Speaker 1>a technology that you're really excited about, whether it's, you know,

0:23:02.940 --> 0:23:07.620
<v Speaker 1>automation or autonomous trucking or, you know, developments in AI

0:23:08.000 --> 0:23:11.500
<v Speaker 1>that you really think are going to, you know, benefit

0:23:12.080 --> 0:23:12.960
<v Speaker 1>your supply chains?

0:23:13.680 --> 0:23:17.520
<v Speaker 2>Well, the two that come to mind immediately is, you know,

0:23:17.540 --> 0:23:22.129
<v Speaker 2>I do think AI is going to make our sustainability

0:23:22.170 --> 0:23:28.389
<v Speaker 2>program even more effective. Getting a package from place A

0:23:28.390 --> 0:23:34.560
<v Speaker 2>to place B in the shortest, most efficient route in

0:23:34.580 --> 0:23:39.040
<v Speaker 2>the face of disruptions, I think we're going to save

0:23:39.100 --> 0:23:40.780
<v Speaker 2>a lot of miles on the road and a lot

0:23:40.800 --> 0:23:43.260
<v Speaker 2>of miles in the air because of AI because of that,

0:23:43.340 --> 0:23:46.510
<v Speaker 2>and the world will be better off for it. I

0:23:46.550 --> 0:23:50.659
<v Speaker 2>think the second thing is robotics. As I said a

0:23:50.660 --> 0:23:54.340
<v Speaker 2>little bit earlier, we've got over a million robots deployed

0:23:54.359 --> 0:23:59.720
<v Speaker 2>in our networks today. And the pace of improvement of

0:23:59.780 --> 0:24:05.590
<v Speaker 2>what those robots can do is amazing, quite frankly. And

0:24:05.690 --> 0:24:10.510
<v Speaker 2>we have moved from moving pallets of things across warehouses

0:24:10.630 --> 0:24:14.260
<v Speaker 2>within a divine zone for the robots to picking and

0:24:14.300 --> 0:24:20.500
<v Speaker 2>packing with arms or robots that can move throughout the

0:24:20.520 --> 0:24:27.980
<v Speaker 2>warehouse intermingled with our associates at a very high rate.

0:24:28.040 --> 0:24:31.899
<v Speaker 2>And I think that is going to keep accelerating over

0:24:31.920 --> 0:24:36.260
<v Speaker 2>the next few years here. That's important because all of

0:24:36.320 --> 0:24:41.120
<v Speaker 2>that both improves safety, but it also lets us get

0:24:41.270 --> 0:24:45.860
<v Speaker 2>more demand over through the same network. And that, of course,

0:24:45.900 --> 0:24:49.480
<v Speaker 2>decreases variable costs. We can pass those lower costs on

0:24:49.500 --> 0:24:50.660
<v Speaker 2>to our ASCS customers.

0:24:51.640 --> 0:24:54.100
<v Speaker 1>So we're in an environment right now where air freight

0:24:54.140 --> 0:24:58.139
<v Speaker 1>rates are relatively high, container rates are relatively high, trucking

0:24:58.180 --> 0:25:03.950
<v Speaker 1>markets here in the U.S. are seeing rates increasing. How

0:25:04.030 --> 0:25:11.070
<v Speaker 1>is that impacting ASCS? And, you know, while obviously higher

0:25:11.150 --> 0:25:15.700
<v Speaker 1>rates might hurt Amazon's margins, but do they benefit? Do

0:25:15.780 --> 0:25:18.369
<v Speaker 1>you have your own operating margins where you're trying to

0:25:18.430 --> 0:25:19.410
<v Speaker 1>operate as a profit?

0:25:19.790 --> 0:25:27.530
<v Speaker 2>Yeah, we're being hit with higher costs, particularly for freight

0:25:27.590 --> 0:25:31.320
<v Speaker 2>and trucking, just like everybody else is, quite frankly. And

0:25:31.340 --> 0:25:34.880
<v Speaker 2>there are the fuel costs that we have to absorb.

0:25:35.480 --> 0:25:39.620
<v Speaker 2>And then there are some new regulations in place that

0:25:40.050 --> 0:25:43.449
<v Speaker 2>that mean that there are fewer truck drivers available, and

0:25:43.490 --> 0:25:48.570
<v Speaker 2>that also increases costs over time. So we're having to

0:25:48.609 --> 0:25:52.630
<v Speaker 2>deal with those on a daily basis. That was not

0:25:53.750 --> 0:26:00.570
<v Speaker 2>the increase in trucking costs. We had models that forecasted

0:26:00.590 --> 0:26:03.530
<v Speaker 2>what we thought the supply cost was going to do

0:26:03.570 --> 0:26:06.800
<v Speaker 2>this year, We did not anticipate the rate at which

0:26:06.859 --> 0:26:09.800
<v Speaker 2>costs increase this year. So we've had to work hard

0:26:09.840 --> 0:26:13.639
<v Speaker 2>to make sure that those increased costs don't show up

0:26:13.660 --> 0:26:14.220
<v Speaker 2>to our customers.

0:26:14.500 --> 0:26:16.879
<v Speaker 1>Yeah, spot trucking rates are up around like 30%, 35%,

0:26:16.880 --> 0:26:21.550
<v Speaker 1>excluding fuel surcharges. And then contractual rates are up, call

0:26:21.630 --> 0:26:24.270
<v Speaker 1>it 9% to 10% year over year. So they're definitely

0:26:24.330 --> 0:26:27.130
<v Speaker 1>moving higher. And given that, so are you guys using

0:26:27.170 --> 0:26:29.930
<v Speaker 1>intermodal more? Do you use intermodal? Is that part of

0:26:29.950 --> 0:26:30.609
<v Speaker 1>your strategy?

0:26:30.730 --> 0:26:37.510
<v Speaker 2>Yeah, we do. We've had an intermodal mode for a

0:26:37.570 --> 0:26:42.890
<v Speaker 2>number of years. And as you can expect, as trucking

0:26:42.930 --> 0:26:46.250
<v Speaker 2>costs go up, we're shifting more and more of our

0:26:46.310 --> 0:26:49.350
<v Speaker 2>volume to intermodal. One of the things we're doing is

0:26:49.390 --> 0:26:54.550
<v Speaker 2>we're working with the railway companies so that they adopt

0:26:54.890 --> 0:26:58.939
<v Speaker 2>our technology. so that things can move faster with higher

0:26:59.200 --> 0:27:03.330
<v Speaker 2>visibility throughout the intermodal network. Nirvana would be we can

0:27:03.369 --> 0:27:06.010
<v Speaker 2>put a lot of stuff on trains, and they get

0:27:06.070 --> 0:27:09.910
<v Speaker 2>there just as fast and just as reliably as they

0:27:09.930 --> 0:27:12.150
<v Speaker 2>do on trucks. We've got a little ways to go,

0:27:12.190 --> 0:27:14.230
<v Speaker 2>but we're making some good strides with our partners there.

0:27:14.430 --> 0:27:17.230
<v Speaker 1>Do you have a one-rail partner that you're using predominantly

0:27:17.290 --> 0:27:19.260
<v Speaker 1>in the west and one in the east, or are

0:27:19.359 --> 0:27:20.420
<v Speaker 1>you kind of agnostic?

0:27:20.700 --> 0:27:23.139
<v Speaker 2>It's a mix. Uh, we, you know, we use most

0:27:23.200 --> 0:27:25.719
<v Speaker 2>of the, you know, again, at our scale, uh, you know,

0:27:25.770 --> 0:27:30.410
<v Speaker 2>we use most of the, um, available supply that's out there. It's, it's,

0:27:30.710 --> 0:27:33.290
<v Speaker 2>it's highly likely that we're using them in one form

0:27:33.310 --> 0:27:33.610
<v Speaker 2>or another.

0:27:33.790 --> 0:27:36.650
<v Speaker 1>So if there's one thing that you could do for

0:27:36.810 --> 0:27:41.420
<v Speaker 1>Amazon to make its supply chain more efficient today, what, what,

0:27:41.480 --> 0:27:42.180
<v Speaker 1>what would it be?

0:27:42.200 --> 0:27:49.020
<v Speaker 2>That's a great question. I think, uh, There are a

0:27:49.280 --> 0:27:52.859
<v Speaker 2>couple of things that we're working on, I guess, that

0:27:53.619 --> 0:27:56.659
<v Speaker 2>I think come to mind first and foremost. First of all,

0:27:56.680 --> 0:28:00.659
<v Speaker 2>there's just the infusion of AI across every aspect of

0:28:00.840 --> 0:28:05.160
<v Speaker 2>our operation. And that continues on a daily basis. Second

0:28:05.180 --> 0:28:08.830
<v Speaker 2>thing is, you know, some of the aspects of our

0:28:08.880 --> 0:28:12.869
<v Speaker 2>services that have worked really well for Amazon, it turns

0:28:13.010 --> 0:28:18.160
<v Speaker 2>out that when we're servicing Amazon, Non-Amazon sellers, we need

0:28:18.200 --> 0:28:21.250
<v Speaker 2>to sort of adjust our operating a bit to meet

0:28:21.290 --> 0:28:26.830
<v Speaker 2>their needs. Here's a case in point. Our whole network

0:28:26.910 --> 0:28:30.190
<v Speaker 2>is built off of speed. And so we frequently will

0:28:30.250 --> 0:28:33.859
<v Speaker 2>arrive at pickups or drop-offs. Let's just say it's freight

0:28:33.940 --> 0:28:37.850
<v Speaker 2>or it could be parcels. Now, you know, in a

0:28:37.890 --> 0:28:41.150
<v Speaker 2>lot of, in most cases, dare I say it in

0:28:41.170 --> 0:28:44.650
<v Speaker 2>the world, you know, early is good or early is okay.

0:28:45.090 --> 0:28:47.730
<v Speaker 2>In the logistics business, it turns out that, of course,

0:28:47.810 --> 0:28:50.040
<v Speaker 2>if we're too early, you know, the doctor might not

0:28:50.100 --> 0:28:54.140
<v Speaker 2>be available. The personnel might not be available. So we've

0:28:54.160 --> 0:28:58.960
<v Speaker 2>had to tighten up our technology controls to make sure

0:28:59.020 --> 0:29:02.360
<v Speaker 2>that our drivers don't show up too early. That's an

0:29:02.400 --> 0:29:05.420
<v Speaker 2>example of the kinds of adjustments we're having to make

0:29:05.820 --> 0:29:08.700
<v Speaker 2>to our network on a daily basis to make sure

0:29:08.740 --> 0:29:12.120
<v Speaker 2>it not only works well for Amazon volume, but also

0:29:12.160 --> 0:29:13.440
<v Speaker 2>for off Amazon volume as well.

0:29:14.280 --> 0:29:17.240
<v Speaker 1>And, you know, are there things that customers are asking

0:29:17.300 --> 0:29:20.630
<v Speaker 1>you today that they weren't asking for a couple of

0:29:20.640 --> 0:29:25.750
<v Speaker 1>years ago, whether it's services or performance measurements?

0:29:26.290 --> 0:29:30.090
<v Speaker 2>Yeah. Well, a couple of things that come to mind

0:29:30.170 --> 0:29:35.200
<v Speaker 2>there is, I talked a little earlier about they just

0:29:35.260 --> 0:29:41.490
<v Speaker 2>continue to want an end-to-end seamless network. They really would

0:29:41.550 --> 0:29:46.130
<v Speaker 2>love the convenience of having one partner that can service

0:29:46.320 --> 0:29:50.380
<v Speaker 2>most of their volume across modes. As I said earlier,

0:29:51.200 --> 0:29:54.180
<v Speaker 2>many customers are using a fragmented supply chain and that

0:29:54.240 --> 0:29:58.440
<v Speaker 2>just makes things much more complicated and it increases costs.

0:29:58.520 --> 0:30:03.390
<v Speaker 2>And so we continue to knit our services together in

0:30:03.430 --> 0:30:06.310
<v Speaker 2>a way that makes it really easy for our customers

0:30:06.390 --> 0:30:09.210
<v Speaker 2>both to use and to get visibility on. And that

0:30:09.830 --> 0:30:13.610
<v Speaker 2>increases ease of use, but it also decreases costs. That's

0:30:13.850 --> 0:30:19.040
<v Speaker 2>one area. Another area that they are increasingly asking for

0:30:19.480 --> 0:30:25.600
<v Speaker 2>is help me take advantage of international markets. Right now

0:30:25.620 --> 0:30:30.660
<v Speaker 2>it's hard or it's relatively hard to, Let's say that

0:30:30.680 --> 0:30:32.480
<v Speaker 2>you sell stuff in the U.S. and you want to

0:30:32.500 --> 0:30:35.120
<v Speaker 2>start to sell stuff outside of the U.S. That's a

0:30:35.180 --> 0:30:39.010
<v Speaker 2>complicated process, and we're trying to make that easier and

0:30:39.110 --> 0:30:44.050
<v Speaker 2>easier for sellers. Because we do it for Amazon.com, we

0:30:44.090 --> 0:30:48.190
<v Speaker 2>can externalize a lot of those capabilities for our non-Amazon

0:30:48.250 --> 0:30:50.090
<v Speaker 2>customers as well to make it easy for them to

0:30:50.130 --> 0:30:54.010
<v Speaker 2>expand across the world. I think a third thing I

0:30:55.030 --> 0:30:58.130
<v Speaker 2>mentioned a little bit earlier is that They basically want

0:30:58.270 --> 0:31:01.910
<v Speaker 2>AI not only to do things reactively, but proactively as well.

0:31:01.970 --> 0:31:05.490
<v Speaker 2>So don't only detect what's going on out there, but

0:31:05.610 --> 0:31:11.130
<v Speaker 2>also action it. That just, for the most part, that's

0:31:11.170 --> 0:31:16.280
<v Speaker 2>going to decrease the amount of work that they have

0:31:16.320 --> 0:31:19.960
<v Speaker 2>to do on their end. And their staff can then

0:31:20.500 --> 0:31:28.060
<v Speaker 2>really only have to deal with the exceptional disruptions. generally

0:31:28.120 --> 0:31:32.320
<v Speaker 2>supply chain is call it 60% of most of our customers'

0:31:33.220 --> 0:31:36.740
<v Speaker 2>cost bases. You know, anything you can do to make

0:31:36.760 --> 0:31:39.200
<v Speaker 2>that a little bit more simple and proactive is going

0:31:39.220 --> 0:31:40.480
<v Speaker 2>to be a good thing for their businesses.

0:31:41.100 --> 0:31:43.260
<v Speaker 1>And so has your strategy in the past been to

0:31:43.320 --> 0:31:46.400
<v Speaker 1>grow all these services organic, or have you guys gone

0:31:46.510 --> 0:31:48.570
<v Speaker 1>out and bought like a freight forwarder or a freight

0:31:48.610 --> 0:31:51.910
<v Speaker 1>broker to, you know, enhance a certain part of the

0:31:51.950 --> 0:31:54.870
<v Speaker 1>market that maybe you're not in, whether that is from

0:31:54.890 --> 0:31:57.420
<v Speaker 1>a you know, a lot of like freight forwarders will

0:31:57.460 --> 0:31:59.410
<v Speaker 1>buy another freight forwarder, a different country where they don't

0:31:59.430 --> 0:32:02.950
<v Speaker 1>have exposure to. Have you guys bought, uh, used acquisitions

0:32:03.010 --> 0:32:03.790
<v Speaker 1>as a growth driver?

0:32:03.810 --> 0:32:07.790
<v Speaker 2>I'm trying to think of any actual acquisitions we've done

0:32:07.850 --> 0:32:11.450
<v Speaker 2>and none come to mind. Uh, we do a lot

0:32:11.490 --> 0:32:13.830
<v Speaker 2>of partnerships, of course, like, you know, we work with

0:32:13.890 --> 0:32:16.850
<v Speaker 2>a lot of third parties and we use our technology

0:32:16.890 --> 0:32:19.590
<v Speaker 2>to integrate them closely into our network in terms of

0:32:20.030 --> 0:32:24.260
<v Speaker 2>outright acquisitions. Um, None are coming to mind. And there's

0:32:24.280 --> 0:32:28.200
<v Speaker 2>a reason for that is that acquisitions come with, you know,

0:32:29.230 --> 0:32:31.870
<v Speaker 2>these companies have their own culture and their own operating

0:32:31.890 --> 0:32:35.950
<v Speaker 2>philosophy and their own technology stacks. And it turns out

0:32:36.030 --> 0:32:39.790
<v Speaker 2>that we have to rebuild a lot of what's behind

0:32:39.810 --> 0:32:43.130
<v Speaker 2>those acquisitions to integrate it effectively into the Amazon network.

0:32:43.190 --> 0:32:45.670
<v Speaker 2>So we tend to build it ourselves or partner for

0:32:45.690 --> 0:32:46.150
<v Speaker 2>the most part.

0:32:46.750 --> 0:32:48.950
<v Speaker 1>And, you know, on a personal note, how did you

0:32:48.970 --> 0:32:51.600
<v Speaker 1>get into the world of supply chains and logistics?

0:32:52.630 --> 0:32:57.760
<v Speaker 2>By accident, just like most of us. I started my

0:32:57.820 --> 0:33:01.219
<v Speaker 2>career and was in devices for a long time. So

0:33:01.240 --> 0:33:03.900
<v Speaker 2>I worked at Apple and I worked in Silicon Valley.

0:33:03.920 --> 0:33:06.460
<v Speaker 2>And then I was part of the founding team at

0:33:06.540 --> 0:33:10.760
<v Speaker 2>Amazon that did our first devices. So the first Kindles

0:33:10.820 --> 0:33:15.660
<v Speaker 2>and the first Fire TVs and the first tablets. When

0:33:15.740 --> 0:33:18.990
<v Speaker 2>Amazon began to build its own middle mile and last

0:33:19.130 --> 0:33:25.140
<v Speaker 2>mile network, the team that was sort of starting that

0:33:25.300 --> 0:33:27.340
<v Speaker 2>up asked me to come over and I was kind

0:33:27.380 --> 0:33:32.720
<v Speaker 2>of ready for a new learning curve. And you know,

0:33:33.380 --> 0:33:35.800
<v Speaker 2>I remember saying to my boss at the time, I

0:33:35.960 --> 0:33:38.760
<v Speaker 2>think it was Dave Clark. I'm like, Hey, you know,

0:33:38.800 --> 0:33:40.960
<v Speaker 2>you realize I know nothing, you know, I have never

0:33:41.040 --> 0:33:44.220
<v Speaker 2>shipped a package in my life. And his response I

0:33:44.240 --> 0:33:47.240
<v Speaker 2>think was very telling about the culture of Amazon. It was, well,

0:33:47.520 --> 0:33:52.330
<v Speaker 2>you know, We have many, many thousands of people who

0:33:52.390 --> 0:33:55.870
<v Speaker 2>are very good at shipping boxes. We'd like to bring

0:33:55.930 --> 0:33:59.530
<v Speaker 2>in other skill sets. Right. How to build a business

0:33:59.590 --> 0:34:04.150
<v Speaker 2>from scratch, how to do product innovation into that team

0:34:04.470 --> 0:34:07.090
<v Speaker 2>so we can have both the operations expertise as well

0:34:07.130 --> 0:34:11.150
<v Speaker 2>as the innovation expertise. So I joined the Middle Mile

0:34:11.210 --> 0:34:16.910
<v Speaker 2>team right when we were first setting it up. I

0:34:17.130 --> 0:34:19.290
<v Speaker 2>worked with the team to set up a lot of

0:34:19.350 --> 0:34:23.870
<v Speaker 2>the technology infrastructure. I talked a little bit earlier about

0:34:23.910 --> 0:34:27.670
<v Speaker 2>how we integrate our third-party partners into our network. I

0:34:27.750 --> 0:34:31.430
<v Speaker 2>ended up running the freight network overall for a period.

0:34:31.510 --> 0:34:34.000
<v Speaker 2>And now for the past five or six years, I've

0:34:34.020 --> 0:34:38.420
<v Speaker 2>been working on taking the Amazon network and externalizing it

0:34:38.840 --> 0:34:39.840
<v Speaker 2>so that everybody can use it.

0:34:40.610 --> 0:34:44.209
<v Speaker 1>And just on that, on externalizing, what do you think

0:34:44.570 --> 0:34:49.610
<v Speaker 1>the biggest challenge is to that or has been doing that?

0:34:49.630 --> 0:34:51.210
<v Speaker 1>Maybe you've overcome that challenge.

0:34:52.190 --> 0:34:55.910
<v Speaker 2>Yeah, well, that's a good question. I would say that

0:34:55.989 --> 0:34:59.250
<v Speaker 2>we've got a good road ahead of us to continue

0:34:59.810 --> 0:35:04.549
<v Speaker 2>to adjust our network to make sure that we have

0:35:04.670 --> 0:35:07.969
<v Speaker 2>all the service capabilities that our customers need. If you're

0:35:08.010 --> 0:35:11.400
<v Speaker 2>working with a large customer, Let's say Procter &amp; Gamble,

0:35:11.420 --> 0:35:14.480
<v Speaker 2>for example, or you could do Land's End, you could

0:35:14.500 --> 0:35:17.549
<v Speaker 2>do 3M, you could do American Eagle. You know, these

0:35:17.590 --> 0:35:22.750
<v Speaker 2>are large, complex supply chains. And I'd say today we're

0:35:22.790 --> 0:35:26.930
<v Speaker 2>doing a good job handling part of their volume. But

0:35:26.969 --> 0:35:29.589
<v Speaker 2>we've got some room to grow in terms of making

0:35:29.630 --> 0:35:32.530
<v Speaker 2>sure we've got the capability so that they feel good

0:35:32.590 --> 0:35:36.120
<v Speaker 2>about working with us for the majority of their volume.

0:35:36.530 --> 0:35:38.750
<v Speaker 1>Well, good luck with that. And, you know, before I

0:35:39.030 --> 0:35:41.330
<v Speaker 1>let you go, there's a question I would like to

0:35:41.450 --> 0:35:43.150
<v Speaker 1>ask our guests. You know, if you have a favorite

0:35:43.170 --> 0:35:48.069
<v Speaker 1>book on technology, leadership or transportation that kind of you've

0:35:48.130 --> 0:35:50.719
<v Speaker 1>read over the years that kind of resonates with you today.

0:35:51.469 --> 0:35:55.759
<v Speaker 2>Well, the one that immediately pops into my mind is

0:35:55.780 --> 0:36:00.420
<v Speaker 2>Zero to One by Peter Thiel. That that was a

0:36:01.340 --> 0:36:07.650
<v Speaker 2>seminal book. when I was a younger person, just in

0:36:07.730 --> 0:36:10.770
<v Speaker 2>terms of the kinds of things that you're likely to

0:36:10.830 --> 0:36:14.009
<v Speaker 2>face when you're truly trying to innovate. One of those

0:36:14.070 --> 0:36:19.140
<v Speaker 2>things is that innovation and failure are inseparable twins. So

0:36:19.200 --> 0:36:21.020
<v Speaker 2>if you're going to innovate, you better get comfortable with

0:36:21.060 --> 0:36:22.719
<v Speaker 2>failure as well. Absolutely.

0:36:23.140 --> 0:36:26.100
<v Speaker 1>Well, Peter, thank you for joining us today and making

0:36:26.140 --> 0:36:29.299
<v Speaker 1>the trip to Bloomberg's global headquarters here in New York City.

0:36:29.700 --> 0:36:30.690
<v Speaker 2>Thank you very much for having me.

0:36:30.910 --> 0:36:34.239
<v Speaker 1>We really appreciate you sharing your perspective on Amazon supply

0:36:34.260 --> 0:36:37.900
<v Speaker 1>chain services, the futures of logistics, and where you see

0:36:38.080 --> 0:36:40.600
<v Speaker 1>the industry heading. It was really a pleasure having you

0:36:40.760 --> 0:36:43.980
<v Speaker 1>on Talking Transport. So thank you very much. Thanks, Lee.

0:36:44.520 --> 0:36:47.319
<v Speaker 1>And thank you for listening. If you enjoyed today's conversation,

0:36:47.360 --> 0:36:50.819
<v Speaker 1>please subscribe, rate, and review, and share the podcast. We've

0:36:50.860 --> 0:36:55.580
<v Speaker 1>got a great lineup of guests coming up featuring CEOs, founders, investors, regulators,

0:36:55.640 --> 0:36:59.950
<v Speaker 1>and innovators from across the transportation and logistics landscape. If

0:36:59.969 --> 0:37:03.070
<v Speaker 1>you'd like to learn more about the freight transportation logistics market,

0:37:03.110 --> 0:37:06.330
<v Speaker 1>you can find our research on the Bloomberg Terminal at BIGo.

0:37:06.730 --> 0:37:09.650
<v Speaker 1>And be sure to connect with me on LinkedIn.

0:37:09.210 --> 0:37:11.129
<v Speaker 2>Or follow me on X at Logistics Lee.

0:37:11.469 --> 0:37:14.240
<v Speaker 1>I'd also like to thank our outstanding producers, Miriam Traor

0:37:14.550 --> 0:37:17.680
<v Speaker 1>and Aditya Samani, for helping bringing Talking Transports to life

0:37:17.940 --> 0:37:21.340
<v Speaker 1>every week. This is Lee Klaskow signing off. Talk to

0:37:21.360 --> 0:37:21.879
<v Speaker 1>you next time.