If I plan a closed-loop supply chain with one forecast, I miss the main risk: returns do not come back on a fixed schedule, in a fixed volume, or in a fixed condition.

I use scenario modeling to test demand, return timing, return volume, product condition, and recovery path before those changes hit cost, margin, service, and emissions. In simple terms, it helps me see where the network breaks, where recovery pays off, and where added capacity may justify its cost.

Here’s the short version:

• I need one shared data base for forward flow and reverse flow.

• I test baseline, growth, downturn, high-return, and disruption cases.

• I compare reuse, repair, remanufacture, recycle, and disposal.

• I read results through total cost to serve, margin, facility loading, circularity rate, and CO2e.

• I use outputs in S&OP, inventory buffers, capacity planning, and facility decisions.

A few numbers from the article frame the issue fast:

• Promotional demand spikes can lead to return surges 30 to 90 days later

• Direct reuse can recover up to 65% of value

• Repair/refurbish can recover 60% to 80%

• Remanufacturing can recover 40% to 60%

• High-return cases can push logistics cost up by 15% to 20%

• High-recovery setups can move circularity above 60%

Stef Lemmens (Eramus Uni.): Closed-Loop Supply Chains and Circular Business models

Quick comparison

What I take from the article is simple: closed-loop planning works better when I model uncertainty up front, compare recovery choices side by side, and use the results to guide inventory, capacity, and investment decisions instead of reacting after returns pile up.

Input Data: Building the Model on Reliable Forward and Reverse Flow Data

Build the model on a shared baseline of forward and reverse flow data. When inputs are missing, teams end up filling the gaps with assumptions, and those assumptions can shift the results in a big way. At a minimum, the data set should cover forward demand, reverse returns, transportation, inventory, emissions and energy, and the planning calendar. Together, these inputs set the baseline for the range of future states the model will test.

These inputs form the starting point for testing demand shifts, return spikes, and recovery choices.

Forward Flow Inputs: Demand, Capacity, Lead Times, and Transportation

Start with the data that grounds demand, capacity, and logistics decisions. That includes demand history and forecasts by product and region, production capacity at each facility, supplier lead times, and lane-level freight costs in $/mile. Just as important, teams should line up every input to the same planning calendar. If demand sits in weekly buckets but returns sit in monthly ones, comparisons get messy fast. A single weekly or monthly structure keeps demand, returns, and costs on the same footing.

Reverse Flow Inputs: Returns, Quality Grades, Collection, and Handling Costs

Next comes the return data, which shapes what can be recovered and how quickly it can move through the network. Teams need return rates by product line and region, return timing, and quality grades A–F so each unit can be routed to the right recovery path. Collection network data fills in the rest: pickup locations, routing distances in miles, pickup frequency, and handling costs per unit in U.S. dollars.

Cost, Carbon, and Data Quality Assumptions

The model also needs unit costs tied to transportation, handling, inventory carrying, recycling, and disposal. Carbon factors - emissions per mile and energy consumption - should sit next to those cost inputs so the model can report on cost, service, emissions, and disposal exposure in one view.

When source data is thin, planners can use stochastic modeling to reflect uncertainty in the timing and quantity of product returns [1]. Small-scale pilots in selected regions or product lines can also help test assumptions before the model is rolled out more broadly [1]. Spell out each assumption clearly, and flag any input with low confidence. That extra honesty up front can save a lot of trouble later.

Designing Scenarios: Demand Shifts, Return Flows, and Recovery Paths

Once the input data is solid, the next move is to turn it into a set of working scenarios. The point isn’t to model every future you can imagine. It’s to test the cases most likely to change network decisions, especially around collection capacity, recovery routing, and inventory planning. Start with demand and return timing. Then add product condition and recovery limits on top.

Demand and Return Scenarios Across Time

A useful scenario set begins with a baseline and then adds growth and downturn cases. After that, planners should vary demand, return rates, and product condition together, because those factors rarely move in isolation.

Monthly scenarios work well here. They line up demand, collection, sorting, and remanufacturing capacity on the same planning cadence. That matters because demand spikes from promotions often show up later as return surges. The sales bump comes first; the return wave follows. Collection and sorting capacity need enough room to absorb that delay.

Return participation can also swing hard when incentives change [2]. That timing issue becomes much more serious once returned items reach the recovery decision point.

Recovery Paths: Reuse, Repair, Remanufacture, Recycle, or Dispose

Return volume only tells part of the story. Product condition does far more than fill a column in a dataset. It shapes the economics of each recovery path.

Quality grade sets the range of feasible recovery options and the cost to process them. That’s why scenarios should test how results change when the quality mix shifts. If a larger share of returns comes back in lower condition, remanufacturing yield drops, processing time goes up, and recovered value shrinks.

The model should also account for the threshold points that change yield, cost, and recovered value. Those breakpoints often drive decisions more than average return volume does.

Scenario Drivers That Shape the Planning Set

Instead of trying to map every possible future, focus on the few drivers that change decisions the most.

Treat these drivers as decision triggers. Each one changes cost, service, and recovery outcomes.

Evaluating Tradeoffs: Cost, Service, Resilience, and Circularity

