Customer-Order Decoupling Point Map¶
Diagram — instantiates Push-Pull Decoupling Point Design
A one-page picture of the flow that marks the exact stage where customer-order information takes over from forecast.
The Customer-Order Decoupling Point Map lays the end-to-end flow out as a left-to-right sequence of stages and draws a single vertical mark: the stage where the specific customer order first begins to govern the work. Everything to the left of the mark runs on forecast, aggregation, and standardization; everything to the right waits for the real order; the buffer of readiness sits on the mark itself. Its defining idea is that it is a positioning diagram — a shared picture that turns the abstract question "where does push become pull?" into a spot on a wall that a roomful of people can point at and argue about. It depicts and locates; it does not measure the real world and it does not decide what the boundary should be.
Example¶
A mortgage lender maps its process to settle a recurring dispute about where "the order" really starts. On the wall go the stages: rate-sheet and program preparation, lead intake, application, document collection, underwriting, conditions and approval, closing, funding. Left to right, the team shades the push region — rate sheets, standard document checklists, pre-underwriting program rules, and a staffed pool of underwriter capacity are all prepared ahead of any individual borrower — and the pull region, where a specific applicant's file drives the work. Drawing it exposes the surprise: operations had been talking as if the boundary was the rate lock, but the applicant's information actually starts governing much earlier, at application. The buffer sitting on the mark is not stock at all — it is reserved underwriter capacity plus prevalidated program rules. Once the picture exists, sales, ops, and compliance can finally negotiate one boundary instead of each assuming a different one.
How it works¶
- Choose the flow granularity. Enough stages to locate the boundary honestly, few enough to fit on one page and stay legible in a meeting.
- Sequence the stages with their handoffs. Material, information, and approval handoffs all count — in a service flow the decisive handoff is usually informational.
- Shade the two regimes and place the mark. Colour the forecast-driven region and the order-driven region, then draw the boundary and set the buffer symbol on it as the visible marker of the point.
- Overlay current versus proposed. The map's most useful form shows where the point sits today and where a redesign would move it, so the change is a picture rather than a memo.
Tuning parameters¶
- Stage granularity — coarse blocks versus fine steps. Finer maps locate the boundary more precisely but get cluttered and harder to align a group around.
- Single-point versus annotated multi-segment — one mark for the whole flow, or several marks for different product or demand classes. More marks capture reality but blur into a segmentation exercise the map is not meant to own.
- Annotation depth — bare stages, or stages tagged with lead time, ownership, and push/pull rationale. Richer annotation informs better but slows the drawing and dates faster.
- Scope — one product line versus an entire network. A wider scope reveals interactions but loses the resolution needed to place any single point well.
When it helps, and when it misleads¶
The map's strength is alignment: it makes an implicit, contested boundary explicit and shared, and it gives the concept its proper name — the customer order decoupling point[n1] — so functions stop optimizing private versions of it. As a first-encounter artifact it is unbeatable, because a boundary you cannot point to cannot be governed.
Its danger is that a diagram is only a depiction. A crisp, confident map of where the point should sit says nothing about where it actually is, and a map left on the wall quietly goes stale as the real flow drifts around it. The classic misuse is treating the act of drawing the boundary as if it moved the boundary — declaring victory at the whiteboard while technicians, planners, and sales keep relocating the point in daily practice. The guarding discipline is to treat the map strictly as design intent and pair it with independent verification of the real point, rather than mistaking the picture for the territory.
How it implements the components¶
flow_stage_map— the diagram is the staged flow, named end to end from first commitment through fulfillment; it is the canonical rendering of that component.decoupling_buffer— the map places and names the buffer's position on the flow, drawing it as the visible marker where forecast-push meets order-pull.
The map draws the intended boundary but does not measure whether reality matches it — the boundary_performance_dashboard that reveals the true point belongs to its nearest twin, Order-Penetration Point Audit — and it neither sizes nor refills the stock it marks; the buffer_replenishment_rule is the Kanban or Reorder Replenishment Rule's. The map draws where the point should be; the audit measures where it actually is.
Related¶
- Instantiates: Push-Pull Decoupling Point Design — the map is the shared design artifact on which the boundary is placed and negotiated.
- Sibling mechanisms: Configuration Cell or Final Assembly Cell · Demand Segmentation ABC/XYZ Matrix · Kanban or Reorder Replenishment Rule · Lead-Time / Inventory Trade-off Curve · Make-to-Stock / Make-to-Order Split Policy · Order-Penetration Point Audit · Postponement Strategy Matrix · Sales and Operations Boundary Review · Semi-Finished Goods Buffer
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Customer-Order Decoupling Point Map operates as a non-executable information artifact that externalizes static or prospective structure because it a one-page picture of the flow that marks the exact stage where customer-order information takes over from forecast.
Independent corroboration: The frozen evidence defines Customer-Order Decoupling Point Map as 'A one-page picture of the flow that marks the exact stage where customer-order information takes over from forecast', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Logistics & Supply Chain Management
Origin pattern: Single lineage
Present-day reach: Specialized
Rationale: Supply-chain management cohered the customer-order decoupling point as the mapped boundary between forecast-driven push stages and order-driven pull stages.
Related originating lineages:
- Operations Research — Inventory and flow modeling supplied buffer-location and postponement analysis around the boundary.
Review resolution: Supply-chain management cohered the customer-order decoupling point as the mapped boundary between forecast-driven push stages and order-driven pull stages.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Customer order decoupling point (CODP), also called the order penetration point — the stage in a flow at which a specific customer order first drives the work, separating the upstream forecast-driven portion from the downstream order-driven portion. Marking it is exactly what this map does. ↩