Restocking decision: like-new versus damaged return
Last updated: 2026-07-31
Written and reviewed by Seller Profit Guard Editorial Team.
The like-new case yields USD 14.88 expected net restock recovery and beats its alternative by USD 11.88. The damaged stress case yields USD -14.87 and trails the alternative by USD 17.87. Condition-specific probability and processing—not the returned-item label alone—drive the difference.
Separate the grades
Do not compare by renaming one template; inspect and source each grade independently. The condition scenario comparison stores source, date, owner, SKU and condition grain, currency, evidence state, transformation, output, decision, and correction route so another reviewer can reproduce a condition-specific explanation of recovery variance.
Control 7.1 keeps buyer, address, email, message, tracking, payment, photo, case, return label, account, credential, and raw-order content outside the public page. Use aliases and protected evidence pointers.
Compare markdown
Like-new uses 10%; the damaged stress case uses 35%. The condition scenario comparison stores source, date, owner, SKU and condition grain, currency, evidence state, transformation, output, decision, and correction route so another reviewer can reproduce a condition-specific explanation of recovery variance.
Control 7.2 keeps buyer, address, email, message, tracking, payment, photo, case, return label, account, credential, and raw-order content outside the public page. Use aliases and protected evidence pointers.
Compare probability
Like-new uses 80%; the damaged case uses 30% within the same declared window. The condition scenario comparison stores source, date, owner, SKU and condition grain, currency, evidence state, transformation, output, decision, and correction route so another reviewer can reproduce a condition-specific explanation of recovery variance.
Control 7.3 keeps buyer, address, email, message, tracking, payment, photo, case, return label, account, credential, and raw-order content outside the public page. Use aliases and protected evidence pointers.
Compare conditional proceeds
Price, fee, fixed charge, and shipping subsidy flow through each grade. The condition scenario comparison stores source, date, owner, SKU and condition grain, currency, evidence state, transformation, output, decision, and correction route so another reviewer can reproduce a condition-specific explanation of recovery variance.
Control 7.4 keeps buyer, address, email, message, tracking, payment, photo, case, return label, account, credential, and raw-order content outside the public page. Use aliases and protected evidence pointers.
Compare labor
The damaged case requires 45 minutes rather than 15. The condition scenario comparison stores source, date, owner, SKU and condition grain, currency, evidence state, transformation, output, decision, and correction route so another reviewer can reproduce a condition-specific explanation of recovery variance.
Control 7.5 keeps buyer, address, email, message, tracking, payment, photo, case, return label, account, credential, and raw-order content outside the public page. Use aliases and protected evidence pointers.
Compare supplies
Cleaning, repair, and packaging consumption differs by condition. The condition scenario comparison stores source, date, owner, SKU and condition grain, currency, evidence state, transformation, output, decision, and correction route so another reviewer can reproduce a condition-specific explanation of recovery variance.
Control 7.6 keeps buyer, address, email, message, tracking, payment, photo, case, return label, account, credential, and raw-order content outside the public page. Use aliases and protected evidence pointers.
Compare storage
Lower-demand or restricted inventory may stay longer and cost more. The condition scenario comparison stores source, date, owner, SKU and condition grain, currency, evidence state, transformation, output, decision, and correction route so another reviewer can reproduce a condition-specific explanation of recovery variance.
Control 7.7 keeps buyer, address, email, message, tracking, payment, photo, case, return label, account, credential, and raw-order content outside the public page. Use aliases and protected evidence pointers.
Compare alternatives
Each grade needs one verified opportunity-cost route. The condition scenario comparison stores source, date, owner, SKU and condition grain, currency, evidence state, transformation, output, decision, and correction route so another reviewer can reproduce a condition-specific explanation of recovery variance.
Control 7.8 keeps buyer, address, email, message, tracking, payment, photo, case, return label, account, credential, and raw-order content outside the public page. Use aliases and protected evidence pointers.
Compare authority
Neither scenario authorizes resale without safety, legal, platform, and disclosure controls. The condition scenario comparison stores source, date, owner, SKU and condition grain, currency, evidence state, transformation, output, decision, and correction route so another reviewer can reproduce a condition-specific explanation of recovery variance.
Control 7.9 keeps buyer, address, email, message, tracking, payment, photo, case, return label, account, credential, and raw-order content outside the public page. Use aliases and protected evidence pointers.
Validate the condition scenario comparison before calculation
Check finite values, whole returned quantity, markdown below 100%, probability no more than 100%, fee below 100%, material-advantage and process-cost thresholds, currency, context, evidence month, real source-review date, typed scope, confirmations, and declared conflicts. Invalid structure Blocks a condition-specific explanation of recovery variance.
Unknown condition, safety, price, probability, labor, storage, failure, or alternative evidence is not silent zero. Inspect, create a named conservative scenario, or stop.
Apply materiality and process-cost gates to a condition-specific explanation of recovery variance
Restocking must beat the alternative by the seller-entered percentage of the larger absolute recovery result. Labor, supplies, and storage must also remain within the entered share of expected recovery before processing.
These are seller-owned operating thresholds, not marketplace, legal, accounting, statistical-confidence, or product-safety rules. Version the owner, rationale, effective date, product class, and correction history.
Confirm the dated evidence packet for a condition-specific explanation of recovery variance
Require explicit yes confirmations for returned condition, safety and resale eligibility, comparable price and probability, fees and shipping, labor and supplies, storage window, alternative recovery, source lineage, and planning boundaries.
Record a real YYYY-MM-DD review date. A plausible narrative without owner confirmation is incomplete evidence and Blocks the result.
Keep safety, resale authority, and customer remedy outside a condition-specific explanation of recovery variance
The model compares expected seller recovery after return receipt. It does not decide buyer rights, refund timing, safety, hygiene, recall status, legal resale eligibility, platform inventory state, warranty, disclosure, tax, or accounting treatment.
Route each operational decision to the current authorized policy, professional, manufacturer, platform, legal, inventory, or finance owner.
Reconcile predicted and realized recovery
After sale or exit, record actual condition, price, fee, shipping, time, labor, supplies, storage, failure, alternative, and correction without exposing buyer data.
Compare complete privacy-safe cohorts with predictions. Keep unsold, delayed, disposed, donated, and reworked items so selection bias does not inflate probability.
Protect return, buyer, and inventory evidence
Public examples are synthetic. Keep names, addresses, emails, messages, tracking, payments, photos, cases, return labels, receipts, inventory accounts, credentials, and raw orders outside the condition scenario comparison.
Apply authorized access, retention, correction, deletion, and incident-response controls. Public content may describe evidence classes without revealing evidence content.
Release, observe, correct, and restore the condition scenario comparison
Preserve narrow local and remote backups plus a rollback identifier. Run typecheck, focused and full tests, integration, build, content and duplicate audits, SEO, routes, images, links, mobile, keyboard, privacy, and restore checks.
After release, verify status, canonical, indexability, schema, answers, tool scenarios, assets, hub discovery, strict 404, sitemap policy, events, and Day 0/7/14/28 evidence. Restore on regression.
Hold channel constant where possible
A channel change introduces another variable requiring a separate comparison. Deep review 1 stores the counterexample, source version, full-precision inputs, expected and realized output, authority, reviewer, expiry, correction, and next action.
State what the evidence can and cannot prove about a condition-specific explanation of recovery variance. Keep competing condition, safety, price, probability, channel, fee, shipping, labor, storage, failure, alternative, currency, timing, or scope evidence as separate scenarios.
Report sample uncertainty
Probability and price evidence need counts, windows, exclusions, and drift. Deep review 2 stores the counterexample, source version, full-precision inputs, expected and realized output, authority, reviewer, expiry, correction, and next action.
State what the evidence can and cannot prove about a condition-specific explanation of recovery variance. Keep competing condition, safety, price, probability, channel, fee, shipping, labor, storage, failure, alternative, currency, timing, or scope evidence as separate scenarios.
Report failed outcomes
Do not omit unsold, disposed, donated, or reworked returns. Deep review 3 stores the counterexample, source version, full-precision inputs, expected and realized output, authority, reviewer, expiry, correction, and next action.
State what the evidence can and cannot prove about a condition-specific explanation of recovery variance. Keep competing condition, safety, price, probability, channel, fee, shipping, labor, storage, failure, alternative, currency, timing, or scope evidence as separate scenarios.
Report capacity effects
A profitable unit can still overload inspection or storage. Deep review 4 stores the counterexample, source version, full-precision inputs, expected and realized output, authority, reviewer, expiry, correction, and next action.
State what the evidence can and cannot prove about a condition-specific explanation of recovery variance. Keep competing condition, safety, price, probability, channel, fee, shipping, labor, storage, failure, alternative, currency, timing, or scope evidence as separate scenarios.
Report prevention signals
Repeated damaged returns create upstream work beyond inventory disposition. Deep review 5 stores the counterexample, source version, full-precision inputs, expected and realized output, authority, reviewer, expiry, correction, and next action.
State what the evidence can and cannot prove about a condition-specific explanation of recovery variance. Keep competing condition, safety, price, probability, channel, fee, shipping, labor, storage, failure, alternative, currency, timing, or scope evidence as separate scenarios.
Sources and further reading
- Seller Profit Guard methodology: Evidence versions, expected-value calculation, validation, privacy, correction, release, and rollback.
- Seller Profit Guard data privacy: Local-first boundaries for buyer, return, message, tracking, payment, photo, account, and raw-order data.
- Etsy Help: Help a Buyer With a Return: Official return coordination, receipt, label, responsibility, and refund timing context.
- Etsy Help: Refunds, Returns, and Exchanges for Sellers: Official seller-policy, buyer-agreement, legal, and Purchase Protection context.
- Shopify Help: Returns and exchanges: Official return receipt, inspection, refund, exchange, and return-rule context.
- Shopify Help: Adjust inventory quantities: Official distinction between return restock for resellable items and damaged inventory adjustments.
- U.S. CPSC: Stopping the Online Sale of Recalled Products: Official recall-search and recalled-product resale boundary for U.S. consumer products.
Related Seller Profit Guard tools
- Restocking Decision Calculator: Run the browser-local expected recovery comparison.
- Damaged Order Loss Calculator: Measure damage and coverage recovery separately.
- Refund vs Replacement Calculator: Compare customer-remedy paths separately.
- Return Window Loss Estimator: Estimate expected return loss across a wider population.
- Methodology: Review evidence, privacy, calculation, correction, release, and rollback.
- Data Privacy: Protect buyer, return, message, tracking, photo, payment, account, and raw-order data.
- Restocking Decision Formula and Inputs: Continue with a distinct formula, example, condition scenario, error, source, threshold, comparison, routine, interpretation, or audit task.
- Like-New Restocking Worked Example: Continue with a distinct formula, example, condition scenario, error, source, threshold, comparison, routine, interpretation, or audit task.
- Damaged Return Restocking Scenario: Continue with a distinct formula, example, condition scenario, error, source, threshold, comparison, routine, interpretation, or audit task.
- Restocking Decision Calculation Mistakes: Continue with a distinct formula, example, condition scenario, error, source, threshold, comparison, routine, interpretation, or audit task.
- Restocking Decision Data Sources: Continue with a distinct formula, example, condition scenario, error, source, threshold, comparison, routine, interpretation, or audit task.
Next step: Open the Restocking Decision Calculator.
This is operational planning help, not tax, accounting, legal, financial, or platform-policy advice. Review the Terms and disclaimer, and verify current platform rules and fee assumptions before changing prices.