What you'll get from this article
- Understand what Amazon Supply Chain Services actually includes. Beyond Prime delivery and FBA — the full stack from bulk warehousing to last-mile delivery, and which parts are directly relevant to shippers operating outside the Amazon marketplace.
- See where Amazon's delivery network competes with traditional parcel carriers. Which shipment profiles, weight ranges, and delivery types Amazon handles effectively — and where UPS, FedEx, and regional carriers still hold the advantage.
- Understand the data and dependency tradeoffs explicitly. What Amazon sees when you use their supply chain services, and why that calculation differs depending on your business and competitive position.
- Know when multi-channel fulfillment makes operational sense for a shipper. The conditions under which Amazon's logistics stack offers real value versus where the tradeoffs outweigh the rates.
- Walk away with a decision framework. A set of questions to model against your actual shipment history before committing volume to any Amazon logistics service.
A standard carrier review starts with UPS and FedEx. Maybe a regional carrier if the volume warrants it. Then someone on the team asks whether Amazon should be in the mix.
A few years ago, that question was easy to dismiss. Amazon was a marketplace, not a carrier. Keep them in the channel column, not the carrier column.
That answer is harder to give now. Amazon has built what is functionally a parallel parcel and logistics network — one that handles hundreds of millions of packages a year, reaches most residential addresses in North America, and is now available to shippers who do not sell a single unit on Amazon.com.
Amazon Supply Chain Services is not just a tool for marketplace sellers. It is a logistics network that now covers fulfillment and last-mile delivery for businesses operating entirely outside Amazon.com — and the tradeoffs are worth modeling before the next carrier review.
This article explains what Amazon Supply Chain Services actually includes, where it competes with traditional parcel carriers, what the data and dependency tradeoffs look like for shippers, and how to evaluate it against your actual freight profile.
What Amazon Supply Chain Services actually includes
Amazon Supply Chain Services is not a single product. It is a set of connected services Amazon built over several years and consolidated under one name in 2023. The pitch was that a brand could hand off inventory at the point of manufacture and let Amazon manage the rest — storage, replenishment, fulfillment, and delivery — without touching any of those steps directly.
The services that make up that stack are:
| Service | What it does | Most relevant to |
|---|---|---|
| Amazon Warehousing & Distribution (AWD) | Bulk upstream storage that replenishes FBA and MCF fulfillment centers automatically | Brands managing large inventory pools upstream of fulfillment; reduces FBA storage costs by holding inventory at AWD until needed |
| Multi-Channel Fulfillment (MCF) | Amazon fulfills orders placed on any channel — Shopify, a brand's own website, other platforms — from inventory stored in Amazon's network | Shippers selling outside Amazon who want Amazon to handle pick, pack, and delivery without managing a separate 3PL |
| Buy with Prime | Amazon Prime checkout on a brand's own website; Amazon handles payment and delivery | Direct-to-consumer brands where Prime customer overlap is high and conversion on the brand site is the primary goal |
| Amazon Global Logistics (AGL) | Cross-border freight from manufacturers, primarily from Asia, into Amazon's fulfillment network | Importers sourcing from overseas who want end-to-end visibility from factory to fulfillment center |
| Amazon Logistics (AMZL) | Amazon's own last-mile parcel delivery network; carries most marketplace orders and all MCF and Buy with Prime deliveries | Any shipper using MCF or Buy with Prime — AMZL handles the final delivery leg by default in covered areas |
For shippers evaluating carrier options, the piece that matters most is Multi-Channel Fulfillment combined with Amazon Logistics. Together, they represent Amazon's direct entry into what has historically been UPS and FedEx territory: fulfilling and delivering orders that have nothing to do with Amazon.com.
How Amazon built a parcel network without announcing it
Amazon's last-mile delivery operation grew out of a capacity problem. In the early part of the last decade, Amazon was so dependent on UPS, FedEx, and the postal service that carrier failures during peak season created visible delivery problems for Prime customers. The response was to build internal capacity.
Over the following years, Amazon built a network of sortation centers, delivery stations, and contracted last-mile drivers operating under the Amazon Delivery Service Partner program. By the mid-2020s, Amazon Logistics had become one of the highest-volume parcel delivery networks in North America — handling a significant share of Amazon marketplace orders and increasingly carrying volume for outside channels.
The key shift for shippers is that Amazon no longer keeps that network internal. When a brand uses Multi-Channel Fulfillment, the customer's package moves through the same sort centers and delivery routes as a Prime order. The delivery speed, tracking, and reliability draw from the same infrastructure.
That is why the question of whether Amazon belongs in a carrier review is harder to dismiss than it used to be. The infrastructure is real, the coverage is broad in major markets, and the rates are openly competitive for certain shipment profiles.
What multi-channel fulfillment actually means for a shipper
Multi-Channel Fulfillment is the part of Amazon Supply Chain Services most directly relevant to shippers who are not primarily marketplace sellers.
The mechanics are straightforward: send inventory to an Amazon fulfillment center — either directly or through Amazon Warehousing and Distribution — and when an order arrives on any channel, submit a fulfillment request to Amazon. They pick, pack, and ship it.
The practical implications require a closer look.
Inventory inside Amazon's network is not inventory you can access directly
Once product is in Amazon's fulfillment centers, redirecting it to a different channel, processing returns, or switching carriers requires working within Amazon's system and on Amazon's timeline. For most standard fulfillment use cases this is not a problem. For shippers with complex reverse logistics or channel-switching requirements, it is an operational constraint worth understanding before going in.
Packaging is Amazon's to manage
Amazon now offers unbranded packaging for MCF orders — they removed the Amazon-branded box requirement that was a common concern for brands. But the shipper is still shipping inside a carton they did not choose, with dimensions and handling standards Amazon controls. For brands where unboxing is a meaningful part of the customer experience, this is a tradeoff to evaluate, not a technicality to overlook.
Coverage is real, but not uniform
Amazon Logistics is strong in major metropolitan areas and dense suburban zones. It weakens in rural markets and smaller communities — and in Canada, AMZL coverage is concentrated in major urban centres. Orders outside covered areas may route through Amazon's carrier partners, which can affect delivery speed and tracking visibility. Before treating Amazon's two-day delivery promise as a given across your customer base, confirm actual coverage against your specific delivery address distribution.
Returns flow through Amazon's system
MCF returns go back to Amazon fulfillment centers by default. How returned inventory is handled — inspected, restocked, disposed, or re-routed — happens under Amazon's process, not yours. If reverse logistics is a complex part of your operations, confirm how MCF returns work before the first return wave arrives, not after.
The rate picture: where Amazon competes and where it does not
Amazon does not publish a simple rate card the way UPS or FedEx does. MCF rates are based on product size tiers and weight, available through seller accounts. For small to medium parcel, standard residential delivery, in areas with strong AMZL coverage, MCF rates are often competitive with — or below — list rates from traditional carriers.
Whether that holds against your contracted rates depends on how deeply negotiated your current carrier agreements are. For a shipper with rates that have been worked down through volume commitments and relationship history, the gap narrows significantly. For a shipper on rates closer to list, Amazon's MCF pricing may look more attractive.
The comparison also requires more than a per-shipment rate. For a framework on what a complete cost comparison should include, see how to evaluate carrier contracts beyond the rate table. The same principles apply here:
| Cost component | Why it belongs in the comparison |
|---|---|
| MCF per-unit fee vs. carrier rate for the same size and weight | The base comparison; model against your actual shipment weight and size distribution, not a single representative shipment — dimensional weight rules differ across providers and can change the effective rate on bulky lightweight freight |
| Storage fees at Amazon vs. your current fulfillment cost | MCF rates include pick-and-pack but not storage; AWD and FBA storage fees are separate and increase significantly during Q4 — hold cost matters if inventory turns slowly |
| Returns cost | Include the cost of returns processing under MCF; reverse logistics cost varies significantly by model and is easy to underestimate if only outbound rates are compared |
| Coverage rate for your specific zone distribution | Where Amazon does not have direct AMZL coverage, orders may route through carrier partners — confirm the share of your volume this affects and what service level those partners deliver |
| Your negotiated carrier rate, not list rate | If your UPS or FedEx rates are meaningfully below list, the gap between MCF and traditional carriers narrows; compare Amazon against what you actually pay today, not what is printed on the carrier's published rate card |
The shipment profiles where MCF tends to be most cost-competitive: lightweight, small to medium parcel, residential delivery, standard goods, concentrated in areas with strong AMZL coverage.
The profiles where traditional carriers often hold the advantage: heavier shipments, commercial addresses, time-definite or signature-required delivery, outbound Canada volumes in smaller markets, and shippers with deeply negotiated contracts whose effective rates already reflect years of volume leverage.
This is a model-it-against-your-mix comparison, not a headline rate decision. The same logic that applies to any carrier comparison applies here. See how small freight decisions quietly reduce gross margins for why this kind of per-shipment analysis matters more than it initially appears.
The data and dependency tradeoff
This part of the evaluation does not appear in a rate comparison, which is exactly why it tends to get skipped. It is also the part that is hardest to unwind if the decision is made without it.
What Amazon sees when you use their supply chain services
When inventory is inside Amazon's network and orders are flowing through MCF, Amazon has operational visibility into your inventory levels and reorder behavior, your sales velocity by channel, your customer delivery address distribution, your demand patterns and seasonality, and which products move fastest.
For a brand that does not sell on Amazon.com and does not compete with Amazon's own product lines, this visibility is a business consideration with limited immediate surface area. For a brand that does sell on Amazon.com — particularly in categories where Amazon competes directly with its own private labels — the calculation is different. Amazon's access to your sell-through data, customer geography, and inventory behavior has been a documented concern for brands in competitive categories. That concern is worth taking seriously before committing supply chain infrastructure to Amazon's network.
Dependency risk is structural
A shipper that moves significant parcel volume into MCF has, in effect, outsourced warehousing and delivery to a single provider. That provider also happens to be one of the largest competitors in retail.
This does not make the decision wrong. It makes the dependency explicit. The question before committing volume is not whether Amazon Supply Chain Services works today. The question is: if Amazon changes pricing, changes terms, or changes program availability on a timeline that does not match your operational needs, how quickly can volume move to an alternative, and what does the transition cost?
That question is worth answering before the first shipment, not after the dependency is already structural.
What the track record shows
Many shippers use Amazon Supply Chain Services and find it operationally effective. The infrastructure is real, the delivery speeds are competitive, and the platform integrations have improved. The risk is not that the service is unreliable. The risk is that decisions made primarily for short-term rate reasons create structural dependencies that are expensive and time-consuming to unwind when circumstances change — terms shift, competitive dynamics change, or operational requirements evolve.
Understanding that risk in advance is what separates a deliberate decision from one that feels obvious until it is not.
A decision framework for shippers
Before adding Amazon Supply Chain Services to a carrier or logistics review, work through these questions against your actual shipment data:
| Question | What it clarifies |
|---|---|
| What percentage of my orders go to residential addresses where Amazon Logistics has direct coverage? | Coverage determines whether MCF can serve the volume you are considering at the speed and reliability your customers expect — confirm this against your actual delivery address distribution, not general market coverage claims |
| What are my current fully loaded fulfillment costs — storage, pick-and-pack, and delivery combined? | MCF rates cover fulfillment and delivery but not storage; the complete cost comparison requires modeling storage separately and accounting for seasonal variation |
| Do I sell on Amazon.com, or in categories where Amazon sells competing products? | Determines the weight to give the data-sharing tradeoff; this question has a different answer for a specialty food brand than for a consumer electronics brand in a category Amazon actively competes in |
| What is my returns volume and how does reverse logistics work under MCF? | Returns processing through Amazon's system may not match your current requirements; worth confirming before go-live, not after the first return volume arrives |
| What is my fallback plan if I move significant volume to MCF and the economics or terms change? | Build the exit scenario before you commit; if the answer is unclear, the dependency risk is higher than the rate comparison suggests |
| How does MCF fit with my current 3PL or warehouse relationships? | Partial channel shifts can complicate inventory visibility and reporting; understand the operational split before committing, especially if you will be running MCF and a traditional 3PL in parallel |
No single answer to these questions rules MCF in or out. The framework is about making the decision with the full picture — not just the rate comparison in isolation.
What to confirm before the first shipment
If the decision framework points toward testing Amazon Supply Chain Services, confirm these items before going live.
Coverage for your customer base. Pull your last 90 days of delivery addresses and confirm what percentage falls within Amazon Logistics' direct delivery zone versus carrier partner territory. The answer matters for both speed and cost.
Full storage cost at seasonal peaks. Amazon's storage fees increase in Q4. If inventory turns slowly or if you carry safety stock, run the hold cost through the peak period, not just the off-peak rate. The total picture can look materially different.
Unbranded packaging availability. Confirm that unbranded packaging is available for your specific product category and that the carton format works for your product. Not all product types qualify under Amazon's current unbranded packaging program.
Platform integration and tracking. MCF connects with major e-commerce platforms, but verify that your specific platform is supported, that tracking passes cleanly to the customer, and that order routing behaves as expected. Test this before scale, not during it.
Current terms. Amazon's program terms change. Review the current terms, understand the volume flexibility and exit provisions, and know what happens to inventory if you need to wind down or redirect volume quickly.
The standard to apply
Amazon has built one of the largest logistics networks in North America. It now makes parts of that network available to shippers outside the marketplace. For the right shipment profiles and the right business situations, that is a carrier option worth evaluating seriously.
The mistake is treating it as a rate decision alone.
The rate comparison is the easy part. The harder part is modeling the full cost picture — storage, coverage, returns, dependency — and being honest about what you are trading away when inventory moves inside Amazon's system. A lower per-unit fulfillment rate does not automatically mean a lower total cost of ownership, and a short-term rate advantage does not account for the structural weight of the dependency it creates.
A well-run evaluation applies the same standard to Amazon as to any other provider. Test the proposal against real shipment history. Model the full cost. Understand the terms before volume is committed. The questions are the same as any other carrier review. The stakes are somewhat higher because the provider also happens to be a major retailer with interests that do not always align with yours.
Amazon Supply Chain Services is not a reason to panic, and it is not a reason to rush in. It is a logistics option that deserves the same disciplined analysis as any other — starting with your actual freight profile, not a headline rate comparison.