Best 3PL for Amazon Sellers: Cost, Fit, Switching Effort

Every “best 3PL for Amazon sellers” post already ranking is written by a 3PL, about itself. Cart.com, Red Stag Fulfillment and ShipHero each publish a version of this exact list with their own name in the first slot, which is a reasonable thing for a vendor blog to do and not a reason to trust the ranking. Pointerflow does not sell warehouse space or pick-and-pack labour, so there is nothing here to rank first — only seven ways an Amazon seller doing $3M–$30M can fulfil a non-Amazon channel, compared on what each actually costs, who each actually fits, and how hard each is to switch into or out of.

What Counts as a 3PL for an Amazon Seller?

A 3PL that fits an Amazon seller has to do one thing none of the seven options below can skip: read and write against Amazon Seller Central’s order feed for Fulfilled by Merchant (FBM) orders, alongside whatever it does for a Shopify or wholesale channel. That single requirement rules out plenty of general 3PLs that fulfil DTC orders well but have never built the Amazon-specific prep — poly-bagging, FNSKU labelling, six-sided barcode placement — that Amazon’s own receiving rules demand of inventory shipped into its warehouses, and that a seller still needs if any part of the catalogue sits inside FBA rather than with the 3PL.

Three genuinely different paths exist, not one spectrum. Fulfilment by Amazon (FBA), used through Multi-Channel Fulfilment (MCF), ships non-Amazon orders out of inventory a seller already holds inside Amazon’s own warehouses. Seller Fulfilled Prime (SFP) is not a warehouse at all — it is a Prime-eligibility programme layered on top of self- or 3PL-fulfilled orders that meet Amazon’s own speed and accuracy bar. An independent 3PL is a separate warehouse relationship a seller contracts directly, with its own SLA, invoice and Amazon integration to build or verify.

Best 3PL for Amazon Sellers: Which Option Fits Which Catalogue?

The honest answer changes with the catalogue, not with which vendor wrote the best-optimised blog post.

Amazon FBA via Multi-Channel Fulfilment

Multi-Channel Fulfilment ships a non-Amazon order out of the same FBA inventory a seller already stocks for Amazon sales, using Amazon’s own warehouses rather than a second vendor relationship. Amazon prices MCF by size tier, weight, units per order and chosen delivery speed, and layers a 3.5% fuel and logistics surcharge on top in the US (vendor-reported, Amazon Seller Central’s 2026 MCF fee schedule). From 15 January 2026, Amazon’s Preferred Pricing programme discounts MCF outbound fees by up to 15% and credits up to $1 per shipped unit for sellers who qualify (vendor-reported, Amazon Selling Partners’ 2026 Preferred Pricing announcement) — worth checking eligibility for before assuming the standard rate card applies.

MCF is not for a brand that wants branded packaging, a custom insert or a gift note on every order: Amazon ships MCF orders in unbranded packaging by default, and it is not the fulfilment method to reach for if the unboxing experience is part of the product. It is also not built for wholesale case- or pallet-level orders with EDI compliance — that runs through a different Amazon programme, not an MCF setting.

ShipBob

ShipBob operates a network of multi-client warehouses and explicitly markets Amazon Seller Central as one of the channels its platform can route FBM orders from, alongside Shopify, BigCommerce and wholesale. It does not publish a public rate card — every quote is built from a seller’s own SKU count, storage footprint and order profile, and the specific per-order or per-pallet rate a given catalogue would pay is — metric to confirm — until that quote exists. Treat any fixed dollar figure attached to ShipBob’s name on a third-party review site as a stale or hypothetical example, not a rate card.

ShipBob is not the fit for a catalogue dominated by oversized or very heavy SKUs — furniture, appliances, anything routinely over about 20 pounds — because a general parcel-focused network prices and picks around standard carton sizes, not freight-class freight.

Red Stag Fulfillment

Red Stag Fulfillment specialises in big, heavy, bulky and high-value goods, operating two owned US facilities — roughly 750,000 square feet in Sweetwater, Tennessee, and roughly 450,000 square feet in Salt Lake City, Utah (vendor-reported, Red Stag’s own facility description) — built with the ceiling height, aisle width and powered-equipment access that standard parcel warehouses are not. Red Stag also publishes its own guidance aimed specifically at Seller Fulfilled Prime compliance, which signals it expects and supports Amazon-facing sellers rather than treating Amazon as an afterthought channel.

Red Stag is not the fit for a catalogue of small, light, parcel-only SKUs with no oversized component: the infrastructure that makes it strong for bulky freight is priced for that profile, and a small-parcel brand pays for capacity it never uses.

