Getting Comfortable: Your Warehouse Story

• Tell us briefly: what type of DC/fulfillment operation is this (retail DC, e-commerce FC, 3PL, manufacturing warehouse, or hybrid)? Options: Retail DC, E‑commerce fulfillment center, 3PL, Manufacturing warehouse, Hybrid / Other
• How many SKUs and daily order lines do you handle on a typical day, and what are your peak multipliers (e.g., 2x, 4x)?
• Which fulfillment channels drive the most complexity for you today? Options: B2C single‑piece orders, B2B bulk/pallet orders, Marketplace/third‑party channels, Store replenishment / omnichannel, Returns/Reverse logistics
• What technologies are currently in core use (ERP, OMS, TMS, WCS, conveyor PLCs, ASRS, AMRs)? Please list versions or vendors if known.
• How would you describe the day‑to‑day relationship between operations and IT when a warehouse problem happens? Options: Collaborative and quick, Requires escalations, Blame often shifts between teams, Silos—slow resolution
• Who at your company will be the final decision‑maker for WMS selection and who else must approve budget and timeline?

Why Keep Tolerating the Daily 'Workarounds'?

• What ongoing workarounds are you relying on today that you know are risky or not scalable?
• How long have those workarounds been in place, and what prompted them initially? Options: Less than 6 months, 6–18 months, 1–3 years, 3+ years
• When a workaround fails, what’s the typical operational impact (orders delayed, overtime, revenue lost, customer complaints)? Options: Order delays, Increased overtime/labor cost, Inventory inaccuracies, Customer service issues/returns, Other
• On a scale from 1–10, how much does that daily friction affect your willingness to approve a major systems change? Options: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
• Can you share a recent incident that illustrates how current limits show up during peak or promotions?
• Which metric or story would convince leadership that the status quo is no longer acceptable?

What Would a Zero‑Drama Shift Look Like?

• If a new WMS eliminated your single biggest daily headache, what would change about your operations tomorrow?
• Which one KPI would you want to move first to prove value (order throughput, pick accuracy, dock-to-stock time, labor cost per unit, on‑time ship rate)? Options: Order throughput, Pick/pack accuracy, Dock‑to‑stock time, Labor cost per unit, On‑time ship rate, Inventory accuracy
• How would decreasing that KPI pain translate into business outcomes (reduced costs, higher revenue, fewer stockouts, better CSAT)? Options: Reduced costs, Higher revenue, Fewer stockouts, Improved customer satisfaction, Faster growth enablement
• Who would see the biggest relief internally if that change happened—operations, IT, finance, or commercial—and why? Options: Operations, IT, Finance, Commercial/Sales, Customer Service
• If we could demonstrate a clear path to that outcome in a pilot or sandbox, what would be the minimum timeline you’d accept to validate it? Options: 2–4 weeks, 1–2 months, 3–4 months, Longer than 4 months

Where Integrations and Automation Keep You Up at Night

• Imagine peak season with an integration outage—how resilient is your current architecture to keep orders flowing? Options: Fully resilient, Partially resilient with manual steps, Major disruption expected, Unsure
• Which integrations are mission‑critical for go‑live (ERP financials, OMS order allocation, TMS carrier handoff, WCS/conveyor, ASRS control)? Options: ERP, OMS, TMS/carriers, WCS/automation PLC, ASRS/AMR fleet management, Other
• For each critical integration you selected, what are the top technical constraints (latency, data model mismatch, authentication, unsupported APIs, vendor SLAs)?
• How confident are you that your automation vendors will coordinate with a new WMS implementation without causing schedule slips? Options: Very confident, Somewhat confident, Unsure, Not confident
• Do you prefer the WMS vendor to own integration delivery, share responsibility, or have your internal team lead it? Options: Vendor owns integrations, Shared responsibility, Internal team leads, Third‑party integrator
• What testing approach would make you feel safe (iterative sandboxes, full end‑to‑end staging, phased cutover by zone, parallel run)? Options: Iterative sandbox testing, Full E2E staging environment, Phased zone cutovers, Parallel run in production

Trade‑offs: Configure, Customize, or Compromise?

