Resources / Warehouse Operations
Warehouse Management System: The Questions to Ask Before You Buy
This warehouse management system buying guide lists the RFP questions, demo scripts, reference checks, and contract terms that expose WMS risk before you sign.
6 min read
· Updated
November 2026
At a glance
The goal
When buying a warehouse management system, surface fit, implementation, and contract risk before you sign, while you still have the bargaining power to fix it.
What to cover
RFP questions, scripted demos with your data, reference calls, the data migration plan, go-live readiness, and contract terms.
When to use it
After you have defined requirements and shortlisted a few platforms, and before final negotiations.
A warehouse management system purchase runs through five stages: an RFP, scripted demos with your own data, reference checks, implementation and data migration planning, and contract negotiation. This warehouse management system buying guide lists the questions to ask at each stage, so fit, delivery, and cost risks surface before you sign.
Many WMS problems are visible before the contract is signed, if you ask the right questions. The gap between a polished demo and your building shows up later as a change order for scope everyone assumed was included, a data migration that slips a month, or a go-live that lands in the middle of peak. By then, most of your bargaining power is gone.
This guide is a working list of questions for each stage of a warehouse management system purchase: the RFP, scripted demos, reference calls, implementation and data migration, go-live, and the contract. It assumes you have already decided what matters (see our guide to WMS selection criteria) and which kinds of platforms belong on your list (see WMS software categories).
Before the RFP: write down what you are buying
An RFP without real requirements gets generic answers. Before you send one, document:
Process maps for receiving, putaway, replenishment, picking, packing, shipping, returns, and counting, both as they run today and as you want them to run.
Volumes: average and peak orders, lines, and units per day, active SKUs, and growth assumptions.
Every system the WMS must connect to, and the data that flows each way.
Must-haves, kept separate from nice-to-haves.
If your team is still debating what the WMS should own versus the ERP and the floor, settle that first. Our explainer on what a WMS controls is a useful starting point.
WMS RFP questions that get real answers
Ask questions that require specifics. "Do you support wave picking?" gets a yes from everyone. "Show how you would release our Monday-morning wave" does not.
Operations
Walk through how your system would handle our three most complex order types, step by step.
What happens on a short pick, a damaged receipt, and an order cancelled after release?
Which of our requirements are met by configuration, which need custom development, and which are not supported?
Technology and security
Which of our integrations are prebuilt, and which are project work? Share the API documentation.
How often do you release upgrades, and what testing do customers do for each one?
Can you provide a current SOC 2 report? A SOC 2 examination covers a service organization's controls relevant to security, availability, processing integrity, confidentiality, or privacy, as defined by the AICPA.
Implementation and support
Who will work on our project, by name and role, and what share of their time is committed?
What do you need from our team, in hours per week, by role?
What are your support hours and response times by severity, and how does escalation work?
Commercial
What would we pay at double today's volume, users, or sites?
What costs extra: test environments, additional integrations, training, or premium support?
Which services are fixed-fee, and which are billed by the hour?
Score written answers before the demos, so the demos test the claims instead of replacing them.
SKU fit check
Send an email to
How to script a WMS demo
Vendor-led demos show the product at its best. Scripted demos show it doing your work. Send every finalist the same scripts and data well ahead of time, and score them the same way.
Use your data. Real SKUs, including the awkward ones: kits, items sold in several units of measure, and lot-controlled or expiring products.
Script a full day. Receive an ASN with a discrepancy, put away, replenish, release work, pick, pack, ship, and close the day.
Include exceptions. A short pick, a mislabeled item, a cycle count variance, and a rush order added after release.
Ask for a live change. Have the vendor modify a rule during the session and time it.
Bring the floor. Have a shift lead run the RF screens, not the sales engineer.
Score every script step the same three ways: done as scripted, done with a workaround, or not supported. Workarounds deserve a follow-up question, because each one becomes a habit, a spreadsheet, or a custom build after go-live.
Reference calls that tell you something
Ask for references that match your size, operation type, and the product version you would actually run, ideally ones that went live recently. Then ask:
What took longer than planned, and why?
How many change orders did you sign, and what were they for?
What happened in the first two weeks after go-live?
Was the team that sold the project the team that delivered it?
What would you do differently?
It is also fair to ask the vendor about a project that went badly and what they changed afterward. How they answer says a lot about how they will handle problems on yours.
Fit call
Send an email to
Implementation and data migration questions
Data migration is where schedules slip. A WMS needs clean item, location, and inventory data on day one, and many teams discover the gaps only once the project has started.
Who cleans and maps item master data: dimensions, weights, units of measure, barcodes, and lot or expiry flags?
Who builds the location master and the initial slotting?
How many trial data conversions happen before cutover?
How do open orders, open purchase orders, and inventory balances move at cutover, and who verifies them?
What does testing include: integration testing, user acceptance testing, and a volume test at peak-like load?
Go-live readiness questions
What criteria must be met before go-live is approved, and who signs off?
What is the rollback plan if a critical process fails?
How long does on-site support (hypercare) last after go-live, and who staffs it?
How does the schedule keep go-live clear of peak season and major client launches?
When and how are floor staff trained, and who trains new hires after the vendor leaves?
Site walkthrough
Send an email to
WMS contract terms to negotiate
Statement of work detail. Deliverables, assumptions, and exclusions in writing. Vague scope becomes change orders.
Change-order rates. Agreed rates and an approval process before work starts.
Service levels with remedies. Uptime, response, and resolution commitments, with credits that actually apply.
Pricing definitions. What counts as a user, site, order, or client, and how fees change as those grow.
Renewal caps. Limits on price increases at renewal.
Data ownership and exit. Your right to export all of your data in a usable format, and help with the transition if you leave.
Security commitments. Ongoing access to security reports and clear incident notification terms.
Source code escrow for on-premise software. Protection if the vendor can no longer support the product.
Red flags
Answers that stay generic even after you share your data.
Pushback on scripted demos or on references in your segment.
A project team nobody can name.
A firm timeline offered before the vendor has seen your integrations.
Where Avatar fits
A new WMS changes how work is planned, not how it gets done on the floor. If robots are part of your plans, add a scripted demo step where work goes to automation and comes back as an exception. Avatar drops into your existing workflows and can use the same scanner devices as your staff. See how Avatar works across warehouse tasks.
How It Works
The process in four steps.
1
Document your WMS requirements
Map current and future processes, record average and peak volumes, list every system the WMS must connect to, and separate must-haves from nice-to-haves.
2
Issue the RFP and shortlist
Send questions that require specific answers about your orders, exceptions, integrations, and team. Narrow the field to two or three finalists.
3
Run scripted demos and reference calls
Give every finalist the same scripts and data, including exceptions, and score them the same way. Call references that match your size and operation type.
4
Negotiate the contract and the plan together
Lock the statement of work, data migration plan, go-live criteria, service levels, pricing definitions, and exit terms before signature, not after.
Frequently Asked Questions
What questions should you ask when buying a warehouse management system?
Ask how the system handles your most complex orders and common exceptions, which requirements need custom development, which integrations are prebuilt, and who will staff your project. Ask references what took longer than planned and how many change orders they signed. Questions that require specifics reveal more than yes-or-no checklists.
What should a WMS RFP include?
A WMS RFP should include your process maps, average and peak volumes, SKU profile, required integrations, and a clear list of must-have requirements. It should also ask about implementation staffing, support levels, upgrade cadence, security reports, and pricing definitions.
What is a scripted WMS demo?
A scripted demo is one where you give each vendor the same scenarios and data, such as receiving an ASN with a discrepancy or handling a short pick, and they show their system running it. It lets you compare vendors on your work instead of their best-case presentation.
What contract terms matter most in a WMS agreement?
Focus on a detailed statement of work, change-order rates, service levels with real remedies, clear pricing definitions, renewal caps, and your right to export your data if you leave. For on-premise software, consider source code escrow.
Sources
1. AICPA & CIMA (2022). SOC 2 Reporting on an Examination of Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy. AICPA.
Keep Reading
Warehouse Operations
Choosing a WMS
This WMS systems guide shows what separates a good fit from a costly one: operation fit, configurability, integration, automation readiness, and true cost.
5 min read
Read guide →
Warehouse Operations
WMS Software
WMS software comparison by platform type: ERP-embedded, enterprise, cloud mid-market, 3PL, and WES, the six differences that matter, and which fits.
5 min read
Read guide →
Core Concepts
WMS Explained
A WMS tracks inventory and directs warehouse tasks but never moves a unit. See what it controls, where control stops, and how it differs from ERP, WES, and WCS.
5 min read
Read guide →
Ready To Scale Your
Workforce?
Tell us your hardest jobs. We’ll show you what an Avatar robot can do on day one.
