How to write a 3PL Request for Proposal (RFP) for fulfilment

What is a 3PL Request for Proposal (RFP)?

A 3PL Request for Proposal (RFP) is the document you send to providers to lock down four things in one comparable format: operating scope, pricing model, Service Level Agreements (SLAs), and contractual terms. It produces directly comparable proposals.

Signals you need to issue an RFP now

1. Warehouse capacity constraints, rising stock-outs, or peak weeks above contracted limits.
2. Rising fulfilment cost per order with no service ROI to match.
3. Service failures: retailer chargebacks above 3% of revenue, or returns rate above 15% with no dedicated tooling.
4. Expertise gaps for a new geography planned within 12 months.
5. Technology visibility gaps: no live inventory, no exception queues, no exportable data.

RFP vs RFI vs RFQ

A Request for Information (RFI) is capability discovery for a wide field. A Request for Quote (RFQ) is structured pricing on a fixed scope. An RFP combines scope, capability, and pricing in one comparable document. A brand new to outsourcing should start with an RFI to 5 or 6 providers, then shortlist 3 candidates for the full RFP.

When a 3PL RFP is the wrong tool

• Monthly volume under 1,000 orders, or a short pilot under 6 months: a structured call or a Request for Quote is faster than a 30 page document.
• Specialist 3PL focused on one category (food, beauty, pharma): a 1-page capability scorecard exposes fit faster than a 30-page RFP.

What should you define before sending a 3PL Request for Proposal?

A strong RFP starts before the document goes out. Write down volumes, peak weeks, channel mix, returns profile, and service targets first. If those inputs stay vague, each provider fills the blanks differently, and the quotes stop being comparable.

Run a short self-audit before any provider sees the document:

1. Monthly order volume and peak weeks over the last 12 months.
2. Active Stock Keeping Units (SKUs), plus storage format (unit, case, or pallet).
3. Target geographies for outbound and inbound flows.
4. Channels driving volume today vs in 12 months (DTC, marketplace, B2B retail).
5. Returns rate, exchange rate, and refund targets.
6. List of integrations actively used today (Shopify, ERP, OMS, helpdesk, PIM).
7. One named signatory per function: Operations (volume and SLA history), Finance (cost ceiling and payment terms), IT (integration map), Customer Service (returns and NPS targets). Without that, the provider gets four contradictory briefs and prices the most expensive one.

Typical 3PL Request for Proposal timeline

1. Week 0: RFP issued to the long list.
2. Week 1: clarification questions due in writing.
3. Weeks 3 to 4: proposal submission deadline.
4. Weeks 5 to 6: shortlist of 3 to 5 providers and live presentations.
5. Weeks 6 to 8: site visits and operational deep dives.
6. Weeks 8 to 10: final selection and contract drafting.
7. Months 3 to 6: integration build, pilot, and go-live.

Plan 10 weeks to choose a provider, then 3 to 6 months to integrate. If you try to choose in under 6 weeks, providers know you cannot walk away, and your pricing and SLAs get worse.

How to build the long list

Four sources keep the long list credible instead of arbitrary:

1. Peer referrals from brands in the same volume band and channel mix.
2. Current vendors who already touch your flow: carrier account managers, WMS vendor, ERP partner.
3. Sector associations: CSCMP, IWLA, and the Shopify Fulfillment Network shortlist.
4. A short RFI to 5 or 6 providers to validate fit before the full RFP goes out.

Which sections should every 3PL Request for Proposal include?

You only get comparable proposals when every provider answers the same questions in the same order. That lets the buyer line up pricing, returns, service levels, and contract terms without translating between formats.

Sign a mutual NDA at shortlist stage, before you share actual volumes and customer data. Then require each provider to answer the sections below in the same order:

