Study guide

12.7 Process Batches, Transfer Batches, and Backflushing

APICS CPIM Certified in Planning and Inventory Management Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 ECM 9.0 Domains and Weights 1.3 How to Study for CPIM

2 Supply Chain Strategy Foundations

2.1 Supply Chains, the Environment, and Strategy 2.2 Environment Analysis and Strategic Scope 2.3 Developing and Managing Organizational Strategy 2.4 Competitive Analysis: Five Forces, Benchmarking, and Value Chain

3 Strategy Performance and Operations Choices

3.1 Performance Monitoring and KPIs 3.2 Functional and Operational Strategies 3.3 Environments, Types, and Layouts 3.4 Service Process Design and Product-Process Trade-offs

4 Sales and Operations Planning

4.1 S&OP Purpose and Process 4.2 Aggregate Demand and Supply Plans 4.3 Reconciling S&OP Plans 4.4 Portfolio, New Product Introduction, and Life-Cycle Planning in S&OP 4.5 Strategic Buffers, Bottlenecks, and Capacity-Constrained Resources

5 Plan and Manage Demand

5.1 Demand Management 5.2 Sources of Demand and Forecasting 5.3 Forecast Performance 5.4 Marketing, Promotions, and Product Management 5.5 Qualitative, Associative, and AI-Driven Forecasting

6 Master Scheduling

6.1 Creating the Master Schedule 6.2 Rough-Cut Capacity Planning and MPS Validation 6.3 Using and Maintaining the Master Schedule 6.4 Planning Bills and Two-Level Master Scheduling 6.5 NPI, DFMA, Prototype, and End-of-Life Schedules

7 MRP, CRP, and Supply Disruptions

7.1 Material Requirements Planning 7.2 CRP, Order Promising, and Final Assembly Scheduling 7.3 Changes and Supply Disruptions 7.4 Product Costing and Variance Analysis for Planners

8 External Supply Sources

8.1 Suppliers and Procurement 8.2 Purchasing and Maintenance 8.3 Supply Chain Risk Management 8.4 Sourcing Footprint and Supplier Relationship Types 8.5 Supplier Release Mechanics and Inbound Logistics

9 Sustainability and Reverse Logistics

9.1 Sustainability Strategies 9.2 Waste Hierarchy and Reverse Logistics 9.3 Sustainability Standards, Reporting, and Life-Cycle Assessment

10 Inventory Planning and Costs

10.1 Inventory Planning 10.2 Inventory Costs, Accounting, Costing, and Metrics 10.3 EOQ, Reorder Point, and Safety Stock

11 Inventory Management and Control

11.1 Inventory Management Policies 11.2 Inventory Control 11.3 Service Levels and Inventory Tradeoffs 11.4 MRO Inventory and Maintenance Planning Inputs 11.5 Traceability Standards and Off-Site Inventory

12 Detailed Schedules and PAC

12.1 Planning Detailed Schedules 12.2 Scheduling and PAC Methods 12.3 Creating Production and Service Schedules 12.4 Managing Detailed Schedules and Scheduling Materials 12.5 Sequencing Rules, Lot Splitting, and Overlapped Scheduling 12.6 Capacity Types, Safety Capacity, and Labor Scheduling 12.7 Process Batches, Transfer Batches, and Backflushing

13 Plan and Manage Distribution

13.1 Planning Distribution 13.2 Replenishment and DRP 13.3 Order Management, Trace/Track, and KPIs

14 Quality and Business Investments

14.1 Quality Systems and Tools 14.2 Capital Equipment and Facilities 14.3 Technology in Planning and Inventory 14.4 The Seven Basic and Seven New Quality Tools 14.5 SPC Charts and Variation Types 14.6 Systems Requirements, Master Data, and Emerging Technologies

15 Continuous Improvement

15.1 Continuous Improvement Overview 15.2 Lean, JIT, and the Seven Wastes 15.3 Six Sigma, Kaizen, and Root Cause Tools 15.4 TPM, SMED, Standardized Work, and Visual Management

16 Integration and Exam Readiness

16.1 Planning Hierarchy Integration 16.2 High-Yield Calculations Drill 16.3 Exam Day, Scoring, and Credential Maintenance

12.7 Process Batches, Transfer Batches, and Backflushing

Key Takeaways Explain This Topic AI

The process batch is the quantity produced between setups and is driven by setup economics; the transfer batch is the quantity moved to the next operation and is driven by flow - the two do not have to be equal

Cutting the transfer batch from 500 to 50 drops throughput time from 38.4 to 23.9 hours, a 38% reduction, with the same two setups - the cost is ten moves instead of one, not extra changeover

Backflushing deducts components from the reported completion of the parent through the bill of material; it requires accurate current-revision BOMs, low scrap variability, short cycle times, and reliable completion reporting

A backflush error leaves no transaction to audit, so it accumulates silently: stale BOM or unreported scrap, wrong deduction, inventory record accuracy falls, MRP nets against a fictitious balance, shortages and excess appear together

An open work order holds allocations that understate net available, still appears to MRP as a scheduled receipt that will never arrive, overstates work-in-process value, and carries phantom remaining hours into work center load

Last updated: July 2026

Process Batch Versus Transfer Batch

A process batch is the quantity produced between setups. It is driven by setup economics : a large setup cost pushes the batch up, carrying cost pushes it down - the same trade-off behind economic order quantity in chapter 10.

A transfer batch is the quantity moved to the next operation. It is driven by flow : container size, handling equipment, distance, and how soon the downstream resource can start.

