Most WMS RFPs fail at the same thing — they count features instead of asking the questions that separate capable vendors from marketing language. This template is the ten sections we wish every mid-market 3PL would send us, including the hard questions we sometimes have to answer "no" to. Use it with every vendor on your shortlist.

How to use this template

Copy the sections below into your own document. Drop anything that does not apply to your operation. Add a scope section at the end that describes your facility count, user count, integration list, master data volumes, and target go-live date. Send the same RFP to every vendor on your shortlist and ask them to reply in writing by a specific date. Score the answers as a team, not by one person.

1. Company & product overview

  • How long have you been delivering WMS to mid-market 3PLs?
  • How many customers do you have today? How many in our revenue band?
  • What is your average customer tenure on the current version of the product?
  • Who owns the product roadmap and how is customer input weighted?
  • Is your WMS a single platform or a suite of separate modules stitched together?

2. Multi-client 3PL billing

  • Describe your multi-client billing model. Storage, handling, accessorials, value-added services, custom billable events — how are each captured and invoiced?
  • Can an operator log a billable event against a client in under 30 seconds without a purchase order?
  • How do you handle catch weight billing?
  • How do you handle retroactive rate changes?
  • Can invoices be previewed before they are sent to the customer?

3. Receiving, putaway, and inventory

  • What receiving workflows are supported (ASN, blind, cross-dock, drop-trailer)?
  • How are putaway locations selected (directed, manual, slotting rules, user override)?
  • How do you enforce lot, serial, and expiration tracking?
  • How do you handle catch weight receiving?
  • What cycle count modes are supported (ABC, blind, directed)?

4. Order management and picking

  • What pick strategies are supported (discrete, batch, zone, cluster, wave)?
  • Is voice picking native or an add-on?
  • Is pick-to-light native or an add-on?
  • How are pick exceptions (short picks, substitutes, damages) handled without breaking the wave?
  • Can operators move between pick strategies by order type without a configuration change?

5. Shipping and parcel

  • List every parcel carrier you connect to natively.
  • How is rate shopping handled?
  • How are manifest files generated and transmitted?
  • How are shipping exceptions (late pickup, failed label, address correction) surfaced to the ops team?
  • Is end-of-day close automated or manual?

6. EDI and customer integrations

  • Which standard EDI documents do you support natively (850, 855, 856, 940, 945, 810, 943, 944, 997)?
  • How do you onboard a new EDI trading partner? Who pays for the mapping work?
  • Can you show a list of every ERP your customers have integrated with and the current status?
  • How are integration failures surfaced, retried, and escalated?

7. Transportation brokerage (TBMS)

  • Do you include native TBMS capabilities for 3PLs running a brokerage arm?
  • If not, which TMS do you partner with and who runs the integration?
  • How are carrier contracts, tariffs, and fuel surcharges managed?
  • How are load tendering, dispatch, tracking, and settlement handled?

8. Reporting, AI, and decision support

  • What operator-facing reporting is included out of the box?
  • Do you ship a conversational AI assistant operators can query in plain language today?
  • What is your stance on predictive labor, slotting, and exception prediction?
  • How do you handle custom reports — self-serve, admin-only, or IT ticket?

9. Implementation, support, and pricing

  • Give us a realistic implementation timeline for our operation (see scope section at the end of this RFP).
  • Who runs the implementation — your team, a partner, or offshored?
  • What is the support model? Hours, location, escalation process, SLA.
  • Provide a written all-in quote including software subscription, implementation services, integrations, hardware guidance, and internal labor expectations.
  • What is your published integration success rate?

10. References and proof

  • List three mid-market 3PL references in our revenue band we can call. We will call them.
  • Share two written case studies with real metrics and named customers.
  • Share any public recognition (Gartner, SupplyTech, G2, Capterra) with links to the source.
  • Confirm that every claim in your response to this RFP is verifiable from a public source, an existing customer contract, or a written product specification — and that you will stand behind it at contract signing.

What to do with the answers

Score each section on a simple 1–5 scale against how specific and verifiable the vendor's answer is. Marketing language scores 1. A specific workflow walk-through with screenshots and a customer reference scores 5. Add up the scores, then ignore the total and read the low-scoring sections again. Those are the workflows that will hurt on day 90 of go-live.

Frequently asked questions

Do I have to give up my contact information to get the RFP template?

No. The template is inline on this page in its full form. If you want a Word version with a cover page and scoring rubric to hand to your team, there is an optional request form at the bottom of the page — but the content is free to read and copy directly.

How long should a WMS RFP be?

Long enough to cover your operation and short enough that vendors actually answer every question. 10 to 15 pages of questions plus your scope section is a realistic upper bound. An RFP that is 80 pages and takes six months to score is a signal the evaluation process itself needs fixing.

What should we do with vendor answers that are marketing language?

Follow up with the same question one more time in writing and ask for specifics. If the second answer is still marketing language, that is a data point about how the vendor will respond when you open a support ticket two years from now.

Should SC Codeworks be in our shortlist?

Only if you are a mid-market 3PL or manufacturer and our strengths (native TBMS, embedded CODI AI assistant, 24/7 US-based human support, 20-year average customer tenure) match your decision drivers. If your decision driver is Gartner MQ presence, Manhattan or Softeon will score better on that dimension. Use this RFP with every vendor on your shortlist, including us.

Who wrote this template?

The SC Codeworks team, drawing on patterns we see across mid-market 3PL evaluations. The questions are the ones we wish every prospect would ask us — including the hard ones we sometimes have to answer "no" to.

Want the Word Version with a Scoring Rubric?

The questions on this page are free to copy. If you want a Word-formatted version with a cover page and a team scoring rubric, reach out — we will send it over with no gating beyond a work email.