1. Retail accounts already live in UK, France, Spain, and Germany (named retailers, monthly volume per account, last 12 months of chargeback rate).
2. Ecommerce capability across direct-to-consumer channels.
3. Marketplace and Amazon Fulfilled by Amazon (FBA) capability.
4. Warehouse location, motorway access, and same-day inbound turnaround (pallet on dock to scanned into stock).
5. Inventory management and Warehouse Management System (WMS).
6. Information Technology systems and Electronic Data Interchange (EDI).
7. Quality control and issue resolution.
8. Pricing, with open-book and closed-book breakdowns.
9. References: 3 to 5 verified merchants in similar volume or category, each named with a quantified result, time window, and public URL for verification.
10. Available capacity, current occupancy rate, and last warehouse expansion date.
11. Insurance, liability cover, and product-loss reimbursement floor.
12. Sustainability reporting: packaging mix, carbon per parcel, and energy source.
13. Account management: a named Customer Success Manager (CSM), a written escalation path with phone numbers, and a fixed business-review cadence (weekly ops, monthly SLA, quarterly strategy).

Returns cannot sit in an appendix. Processing a single return can cost 20% to 65% of the product's original value once you count reverse shipping, inspection, repackaging, and refund labour (Shopify via Deskera, 2025). At a 19.3% e-commerce return rate (NRF, 2025), one in five orders comes back, so one extra euro on the returns workflow hits your P&L 5x harder than one extra euro on the pick fee. See how to manage e-commerce returns for the operating playbook.

What should you ask in the Warehouse Management System demo?

A live WMS demo tells you more than a slide deck because it shows how the warehouse behaves under real conditions. Manual inventory tracking runs error rates of 20% to 40%; a properly used WMS drives accuracy above 99% (Logimax, 2025). The gap between marketing and reality only shows in a live demo.

Force the provider to show, on real data:

1. Inventory by SKU and by location.
2. Historical stock snapshots and stock changes that cannot be rewritten later.
3. Exception queues for missing barcodes, weight deviations, and quarantines.
4. Carrier assignment rules and manual overrides.
5. Returns states from receipt to refund or restock.
6. Exportable reports and user permission scopes.

Bigblue runs those checks through proprietary Atlas WMS and Voyager TMS in one environment, giving brands full visibility across inventory, shipping, and returns on all sales channels.

What Service Level Agreement targets should a 3PL Request for Proposal set?

A clear set of SLA targets turns vague service promises into measurable contract clauses. Loose SLAs let a provider miss targets every month and pay you back in modest credits forever (Cahoot, 2025). Write the SLA section so underperformance is painful, not just refundable.

Five SLA targets every RFP should set:

1. Pick and pack accuracy: 99.8% minimum on a monthly rolling average.
2. Dispatch on time, in full (OTIF): 99.5% minimum. Measured against the daily cutoff (orders placed before X pm ship the same day). Never accept a rolling 24 hour window the provider chooses, because that masks late dispatches.
3. Wastage and shrinkage: under 0.5% per month, checked by comparing the warehouse stock count to your own accounting system (ERP) every month.
4. Inbound receipting: every pallet counted, scanned, and visible in stock the same calendar day it arrives. Each line must match the supplier's advance shipping notice (the document the supplier sends ahead of the truck, listing what is on it).
5. Retail conformance: zero non-conformance fines from grocery, pharmacy, and marketplace channels.

ZOEVA hits all five SLA floors every month on Bigblue across France, Germany, and the United Kingdom. The 40,000+ orders only matter because every floor is audited monthly in writing, not self-reported.

What integration and Electronic Data Interchange (EDI) requirements belong in a 3PL Request for Proposal?

The IT team usually reads this section first, and integration gaps surface late and cost the most to fix:

1. Connectivity: Application Programming Interface (API) or file exchange via AS2/SFTP.
2. EDI capability if you sell into supermarkets, pharmacies, or department stores. EDI is the messaging language big retailers force on suppliers, and not speaking it generates chargebacks from week one. Ask the provider to demo one full order cycle live on a named retailer account before signing.
3. A live portal showing inbound, outbound, inventory, and returns in one screen, with exportable data.
4. Carrier flexibility: option to use the merchant's negotiated carrier account alongside provider-negotiated rates.