ShipHero fulfilment network (LVK)

ShipHero sells two different things under one brand, and conflating them is the single most common mistake in shopping this vendor. One product is ShipHero’s warehouse-management software, licensed to a brand running its own warehouse. The other is a separate fulfilment network, run through its LVK subsidiary, for a brand that wants pick-and-pack work outsourced rather than software to run it in-house — and only the LVK network is a 3PL in the sense this list means. The network sets a minimum incoming order volume before onboarding a new account; the exact current threshold is — metric to confirm — since published figures vary across third-party listings and only ShipHero’s own sales process confirms the live number.

ShipHero’s LVK network is not for a brand that actually wants the WMS to run its own warehouse — that is the other product — or for a brand below the network’s onboarding volume, which rules out a genuinely early-stage Amazon seller.

ShipNetwork (formerly Rakuten Super Logistics)

Rakuten Super Logistics has rebranded to ShipNetwork; a seller researching it under the old name is working from an outdated vendor list. ShipNetwork owns and operates a multi-region US network — including facilities in New York, Atlanta, Scranton, Las Vegas, Austin and Reno — and markets it for one- to two-day ground coverage across most of the country (vendor-reported, ShipNetwork’s own published network description), alongside its SmartSuite tooling for inventory forecasting and shipment-method selection.

ShipNetwork is not the specialist choice for oversized or bulky freight — that infrastructure sits with Red Stag — and it is not the right search term if a seller is still comparing quotes under the Rakuten Super Logistics name, since a stale name can mean a stale rate card too.

Ryder e-commerce by Whiplash

Ryder System acquired Whiplash in a deal that closed 1 January 2022 for approximately $480 million (vendor-reported, Ryder System’s own acquisition announcement), and the combined operation runs nineteen dedicated and multi-client warehouses positioned near major US import gateways — Seattle/Tacoma, New York/New Jersey, Savannah and Long Beach. That gateway placement is the actual differentiator: a brand importing high container volume gets inventory from port to a fulfilment-ready warehouse faster than a network built around domestic distribution alone, which matters more for an Amazon seller carrying significant import volume than for one sourcing domestically.

Ryder e-commerce by Whiplash is not for a brand with a small SKU count and low import volume — the port-adjacent infrastructure that makes it strong for import-heavy operations is not the differentiator a domestically-sourced, single-warehouse-sized catalogue is paying for.

ShipMonk

ShipMonk runs multiple fulfilment centres and has built category-specific capacity rather than staying a pure generalist, opening a facility purpose-built for apparel brands in April 2026 (vendor-reported, ShipMonk’s own announcement) on top of existing focus on wellness and subscription-box handling. That specialisation is the pitch: apparel needs folding, tagging and sizing logic a generic parcel warehouse does not build for, and a 3PL that has built it is worth the search for a brand in that category.

ShipMonk is not the cheapest generalist option for a simple, single-SKU parcel catalogue with no category-specific handling need — the specialisation that makes it strong for apparel and wellness is infrastructure a plain commodity product does not use, and it is priced accordingly.

What Does a 3PL Actually Cost per Order Compared with Amazon FBA?

No source on this list, Amazon included, publishes a single per-order cost figure for a 3PL versus Amazon FBA — the real number depends on size tier, SKU mix, order volume and return rate, and for a specific catalogue it is — metric to confirm — until that catalogue’s own numbers go through the five-line method that follows. What does exist is a real, published cost basis on one side of the comparison: Amazon’s MCF fee is set by size tier, weight, units per order and delivery speed, plus the US fuel and logistics surcharge that layers on top of it. A seller can look up the exact fee for a real SKU today. No independent 3PL on this list publishes an equivalent public rate card; every one of the six requires a quote, and any per-unit dollar figure attached to one of their names on a third-party review site should be treated as an unsourced estimate rather than a rate.

The five lines that make the two sides comparable are storage (charged per unit or per bin, monthly, regardless of whether that stock moved), receiving or prep (charged per unit or per hour when inventory arrives), pick-and-pack (charged per order, sometimes with a base allotment before per-item add-ons), outbound shipping (either bundled into the fulfilment fee or billed separately at the carrier’s actual cost), and returns processing (charged per unit inspected and restocked). Amazon’s MCF fee already bundles pick-and-pack and outbound shipping into one number; a seller pricing an independent 3PL has to ask for all five lines separately, or the comparison is a bundled number against an itemised guess.

