The Physical Return Route Evidence Framework

PHYSICAL RETURN ROUTE REVIEW — original Growthcraft synthesis
Decision owner / operations owner / data owner / reviewer:
Anonymous product-condition segment, route and version:
Currency, valuation horizon, extract cutoff and cost-source version:

1. ELIGIBILITY BEFORE ECONOMICS
Customer rights / contractual / safety constraints reviewed by qualified owner:
Same refund and customer entitlement in both routes? Evidence:
Every modelled item physically returns in the return scenario? If not, use another model:
Common costs excluded; differences not represented by the calculator:

2. RECONCILE THE ITEM SPINE
One item decision ID; quantity split into separate units:
Closed dispositions / open / unknown / missing-cost items:
Recovered-state definition and denominator:
Yield source, observation horizon and missingness:
R: net recovered value after downstream selling costs:
S: net unrecovered salvage or negative disposal cost:
L: inbound logistics; H: intake/inspection; F: extra fixed route cost:
Cost allocation map; each cost in exactly one bucket:

3. COMPARE AND STRESS
N items / assumed yield / calculator JSON reference:
Base incremental value and break-even yield:
Lower yield / lower value / higher cost scenarios (not confidence intervals):
Missing evidence that could reverse the sign:

4. BOUNDED HANDOFF
Hold / gather evidence / propose controlled operational pilot:
Customer-experience and abuse risks reviewed separately:
Owner, action, due date, stop condition and review horizon:
Actual receipts, inspection states and net proceeds needed for reconciliation:
No automated customer denial; no causal or company-profit conclusion.

A routing decision, not a returns-policy shortcut

This original framework is for D2C operators, growth leads and consumer startup teams asking whether recovering a physical product creates value after logistics. It compares physical return with a refund-without-return alternative that gives the customer the same refund. Use it to scope an internal operational review, not to determine who deserves a refund. Qualified owners must establish legal, contractual and safety constraints first.

The method is incremental: original sale revenue, original product acquisition cost and the common refund cancel between alternatives. It does not answer whether the initial sale was profitable, whether a channel should scale, or whether denying a return increases margin. Prerequisites are an item-level decision spine, explicit condition states, route-cost evidence and a defensible estimate of net disposition value.

Gate 1 — prove that the alternatives are comparable

The decision owner writes the two routes in full. In the synthetic comparison, every item either physically returns for inspection or remains with the customer, and the refund is identical. If a restocking charge, exchange offer, different refund timing or replacement item changes between routes, this simple model is incomplete. Record the missing difference instead of forcing it into a convenient field. Do not use it for hazardous items or mandatory product recalls without the relevant specialist process.

The operations owner fixes one route and one valuation horizon. Do not compare a domestic parcel cost with an international resale value and label the blend a market benchmark. Cross-border duties, currency conversion, product restrictions and disposal obligations need their own reviewed treatment. A common reporting currency does not make operational routes equivalent.

Gate 2 — separate inspection yield from payment status

The data owner defines recovered and unrecovered states before calculating a yield. A recovered item has the documented disposition expected to earn R, net of downstream selling costs. An unrecovered item earns S, which may be negative when disposal costs exceed salvage. Open inspections and missing-cost items remain visible; they are not silently called recovered or removed from the denominator.

Record every cost exactly once. Inbound transport belongs to L. Intake and inspection performed on every received item belong to H. Subsequent selling fees or refurbishment specific to a state are netted into R or S. Additional route setup belongs to F. Historical product cost is not another incremental outflow at this decision point, and restored inventory at book value is not cash proceeds.

Gate 3 — reproduce the synthetic decision

For 100 items, assume a 60% recovered yield, R = 30, S = −2, inbound cost 6, handling 4 and additional setup cost 200, all in EUR. Expected disposition value per item is 0.6 × 30 + 0.4 × (−2) = 17.20. Variable incremental value is 17.20 − 6 − 4 = 7.20. Total incremental value is 100 × 7.20 − 200 = 520, or 5.20 per item.

The tie occurs at (6 + 4 + 200/100 − (−2)) / (30 − (−2)) = 43.75% recovered yield. This is an algebraic hurdle, not a probability of success or a universal target. At 40% yield, the same scenario loses 120. At 60% yield but recovered value 20, it loses 80. These explicit sensitivities show why a positive base case is not approval.

The reviewer asks where 60% and 30 came from. If they came from only fast-closing inspections or unsold list prices, obtain representative evidence before acting. A matured item ledger and actual net sale proceeds are better evidence than a refund dashboard alone, but historical performance can still fail to predict a changed product mix.

Gate 4 — turn uncertainty into an owned next step

Choose hold, gather evidence or propose a bounded operational pilot. Name the missing evidence, owner, due date and condition that would change the decision. Monitor actual logistics costs, completed inspections, customer complaints and reconciled proceeds separately. A pilot design must not override customer rights. Review whether returns completion, support contact rates or abuse behaviour differ between alternatives; those effects are outside the calculator.

Reject shortcuts such as using gross resale price as R, treating a refund event as a received parcel, combining units and multi-item parcels without cost allocation, or spreading setup cost over an aspirational annual volume while evaluating a small first batch. The framework is an auditable handoff, not an automatic policy engine.

Sources and evidence boundary

Retrieved 28 September 2026. Shopify's 23 September shipping and duty analytics update motivates reviewing route-cost inputs after reporting changes; it does not validate this model. Stripe's refund documentation distinguishes refund states, including pending and failed. A refund record is not warehouse disposition evidence. No provider endorses this original synthesis, and no current provider prices or legal requirements are assumed.