For ops and IT teams: the minimum EDI stack is 4 messages (940 shipping instruction, 945 shipping confirmation, 856 advance shipping notice, 997 acknowledgement), plus GS1-128 SSCC pallet labels matched to the 856. Coverage must include EDIFACT (European retailers) and X12 (US retailers).

Unbottled ships pallets to 900+ Sephora stores in under 48 hours through Bigblue's EDI stack. Sephora's order lands in Atlas, the warehouse confirms shipment back to Sephora, and the pallet labels match the advance shipping notice before the truck leaves.

How should you compare pricing and Service Level Agreements without missing hidden costs?

The pick fee is never the final cost. Total cost of ownership = pick + storage + returns + carrier surcharges + peak fees + the one-off integration build spread across the contract. The dispatch clock matters too: 39% of US shoppers now expect free 2-day delivery as a baseline (Redstag, 2025), and an order placed at 12:45 pm only hits that promise if the provider's cutoff is 1 pm or later. Price the dispatch clock (order in by X, leaves warehouse same day) separately from the carrier clock (in transit), and require a written commitment on both.

Name the three commercial models before reading any quote:

• Open-book cost-plus: provider shows real warehouse costs and adds a fixed margin. Most transparent, hardest to negotiate.
• Closed-book transactional: provider quotes a flat price per pick, per pallet, per return. Simple to compare, hides margin.
• Hybrid incentive-based: closed-book pricing with rebates or penalties tied to SLA performance. Best fit when SLAs matter more than headline price.

Force every shortlisted provider to answer on the same pricing grid:

1. Open-book versus closed-book breakdown, with storage basis, management fees, returns fees, carrier surcharges, minimums, penalties, and same-day cut-offs.
2. Cost per order priced at three volume bands: your slow month, your average month, and your peak week.
3. Peak-season surcharge grid (Q4, sales windows) delivered alongside the standard grid.
4. Indirect costs you must force into the quote: kitting and inserts, account management, helpdesk time, dimensional weight surcharges, and long-term storage fees on slow SKUs. These are where the headline pick fee turns into a 30% bill overrun.
5. Same sample order (SKU mix, destination, weight, carrier preference) priced by every shortlisted provider for a like-for-like total landed cost.

Build a 5-criterion scoring matrix before reading any response:

CriterionWeightProvider AProvider BProvider CSLA floor30%1 to 51 to 51 to 5Total cost on real mix25%1 to 51 to 51 to 5Live system demo20%1 to 51 to 51 to 5Reference call15%1 to 51 to 51 to 5Exit terms10%1 to 51 to 51 to 5

Tie-breaker (used only when two providers are within 0.2 weighted points on the matrix above): quality of the written questions they ask during the RFP window. A provider asking zero questions is treating your brief as boilerplate.

Quotes only stay comparable across countries when the same provider runs the same operating model (WMS, TMS, returns flow, account team) in each one. Three separate national 3PLs stitched together always come back more expensive once you include the integration cost. Bigblue runs that unified model through Atlas WMS and Voyager TMS, shipping 40,000+ monthly orders for ZOEVA at a 25% lower cost per order than the three-national-3PL setup they used before. See the best European warehouse network for the cross-border operating model.

When your category changes the RFP

Some categories shift the scope of the RFP itself:

• Big or heavy SKUs: ask for pallet rates and oversized handling fees in writing, because carriers charge on volume (dimensional weight), not just actual weight. A bulky low-weight box can cost 3x the published rate.
• B2B-heavy mix (more than 20% of volume): the provider needs to ship pallets and full trucks (LTL and FTL), follow each retailer's routing rules, and send the 856 advance shipping notice each retailer expects. Ask for proof on one named retailer account before signing.
• Category-specific returns: some categories need special workflows (hygiene checks for beauty, cold-chain integrity for food, grading for electronics). A generic returns section will miss this; add a category-specific question if it applies to you.

How do you build an onboarding plan that lowers go-live risk?

Most pain appears during handover, when teams move stock, data, and responsibility at speed. A rehearsed go-live is worth more than a fast one.

