SupplyGrid · Glossary Definition

Factorial Design

A factorial design is a design of experiments in which two or more factors are studied simultaneously, with every combination of their levels included. This allows estimation of both main effects and interactions. Full factorial designs require 2^k runs for k two-level factors, while fractional factorial designs test a subset to reduce run count.

In a manufacturing or warehousing setting, factorial design helps teams test how operational inputs jointly drive outcomes such as throughput, defects, lead time, stockout risk, picking accuracy, receiving delay, or material availability. Typical factors include reorder point, safety stock, supplier lead time, batch size, barcode scan compliance, forklift availability, and receiving dock staffing; responses include fill rate, line stoppage minutes, inventory record accuracy, and dock-to-stock time. The key advantage is that factorial experiments expose interaction effects that one-factor-at-a-time testing misses. For example, higher safety stock may improve service only when supplier lead time variability is high, or extra receiving labor reduces congestion only when inbound volume exceeds a threshold. A supply-chain team defines the objective, selects factor levels, runs a planned matrix of scenarios, and analyzes results with ANOVA, effect plots, or regression to identify the inputs that materially drive performance.

Operational Failure Matrix
Risk LevelOperational Pitfall Description
⚠️ Warning 1Invisible interaction effects: A shop raises inventory yet still sees stockouts because the real trigger is the interaction between forecast error and supplier lateness. Testing factors separately hides this combined effect, producing false conclusions about inventory.
⚠️ Warning 2Full factorial bloat: Adding too many factors doubles or more the number of runs, quickly becoming expensive and disruptive. With five or more factors, the experiment matrix can overwhelm operations, overload receiving, and make clean analysis unrealistic.
⚠️ Warning 3Confounded by bad execution: Inaccurate cycle counts, inconsistent scan compliance, or non-randomized trials can make the experiment blame the wrong factor. In warehouses, the response depends on disciplined execution, so poor data hides the true driver.
Technical FAQs
What is the difference between a factor and a level?

A factor is an input variable, and a level is a specific setting of that factor.

Why use factorial design instead of one-factor-at-a-time testing?

Factorial design estimates both individual factor effects and interactions, which is essential when inventory, procurement, and warehousing variables influence each other. One-factor-at-a-time testing misses these interaction effects and can lead to incorrect conclusions.

When is fractional factorial design preferred?

When the number of factors is too large for a full factorial and the goal is screening—identifying the few most important drivers with fewer runs. NIST notes full factorial designs are not recommended for five or more factors.

Software that works like your best tools.

This Glossary is maintained by Ryxen — focused software tools that solve specific operational friction points for Canadian small businesses. No ERP bloat, no per-user pricing, no demo calls.