Closed-Loop Recovery Options: Cost, Value & Emissions Compared

Once the scenarios are set, the next job is simple in theory and hard in practice: compare them using the metrics that drive actual decisions. A good scenario model makes the tradeoffs visible across cost, service, emissions, resilience, and circularity. That matters because most teams don’t win by chasing one metric in isolation. They win by finding the right balance.

Comparing Recovery Options and Total Cost Outcomes

Use the scenario model to test how each recovery path changes total cost, emissions, and service under different return mixes. Direct reuse tends to deliver the most value and the lowest emissions when product condition allows it. Move further down the recovery hierarchy toward recycling and disposal, and the picture changes fast: value recovery falls while emissions intensity goes up.

The table below shows those differences side by side.

These comparisons summarize the cost, value recovery, lead time, and emissions tradeoffs across recovery options. [1]

Remanufacturing deserves a closer look. On a per-unit basis, it can seem costly and slow. But scenario work often shows a different story once you measure it against total cost to serve. In the right case, recovered value can offset the added cost and longer lead time. Life-cycle assessment can also put numbers around the carbon and energy savings of recycling compared with new production. [1]

Reading Scenario Results for Executive Decisions

To turn scenario outputs into decisions, compare each case across total cost to serve, margin, emissions, facility loading, and circularity rate.

These scenario comparisons show how cost, margin, emissions, and circularity can move together - or pull against each other. [1]

The High Recovery Capacity scenario is a good example. It may come with higher fixed costs up front, yet the longer-term margin lift and circularity gains can change the business case. Scenario modeling gives teams a way to test that investment with numbers instead of gut feel. Facility loading adds another layer, showing where spikes in returns will put pressure on sorting and repair capacity. [1]

Those results then feed S&OP, capital planning, and circularity governance.

Using Model Outputs in Planning, Governance, and Circular Strategy

Scenario outputs start to matter when teams use them to make day-to-day and long-range decisions. Once those outputs plug into S&OP, capital planning, and governance, they stop being analysis on a slide and start shaping what the business does next. The same set of results can guide operations, finance, and sustainability oversight at the same time.

How Teams Apply Outputs in S&OP and Investment Planning

One model can support three core decisions: inventory buffers, bottleneck detection, and facility location. That matters because these choices are linked. A spike in returns, for example, can strain labor, transport, and recovery capacity all at once.

In S&OP, high-return scenarios can act like an early warning signal. Teams can adjust inventory, labor, and recovery capacity before the network starts to tighten. The same scenarios can also reset labor plans, transport flows, and recovery schedules before constraints hit.

This is where scenario work earns its keep. Instead of reacting after backlogs build, planners can see pressure coming and make calmer, better-timed moves.

Linking Closed-Loop Scenarios to Circular Economy Metrics and Regulatory Readiness

Once teams make operational choices, they can reuse the same scenarios to test long-range circular strategy. That gives leaders one decision set for comparing cost, service, resilience, and circularity, rather than treating each topic as a separate workstream.

The spread between scenarios helps teams stage investment with more discipline. It also makes it easier to test policy exposure before rules, reporting demands, or market pressure force a rushed response.

Conclusion: What Good Scenario Modeling Delivers

Good scenario modeling brings bottlenecks into view, shows where inventory buffers need to change, and turns circular economy commitments into quantified choices that teams can test. Council Fire helps turn scenario outputs into phased action plans, investment roadmaps, and measurable circular supply chain outcomes.

FAQs

What data do I need first?

Start with a material flow analysis that covers the full supply chain. Map each stage - procurement, manufacturing, distribution, and reverse flows - so you can track material inputs, process steps, waste outputs, and emissions.

Use production records, waste audits, and trade statistics to build a clear baseline. That baseline shows where material slips through the cracks, where waste builds up, and where recovery may return the most value.

How do return conditions change recovery decisions?

Return conditions shape recovery decisions because an item’s condition sets both its value and the best next step. After triage and quality assessment, items in better shape can go to remanufacturing or refurbishment. Damaged or nonfunctional products, on the other hand, are sent to recycling, parts recovery, or disposal.

Return flows don’t arrive in a neat, predictable stream. They vary by product type, damage level, timing, and cause of return. That’s why fast assessment matters. The longer items sit without a clear decision, the more value slips away.

Tools like machine vision, sensors, and AI can help speed up categorization, cut manual inspection costs, and route each item to the recovery channel that makes the most sense from both an economic and environmental standpoint.

How do teams use scenario outputs in planning?

Teams use scenario outputs to turn messy, complex data into plans they can actually act on. Instead of guessing, they compare options - like shifts in recycling rates, material swaps, or product design changes - to see which path best balances financial targets with sustainability goals.

That side-by-side view makes decision-making much clearer. It helps teams find bottlenecks, improve collection routes, pick better facility locations, tighten logistics, and get stakeholders on the same page around practical, scalable circular economy plans.

Related Blog Posts

• Current Practices in Closed-Loop Supply Chains

• How to Design a Circular Supply Chain Roadmap for Corporations

• How to Design a Circular Supply Chain Roadmap for NGOs & Nonprofits

• How to Design a Circular Supply Chain Roadmap for Maritime & Logistics Companies