LGT5015 Chap.4 Push, Pull and Supply Chain Integration
Push, Pull and Supply Chain Integration
One chain can use two decision logics
Push commits resources from forecasts, while pull responds to realised demand. This chapter places their boundary at a named operation and uses postponement to keep scale in common work while delaying uncertain differentiation.
Demand uncertainty, economies of scale, lead time and the customer response promise determine whether a proposed boundary is feasible.
Push protects scale and time
Forecast-driven work is valuable where setup costs are large, demand is sufficiently stable or production and transport lead times exceed what a customer will tolerate.
The risk is committing to the wrong item, place or quantity before demand becomes known. Push should therefore be attached to a specific upstream activity rather than used as a description of the whole company.
Pull protects against forecast error
Order-driven work waits for realised demand and can reduce finished-goods exposure. Its limit is response capability.
If fabrication or customisation takes longer than the promised delivery time, a purely pulled flow is infeasible unless the process is redesigned.
Pull also sacrifices some batching or scale benefit, so the saved uncertainty must be worth the additional responsiveness cost.
The boundary resolves the conflict
A hybrid chain produces a common form from forecasts and completes uncertain differentiation after an order.
Postponement is valuable when final variants share components or processes, aggregate demand is more stable than variant demand, and the delayed step can be completed quickly. Locate the boundary at a named operation such as assembly, finishing, packaging or allocation.
Without that location, no inventory or lead-time consequence can be tested.
Stress-test both sides
A boundary too far upstream exposes the chain to many specific forecasts and more finished stock. A boundary too far downstream may create excess generic inventory or make the final response too slow. Compare demand uncertainty, economies of scale and lead time on both sides, then state the customer-time constraint.
A credible recommendation shows what is pooled before the line, what is triggered after it and the condition that would force the boundary to move.
What this chapter covers
- 01
Forecast-driven push
- 02
Order-driven pull
- 03
Push-pull boundary
- 04
Postponement
- 05
Demand uncertainty
- 06
Lead time and scale
Worked example · free
Place a postponement boundary
- 2Identify common work.
- 2Locate the boundary.
- 3Justify service and pooling.
Key terms
- Push System
- A flow driven by forecasts before a specific customer request.
- Pull System
- A flow triggered by realised customer demand.
- Push-Pull Boundary
- The interface between forecast and order-driven stages.
- Postponement
- Delaying differentiation until better demand information arrives.
Push, Pull and Supply Chain Integration FAQ
When does push make sense?
Push is favoured where demand is relatively stable, scale economies are strong or upstream lead times are too long for a customer to wait. Final allocation can still remain pull-driven. Name the forecast-driven operation and test how much generic stock is created, because describing an entire chain as push hides the boundary where real demand can still govern.
What makes postponement valuable?
It pools uncertain demand for final variants into a common form. The delayed conversion must be fast enough to meet service and the generic form must be economical to hold. Otherwise postponement merely moves excess inventory to another stage.
How can a boundary be placed too far downstream?
Late commitment can create excessive generic stock or leave too little time for final conversion. Test inventory on the upstream side and response time on the downstream side together. A feasible boundary must preserve pooling before the line while leaving enough downstream capability to meet the customer promise.
Exam move
For each product, mark the common form, differentiation step and response promise. Move the boundary and explain how inventory and customer time change. Draw the operating sequence as boxes, then place a vertical line at assembly, finishing, packaging and allocation in turn. For each candidate, list the demand pooled before the line, the activities waiting for an order and the downstream time required.
Reject any location that misses the service promise. Next, compare a stable commodity, a configurable item and a highly uncertain fashion product using demand uncertainty, economies of scale and lead time. Avoid memorising push as bad or pull as good; write the condition that gives each logic value. Finish each practice with one failure mode on either side of the chosen boundary.
A complete recommendation names the operation, the generic stock or capacity held before it, the customer-specific work after it and the measurement that would reveal the boundary needs to move.
Working through Push, Pull and Supply Chain Integration in LGT5015? Sia is AskSia’s AI Management tutor — ask any LGT5015 Push, Pull and Supply Chain Integration question and get a clear, step-by-step explanation grounded in how LGT5015 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