• If a needed capability requires customization, how do you weigh the long‑term maintenance cost versus a faster, customized win today? Options: Prefer configuration even if slower, Ok with light customization, Willing to customize for business‑critical features, Undecided
• Which areas are you most likely to consider customizing (unique pick flows, bespoke reporting, ERP data model bridging, automation exceptions)? Options: Pick flows, Reporting/analytics, ERP/OMS data mapping, Automation exception handling, User interface tweaks
• How do you currently handle vendor patches and upgrades—are customizations blocked, regularly reworked, or automated into your CI/CD? Options: Customizations blocked, Manually reworked each upgrade, Automated/CI process, No formal process
• Who in your organization ultimately approves trade‑off decisions between faster delivery and long‑term total cost of ownership?
• Tell us about a past customization that created ongoing pain—what happened, and what would you change now?

Stakeholders, Timeline, and the Moment of Truth

• If your proposed go‑live window slips, what is the first business consequence you'll face (missed season, contractual penalties, lost sales, resource burnout)? Options: Missed peak season, Contract penalties, Lost sales, Increased labor cost/overtime, Other
• Who are the non‑negotiable stakeholders that must be involved in executive decisions, weekly status, and go/no‑go reviews?
• What is your target timeline for decision, contract, and go‑live today, and how flexible is each milestone? Options: Decision in 30 days, Decision in 60–90 days, Decision in 3–6 months, Longer than 6 months
• What are your top 3 go/no‑go criteria for cutover (acceptance tests passing, integration SLAs met, automation commissioning, staffing/training complete)? Options: Acceptance tests passed, E2E integrations validated, Automation commissioned, Training complete, Support/onsite coverage scheduled
• How do you prefer to manage change during cutover—big bang, phased by zone, or hybrid—and why does that feel right for your operation? Options: Big bang cutover, Phased by zone/shift, Hybrid approach, Unsure
• What escalation path and vendor response times would make you feel secure for the first 90 days post‑go‑live? Options: 24/7 onsite support, 24/7 remote support with SLA, Business hours support, Tiered on‑call rotations

Measuring Success and Risks You Can't Ignore

• If we measure success at 30, 90, and 180 days, which success signals matter most (throughput, accuracy, MTTR for incidents, cost per order, customer complaints)? Options: Throughput/volume, Pick/pack accuracy, MTTR for incidents, Cost per order, Customer complaints/returns, Inventory accuracy
• Which KPI target would feel like a clear win for leadership in the first 90 days (specific % or absolute number)?
• What known risks keep you awake regarding implementation (data quality, resource availability, vendor delivery, automation integration), and which of those are showstoppers? Options: Data quality, Resource availability, Vendor delivery risk, Automation integration, Executive buy‑in
• How should we jointly handle unknowns that surface during implementation—change requests, scope creep, or emergent automation issues? Options: Change control board, Time & materials with caps, Fixed‑scope change orders, Other
• Finally, what would give you confidence in a WMS partner on day one—references from similar operations, a pilot, a written risk mitigation plan, or something else? Options: References from similar operations, Pilot/sandbox proof, Detailed risk mitigation plan, Clear SLA/penalties, Other

• Pre-work Alignment & Current State Confirmation
• Scenario Mapping & Process Walkthrough
• Integration & Automation Concurrency Session
• Sandbox Hands-On Scenario Execution
• Acceptance Criteria Finalization & Go/No-Go Review

