Constraints & Product Mix — Constraint/bottleneck and product mix decisions (intro)

Every business operates within a finite set of resources—machine hours, labor hours, raw materials, warehouse space—and the challenge of deciding which products to emphasize when those resources run short is as old as manufacturing itself. During the Industrial Revolution, factory managers already wrestled with the question of how to allocate limited loom time or furnace capacity across multiple product lines. However, it was not until the twentieth century that formal analytical tools emerged to guide these decisions beyond intuition and rule-of-thumb heuristics.

The concept of a constraint—a resource whose limited availability restricts overall output—became a cornerstone of operations management and managerial accounting during the mid-twentieth century. The development of linear programming during World War II gave decision-makers a mathematical framework for optimizing product mix under multiple constraints, and Eliyahu Goldratt's Theory of Constraints (TOC) in the 1980s elevated bottleneck management from a technical exercise to a strategic philosophy. Together, these milestones shaped how modern managers approach the fundamental question: When you cannot produce everything, what should you produce?

Against this backdrop, the introductory product-mix problem asks a deceptively simple question: if a single resource limits your total output, which products should receive priority? The answer hinges not on which product earns the highest contribution margin per unit, but on which product earns the highest contribution margin per unit of the binding constraint. Understanding why this distinction matters is the central lesson of this module.

Before diving into the mechanics of product-mix optimization, it is essential to establish a precise vocabulary. Several interrelated concepts form the foundation of constraint-based decision-making, and each plays a distinct role in the analysis. A constraint is any factor that limits the system's ability to achieve more of its goal—typically, generating throughput or profit. When a constraint is internal (such as a machine with insufficient capacity), it is commonly called a bottleneck. The binding constraint is the one constraint whose capacity is fully consumed in the optimal solution; non-binding constraints have slack capacity remaining.

The diagram below illustrates how a single binding constraint forces a product-mix decision. Three products (A, B, and C) each demand a share of a limited resource—in this case, machine hours. The total demand for machine hours across all products exceeds the available capacity, creating a bottleneck that requires prioritization. Products are ranked by their contribution margin per machine hour, and the available capacity is allocated starting with the highest-ranked product and working downward until the resource is exhausted.

Notice the counterintuitive result: Product B earns the highest contribution margin per unit ($60), yet it consumes the most machine hours per unit (4 MH). When capacity is scarce, each machine hour is precious, and the product that converts those hours into the most contribution margin receives priority. This principle—ranking by CM per unit of the binding constraint—is the single most important decision rule in introductory product-mix analysis.

The product-mix decision under a single constraint can be expressed with a small set of equations. The objective is to maximize total contribution margin subject to the constraint that total resource consumption cannot exceed available capacity. While multi-constraint problems require linear programming, the single-constraint case yields a clean, closed-form solution that business students can execute by hand.

To solidify the ranking concept, consider the following illustrative data. A factory produces four products (W, X, Y, and Z) and has only 1,200 labor hours available per week. The table below presents unit-level data, computes CM per labor hour, and shows the correct priority order. Observe that the product with the highest CM per unit (Product Z at $90) does not rank first because it consumes 6 labor hours per unit—its CM per labor hour is only $15.

The visual contrast between the two bar series drives the lesson home: a high per-unit margin can mask poor resource efficiency. Managers who allocate scarce labor hours to Product Z first—because its $90 CM looks most attractive—would sacrifice significant total contribution margin compared to filling demand for Products W and X first. The grouped bar chart makes this trade-off immediately visible and memorable.

Greenfield Manufacturing produces three products—Alpha, Beta, and Gamma—using a single CNC milling machine. The machine is available for 600 machine hours per month. Demand, pricing, and cost data are as follows:

The single-constraint product-mix model is a powerful introductory tool, but it operates under simplifying assumptions. Understanding both its strengths and limitations prepares you for the more sophisticated models—such as linear programming and Theory of Constraints throughput accounting—that you will encounter in advanced coursework and professional practice.

The introductory single-constraint approach is a special case of broader optimization frameworks. As you progress in managerial accounting and operations management, you will encounter techniques that relax the simplifying assumptions of this module. The table below maps the introductory concept to its advanced counterparts, providing a roadmap for future study.

Perhaps the most important conceptual bridge is between the CM-per-constraint-unit ratio and the shadow price in linear programming. In a single-constraint world, the shadow price of the binding constraint equals the CM per constraint unit of the product ranked last (i.e., the marginal product). This tells management the maximum they should be willing to pay to acquire one additional unit of the scarce resource—a direct input to capacity-expansion decisions. Mastering the introductory model therefore builds the intuition needed to interpret LP sensitivity reports and make strategic investment decisions about bottleneck relief.