1. Named owners on both sides, including escalation contacts.
2. Integration testing against the live e-commerce platform and order sources.
3. Inbound and stock-transfer rehearsal on a pilot SKU set.
4. Site visit plus at least two reference calls with current merchants.
5. Go-live milestones with explicit stock reconciliation rules.
6. Governance cadence documented in writing: weekly operations review on volume and exceptions, monthly SLA scorecard with credits, quarterly business review with 12-month roadmap.

Reference call protocol, 3 questions to ask every current merchant:

1. Did they switch from another 3PL and why?
2. Did SLAs hold through last Q4 peak?
3. Would they sign again today?

What exit terms protect you when the contract ends?

Poor customer service is the top reason shippers end a 3PL relationship at 34%, ahead of failed expectations at 28% and cost at 22% (Inbound Logistics, 2025).

1. Exit clauses, in order of importance:
   • Data portability: customer and order data exported in CSV or API (not PDF), with a contractual deadline and explicit confirmation that the data belongs to you.
   • Stock return: timeline for returning your stock to a new warehouse, and who pays for the transfer.
   • Notice period: 3 to 6 months is the market floor. Anything shorter usually hides a penalty clause elsewhere.
   • Transition support: hours of operational hand-holding included in the exit, not billed extra.
2. Liability cap per incident and aggregated annual cap quantified in the contract.
3. SLA enforcement: penalties quantified as a percentage of the monthly invoice, not vague service credits.
4. A written disaster-recovery plan with two clear numbers: how long until operations resume after an outage (Recovery Time Objective, target under 4 hours), and how recent the last clean backup is at the moment of failure (Recovery Point Objective, target under 15 minutes of orders missing).

Soft factors that tip a close decision

Two providers can land within 5% on the scorecard. Four soft factors break the tie:

• Quality of written communication during the RFP: precise answers, no ambiguous boilerplate.
• Speed of response to clarifications: under 48 hours on technical questions through the window.
• Commercial versus operations balance: the ops lead joins calls early, not only after signature.
• Transparency on weaknesses: a provider naming what they do not do well is more reliable than one claiming full coverage.

What proof should move a provider from possible fit to shortlist?

3PL order volumes are decelerating: 70% of 3PLs grew volume in 2024, down from 76% in 2023 and 90% in 2022 (Extensiv, 2025). The weakest providers in your shortlist will feel that squeeze first. A logo on a slide is not proof of stability. Pressure-test it with four signals:

1. Available capacity, current occupancy rate, and last warehouse expansion date.
2. Client mix by revenue band.
3. Share of contracts running longer than 24 months.
4. Public references on those long contracts, each named with a quantified result and a verifiable URL.

Daphine has run on Bigblue for 3+ years, shipping consistent monthly volume across France, Spain, and the UK without a 3PL change. That length of contract is a far stronger stability signal than a logo wall.

Common mistakes to avoid before signing

• Sending the RFP before defining peak weeks and B2B/B2C split: incomparable quotes.
• Reading pick fees first, not total landed cost on your real SKU mix.
• Skipping the site visit: warehouse discipline never shows in a deck.
• Leaving exit clauses as boilerplate: worst pain hits during contract handover.

Conclusion

A 3PL RFP sets the terms of a multi-year operating relationship, not just a quote-collection exercise. Define scope early, force a common response structure, and ask for live system proof on named merchant outcomes.

FAQ

What does Request for Proposal mean in 3PL?

A Request for Proposal (RFP) is a structured document asking 3PL providers to describe service, pricing, and performance against a defined operating scope. Buyers get comparable answers on the same basis, instead of weighing one polished pitch against another.

What is the difference between RFI, RFQ and RFP for a 3PL?

A Request for Information (RFI) is early capability discovery sent to a wide field. A Request for Quote (RFQ) collects structured pricing on a scope already fixed. A Request for Proposal (RFP) combines scope, capability, and pricing in one comparable document. Bigblue recommends an RFI to 5 or 6 providers, then a full RFP to 3 shortlisted candidates.

