Skip to content

Appendix

Methodology and Analytical Framework 

This benchmark analyzes 100 businesses operating on NetSuite ERP that were actively evaluating warehouse management technology to bridge operational gaps.  

The sample spans 22 industries across North America. Companies range from single-digit annual revenue and low SKU counts to organizations over $150+ million in annual revenue and managing more than 50,000 SKUs. 

The study uses a structured sample of companies that had identified warehouse operational challenges and were actively considering a technology solution. It is not a randomized survey of all SMB warehouse operations. The findings therefore describe the evaluating population rather than the entire market. Companies experiencing similar conditions without actively pursuing a warehouse technology solution are not represented. 

The sample contains companies classified at Warehouse Complexity Index levels L1 through L4. L5 Highly Automated operations are not represented and should not be inferred from these findings. 

 

Research and Validation Approach 

Each company was analyzed using a structured framework designed to identify warehouse pain dimensions, operational conditions, existing technology environment, and complexity signals. 

The analytical framework was developed iteratively and reviewed through multiple quality-control cycles. Findings were checked against the underlying source materials to confirm that operational conditions, technology classifications, and supporting evidence were applied consistently across the sample. 

All company-level classifications were reviewed before aggregation. Statistical calculations and report tables were generated programmatically and reviewed for accuracy. 

This approach is designed to identify recurring patterns in operational requirements and technology gaps. It is not intended to function as a comprehensive warehouse assessment of each individual company. 

 

Warehouse Complexity Index 

Each company was classified using a five-level Warehouse Complexity Index adapted from Gartner’s warehouse complexity framework. The Index evaluates the operational requirements present in the warehouse, rather than the technology already deployed. 

Classification considered documented signals, including location count, fulfillment-channel complexity, inventory-tracking requirements, regulatory obligations, integration dependencies, and specialized operating conditions. 

When an operational dimension was not documented clearly enough to support a higher classification, it was not used to increase the company’s WCI level.

Operational Requirement Profile  
Level Operational Requirement Profile  
L1 Basic Single-site operations with limited channels and minimal tracking or regulatory requirements. 
L2 Standard Operations with multiple locations or fulfillment channels, plus basic bin, lot, or serial tracking requirements.  
L3 Moderate Multi-site or multi-channel operations with more advanced traceability, serialization, regulatory, or integration requirements. 
L4 Complex Multi-subsidiary, global, highly specialized, or complex omnichannel operations. 
L5 Highly Automated Operations requiring orchestration of advanced automation, robotics, conveyors, sorters, or goods-to-person workflows. 

Source Framework: Gartner, “Use the 10 Dimensions of Warehouse Complexity Before Selecting a WMS” and related warehouse complexity research  

 

Pain Dimension Framework 

The study tracks five pain dimensions based on operational performance concepts reflected in the ASCM Supply Chain Operations Reference model. The framework identifies the category of operational challenge present, rather than treating each issue as a separate or mutually exclusive problem. 

Pain Dimension Framework  
Pain Dimension SCOR Performance Area Included Conditions
Process and Technology Friction Cost and Agility  Disconnected, absent, or ineffective tools; manual processes; spreadsheet dependency; no scanning; duplicate data entry. 
Inventory Visibility and Accuracy Reliability  Inventory inaccuracies, location-management gaps, inability to locate inventory, and limited real-time visibility. 
Labor and Resource Inefficiency Cost  Labor-intensive work, institutional knowledge dependencies, difficult training, and reliance on manual intervention. 
Execution and Throughput Bottlenecks Responsiveness  Slow or constrained receiving, picking, packing, shipping, capacity, and scalability processes. 
Quality, Compliance, and Risk Reliability and Asset Management  Picking errors, lot and serial-tracking gaps, audit exposure, compliance risk, and financial leakage. 

 

A single operational condition may contribute to more than one pain dimension. For example, manual data entry may represent both process and technology friction and labor inefficiency. The dimensions are overlapping lenses on the same operational environment. 

 

Warehouse Operator Persona Framework  

Each company was assigned to one of four mutually exclusive warehouse operator profiles. Personas are based on the combination of execution and quality or compliance pain dimensions present in the company’s operational profile. 

Warehouse Operator Persona Framework  
Persona Assignment Logic
Analog Operator Neither Execution and Throughput Bottlenecks nor Quality, Compliance, and Risk are active. 
Throughput Ceiling Execution and Throughput Bottlenecks are active; Quality, Compliance, and Risk are not active. 
Regulated Operator Quality, Compliance, and Risk are active; Execution and Throughput Bottlenecks are not active. 
Full System Breakdown Both Execution and Throughput Bottlenecks and Quality, Compliance, and Risk are active. 

 

The persona framework is designed to segment companies by what is breaking operationally. It is not determined by industry, annual revenue, headcount, or warehouse complexity level. 

Assignment reflects the pain dimensions documented at the time of evaluation, rather than every condition that may ultimately be identified. Execution and quality or compliance concerns can become more evident as an evaluation progresses. Exact persona shares varied when assignment definitions were tested, particularly for the Regulated Operator and Full System Breakdown profiles, which depend on a documented quality, compliance, or risk signal. The persona percentage distribution should therefore be read directionally. The four profiles remain useful for distinguishing operational failure states, even where their exact shares vary.

 

Prior Warehouse Technology Classification  

A company was classified as having prior warehouse technology when the available records identified an existing WMS or barcode-scanning solution in use before the current evaluation. ERP inventory functionality alone was not classified as prior warehouse technology unless it included a warehouse-management or scanning component. 

Companies with prior warehouse technology were further categorized into one of four failure patterns based on the primary reason the existing solution did not meet operational needs. 

