How to Choose a Seller Fulfilled Prime 3PL: 10 Questions

In this instructional video, Manish Chowdhary, founder and CEO of Kahoot!, walks Amazon sellers through ten essential questions to evaluate any third‑party logistics provider (3PL) for Seller‑Fulfilled Prime (SFP). He explains why common surface‑level queries (warehouse count, 2‑day coverage, pick‑and‑pack rates) are insufficient, and he details the deeper evidence sellers must demand. The questions cover: (1) the provider’s actual SFP experience; (2) how the provider assesses product eligibility using SKU dimensions, order history, and zip‑code data; (3) SKU inclusion/exclusion recommendations; (4) fulfillment footprint and inventory placement modeling; (5) a full cost model beyond headline rates; (6) ownership of Amazon setup and trial responsibilities; (7) weekend and cutoff operations; (8) automatic rerouting when a node cannot fulfill; (9) carrier selection logic and fallback plans; (10) proactive detection and remediation of at‑risk orders. After the questions, Chowdhary emphasizes three decisive tests: ability to model SFP with the seller’s own data, clear ownership of every operational responsibility, and real‑time order rescue capability. He encourages sellers to download a readiness scorecard and stresses that a credible provider may advise against SFP for certain SKUs or footprints, which is a sign of expertise rather than weakness.
Chapters
Most sellers ask a prospective 3PL 3 questions: How many warehouses do you have? Do you offer nationwide 2-day delivery? And what is your pick and pack rate? Those are reasonable questions for ordinary e-commerce fulfillment, but they are not enough to determine whether a provider can actually operate Seller Fulfilled Prime. The right provider should be able to prove it, plan it, operate it, and protect it. And for every question in this video, do not settle for a simple yes. Ask the provider to show you the evidence. Question 1: What seller-fulfilled Prime programs have you actually supported? Notice that I did not ask whether the provider supports Amazon FBA preparation, ordinary FBM orders, marketplace fulfillment, and and Seller Fulfilled Prime are not the same operation. Ask whether the provider has supported a Seller Fulfilled Prime trial, operated live Prime orders, and managed the responsibilities that are specific to the program. A strong provider should be able to explain what it owned, what the seller owned, and what happened when performance came under pressure. It may not be able to name every client, but it should still be able to describe the operation concretely. If the entire answer is, we fulfill thousands of Amazon orders, keep digging. Question 2: How will you determine whether my products can meet Seller-Fulfilled Prime requirements? Amazon measures delivery speed based on the delivery dates Prime customers see before they buy, not on a 3PL's generic coverage map. That customer-facing promise changes based on the product, its size tier, where inventory is available, the shopper's location, the time of the page view, fulfillment settings, cutoffs, and carrier services. A credible provider will therefore ask for SKU dimensions, weights, order history, customer zip codes, inventory locations, order timing, and shipping costs before promising coverage. It should use that information To model which delivery promises your operation can actually generate and where the gaps will appear. A strong answer sounds like, we need your data before we can tell you. A red flag answer sounds like, our network reaches 95% of the population in 2 days. Ask to see a readiness analysis built around your products and orders, not the provider's sales deck. Question 3: Which of my SKUs should shipping feasibility and operational predictability to protect both the Prime promise and the seller's economics? A low margin product may not survive an occasional expedited shipment, while a low volume product may provide very little room for normal delivery exceptions. A strong provider should identify good candidates, marginal candidates, and products that should remain in FBA. Or another fulfillment method. Ask to see a SKU inclusion and exclusion recommendation with the reason behind every decision. Question 4: What fulfillment footprint and inventory placement will my products require? Warehouse count alone is not the answer. A population coverage map does not tell you what delivery promise Amazon will show for your products after inventory availability cutoffs weekends, carrier pickups, and shipping settings are considered. For example, a single warehouse in Pennsylvania may reach much of the country eventually, but distant orders may require expensive air services to meet a fast promise. Adding nodes can reduce shipping zones and premium shipping exposure, but it also fragments inventory and creates additional replenishment and safety stock requirements. The provider should model your demand geography, inventory depth, product characteristics, order timing, and acceptable shipping costs together. A strong answer explains not only where the warehouses are, but which SKUs should be stocked in each one and why. A red flag answer gives every seller the same 2-warehouse or 3-warehouse recommendation. Ask to see a node-by-node inventory and delivery promise plan. Question 5: What will Seller Fulfilled Prime actually cost? The base pick fee and parcel rate are only the visible portion of the cost. The complete model may include inbound inventory splits, storage, safety stock, transfers, packaging, fulfillment labor, weekend operations, software, additional nodes, and expensive rescue shipments. Those costs should be compared against FBA at the SKU level because Seller Fulfilled Prime is not automatically the lower-cost option. The provider should also show what happens under normal conditions and what happens when inventory is in the wrong location or an expedited service becomes necessary. The best model does not merely produce one attractive average, it makes the assumptions and risk visible. A red flag is a provider that quotes low fulfillment rates without modeling the inventory and transportation required to protect Prime performance. Ask to see a complete Seller-Fulfilled Prime cost model, not merely a fulfillment rate card. Question 6: Who owns the Amazon setup and the Seller-Fulfilled Prime trial? A warehouse can ship every order correctly, and the seller can still struggle because of shipping templates inventory feeds, SKU assignments, fulfillment settings, or the promises customers see. Before launch, define who owns each part of the operation. That includes Amazon configuration, Prime templates, buy shipping, trial monitoring, inventory activation, order routing, carrier setup, and corrective action. Some responsibilities may remain with the seller, And that is perfectly reasonable. The important thing is that every responsibility has a named owner before the trial begins. If every Amazon— Question 7: What happens after cutoff and on weekends? Amazon requires seller-fulfilled Prime operations 6 days a week, including Monday through Friday and at least 1 weekend day. But saying that a warehouse is open on Saturday does not answer the question. The order must be received, released, picked, packed, labeled, handed to the carrier, and scanned according to the applicable promise. If the warehouse finishes the package on Saturday but the carrier does not collect it until Monday, the box has simply spent the weekend waiting on a dock. Ask for the real order cutoff, staffing schedule, carrier pickup time, and first scan expectation for for every seller-fulfilled Prime-capable location. A strong answer follows the order all the way from checkout to carrier possession. A red flag answer stops at, yes, we operate Saturdays. Ask to see the warehouse calendar and the actual carrier pickup schedule. Question 8: What happens when the assigned warehouse cannot fulfill the order? Normal routing is easy when inventory is accurate The warehouse has capacity, and every carrier is operating normally. The real test begins when a node is out of stock, inventory data is wrong, capacity is constrained, severe weather interrupts operations, or a facility misses its cutoff. The provider should be able to determine whether another eligible node has inventory, can still process the order, and has a carrier service capable of protecting the promise. That decision may need to happen before a person has time to open, read, and respond to a support ticket. A strong provider should explain whether rerouting is automatic, which conditions trigger it, and who intervenes when automation cannot resolve the problem. A red flag is discovering the inventory problem Only after the warehouse rejects the order. Ask to see the routing logic and the escalation path for an unavailable node. Question 9: How do you select carriers, and what happens when the preferred service fails? Choosing the fastest service or the cheapest label is not a complete carrier strategy. The decision may need to consider the promised delivery date, Amazon Buy Shipping availability, Applicable on-time delivery protection, pickup schedules, first scan performance, lane reliability, service disruptions, and cost. A carrier that performs well in one region or service level may be weaker somewhere else. And if the preferred service is unavailable, full, delayed, or unable to collect the package, the operation needs A qualified alternative while action is still possible. A strong answer explains the decision rules and the fallback, not just the provider's negotiated carrier rates. A red flag answer is, our system always chooses the cheapest label. Ask to see the carrier selection logic and contingency plan. Question 10: How will you detect and resolve an at-risk order before it damages my performance? This is the difference between reporting and operational control. A dashboard that shows yesterday's late shipment may be useful, but it cannot recover yesterday's order. The operation should monitor the milestones that occur before delivery. That includes order release, routing, inventory confirmation, label creation, pick and pack completion, carrier handoff, and the first scan. If one of those events does not happen when expected, someone or some system needs to recognize the risk while another action is still available. Ask who receives the alert, how quickly they must respond, what alternatives they can authorize, and when the seller is notified. A strong provider should be able to describe a specific exception, the signal that detected it, and the action that protected the order. A red flag is learning about a pattern of failures for the first time in a weekly performance report. Ask to see the alerting rules, response expectations, escalation owners, and performance reporting. After all 10 questions, 3 tests matter more than anything else. First, can the provider model Seller Fulfilled Prime using your actual products and order data? Second, does every Amazon warehouse, inventory, and carrier responsibility have a clear owner? And third, can the provider detect and recover an order before the problem becomes a performance defect? A credible provider may sometimes tell you that a SKU should remain in FBA, that your current footprint is insufficient, or that you should delay the Seller Fulfilled Prime trial. That is not a weakness. It is evidence that the provider understands the difference between winning your account and protecting your Prime eligibility. Seller-Fulfilled Prime capability becomes most visible on a bad day, not a normal day. If a provider's explanation begins and ends with a 2-day coverage map, you have probably been shown a sales slide, not a Seller-Fulfilled Prime operating plan. I'm Manish Chowdhary, founder and CEO of Kahoot! At Kahoot!, we help sellers evaluate SKU fit, plan distributed inventory, prepare for the Seller Fulfilled Prime trial, route orders, manage carriers, and protect Prime performance when exceptions occur. These are questions we encourage sellers to ask every provider they evaluate, including us. To pressure test your own operation, download the Seller Fulfilled Prime Trial Readiness Scorecard, link below, Use it before you select your SKUs, commit inventory, sign a 3PL contract, or begin the trial. The goal is not simply to earn the Prime badge, it is to build an operation capable of keeping it.










