Shipping Buffer §

Concept: Vocabulary that names a phenomenon.

A time-based reserve placed between the constraint’s output and the customer-commitment point, sized to protect the quoted due date from variability downstream of the constraint and from constraint disruptions that the constraint buffer absorbed but didn’t make up.

Also known as: due-date buffer; production buffer (in Simplified Drum-Buffer-Rope (S-DBR), where the shipping buffer is the only buffer).

Context §

The shipping buffer is the time reserve that couples the production system to the customer promise. Where the Constraint Buffer protects the constraint from being starved by upstream variability, the shipping buffer protects the customer-due-date commitment from variability that occurs after the constraint has done its work, and from the residual effect of any constraint disruption the constraint buffer absorbed without fully recovering. In full Drum-Buffer-Rope (DBR) the shipping buffer sits at the back of the order’s flow as a sibling to the constraint buffer at the front. In Simplified Drum-Buffer-Rope (S-DBR) the constraint buffer disappears and the shipping buffer (renamed the production buffer in Schragenheim’s later work) absorbs the whole protective role for the entire production interval.

The concept sits at the production-operations boundary between internal flow control and the external due-date promise. It matters to practitioners who already understand Constraint, full DBR, S-DBR, and Buffer Management, because the shipping buffer’s placement changes with the constraint type: in full DBR it protects the post-constraint interval, while in S-DBR it becomes the single production buffer for the order’s whole release-to-completion interval.

What It Is §

A shipping buffer is a time reserve, not an inventory reserve. The TOCICO Dictionary defines it as “one of the time buffers used to protect the shipping date of finished goods”: the order’s release into the plant is scheduled so that, on its expected path through the constraint and out the back of the plant, the order arrives at the shipping point one shipping-buffer’s worth of time before the quoted due date. The duration is what the planning system commits to; the work-in-process or finished-goods inventory that sits at the back of the flow when the buffer is doing its job is a consequence of the duration interacting with downstream operations’ actual pace.

Srikanth’s TOC Handbook Ch. 8 (“DBR, Buffer Management, and VATI Flow Classification”) is explicit on the structural placement. In a make-to-order DBR implementation, the constraint buffer ahead of the drum and the shipping buffer at the shipping point are placed independently and sized independently. The constraint buffer absorbs variability from material release through to the constraint; the shipping buffer absorbs variability from the constraint through to shipping. The two buffers protect against different sources of variability and converge at different operational signals: the constraint buffer’s color reading tells the floor whether the constraint is at risk of starving, the shipping buffer’s color reading tells the floor whether the due date is at risk of slipping. Both are read through the same three-zone (green / yellow / red) discipline of Buffer Management, but the actions they trigger differ.

For orders whose parts don’t pass through the constraint at all, the shipping buffer is the only time buffer the planning system carries. The TOCICO Dictionary names the practice explicitly: “For parts that do not go through the constraint or assembly buffers, the shipping buffer is used to determine raw materials release and shipping date for the item.” A plant whose constraint touches only some of its product mix uses the constraint buffer where the constraint is in the flow and the shipping buffer everywhere else; the shipping buffer is the universal protection, the constraint buffer is the specialized one.

In S-DBR the structural placement collapses. The constraint is in the market (the plant has enough internal capacity to satisfy demand most of the time, and the binding constraint is the rate at which customers actually order), so the constraint buffer ahead of any interior resource protects nothing. The shipping buffer becomes the single time reserve covering the full interval from material release to order completion. Schragenheim’s later work renames this single buffer the production buffer (also called the reliable production lead time or RPLT) to mark the structural difference. The orientation is the same (protect the due date against variability), but the variability the buffer absorbs now includes everything from raw-material release onward, not only the post-constraint segment.

How It Is Measured or Recognized §

The shipping buffer is divided into three equal time-thirds and read against the same operational color zones as the constraint buffer. Green is the upper third (the order is on track for its due date, no action required). Yellow is the middle third (the order’s flow has consumed enough of the buffer that intervention may become necessary; the order is watched). Red is the bottom third (the due date is at imminent risk and intervention is required now). The reading is taken at the shipping point: each in-flight order is plotted by the fraction of its shipping buffer that has been consumed by the time it reaches the shipping operation, and the board or screen that displays the reading shows every in-flight order in the buffer with its current zone and its upstream location.

The production buffer in S-DBR carries a second operational refinement Schragenheim documents in the TOCICO Dictionary’s entry. On average, orders complete in about half the length of the production buffer; an order enters the red zone when it requires more than 33 percent longer than the average production lead time. The asymmetry matters in practice. A buffer sized as three equal thirds of a liberal lead-time estimate produces operationally crisp red events while still finishing the bulk of orders well before the due date; a buffer sized too tightly produces red events on most orders and floods Buffer Management’s expediting capacity with normal variability.

Wait time before release isn’t part of the shipping buffer. When an order is placed with a due date further out than the buffer’s length, the order waits for release until the buffer’s start point is reached. The TOCICO Dictionary names this wait pre-release production lead time and excludes it from the buffer reading. The distinction prevents the buffer from being padded with planning-side queue time, which would let oversized buffers go unnoticed in the color readings.