Warehouse Operator Persona Framework  
Failure Pattern Definition
WMS Lacks Required Functionality An existing warehouse system could not support the operation’s required workflows, controls, or operating conditions. 
Deployed but Bypassed by Workers A WMS or scanning solution was available, but workers did not use it consistently or actively worked around it. 
Hardware Purchased Without WMS Software Barcode scanning hardware was acquired without the warehouse software needed to direct work and connect scan activity to ERP transactions. 
Implementation Degraded Operations A deployed solution introduced operational disruption, performance issues, data issues, or was abandoned after implementation. 

 

Study Limitations  

  • Sample Scope: This benchmark analyzes 100 companies actively evaluating warehouse technology. It describes an evaluating population, not all SMB warehouse operations. Companies with similar conditions that were not pursuing a solution are not represented. The sample does not include L5 Highly Automated operations, and findings from small subgroups, including L4 Complex operations, should be read directionally. 

  • Classification and Measurement: The Warehouse Complexity Index is based on documented operational signals rather than full site assessments. Revenue figures are estimates rather than verified financial results. Pain prevalence reflects the operational concerns documented at the time of evaluation, not every challenge present in an operation. Future studies with more in-depth discovery may provide comprehensive representation of this.

  • Interpretation: The study identifies recurring patterns among operational requirements, pain conditions, and technology gaps within this sample. It does not establish their prevalence across the broader market or the underlying causes of reported technology shortcomings.   

 

 

Key Definitions

Key Definitions
Term Definition
Pain Dimension One of the five categories of warehouse operational pain: Process and Technology Friction; Inventory Visibility and Accuracy; Labor and Resource Inefficiency; Execution and Throughput Bottlenecks; and Quality, Compliance, and Risk. 
Operational Condition (micro-tag) A specific warehouse-floor issue identified in the sample, such as manual processes, disconnected systems, no scanning, or cycle-counting pain. One condition may contribute to more than one pain dimension. 
Warehouse Complexity Index (WCI) A five-level classification of the operational requirements a warehouse must support. Classification considers documented signals such as locations, fulfillment channels, tracking needs, regulatory obligations, and integration requirements. 
Persona One of four operational profiles defined by the combination of active pain dimensions. Personas identify what is breaking in the operation and are not determined by industry, revenue, headcount, or warehouse complexity level. 
Prior Technology An existing warehouse management system or barcode-scanning solution in place before the company’s current technology evaluation. ERP inventory functionality alone does not qualify unless it includes a warehouse-management or scanning component. 
Prevalence The percentage of companies in the sample exhibiting a given pain dimension, operational condition, technology status, or other reported characteristic. Unless otherwise noted, percentages are calculated at the company level. 
Hidden Warehouse Complexity A market condition in which a warehouse’s operational requirements exceed what conventional company-level measures, such as revenue, headcount, or volume, suggest. It occurs when an operation appears simple on paper but requires more capable or connected warehouse technology in practice. 

 

 

Citations

Citations
ID Source Stat / Framework Section Used 
C1 Warehousing Education and Research Council, 2023 DC Measures Annual Survey and Report  Respondent revenue distribution: 94% above $100 million, subject to final source verification  Part 1: The SMB Warehouse Operations Gap 
C2 U.S. Small Business Administration, Office of Advocacy  Number of small-business manufacturers and wholesale distributors in the United States, subject to final source verification  Part 1: The SMB Warehouse Operations Gap 
C3 Gartner as stated in Supply Chain 24/7, Use the 10 Dimensions of Warehouse Complexity Before Selecting a WMS  Warehouse complexity should inform WMS requirements and selection criteria  Part 3: The Risk of Complexity Misclassification; Methodology 
C4 Association for Supply Chain Management. SCOR Digital Standard, Version 14.0, Introduction and Front Matter, ©2025. Document Performance attributes, particularly Reliability, Responsiveness, Agility, Costs, and Assets, informed the organization of the report’s five operational pain dimensions. See “Performance,” pp. vii–viii. Methodology: Pain Dimension Framework
C5 Gartner. Original warehouse-complexity research. Gartner document Cited as background to the five-level warehouse framework. The original research is gated and was not consulted directly for this study. Methodology: Warehouse Complexity Index
C6 Todd Kolber. “Five Levels of Warehouse Maturity and Why They Can Coexist.” Supply Chain 24/7. Article Publicly accessible discussion of five warehouse-maturity levels. Adapted by RF-SMART to better represent warehouse implementation complexity and operational requirements in this study. Part 1: Warehouse Complexity; Methodology: Warehouse Complexity Index

 

 

 

About the Researcher 

Blair Gordon is a Senior Digital Marketing Analytics Specialist at RF-SMART with more than 10 years of experience in data analytics and five years in supply chain technology. Blair holds specializations in Supply Chain Management and Supply Chain Analytics through Rutgers University’s Coursera curriculum, as well as the Google Data Analytics Professional Certificate. 

Blair led the study design, analytical framework development, data validation, and statistical analysis for this benchmark. 

About RF-SMART 

RF-SMART is the leading warehouse management system (WMS) for NetSuite, providing tailored solutions that improve inventory accuracy, streamline operations, and support every stage of the supply chain. Trusted by more than 2,800 NetSuite customers across 40+ countries. RF-SMART delivers robust capabilities that support all businesses – from companies generating less than $1 million in annual revenue to enterprises exceeding $1 billion. Built natively in NetSuite, RF-SMART eliminates integration costs and removes the need for additional IT infrastructure. Beyond NetSuite, RF-SMART brings comprehensive inventory management solutions to Oracle SCM Cloud, JD Edwards, and Microsoft ERPs.