• Vendor to produce a runbook of measured KPIs, logs, and a defect report from the sandbox session.
• Lock down interface contracts and sample messages required for scenario execution.
• Agree automation commissioning test cases and fallback behaviors for failure modes.
• Define measurable latency and concurrency SLAs to be validated in sandbox runs.
• Establish the test harness owner and integration test schedule.
• Customer to provide API specs, sample payloads, and access endpoints or test simulators.
• Vendor to supply any required interface adapters, message validators, and automation integration templates.
• Schedule integration test windows and assign troubleshooting contacts for each system owner.
• Kickoff: Validation Checklist & Rules of Engagement
• Demonstrate the WMS executing prioritized real-world scenarios and meeting the defined acceptance metrics where feasible.
• Capture and prioritize defects with assigned owners and target remediation timelines.
• Validate integration and automation behavior under load and surface any non-conformant behaviors.
• Decide which scenarios are passing, which require fixes, and the retest plan.
• Introductions & Objectives
• Customer SMEs to verify and sign off the factual accuracy of scenario outcomes and accept or challenge defect severity.
• Both parties to schedule follow-up remediation runs and a final validation session.
• Evidence Presentation
• Finalize a measurable acceptance matrix with owner sign-offs for each scenario and criterion.
• Agree remediation owners and retest timelines for any failed criteria or high-risk defects.
• Decide go/no-go to proceed to Solution Scope or require additional work and capture the decision formally.
• Document any scope/timeline impacts to be folded into commercial discussions in Mutual Commit stage.
• Both parties to sign and circulate the acceptance matrix and the list of agreed remediation items with owners and due dates.
• Vendor to update the Solution Scope assumptions and milestone impacts based on sandbox outcomes.
• Customer to confirm executive approval path for proceeding to Mutual Commit based on the documented results.
• Agree on a single-sentence current state that precisely captures what is breaking today.
• Quantify the business consequences (cost/time/risk) tied to the current state.
• Define one concise future-state outcome that will be proven by the experience.
• Produce a finalized pre-work checklist with owners and deadlines to enable scenario testing.
• Customer to deliver peak-day transaction export, SKU mix, automation flow diagrams, integration message logs, and any existing acceptance criteria.
• Vendor to provision sandbox environment and confirm required connectivity and data import formats.
• Both parties to agree on the timeline for the Scenario Mapping meeting and participants.
• Recap Preconditions
• Produce a prioritized list of real-world scenarios mapped to explicit WMS flows.
• Define measurable acceptance criteria for each scenario that prove the future-state outcomes.
• Agree interface and data dependencies required to execute each scenario in the sandbox.
• Assign owners to prepare executable scenario scripts and test data.
• Vendor to draft per-scenario execution scripts and required data files for sandbox import.
• Customer to validate and provide missing test data, confirm automation equipment behavior details, and nominate scenario SMEs.
• Both parties to agree on the timeline for the Sandbox Hands-On execution meeting.
• Integration Architecture Recap
• Message Samples & Data Contracts
• Execute Scenario: Peak Inbound/Outbound Run
• Current State (one sentence)
• Acceptance Matrix Review
• Prioritized Scenario List
• Residual Risks & Mitigations
• Consequence Quantification
• Automation Flow & Failure Modes
• Measure & Compare KPIs
• Per-Scenario WMS Flow Mapping
• Acceptance Criteria by Scenario
• Concurrency, Latency & Throughput Requirements
• Triage Defects & Test Workarounds
• Scope & Timeline Implications
• Future State (one sentence)
• Dependencies & Integration Points
• Test Harness & Responsibility Matrix
• Pre-work Checklist & Data Handover
• Repeat Additional Scenarios (as time allows)
• Decision & Next Steps

• Deploy RF-Directed Receiving and Inspection
• Implement Directed Put-away by Velocity and Cube
• Activate Lot, Serial, and Date Code Tracking
• Deploy Wave Planning and Order Release Engine
• Configure Pick Optimization (Batch/Zone/Cluster)
• Install Voice Picking and Pick-to-Light Interfaces
• Integrate Automation Controls (Conveyor/ASRS/AMR)
• Deploy Packing, Carrier Rate Shopping, and Labeling
• Enable Multi-Channel Order Allocation and Fulfillment
• Implement Replenishment and Min/Max Rules
• Deploy Cycle Counting and Inventory Reconciliation
• Integrate ERP/OMS/TMS via APIs and Data Mapping
• Activate Labor Management and Task Interleaving
• Deploy Yard Management and Dock Door Control

Deploy RF-Directed Receiving and Inspection

