A useful warehouse RFP tests the provider against your real inventory, order, systems, labor, and exception profile before price is normalized.

The cheapest warehouse proposal is often the one built on the most favorable assumptions. Receiving is priced by pallet although much of the inbound freight arrives floor-loaded. Storage is quoted against an average that conceals peak inventory. Pick fees assume clean each-pick orders, while the operation depends on lot control, kitting, retailer labels, and same-day cutoffs.

Choosing a 3PL warehouse is therefore not a vendor-ranking exercise. It is an operating-design test.

The direct answer is:

Give candidates the same transaction-level operating profile, require them to show how the work will run, test their exception controls, and normalize the resulting cost before scoring the relationship.

Capability comes first, but “capable” must mean capable of your inventory and order flow at normal and peak conditions. A large building, recognizable WMS, or polished tour is not a substitute.

Define the operation before issuing the RFP

Start with a data pack that a warehouse can actually engineer. At minimum, include:

Inventory and inbound

  • SKU count, active SKU count, new-item velocity, and item-master quality;
  • unit, inner, case, and pallet dimensions and weights;
  • lot, serial, expiration, country-of-origin, status, or temperature attributes;
  • average and peak on-hand units, pallets, cases, and cubic volume;
  • inbound purchase orders and shipments by day and week;
  • palletized, slip-sheeted, parcel, container, and floor-loaded mix;
  • cases or units per receipt, labeling quality, and ASN compliance;
  • expected quarantine, inspection, sampling, or quality holds; and
  • seasonal build, promotions, launches, and end-of-life inventory.

Orders and outbound

  • orders and lines by day and week, with peak-day and peak-hour profiles;
  • units per line, lines per order, split-case and full-case mix;
  • business-to-business, direct-to-consumer, retail-compliance, and transfer-order mix;
  • order-entry times, promised ship times, carrier cutoffs, and appointment requirements;
  • parcel, LTL, FTL, courier, customer pickup, and will-call mix;
  • packing, documentation, label, routing-guide, and ASN requirements;
  • kitting, assembly, personalization, inspection, or other value-added work;
  • returns by reason, disposition, and expected cycle time; and
  • cancellation, change, expedite, and backorder behavior.

Provide at least twelve representative months when seasonality matters, plus the busiest weeks and days. Averages alone produce an average design. The facility must be able to explain labor, storage, dock, packing, and systems capacity at the point where your service promise is hardest to keep.

Also disclose known data defects. If carton dimensions are incomplete or suppliers miss ASNs, say so and ask how the provider will detect, price, and correct the issue. A proposal based on fictional master-data cleanliness is not comparable.

Decide what kind of warehouse relationship you need

Before comparing sites, resolve three structural choices.

Shared-user or dedicated operation

A shared-user facility can provide variable labor, space, and equipment across accounts. It may be the right fit for modest or seasonal volume, but ask how your peaks correlate with the building's other accounts and who has priority when they collide.

A dedicated operation gives more direct control over layout, labor model, and process. It can also leave you carrying fixed capacity and implementation risk. The answer follows volume stability, process uniqueness, control requirements, and the cost of service failure—not a universal volume cutoff.

Standard process or engineered exception

Every exception has a cost. If the operation requires unusual inspection, delayed allocation, serial capture, customer-specific labels, heavy assembly, or regulated handling, make that work part of the base design. Do not allow “we can handle it” to remain an unpriced promise.

One node or a network

More facilities may reduce outbound distance or transit, but split inventory creates additional safety stock, transfers, system dependencies, and imbalance risk. Model inbound cost, inventory duplication, service area, order allocation, and transfer rules together. A postal-code heat map by itself does not select the network.

Use a staged selection process

An effective warehouse RFP has five gates.

1. Qualification

Confirm geography, building and dock constraints, service scope, available capacity, labor market, systems fit, operating hours, regulated capabilities, financial condition, insurance, and willingness to accept the proposed contract structure. Remove clearly ineligible sites before asking for a full solution.

2. Written solution and pricing

Require candidates to state:

  • proposed facility and exact operating entity;
  • layout and storage media assumptions;
  • labor and management plan for average and peak;
  • receiving, putaway, replenishment, picking, packing, shipping, returns, and inventory-control methods;
  • WMS and integration design;
  • implementation plan and client dependencies;
  • capacity limits and expansion options;
  • subcontracted functions;
  • service definitions, exclusions, and assumptions; and
  • a complete rate card tied to the supplied activity units.

