More data, as one can never have enough data… Amazon is ALSO doing more shipping. Below is just one shipment. Note that for the first shipment listed to SBD1, 36 of 48 units were immediately sent to locations back on the OTHER side of the Rockies from CA, save for 2 units sent to NM.
The data below is not pretty - sorry, but I can’t figure out a “table” for this forum thing. The Data for the “SBD1” FC is the destination FC, the city/state, the number of units sent to it, and the date that each arrived at that destination FC.
Three of the other cartons of 48 were all distributed reasonably well, but the pattern seems that CONSISTENLY 1 of each of my 5 cartons is being sent to California, only to have the bulk of it backhauled immediately to the other side of the Rockies.
Also, it is interesting to see that 2 cartons of 48 were sent to Greenfield IN, only to have one of them immediately sent back to Charlotte, NC (CLT4) when we shipped 2 of the other cartons directly to Charlotte, NC (CLT2). Why not just send 3 to Charlotte? All I can think is that we are paying extra to better-utilize Amazon’s backhauling trailers.
And I think I see the “cost savings” for Amazon here - due to customer population alone, lots of stuff goes to the West coast from the East coast. But the trucks going back go back at least partly empty. So, by forcing me to pay more shipping to send things to California, Amazon uses a truck that would otherwise go back East half empty, rather than increasing the number of trucks already in the east. So, if your product sells overwhelming east of the Rockies, you subsidize the cost of the more generic-demand products, which can be evenly distributed based solely upon population.
What do we do? Well, if this is causing you to slide into “Low Inventory Fee”, you jam a shipment to ONE location, and pay the “placement fee”, if that is lower than the low inventory fee you would avoid by doing so. Either way there is a fee, and these are new fees, so they are still not well understood (to us, at least).
WHERE AMAZON HIDES THIS DATA: Shipment “Shipment Events” show which FCs were distributed to from the first, but [grrr!] NOT the quantities. The inventory ledger, which shows to and from and quantity and date, but NOT which shipment each unit came from [grrr! again!]
So, you end up sorting the inventory ledger by FC, and then looking for dates that come after the date of delivery to the FC that shipped to each downstream FC.
You could lather, rinse, repeat and see further FC transfers down the chain, but therein lies madness.
3/5/2025
SBD1 48
Bloomington, CA
DSM5 (BONDURANT, IA 1 3/31/2025
STL8 (SAINT PETERS, MO 4 3/30/2025
DAL2 (DFW Airport, TX 1 3/31/2025
DFW7 (Fort Worth, TX 6 3/28/2025
ELP1 (EL PASO, TX 1 3/25/2025
OMA2 (OMAHA, NE 1 4/6/2025
MDW7 (Monee, IL 1 3/28/2025
AUS3 (WACO, TX 4 3/27/2025
FTW6 (Dallas, TX 5 3/27/2025
ABQ1 (ALBUQUERQUE, NM 2 3/24/2025
TUL2 (TULSA, OK 1 3/27/2025
OKC1 (OKLAHOMA CITY, OK 3 3/27/2025
HOU2 (Houston, TX 1 3/16/2025
DAL3 (DALLAS, TX 5 3/27/2025
ORD5 (MATTESON, IL 1 3/28/2025
IGQ1 (HARVEY, IL 1 3/29/2025
MQJ1 96 3/16/2025
Greenfield, IN CLT4 (CHARLOTTE, NC 48 3/18/2025
AKC1 (AKRON, OH) 48 3/19/2025
SWF2 48
Yonkers, NY
SYR1 (LIVERPOOL, NY)
LGB8 48
Rialto, CA
ONT6 (Moreno Valley, CA
OXR1 (OXNARD, CA
DEN3 (Thornton, CO
SAN3 (SAN DIEGO, CA
SCK6 (TRACY, CA
SMF1 (Sacramento, CA
BFI4 (Kent, WA
PDX9 (Troutdale, OR
SBD6 (Ontario, CA
PAE2 (ARLINGTON, WA
FAT1 (Fresno, CA
GEG1 (SPOKANE, WA
CLT2 96
Charlotte, NC
TPA1 (Ruskin, FL
MEM4 (MEMPHIS, TN
JAX7 (JACKSONVILLE, FL
BTR1 (BATON ROUGE, LA
TPA4 (Temple Terrace, FL
BHM1 (BESSEMER, AL
AGS1 (APPLING, GA
SHV1 (SHREVEPORT, LA
MIA1 (Opa-Locka, FL
ATL2 (STONE MOUNTAIN, GA
TLH2 (TALLAHASSEE, FL
MCO1 (Orlando, FL