• What is your average and peak inbound transactions per day (lines and pallets)? Options: Average < 100 lines / day, 100-500 lines / day, 500-2,000 lines / day, More than 2,000 lines / day
• Do you receive advance shipment notices (ASNs) or rely on vendor paperwork? Options: ASNs for most receipts, Occasional ASNs, No ASNs - vendor paperwork only, Other
• Which receiving inspection steps are required (e.g., quantity check, quality inspection, sampling)? List specifics if custom.
• What barcode/labeling standards are on inbound cartons/pallets (e.g., GS1-128, custom labels, none)? Options: GS1-128 / standard labels, Vendor-specific barcodes, No barcode - manual ID, Other
• What percentage defect or exception rate will constitute a failed inspection (acceptance criteria)? Options: 0%, 0.1% - 1%, 1% - 5%, Custom threshold
• What mobile devices and OS do you plan to use for RF scanning, and do you require offline mode?

Implement Directed Put-away by Velocity and Cube

• Do you want put-away prioritized by velocity, cube, weight, or a combination? Options: Velocity (fast movers), Cube/space optimization, Weight/handling constraints, Combination of factors
• Describe your storage types (bulk, rack, mezzanine, shelf, ASRS) and approximate counts for each.
• Are there size/weight limits or cube thresholds that must drive location selection? Options: Yes - strict limits, Yes - advisory limits, No strict limits
• Do you require cross-dock or immediate put-away exceptions for certain SKUs or orders? Options: Yes - cross-dock for some SKUs, No - everything put away, Other
• How many unique SKUs and what % are high-velocity vs low-velocity? Options: <1,000 SKUs, 1,000-10,000 SKUs, 10,000-50,000 SKUs, 50,000+ SKUs
• What acceptance test would validate correct put-away (e.g., % items in correct tier, average put-away time)?

Activate Lot, Serial, and Date Code Tracking

• Which tracking modes do you require? Options: Lot tracking, Serial number tracking, Date/expiration code tracking
• Do you need traceability from receipt through shipment and returns (full chain-of-custody)? Options: Yes, full traceability, Partial traceability, No
• Are there regulatory or customer compliance requirements (e.g., FDA, FSC, retailer mandates)? Options: Yes - regulatory, Yes - customer-specific, No
• How should expiration/lot rules be enforced (FIFO, FEFO, manual override allowance)? Options: FEFO (first-expiry), FIFO (first-in), Manual override allowed, Custom rules
• What labeling and scanning requirements exist for serialized or lot-tracked items (label format, barcode symbology)?
• Describe recall scenario requirements (time to isolate affected units, report formats).

Deploy Wave Planning and Order Release Engine

• Which order release criteria are required (e.g., ship-by date, carrier cutoff, SLA, priority customer)? Options: Ship-by date, Carrier cutoff, SLA/priority, Manual release, Other
• What is your typical order mix (lines per order, cases vs eaches, split orders)? Options: Average lines/order < 5, 5-20 lines/order, 20+ lines/order
• Do you require dynamic re-prioritization of waves for rush orders or same-day fulfillment? Options: Yes - dynamic reprioritization, No - static waves, Occasionally
• Are there constraints for wave composition (e.g., weight, freight class, pick batch size)? Options: Yes - multiple constraints, Single constraint, No constraints
• What KPIs will confirm wave engine success (e.g., orders released per hour, on-time shipments)?
• Which upstream systems provide orders and cutoffs and at what cadence (real-time, hourly, batch)? Options: Real-time/API, Hourly, Daily batch, Other

Configure Pick Optimization (Batch/Zone/Cluster)

• Which pick strategies do you want to use or test (batch, zone, cluster, single-order)? Options: Batch picking, Zone picking, Cluster picking, Single-order picking
• How is your warehouse zoned and what are typical pick path constraints?
• What is the average lines per order and percent of split-case vs full-case picks? Options: Mostly full-case, Mostly split-case, Mixed
• Do weight/fragility/temperature rules need to influence pick grouping? Options: Yes - weight/fragility/temperature constraints, No
• Are there existing pick speed or accuracy targets we should use for acceptance tests? Options: Yes - provide targets, No - need vendor recommendation
• Will pick optimization need to integrate with pick-to-light or voice devices? Options: Pick-to-light, Voice, Both, None

Install Voice Picking and Pick-to-Light Interfaces