Force every assumption into a numbered schedule. Assumptions left in emails are hard to compare and easy to forget during implementation.

3. Scripted process demonstration

Do not accept a generic WMS demonstration. Give each candidate the same scenarios:

  • receive a PO with an overage, damage, and a missing ASN;
  • place one lot on quality hold without blocking unrelated stock;
  • allocate an order across case and each units;
  • change or cancel an order after wave release;
  • generate a customer-specific label and ASN;
  • reconcile a short pick and inventory adjustment;
  • process a return with uncertain disposition; and
  • trace who changed an item, order, or inventory status.

The candidate should show the workflow in the proposed system, including queues, permissions, alerts, audit history, and client communication. A slide that says “exception management” is not a demonstration.

4. Site validation and references

Walk the proposed building during an operating shift. Follow product through receiving, staging, storage, replenishment, picking, packing, shipping, returns, hold areas, damage control, and yard or dock flow. Inspect housekeeping, rack condition, pedestrian and powered-equipment separation, blocked egress, trailer restraint practices, battery or charging areas, and evidence that standard work is actually used.

OSHA identifies powered industrial trucks, ergonomics, material handling, chemicals, slips and falls, and robotics among important warehouse hazards. Its warehousing hazards and solutions guidance gives procurement teams a useful set of observations, although a tour is not a compliance audit. OSHA's National Emphasis Program for warehousing and distribution centers is another reason to treat safety management as operating capability rather than boilerplate.

Call references with a similar order profile, peak pattern, commodity, and systems design. Ask about inventory adjustments, billing disputes, peak planning, staff turnover, issue escalation, implementation misses, and how the provider behaves when it caused the exception.

5. Design validation and contract

Before signature, reconcile the solution design, implementation statement of work, rate card, service levels, and contract. The same operating assumptions must appear in all four. If the proposal assumes one cutoff but the SLA measures another, the disagreement is already designed into the deal.

What the RFP must expose

Inventory control

Require the provider to explain:

  • item-master ownership and approval;
  • unit-of-measure and conversion controls;
  • receiving count and condition evidence;
  • license-plate or pallet identity;
  • location and status control;
  • lot, serial, expiration, and FEFO/FIFO rules where applicable;
  • cycle-count classes, triggers, and adjustment authority;
  • inventory-hold and release permissions;
  • shrink, damage, and claims workflow; and
  • physical inventory and reconciliation procedure.

GS1's logistics-label guidance uses the Serial Shipping Container Code to identify a logistics unit and link its physical movement to electronic messages. If SSCCs and ASNs are part of your flow, specify who creates, validates, scans, and retires them. Review the GS1 Logistic Label Guideline rather than writing “GS1 compliant” without an implementation rule.

Systems and data

Ask for the actual integration contract:

  • EDI, API, file, or portal transactions and direction;
  • source of truth for items, orders, inventory, shipment, and tracking;
  • event timing and acceptable latency;
  • acknowledgments, retries, duplicate handling, and reconciliation;
  • test environments and volume testing;
  • role-based access, multifactor authentication, logging, and privileged support access;
  • outage operations and recovery objectives;
  • data retention, export, ownership, and deletion; and
  • notice and response obligations for a security incident.

Do not limit cybersecurity review to a SOC report. Use the report as evidence, then test the controls relevant to your interface and data. CISA's Cross-Sector Cybersecurity Performance Goals provide a practical baseline, while NIST SP 800-161 frames supplier and service risk across acquisition and operation.

Labor and capacity

Require a peak plan with measurable inputs:

  • productive hours by process;
  • planned shifts, overtime, temporary labor, and cross-training;
  • recruiting and training lead times;
  • equipment, workstation, dock, staging, and carrier-cutoff constraints;
  • inventory and throughput capacity by relevant unit;
  • forecast freeze and change process; and
  • volume bands beyond which price, service, or lead time changes.

Ask what happens when your forecast is wrong in both directions. Unused fixed labor can generate minimums; demand above plan can miss service. The agreement should define the forecast you owe, the capacity the provider commits, and the escalation path when either party misses.

Regulated and high-control freight

Add requirements by commodity, not by generic “certification”:

  • Food operations may need sanitation, allergen, temperature, pest, traceability, and transportation-handoff controls. FDA's sanitary transportation rule assigns practices and records across shippers, loaders, carriers, and receivers; review the FDA role summary.
  • Prescription-drug 3PL operations can trigger state licensure and federal reporting considerations. FDA directs buyers to verify both applicable state licenses and annual reporting in its 3PL and wholesale-drug-distributor licensure lookup guidance.
  • Import programs may require supply-chain security controls, business-partner diligence, and documented risk assessment. CBP explains those principles through CTPAT.
  • Hazmat, alcohol, firearms, chemicals, medical devices, bonded merchandise, and other specialized products need their own jurisdiction and license review.

