RFP checklist for warehouse automation
What to include in an automation RFP, how to structure vendor responses for meaningful comparison, and the questions most buyers overlook.
10 min read · Vendor-agnostic
Why most automation RFPs produce poor proposals
A poorly structured RFP produces proposals that are difficult to compare, missing critical information, and optimised for the vendor rather than the buyer. The most common problems are specification gaps that allow vendors to interpret requirements differently, absence of structured response formats, and failure to request the commercial and support information needed for a complete evaluation.
- No operational baseline provided: vendors make their own assumptions about current throughput and labour cost
- Requirements too vague: vendors interpret minimum throughput as their target, not their floor
- No structured response format: proposals cannot be scored on comparable terms
- Integration requirements missing: vendors omit integration cost from the proposal
- No commercial transparency requested: support SLA, software licence terms, and exit provisions are absent from proposals
The purpose of a well-written RFP
A well-written RFP forces vendors to respond to your requirements rather than to present their standard pitch. It gives all vendors the same information, requires the same structure in their response, and makes comparison objective. The goal is not to get the cheapest proposal. It is to get the most comparable proposals from the most qualified vendors.
RFP structure: eight sections
01 Introduction and context
Company overview, warehouse location, operational context, and the purpose of the RFP. Include your timeline and the evaluation process you will follow. State explicitly that the RFP is competitive and that all vendors will be evaluated on the same criteria.
02 Operational baseline
Provide your documented operational baseline: warehouse size, current throughput (average and peak), labour headcount and cost in scope, order profile (lines per order, SKU count, order type mix), WMS system and version, and shift pattern. This is the foundation on which vendor proposals will be built.
03 Technical requirements
Minimum throughput at average and peak. Payload requirements. Load compatibility (tote dimensions, pallet type). Floor plan constraints (aisle width, ceiling height, floor condition). Safety requirements. Integration requirements (WMS system, API format). Charging and energy requirements.
04 Integration requirements
WMS system name and version. Required integration depth (task assignment, inventory updates, exception reporting, analytics). Required response times. Expected integration architecture (direct API, middleware, native connector). Integration testing and acceptance requirements.
05 Commercial requirements
Request itemised pricing: hardware, software, integration, implementation, training, annual maintenance, and software licence. Request pricing for fleet expansion beyond initial scope. Request the SLA in full. Request exit provisions for RaaS models.
06 References and track record
Require a minimum of three reference sites with comparable operational profiles (sector, WMS, throughput). Request contact details for independent verification. Ask vendors to disclose any material performance gaps at reference sites in the last 24 months.
07 Implementation plan
Request a phased implementation plan with named milestones, dependencies, and vendor resource commitments. Require timeline estimates to be based on comparable past implementations, not best-case assumptions. Ask for the typical range of implementation timelines, not just the minimum.
08 Vendor financial stability and platform investment
Request evidence of financial stability (last two years of accounts or equivalent). Ask for the product development roadmap for the next 12-24 months. Ask how many full-time engineers are working on the fleet management software platform.
Common omissions and their impact
No peak throughput requirement specified
If only average throughput is specified, vendors will size the system for average conditions. When peak loads arrive, the system will underperform. Always specify both average and peak throughput requirements, and request that the vendor confirm which specification they are designing to.
Integration cost not requested separately
Vendors who bundle integration with implementation make it impossible to compare integration cost across proposals. Request integration cost as a separate line item in the commercial response.
No specification of what constitutes a system failure
Without a definition of failure, SLA uptime commitments are unenforceable. Define what constitutes a system failure (percentage of fleet non-operational, inability to process orders above a threshold) in the RFP.
No request for sensitivity analysis
Ask vendors to show what happens to their ROI model if throughput is 15% lower than projected and if implementation takes 2 months longer than planned. Vendors who cannot or will not produce sensitivity analysis are presenting a marketing model, not an engineering proposal.
Missing exit and data portability provisions
For RaaS and software-as-a-service models, exit provisions and data portability rights must be specified upfront. These terms are significantly easier to negotiate before contract signature than after.
Managing the RFP process
The RFP process is a structured commercial negotiation. Manage it with the same discipline as any other procurement process.
- Issue the RFP to all shortlisted vendors on the same day with the same information. Do not give any vendor an advance briefing that others do not receive.
- Hold a structured vendor Q&A session (written, not individual calls) and circulate all Q&A responses to all vendors simultaneously.
- Evaluate proposals against your defined scoring criteria. Require internal sign-off on scores before any vendor is contacted with feedback.
- Conduct final presentations with shortlisted vendors after scoring. Limit presentations to addressing gaps in the written proposal, not to a repeat of the standard vendor pitch.
Generate your RFP pack
Build a structured automation RFP from your workspace, using your operational profile and technology requirements.
Start Free Assessment