• Which hardware vendors/models are already deployed for voice or pick-to-light?
• Do you require multi-language voice prompts or specialized pronunciations? Options: Yes - multi-language, Yes - single language, No
• How many concurrent picking users will rely on voice or pick-to-light at peak? Options: <50 users, 50-200 users, 200-500 users, 500+ users
• What is the fallback workflow if devices lose connectivity (paper, RF, queued tasks)? Options: RF handheld fallback, Paper, Queued/resync later, Other
• Are there safety or ergonomic constraints for pick-to-light mounting or wearable devices? Options: Yes - constraints, No
• What acceptance criteria will validate a successful voice/pick-to-light deployment (accuracy, picks/hour)?

Integrate Automation Controls (Conveyor/ASRS/AMR)

• Which types of automation are in scope for integration? Options: Conveyor/sortation, ASRS, AMRs/AGVs, Robotic pick/depalletizers, Other
• Who owns the automation PLC/controls and who will provide interface documentation (vendor, integrator)? Options: Vendor owns controls, Integrator owns controls, Customer owns controls, Other
• Do you require real-time motion control or higher-level orchestration only? Options: Real-time control (PLC-level), Orchestration/commands only, Both
• What communication protocols are used (e.g., SOAP/REST API, OPC-UA, MQTT, proprietary PLC)?
• What throughput and latency SLAs must the integration meet (e.g., events/sec, ms latency)?
• Who is responsible for safety interlocks, emergency stop handling, and on-site testing? Options: Customer, Automation vendor, WMS integrator, Shared

Deploy Packing, Carrier Rate Shopping, and Labeling

• Which carriers and services must be integrated for rating and label generation?
• Do you require dimensional capture and automated dimensional weight calculation? Options: Yes - dim capture required, No - manual dims, Not at this time
• Are there multi-leg shipments, customs documents, or pallet/LTL workflows to support? Options: Yes - LTL/pallet, Yes - international/customs, No
• What carrier selection rules should be applied (rate, transit time, preference, account mapping)? Options: Lowest price, Guaranteed delivery time, Account/contract mapping, Custom rules
• What labeling templates and scan sequences are required (carrier labels, pallet labels, internal SSCC)?
• What acceptance tests validate packing and carrier flows (correct label, successful manifest upload)?

Enable Multi-Channel Order Allocation and Fulfillment

• Which sales channels are in scope (e-commerce, retail stores, marketplaces, wholesale, 3PL)? Options: E-commerce, Retail/Store Fulfillment, Marketplaces (Amazon/eBay), Wholesale/B2B, 3PL partners
• How should inventory be allocated across channels (shared pool, dedicated pools, reserved quantities)? Options: Shared inventory pool, Dedicated inventory per channel, Reserved/threshold allocations, Hybrid
• How do you want to handle split shipments and partial fulfillment across channels? Options: Allow split shipments, Prevent splits, Configurable per order
• Do channel-specific SLAs or prioritization rules exist (e.g., marketplace orders prioritized)? Options: Yes - channel SLAs, No - uniform SLA, Custom per channel
• Are there channel-specific returns or remediation workflows to include? Options: Yes - include returns, No
• What acceptance metrics will show allocation is working correctly (e.g., correct channel fulfillment rate)?

Implement Replenishment and Min/Max Rules

• Which replenishment triggers are preferred (min/max, time-based, demand-driven, scheduled)? Options: Min/Max, Periodic review, Demand-driven (consumption), Scheduled replenishment
• What are typical min/max values or how are they calculated (manual, ERP feed, statistical forecast)? Options: Manually defined, ERP-provided, Calculated from forecast/historical usage, Other
• Which source locations replenish pick faces (bulk, reserve, vendor managed inventory)? Options: Bulk/reserve, Vendor managed, Direct from inbound, Other
• Do replenishment tasks require slotting or constraints by equipment (pallet jack vs conveyor)? Options: Yes - equipment constraints, No
• What frequency and lead time expectations exist for replenishment cycles? Options: Continuous/near-real-time, Hourly, Daily, Custom schedule
• What acceptance criteria validate replenishment (stockout reduction %, replenishment cycle time)?