The central lean and theory-of-constraints insight is that these two quantities do not have to be equal , even though most enterprise resources planning defaults make them equal. Shrinking the transfer batch shortens lead time without touching setup cost at all , because you still run one setup per operation. You pay in moves, not in changeovers.

Worked comparison

A process batch of 500 units runs through two operations. Operation A: 2.0-hour setup, 0.04 hours per piece (20.0 hours run). Operation B: 1.0-hour setup, 0.03 hours per piece (15.0 hours run). Move time is 0.4 hours; queue excluded.

Transfer batch = process batch (500): 2.0 + 20.0 + 0.4 + 1.0 + 15.0 = 38.4 hours .

Transfer batch = 50: operation A completes its first 50 at 2.0 + 2.0 = 4.0 hours; they arrive at B at 4.4 and B's setup finishes at 5.4. B is the faster operation, so it starves between transfers and the finish is governed by the last transfer batch: A completes all 500 at 22.0 hours, move to 22.4, run the final 50 at 50 x 0.03 = 1.5 hours, complete at 23.9 hours .

That is 14.5 hours - a 38% reduction in throughput time - with the same two setups and the same 500-piece process batch. What changed is ten moves instead of one, ten move transactions, and work-in-process sitting in two places at once. This is the principle underneath the overlapped-scheduling technique in section 12.5: overlapping is the scheduling mechanic, and "transfer batch need not equal process batch" is the reason it works.

What Is Actually Runnable Today

A schedule says what should run. Four status feeds say what can run, and the gap between them is where dispatching earns its keep:

Equipment status - up, down, degraded, or not qualified for this part; tooling, dies, fixtures, and programs present and within calibration.

Labor status - who reported, who is certified on the operation, and whether overtime is authorised.

Work-order status - planned, firm planned, released, in process, on hold (quality, engineering, or material short), complete, closed. Only a released order with material allocated and no hold is dispatchable. A planner who dispatches from the order pool rather than the released pool is scheduling work the floor cannot start.

Preventive maintenance schedules - planned downtime must be netted out of available capacity before loading , not discovered afterwards. Deferring preventive maintenance to protect this week's schedule borrows hours at a punitive rate: the unplanned breakdown arrives without warning, usually in the week you can least afford it.

Backflushing

Backflushing (post-deduct inventory transaction processing) deducts component inventory automatically from the reported completion of the parent . Report 400 finished units and the system explodes the bill of material (BOM) , relieving 400 times the per-unit quantity of every backflushed component from its point-of-use location. No picks, no issue transactions, no material-issue paperwork.

The appeal is transaction cost. On a repetitive line building thousands of units a day from dozens of components, discrete issues would flood the system with transactions that add no control value.

The prerequisites are cumulative - you need all of them, not most:

Accurate bills of material at the current revision, with realistic scrap and yield factors

Low, predictable scrap and substitution - the system deducts what the BOM says, never what was actually consumed

Short cycle times and low work-in-process , so the timing error between real consumption and the reported deduction stays small

  • Accurate completion reporting at the count point, with correct unit-of-measure conversions
  • Disciplined point-of-use replenishment , so the location being deducted is the location being consumed

The failure mode is silence. A discrete issue that goes wrong leaves a wrong transaction somebody can find. A backflush that goes wrong leaves no transaction at all - an undocumented substitution, an unreported scrap event, a BOM one revision stale - and the balance simply drifts. Errors accumulate invisibly until inventory record accuracy collapses, and then the consequence chain the exam loves runs to its end:

stale BOM or unreported scrap, wrong quantity deducted, inventory record accuracy falls, MRP nets against a fictitious on-hand balance, wrong planned orders, shortages and excess appear at the same time, expediting.

Controls that keep backflushing honest: backflush only low-value, high-usage, stable components and issue high-value, serialized, or lot-traced items discretely; place count points at meaningful intermediate stages rather than only at final completion; treat any negative on-hand balance as a backflush error alarm; and cycle count backflushed items more frequently, because cycle counting is the only detector you have.

Transaction method Record accuracy Transaction cost When appropriate

Discrete issue (pick and issue each component to the order) High - every movement is recorded and auditable High - one transaction per component per order High-value, serialized or lot-traced items; regulated product; long cycle times; unstable BOMs; job shop and make-to-order

Backflush (deduct from parent completion through the BOM) Only as good as the BOM and the completion report; errors are silent Low - one reporting event relieves every component Repetitive or lean flow; short cycle times; stable BOMs; low-value, high-usage components held at point of use

Hybrid High where it matters, lower elsewhere Moderate Most real plants: discrete-issue the expensive and traced items, backflush fasteners and consumables

Closing Work Orders

Closing an order is a control transaction, not clerical tidying. At close you capture the final quantity completed , the scrap and reject quantity with its disposition, actual labor and machine hours, and any material issued but unused and returned. Those numbers produce the variances - material usage, labor efficiency, yield - and they feed the scrap factors and time standards used to plan the next order.

Leaving an order open does specific, traceable damage:

Allocations stay live. Components remain reserved for an order that is already finished, so net available and available-to-promise are understated and MRP plans replenishment nobody needs.

The open order still looks like a scheduled receipt. MRP believes supply is coming that will never arrive, under-plans against it, and the shortage surfaces later.

Work-in-process value is overstated , and the residual eventually falls out as a write-off nobody can explain.

Capacity reports carry phantom load - remaining operation hours on a completed order inflate work center load and distort every capacity decision built on it.

Close orders promptly, and close them with real numbers. An order closed at the planned quantity instead of the actual one is a backflush error with a signature on it.