The Excel workbook warehouse teams use to run a warehouse management system RFP: pre-written requirements, a weighted vendor scoring matrix, a 5-year TCO worksheet, and a week-by-week process plan.
This WMS RFP template is an editable Excel workbook for warehouse management system selection. It includes a WMS requirements template, vendor response dropdowns, weighted scoring, a 5-year total-cost worksheet, implementation timeline, due-diligence questions, and data-capture requirements for dimensions, weight, photos, integrations, and billing workflows.
This template condenses the requirements we see in warehouse RFPs every week — from 3PLs, freight forwarders, and fulfillment operations — into one editable workbook.
Answer a few quick questions about your operation and the Excel template downloads instantly — no waiting on an email.
A WMS RFP fails in one of two ways: it lists features without describing the operation, or it describes the operation without forcing comparable answers. This template avoids both by pairing a company profile with 107 specific requirements across twelve categories — every one answerable with a dropdown, so three vendor responses line up row by row.
The twelve requirement categories, with examples of what each covers:
ASN/PO matching, blind receiving, capturing dimensions, weight and photos at the dock without manual typing, cross-docking, dock-to-stock KPIs.
Real-time visibility by location/lot/serial, LPN tracking, cycle counting, holds and quarantine, units of measure, kitting and VAS.
Real-time order import, allocation rules, wave/batch/cluster picking, RF scan validation, priorities and cutoffs.
Carton recommendations from item dims, DIM-weight rating by carrier, rate shopping, manifest audit against measured dimensions.
RMA and blind returns, disposition workflows, photo evidence at inspection, credit triggers.
Client-configurable billable events, storage billing from measured dimensions, rate cards, client portals, margin reporting.
Documented REST API, webhooks, EDI 940/943/944/945/856/810, carrier and e-commerce connectors, dimensioner and scale integration, data export rights.
Rugged mobile support, ZPL printing, scales, NTEP-certified dimensioner data, photo capture, offline tolerance.
Operational dashboards, report builder, KPI library, client-facing reports, BI access without per-query fees.
RBAC, SSO/MFA, audit logging, hosting model, uptime SLA, DR commitments, vendor security attestations.
Methodology and exit criteria, data migration, UAT, hypercare, support SLAs by severity, upgrade policy, references.
Itemized pricing tied to your real volumes, increase caps, growth costs, termination and data-return rights, milestone payments.
These requirements fall through the cracks because they sit between departments: operations assumes the system will capture dimensions, IT assumes the hardware vendor handles it, and finance only notices when carrier invoices and storage charges stop reconciling. By then the fields, the integration, and the audit trail all have to be added to a live system. If measurement data touches your billing, specify it in the RFP the way you specify picking or invoicing — and hold the hardware side to the same standard with a dimensioner RFP template.
Require that dimensions, weight, and photos are captured at receiving and packing without manual typing, and that they attach to the receipt, LPN, and shipment records rather than living in a separate file. An RFP that only asks "does it store dimensions?" gets a yes — and a text field.
Ask how measurement data actually arrives — API, webhook, middleware, or file drop — who owns and maintains the mapping, what happens on retries and duplicate reads, and whether you can export the raw measurement history without per-query fees.
Require that each reading retains device ID, timestamp, and unit of measure, and that certified data (NTEP-certified dimensioner output, for example) stays distinguishable from typed or estimated values. Without provenance you cannot tell a billable measurement from a guess six months later.
State the units your operation and carriers work in, then ask how the system converts, rounds, and orders length/width/height across modules — and which source wins when the item master and a fresh measurement disagree. Silent rounding differences between rating and billing are a common dispute trigger.
Ask whether the WMS rates shipments from measured dimensions rather than item-master estimates, and whether it can audit manifested dimensions and weights against measured values before carrier pickup. This is the requirement that turns capture into recovered spend.
If you bill clients for storage, require that billable events can be driven by measured dimensions and cube instead of a fixed per-pallet assumption — and that the underlying measurement is retrievable by shipment or LPN when a client questions the charge.
Every one of these is cheaper to require up front than to retrofit after go-live. For how to write and score them in detail, see our guide to warehouse dimensioning system RFP requirements; if you're evaluating capture hardware alongside the WMS, AI dimensioning systems covers where automated measurement fits into the flow.
Fifteen of the 107 requirements, exactly as they appear in the WMS requirements template. Each row in the workbook carries a Must/Should/Nice priority and a vendor response dropdown (Standard, Configuration, Customization, Partner, Roadmap, Not supported).
| Category | Requirement | Priority |
|---|---|---|
| Receiving | Receive against ASN or PO with automatic quantity and line matching, and support blind receiving when no ASN exists. | Must |
| Receiving | Capture carton dimensions, weight, and photos at receiving without manual typing, and attach them to the receipt record. | Must |
| Inventory | Real-time inventory visibility by location, lot, serial, and LPN, with full movement history per unit. | Must |
| Inventory | Cycle counting by zone, velocity, or exception trigger, with counts executable from a mobile device. | Must |
| Picking | Support wave, batch, zone, and cluster picking with RF scan validation at pick confirmation. | Must |
| Packing & shipping | Recommend carton size from item dimensions (cartonization) and rate-shop across carriers using DIM weight. | Should |
| Packing & shipping | Audit manifested dimensions and weights against measured values before carrier pickup. | Should |
| Returns | Process RMA and blind returns with disposition workflows and photo evidence captured at inspection. | Should |
| 3PL billing | Bill clients from configurable billable events, including storage billed from measured dimensions. | Must |
| Integrations | Documented REST API and webhooks; EDI 940/943/944/945/856/810; native dimensioner and scale integration. | Must |
| Hardware | Ingest NTEP-certified dimensioner data with device ID and timestamp retained for legal-for-trade billing. | Should |
| Reporting | Operational dashboards plus a report builder; export any dataset without per-query professional-services fees. | Must |
| Security | Role-based access control, SSO/MFA, and a complete audit log of user and API actions. | Must |
| Implementation | Documented implementation methodology with exit criteria per phase, UAT support, and hypercare period. | Must |
| Commercial | Itemized pricing tied to stated volumes, annual increase caps, and data-return rights at termination. | Must |
The full workbook covers all 107 requirements across the twelve categories above — download the complete WMS RFP template to get every row, the scoring matrix, and the TCO worksheet.
Fill in the Company Profile sheet with real volumes (average and peak), freight mix, current systems, and your top three problems. Vague RFPs get padded pricing.
Review the 107 requirements with operations, IT, finance, and billing. Delete what doesn't apply, set a Must/Should/Nice priority on every row you keep, and add anything unique to your operation.
Ask vendors to answer every requirement with Standard, Configuration, Customization, Partner, Roadmap, or Not supported — and to quote pricing against your stated volumes, including peak season.
Use the scoring matrix to compare coverage, then weight demos, references, implementation approach, and 5-year TCO. Treat must-haves answered with Customization or Roadmap as project risk.
Run scripted demos with your data and workflows, call references that match your size and industry, and complete the TCO worksheet before negotiating best-and-final offers.
Carton and pallet dimensions, weights, and photo evidence drive carrier rating, storage billing, cartonization, and dispute defense — so the template bakes data-capture requirements into receiving, shipping, billing, and hardware sections. If you're also selecting dimensioning hardware, our guide to warehouse dimensioning system RFP requirements covers that side, and the ROI calculator puts numbers on automated capture.
The workbook is editable, but security, interoperability and legal-for-trade claims should be checked against the organizations that own those standards.
A WMS RFP (request for proposal) is a structured document a warehouse sends to warehouse management system vendors describing its operation, volumes, and requirements, so vendors respond with comparable proposals and pricing. A good WMS RFP describes the work the system must support — receiving, inventory, picking, shipping, billing, integrations — not just a feature wish list.
A complete WMS RFP template includes a company profile (volumes, freight mix, systems), a categorized requirements checklist with priorities, vendor response options, a weighted scoring matrix, a total-cost-of-ownership worksheet covering one-time and recurring fees, an RFP process timeline, and open due-diligence questions about implementation, support, and data portability.
Yes. The workbook includes 107 pre-written warehouse management system requirements across receiving, inventory, picking, shipping, returns, 3PL billing, integrations, hardware, reporting, security, implementation, and commercial terms. Each row can be prioritized as Must, Should, or Nice and sent directly to vendors for comparable responses.
For a mid-size warehouse, a realistic WMS RFP process runs 12–16 weeks: two weeks to define requirements, three weeks for vendor responses, two to three weeks for scoring and demos, and the remainder for references, TCO analysis, security review, and contract negotiation. Implementation comes after and typically takes 3–9 months.
Three to five. Fewer than three gives you no pricing leverage and no calibration on what 'standard' functionality looks like. More than five multiplies evaluation work without improving the decision — do that filtering with a shortlist or RFI first.
Yes. Carton dimensions, pallet dimensions, weights, and photo evidence drive carrier billing, storage billing, cartonization, and dispute defense. Specifying how the WMS ingests certified dimensioner data, where measurements attach to receipts and shipments, and how evidence is retrieved by shipment ID is far cheaper to require up front than to retrofit after go-live.
Yes. It's a fully editable Excel workbook with no watermarks — we ask a few questions about your operation so we can help if your RFP touches measurement data, which is our specialty. You can use, modify, and share the template inside your company freely.
250+ installations · 99.5% accuracy
Book a Demo