Every number in the worked example that follows is invented, for illustration only — not Amazon’s rate, not any named 3PL’s quote, and not a figure to repeat anywhere else in this comparison.

In this invented example, the independent 3PL costs more per order than Amazon’s own MCF fee — which is not a claim about which is actually cheaper for a real catalogue, only a demonstration that the two sides do not have to be assumed equal, or assumed in either direction, before the real quotes are in. A catalogue with oversized SKUs, a high return rate, or peak-season surcharge exposure can flip that result in either direction, which is exactly why the arithmetic has to run on a seller’s own numbers rather than borrow this one.

When Does It Make Sense to Move Off Amazon FBA to Seller Fulfilled Prime or an Independent 3PL?

There is no published order-volume threshold that marks the point — the decision turns on SKU characteristics and channel mix, not a revenue or unit number, and treating $3M–$30M itself as the trigger misreads what actually forces the move.

Seller Fulfilled Prime is not itself a warehouse choice — it is a Prime-eligibility bar layered on top of self- or 3PL-fulfilled orders, and the bar is published and specific. A seller has to pass a 30-day trial shipping at least 100 Prime packages, and hold at least 45 days of inventory coverage for every SKU going into the programme, before enrolling. After enrolment, Amazon reviews performance weekly against an on-time delivery rate of at least 93.5%, a valid tracking rate of at least 99%, an order defect rate under 1%, a pre-fulfilment cancellation rate under 0.5% and a late-shipment rate under 4%, and it tightened the delivery-speed display thresholds again on 6 July 2026 (vendor-reported, Amazon’s own Seller Fulfilled Prime programme requirements). Those numbers are the actual gate — not a revenue figure, and not a unit count.

What genuinely forces a seller off Amazon FBA, in the order it actually shows up in practice: a catalogue that has grown past what FBA prices efficiently for its dimensions — oversized or bulky SKUs draw long-term storage charges FBA was never priced around, which is why Red Stag’s specialisation exists. A channel mix that has grown past what MCF alone comfortably serves — a seller running Shopify, wholesale and Amazon at real volume starts wanting one warehouse relationship across all three rather than Amazon inventory feeding everything else. And inventory-performance pressure inside Amazon itself — a seller repeatedly brushing against FBA’s own storage-utilisation limits has a reason to hold less stock inside Amazon’s warehouses specifically, independent of what any other channel is doing.

How Do You Run a 3PL RFP That Isn’t Just Picking the Vendor Whose Blog You Read?

Running a 3PL RFP that beats a vendor’s own comparison post starts with one specimen order profile, sent identically to every shortlisted provider, rather than letting each provider quote against whatever information it individually asks for.

The specimen profile needs five things, pulled from a seller’s own real numbers rather than estimated: the top 20 SKUs by order volume, with actual dimensions and weight; total monthly order count, split by channel — Amazon FBM, Shopify, wholesale — since a provider prices channels differently; the current return rate; a stated peak-season multiplier, since November and December volume is what actually strains a new fulfilment relationship first; and whether any SKU needs Amazon-specific prep alongside standard DTC packing.

Send that same document to three or four shortlisted providers in the same week and ask each to quote the same five cost lines — storage, receiving, pick-and-pack, outbound shipping, returns — as separate figures, not one bundled number. A provider that will not itemise is telling a seller something about how the eventual invoice will read. Alongside the quote, verify three things directly rather than taking a sales conversation’s word for them: current Amazon Seller Central integration, tested against a real FBM order rather than a demo account; the contract’s chargeback-liability clause, stating who pays when the 3PL’s own pick error causes an Amazon account-health issue; and the minimum contract term and its renewal-notice window, since that clause is what actually determines how expensive changing course again will be.

Choosing a 3PL for Amazon-and-DTC multichannel fulfilment does not resolve the actual mechanism running underneath the decision: a SKU record — dimensions, weight, FNSKU, kitting components — has to stay correct and identical in Amazon Seller Central, in Shopify and in whichever 3PL’s warehouse-management system holds the physical stock. That is the same multi-channel product feed problem a catalogue hits the moment it sells through more than one storefront, and a 3PL RFP compares warehouses without touching it. A catalogue that drifts between those three records is what turns a well-chosen 3PL into a source of mis-picks and Amazon account-health strikes nobody can trace back to a cause. Keeping that feed accurate across every channel a $3M–$30M brand sells through — Amazon included — is catalogue and feed automation work, and it is usually the first system worth building once a brand has grown past its founding team’s spare attention to watch three inventory records by hand.