• Statement of Work (SOW)
• Master Services Agreement (MSA)
• Order Form & Pricing
• Payment & Invoicing Schedule
• Acceptance Criteria & Test Plan
• Implementation Milestones & Go/No‑Go Plan
• Service Level Agreement (SLA)
• Support & Maintenance Agreement
• Change Order & Scope Management
• Data Processing & Privacy Addendum (DPA)
• Integration Responsibility Matrix
• Security & Compliance Addendum
• Training & Knowledge Transfer Plan
• Cutover, Rollback & Escalation Runbook
• Hardware & Automation Commissioning Agreement
• Termination, Transition & Exit Plan

• Success Executive Review
• Operational KPI Deep Dive
• Lessons Learned & Continuous Improvement Workshop
• Backlog Prioritization & Roadmap Sync
• Peak Readiness & Escalation Drill

• Assign clear owners and SLAs for each committed backlog item.
• Schedule the Operational KPI Deep Dive within 7 days with pre-read data extracts.
• Pre-work & Data Set Confirmation
• Confirm the integrity and calculation method of each success KPI.
• Isolate the root causes for KPI variances and quantify their operational impact.
• Agree on a prioritized list of corrective experiments and measurement changes with owners and timelines.
• Ensure acceptance-test evidence is reproducible and stored for audit.
• Deliver cleaned data extracts and transaction traces for the identified anomalies.
• Update KPI definitions and dashboards with agreed calculation changes.
• Create experiment tickets in the shared backlog with owners, success criteria, and test windows.
• Workshop Framing & Rules of Engagement
• Document evidence-based lessons learned tied to KPIs and customer impact.
• Agree a short list of prioritized experiments and process changes with owners and success measures.
• Convert learning outcomes into backlog items and training/SOP updates.
• Create improvement epics in the shared backlog with acceptance criteria and test windows.
• Schedule required training sessions and assign SOP updates to document owners.
• Assign a bi-weekly check-in to review experiment results and update priorities.
• Backlog Health & Governance Review
• Produce a prioritized, timebound backlog aligned to business impact and release windows.
• Introductions & Meeting Objectives
• Agree communications and stakeholder notification process for roadmap changes.
• Publish the prioritized backlog and release commitments with owners and SLAs.
• Schedule required engineering and QA windows for committed fixes.
• Document the hotfix escalation path and on-call roster for peak windows.
• One-sentence Peak-State Definition & Success Criteria
• Confirm readiness to meet peak success signals with clear contingency plans.
• Validate the escalation and recovery playbooks through a realistic drill.
• Identify and assign remediation actions for any operational or tooling gaps found.
• Update runbooks and escalation contacts based on drill findings.
• Schedule smoke tests and automation failover tests prior to the actual peak period.
• Assign owners and deadlines for closing drill-identified gaps in the backlog.
• Confirm whether success signals have been met or identify precise acceptance gaps.
• Translate operational performance into business impact to secure executive decisions.
• Obtain executive approval for the prioritized fixes, resources, or scope changes needed to reach success.
• Align on timing and owners for follow-up operational actions and releases.
• Produce one-page executive summary showing KPI-to-target variance and recommended executive decisions.
• Assign executive owners and deadlines for any approved scope or funding changes.
• Top Backlog Items Review (Impact Summaries)
• One-sentence Current State
• Capacity & Headroom Review
• One-sentence Future State Revisit
• One-sentence Current State (Operational)
• Data-driven Retrospective (What went well / What didn't / Opportunities)
• KPI Walkthrough (Metric-by-Metric)
• Prioritization Exercise (RICE / Impact/Effort)
• Review Escalation Playbooks & SLAs
• Success Signals & Acceptance Criteria Review
• Roadmap & Release Window Alignment
• KPI Summary vs Targets (Executive Dash)
• Root-cause Themes and Impact Mapping
• Root Cause Analysis of Top Anomalies
• Tabletop Incident Simulation
• Owner / SLA Commitments & Communication Plan
• Prioritization & Timeboxing of Improvements
• Validation of Acceptance Tests with Sample Transactions
• Manual Workarounds & Automation Failover Validation
• Business Consequence of Gaps
• Proof Points & Validation Examples
• Training & SOP Updates Planning
• Escalation & Hotfix Process