A certification or license is an eligibility record. Verify scope, facility, expiration, and the procedure that makes it operational.

Normalize price with scenarios, not rate-card intuition

Build a cost model from the RFP data:

Total scenario cost = inbound handling + storage + replenishment + picking + packing + materials + outbound handling + value-added services + returns + systems/admin + minimums and peak charges

Run at least:

  • a normal month;
  • the peak month and peak week;
  • a slow month where minimums matter;
  • a growth case;
  • an unfavorable mix case, such as more each-pick orders or floor-loaded receipts; and
  • an exit or transfer case.

Clarify the billing unit for every rate. “Pallet in” can mean unloaded pallet, received pallet, or pallet after inspection and putaway. “Order fee” may exclude lines, labels, materials, or account minimums. Include annual escalators, labor-index treatment, overtime, weekend work, project rates, storage aging, dunnage, technology fees, postage or parcel administration, and pass-through markups.

Then compare the operating assumptions behind the cost. A lower price built on fewer cycle counts, later cutoffs, or client-supplied labor is not the same service.

Define service levels so both parties can calculate them

Each KPI needs a start event, stop event, denominator, exclusions, data source, reporting clock, owner, and remedy. Useful measures may include:

  • dock-to-stock time;
  • order release to ship confirmation;
  • on-time shipment against the agreed cutoff;
  • order, line, and unit accuracy;
  • inventory accuracy by unit and location;
  • ASN and label compliance;
  • return-to-disposition time;
  • response and containment time for critical incidents; and
  • billing accuracy and dispute cycle time.

Do not combine all misses into one average. A 99-percent measure can hide systematic failure for one customer, shift, SKU class, or peak period. Require drill-down and a corrective-action trigger.

Contract for custody, failure, and exit

The storage agreement deserves specialist review. Address:

  • when custody starts and ends;
  • standard of care and inventory-liability limits;
  • declared or increased valuation options;
  • claims evidence, notice, and resolution;
  • insurance and deductibles;
  • subcontracting and relocation of goods;
  • confidentiality, cybersecurity, and data rights;
  • audit and inventory-count rights;
  • liens, payment disputes, and release of goods;
  • service remedies and chronic-failure termination;
  • business continuity and disaster recovery;
  • termination assistance, final inventory reconciliation, and data export; and
  • transition labor, rates, timing, and access.

State law varies, but the model UCC provisions illustrate why these terms cannot wait. UCC § 7-204 addresses warehouse care and certain contractual liability limits; UCC § 7-209 addresses warehouse liens. This is operational education, not a substitute for counsel on the governing state law and agreement.

Exit design is part of selection. Ask for a sample full inventory export, order history, adjustment history, document set, and transition plan before award. If the warehouse cannot produce usable records during the sales process, do not assume an urgent exit will improve the result.

A scorecard that preserves the gates

Use pass/fail gates for legal eligibility, required licenses, security or food controls, core systems compatibility, and non-negotiable capacity. Score only candidates that pass.

An illustrative weighted comparison is:

Dimension Example weight Evidence
Process and inventory fit 25% Scripted scenarios, operating design, reference performance
Systems and data control 20% Demonstration, interface design, audit and recovery controls
Capacity, labor, and implementation 20% Peak model, staffing plan, cutover plan
Risk, safety, and regulatory fit 15% Site evidence, licenses, insurance, control procedures
Normalized commercial value 15% Multi-scenario total cost and contract allocation
Exit and relationship governance 5% Escalation, data portability, transition terms

Change the weights for the operation. A pharmaceutical program and a basic overflow pallet-storage program should not use the same emphasis. Record deductions and the evidence behind them.

The operating takeaway

Choose the warehouse whose demonstrated process, systems, people, capacity, controls, and contract fit the real work. The RFP should make weak assumptions visible before they become charge codes or service failures.

Use the broader operator's map of how freight moves across America to define the warehouse's inbound and outbound handoffs before asking it to price the work.

Start candidate discovery with 3PL providers and warehouse operators, then use the same data pack and scenarios for each. Connect the selected operation to a working routing guide, the carrier-vetting gate, and a defined freight-claims evidence process.

Sources and further reading

Best Practices