Sizing follows the same field practice as the constraint buffer: start with a generous estimate (typically half of the operation’s current production lead time for the constraint buffer, or a liberal estimate of total production time for the shipping/production buffer), then resize against the pattern of color readings over weeks. Buffers that spend most of their time green and rarely produce red events are oversized and should shrink. Buffers that produce frequent red events traceable to a single upstream source should not be lengthened until that source has been addressed.

Why It Matters §

Throughput is money generated through sales, not money generated through production. An order completed inside the plant but shipped late earns customer dissatisfaction and (in many contract regimes) liquidated damages or rate concessions that reduce the throughput the order produces. The shipping buffer is the device that protects throughput against the gap between “finished” and “shipped,” and against the residual constraint variability the constraint buffer absorbed without quite making up.

The shipping buffer also makes a second move that the constraint buffer cannot make on its own: it protects orders whose parts never touch the constraint. In any real plant with mixed product mix, some products pass through the constraint and others don’t; the constraint buffer protects the former, but the latter are still subject to variability in their own flow. The shipping buffer is the universal protection that gives the planning system a single rule for every order: release one shipping-buffer’s worth of time before the due date, regardless of whether the order passes through the constraint or skips it.

The pattern’s value also shows up in the S-DBR case, where the shipping buffer (renamed the production buffer) is the only buffer in the system. Schragenheim’s structural argument for S-DBR rests on the observation that an internal capacity-constrained resource that isn’t tight enough to be the system constraint doesn’t need a dedicated time buffer ahead of it; the single shipping buffer covering the whole production interval is simpler and produces fewer competing color readings for the floor to act on. The simplification is operationally significant: an S-DBR implementation reads one buffer per order, the foreman walks one board, and the expediting decisions follow one priority queue. Reducing the number of buffers without losing protection is exactly the kind of move TOC’s Inherent Simplicity principle predicts will pay off in execution-discipline terms, and the shipping buffer is the buffer that survives the simplification.

For implementations running against a cost-world measurement frame, the shipping buffer is also the device that visibly costs finished-goods inventory time to protect due-date reliability. The buffer’s offset produces work-in-process that arrives before it’s needed at the shipping point; the cost-world reading interprets that work-in-process as inventory excess and the upstream operators’ “early” pace as overproduction. Holding the shipping buffer’s discipline against that reading requires naming the trade explicitly: the buffer’s small finished-goods inventory pays for the throughput the system would otherwise lose to late shipments, and the same color-reading discipline that surfaces oversized buffers will catch and correct any over-investment.

Common Misunderstanding §

The shipping buffer is not the same as a finished-goods stock buffer. Srikanth’s chapter is explicit on the distinction: time buffers (constraint buffer, shipping buffer, assembly buffer) absorb time variability and are sized as durations; stock buffers absorb consumption variability and are sized as quantities of physical inventory. The two protect different things, are read through different signals, and are not substitutes for each other. A make-to-order plant running DBR uses a shipping buffer; a make-to-stock plant running Make-to-Stock vs. Make-to-Availability (MTS vs. MTA) uses stock buffers. The vocabulary slip (calling finished-goods inventory “the shipping buffer”) produces an implementation that doesn’t have time protection where it needs it and doesn’t have stock protection where it needs it either.

The shipping buffer is also not redundant with the constraint buffer. Full DBR carries both, and dropping either degrades a different protection. Dropping the constraint buffer (the move S-DBR makes deliberately, on a system where the constraint is in the market) leaves the constraint vulnerable to upstream variability and only makes sense when the constraint isn’t an interior resource that needs that protection. Dropping the shipping buffer (a mistake some DBR implementations make to “tighten up” their inventory) leaves the due date vulnerable to downstream variability and to any constraint variability the constraint buffer absorbed but didn’t quite recover from. The two buffers protect different intervals against different sources of variability; the decision to carry one and not the other rests on the Constraint Type Identification at Step 1 of the Five Focusing Steps, not on the planner’s preference about how much inventory the plant should carry.

Confusing the shipping buffer with planning slack at the back of the operation is the third common slip. The shipping buffer is not “padding the due date.” The customer’s quoted date is the customer’s quoted date, and the buffer’s offset is from material release inward, not from the due date outward. Implementations that quote a longer due date and call the difference “the shipping buffer” have moved the protection into the customer-facing commitment, which lengthens lead times without producing the operational signal that buffer penetration would otherwise produce. The buffer’s value is in its readability as an internal signal; the customer-facing commitment is a separate decision.

In S-DBR, the misunderstanding that most commonly shows up is treating the production buffer as if it were three structurally separate buffers (one ahead of the gating operation, one through the plant, one at shipping) instead of as a single time reserve covering the whole interval. Schragenheim’s S-DBR drops the constraint buffer specifically to avoid that fragmentation, and the production buffer’s color reading runs against the single interval, not against sub-intervals within it. Implementations that informally re-introduce sub-buffers inside S-DBR re-create the multi-buffer complexity S-DBR was designed to eliminate.

Related Articles §

Sources §