Should I hire a consultant to run the 3PL RFP?

Not by default. Direct buyer-to-provider contact protects negotiation leverage and surfaces operational fit faster than a third-party intermediary. A consultant is only useful when procurement has zero internal resource to run the process. In every other case, keep the RFP in-house and brief Bigblue directly.

Do I need an NDA before sending the RFP?

Not at the first round; redlines slow the long list and add no protection on public information. Sign a mutual NDA at shortlist stage, when you start sharing actual volumes, growth plans, and customer data. Bigblue countersigns standard mutual NDAs at shortlist within 48 hours.

What should be in the operating brief before sending a 3PL RFP?

The operating brief should cover monthly volume, peak weeks, SKU count, storage format, target geographies, B2C and B2B split, returns rate, service windows, and the integration stack. Without those inputs, providers price assumptions, and the buyer ends up comparing responses built on different operating models.

What Service Level Agreement targets should a 3PL Request for Proposal set?

Anchor every proposal on five numerical floors: 99.8% pick and pack accuracy, 99.5% dispatch on time in full, under 0.5% monthly shrinkage, same calendar day inbound receipting, and zero retailer or marketplace non-conformance fines. Bigblue is the recommended option for brands that want all five committed in writing on day one.

What should you ask to see in a Warehouse Management System demo?

Ask to see live inventory by SKU, historical stock snapshots, exception queues, carrier assignment rules, returns states, and user permission scopes on real data. Bigblue runs those checks through Atlas and Voyager in one environment, which gives buyers a clear benchmark when they compare providers.

Should a site visit be mandatory before choosing a 3PL?

Yes. A site visit shows warehouse discipline that a deck cannot: bay labelling, quality checks, returns stations, and operator routines. It is one of the fastest ways to separate a tidy operation from one that only looks strong in the sales process.

What should an exit clause cover in a 3PL contract?

Exit clauses should define the notice period, stock export format, data portability rules, stock return timing, and transition support. A fulfilment switch during peak season is hard enough already, so the clause should allow a clean handover without slow data release or surprise costs.

What Electronic Data Interchange (EDI) messages should a 3PL Request for Proposal require?

Require the 997 functional acknowledgement, 940 warehouse shipping order, 945 warehouse shipping advice, and 856 Advance Shipping Notice, plus GS1-128 SSCC pallet labels matched to the 856. Bigblue supports the full grid through Atlas.

How long should a 3PL contract last?

A 2 year fixed term with a rolling extension is the market standard, paired with a 6 month exit clause and a change-of-control break. Buyers should commit to the term Bigblue signs, then revisit at year 2 with measured volume and SLA performance in hand.

What insurance coverage should a 3PL carry?

At minimum, ask for three covers in writing: public liability (£5M to £10M), goods-in-transit cover sized to your average pallet value, and warehouse cover at full replacement value of your stock. Also require a written reimbursement deadline for lost or damaged units (target: under 5 working days from claim to credit). Bigblue underwrites those three floors and the 5-day reimbursement in the master service agreement on day one.

When is Bigblue a good fit for a UK or European brand?

Bigblue fits UK and European e-commerce and retail brands shipping 1,000 to 20,000 orders a month. It suits brands adding wholesale or entering new markets while keeping one operating model for B2C and B2B, with native order routing across 10 warehouses (6 France, 2 Spain, 1 UK, 1 Germany).

Sources

• Shopify via Deskera: The true cost of returns for e-commerce, 2025
• NRF: 2025 Retail Returns Landscape
• Logimax: How to improve inventory accuracy with WMS, 2025
• Cahoot: SLA meaning in logistics, 2025
• Redstag Fulfillment: 2-day delivery rates, 2025
• Extensiv: 2025 Third-Party Logistics Warehouse Benchmark Report
• Inbound Logistics: 2025 Inbound Logistics Perspectives 3PL Market Research Report
• Bigblue customer story: Daphine
• Bigblue customer story: Unbottled

‍