Refund vs replacement formula, inputs, and assumptions
Last updated: 2026-07-31
Written and reviewed by Seller Profit Guard Editorial Team.
Start from one original order contribution at a defined evidence date. Calculate refund loss from customer cash returned, return shipping, and processing minus verified credits and recovered inventory. Calculate replacement loss from new product, shipping, packaging, and processing minus verified recovery or buyer payment.
Type original order economics
Specify control 1: Declare quantity, price, buyer shipping, product cost, original outbound shipping, original fees, transaction state, currency, and evidence month. This formula role types each order, refund, replacement, recovery, target, and authority boundary. Record case alias, source state, full-precision value, display value, currency, responsibility, reviewer, and review date.
Test the nearest valid boundary and counterexample. State how a mismatch changes a typed and reproducible resolution comparison, which evidence resolves it, who owns correction, and whether the packet must be blocked, reviewed, limited, superseded, or restored.
Type merchandise and shipping refund
Specify control 2: Separate original merchandise returned to the buyer from original shipping returned; cap each at its matching order amount. This formula role types each order, refund, replacement, recovery, target, and authority boundary. Record case alias, source state, full-precision value, display value, currency, responsibility, reviewer, and review date.
Test the nearest valid boundary and counterexample. State how a mismatch changes a typed and reproducible resolution comparison, which evidence resolves it, who owns correction, and whether the packet must be blocked, reviewed, limited, superseded, or restored.
Type refund-path costs
Specify control 3: Record seller-paid return shipping plus inspection, support, restocking, repair, disposal, and processing without duplicating original cost. This formula role types each order, refund, replacement, recovery, target, and authority boundary. Record case alias, source state, full-precision value, display value, currency, responsibility, reviewer, and review date.
Test the nearest valid boundary and counterexample. State how a mismatch changes a typed and reproducible resolution comparison, which evidence resolves it, who owns correction, and whether the packet must be blocked, reviewed, limited, superseded, or restored.
Type refund-path recovery
Specify control 4: Separate verified fee credit, recovered inventory value, carrier or platform recovery, supplier credit, and other evidence-backed amounts. This formula role types each order, refund, replacement, recovery, target, and authority boundary. Record case alias, source state, full-precision value, display value, currency, responsibility, reviewer, and review date.
Test the nearest valid boundary and counterexample. State how a mismatch changes a typed and reproducible resolution comparison, which evidence resolves it, who owns correction, and whether the packet must be blocked, reviewed, limited, superseded, or restored.
Type replacement fulfillment
Specify control 5: Record replacement quantity, current unit cost, outbound shipping, packaging, handling, and case-processing work. This formula role types each order, refund, replacement, recovery, target, and authority boundary. Record case alias, source state, full-precision value, display value, currency, responsibility, reviewer, and review date.
Test the nearest valid boundary and counterexample. State how a mismatch changes a typed and reproducible resolution comparison, which evidence resolves it, who owns correction, and whether the packet must be blocked, reviewed, limited, superseded, or restored.
Type replacement recovery
Specify control 6: Separate verified claim, insurer or platform coverage, supplier credit, and additional buyer payment from speculative recovery. This formula role types each order, refund, replacement, recovery, target, and authority boundary. Record case alias, source state, full-precision value, display value, currency, responsibility, reviewer, and review date.
Test the nearest valid boundary and counterexample. State how a mismatch changes a typed and reproducible resolution comparison, which evidence resolves it, who owns correction, and whether the packet must be blocked, reviewed, limited, superseded, or restored.
Derive both losses and contributions
Specify control 7: Subtract each incremental loss from original contribution and retain full precision, display precision, currency, source state, and version. This formula role types each order, refund, replacement, recovery, target, and authority boundary. Record case alias, source state, full-precision value, display value, currency, responsibility, reviewer, and review date.
Test the nearest valid boundary and counterexample. State how a mismatch changes a typed and reproducible resolution comparison, which evidence resolves it, who owns correction, and whether the packet must be blocked, reviewed, limited, superseded, or restored.
Type target and precedence
Specify control 8: Block invalid evidence before tie or target Review; keep remedy authority, law, policy, platform process, coverage, and customer agreement outside the formula. This formula role types each order, refund, replacement, recovery, target, and authority boundary. Record case alias, source state, full-precision value, display value, currency, responsibility, reviewer, and review date.
Test the nearest valid boundary and counterexample. State how a mismatch changes a typed and reproducible resolution comparison, which evidence resolves it, who owns correction, and whether the packet must be blocked, reviewed, limited, superseded, or restored.
Use the resolution formula specification with one protected case packet
Open the calculator only after the resolution formula specification identifies order alias, original economics, refund cash, return cost, processing, credits, recovered inventory, replacement quantity and costs, recovery, buyer payment, absolute target, lower-loss-share maximum, scenario-difference minimum, source review date, nine evidence confirmations, currency, policy and case context, month, complete scope, and issues.
Save original contribution, both incremental losses, both remaining contributions, lower scenario, absolute difference, normalized difference rate, lower-loss share, threshold headroom, decision, and issues at full precision. Preserve every version when policy, posting, inspection, claim, or invoice evidence changes.
Separate cost review from remedy authority before a typed and reproducible resolution comparison
Use the model to compare declared seller costs only. Route buyer rights, shop obligations, platform eligibility, case instructions, agreement, consumer law, coverage, timing, and actual remedy to the authorized evidence and decision process.
A lower modeled loss never permits an inaccurate refund, unsupported refusal, delayed obligation, unwanted replacement, or customer-facing promise.
Version expected, approved, and received recovery
Keep fee credits, inventory recovery, carrier claims, insurance, platform coverage, supplier credits, and buyer payments in separate evidence states with amount, currency, source, date, owner, and dispute status.
Expected recovery is not received cash. Unknown, denied, expired, disputed, or missing recovery is not zero and cannot silently retain Ready.
Protect buyer, message, payment, and case records
Public examples are synthetic. Keep names, addresses, emails, messages, tracking, case records, payment data, claims, accounts, invoices, credentials, photos, and raw orders outside the resolution formula specification.
Use aliases, aggregates, redacted pointers, access controls, and approved fixtures. An authorized reviewer should reproduce totals without public personal data.
Release, observe, correct, and restore the resolution asset
Before release, preserve narrow local and remote backups and a rollback identifier. Run typecheck, focused and full tests, integration, build, content and duplicate audits, SEO, routes, sources, images, links, mobile, keyboard, privacy, and restore checks.
After release, verify status, canonical, indexability, schema, answer blocks, images, hub discovery, strict 404, sitemap policy, events, and production scenarios. Record Day 0/7/14/28 evidence and restore on formula, privacy, source, accessibility, routing, content, or health regression.
Build a field dictionary
Store definition, sign, unit, source role, grain, null policy, effective date, privacy class, and owner for every input.
Reject ambiguous refund, recovery, replacement, and fee fields that hide several processes.
Build equation identities
Recompute original contribution, total customer refund, total refund recovery, refund loss, replacement cost, replacement recovery, replacement loss, difference, and headroom.
Require every monetary line to appear once.
Build a boundary truth table
Test zero and positive quantities, caps, negative costs, target equality, exact tie, currency, context, month, scope, and conflicts.
Store expected Block, Review, or Ready plus the exact first issue.
Data type
Prove money, quantity, currency, period, text, and issue-list handling. Deep check 1 stores case and order aliases, source versions, protected pointers, full-precision transformations, output, decision, authority, reviewer, expiry, and correction route. Another reviewer must not guess refund scope, recovery state, replacement grain, or formula sign.
Find the closest counterexample and state why it invalidates or narrows a typed and reproducible resolution comparison. Preserve competing policy, agreement, platform, payment, return, inventory, replacement, claim, fee, target, or scope evidence as named scenarios rather than blending uncertainty.
Formula sign
Prove cash returned and costs add while verified recovery subtracts. Deep check 2 stores case and order aliases, source versions, protected pointers, full-precision transformations, output, decision, authority, reviewer, expiry, and correction route. Another reviewer must not guess refund scope, recovery state, replacement grain, or formula sign.
Find the closest counterexample and state why it invalidates or narrows a typed and reproducible resolution comparison. Preserve competing policy, agreement, platform, payment, return, inventory, replacement, claim, fee, target, or scope evidence as named scenarios rather than blending uncertainty.
Sunk cost
Separate original cost from incremental resolution cost. Deep check 3 stores case and order aliases, source versions, protected pointers, full-precision transformations, output, decision, authority, reviewer, expiry, and correction route. Another reviewer must not guess refund scope, recovery state, replacement grain, or formula sign.
Find the closest counterexample and state why it invalidates or narrows a typed and reproducible resolution comparison. Preserve competing policy, agreement, platform, payment, return, inventory, replacement, claim, fee, target, or scope evidence as named scenarios rather than blending uncertainty.
Precision
Calculate before rounding. Deep check 4 stores case and order aliases, source versions, protected pointers, full-precision transformations, output, decision, authority, reviewer, expiry, and correction route. Another reviewer must not guess refund scope, recovery state, replacement grain, or formula sign.
Find the closest counterexample and state why it invalidates or narrows a typed and reproducible resolution comparison. Preserve competing policy, agreement, platform, payment, return, inventory, replacement, claim, fee, target, or scope evidence as named scenarios rather than blending uncertainty.
Authority
Prove the calculator cannot select the customer remedy. Deep check 5 stores case and order aliases, source versions, protected pointers, full-precision transformations, output, decision, authority, reviewer, expiry, and correction route. Another reviewer must not guess refund scope, recovery state, replacement grain, or formula sign.
Find the closest counterexample and state why it invalidates or narrows a typed and reproducible resolution comparison. Preserve competing policy, agreement, platform, payment, return, inventory, replacement, claim, fee, target, or scope evidence as named scenarios rather than blending uncertainty.
Sources and further reading
- Seller Profit Guard methodology: Comparable case evidence, deterministic scenarios, validation, correction, release, and rollback.
- Seller Profit Guard data privacy: Local-first boundaries for buyer, message, tracking, case, claim, payment, and raw order data.
- Etsy Help: Refunds, Returns, and Exchanges for Sellers: Official Etsy context for seller policies, agreements, replacement proof, and Purchase Protection boundaries.
- Etsy Help: Issue a Full or Partial Refund: Official Etsy refund workflow and fee-credit context.
- Etsy Help: Help a Buyer With a Return: Official Etsy return coordination, label responsibility, receipt, and refund timing.
- Shopify Help: Refunding Orders: Official Shopify full and partial refund, shipping-refund, payment-method, permission, restocking, fee-treatment, and irreversible-action considerations.
Related Seller Profit Guard tools
- Refund vs Replacement Calculator: Run the browser-local two-resolution cost comparison.
- Return Window Loss Estimator: Model expected return loss across an order population.
- Refund Fee Reconciliation Calculator: Reconcile actual refund and fee-credit records after processing.
- Shipping Zone Margin Calculator: Test replacement postage exposure separately.
- Methodology: Review evidence, calculation, privacy, testing, correction, and rollback.
- Data Privacy: Keep buyer, message, tracking, case, payment, and raw-order data protected.
- Refund vs Replacement Worked Example: Continue with a distinct resolution formula, example, shipping stress, source, threshold, comparison, routine, interpretation, or audit task.
- Refund vs Replacement With High Shipping: Continue with a distinct resolution formula, example, shipping stress, source, threshold, comparison, routine, interpretation, or audit task.
- Refund vs Replacement Calculator Mistakes: Continue with a distinct resolution formula, example, shipping stress, source, threshold, comparison, routine, interpretation, or audit task.
- Refund vs Replacement Data Sources: Continue with a distinct resolution formula, example, shipping stress, source, threshold, comparison, routine, interpretation, or audit task.
- Refund vs Replacement Decision Thresholds: Continue with a distinct resolution formula, example, shipping stress, source, threshold, comparison, routine, interpretation, or audit task.
Next step: Open the Refund vs Replacement 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.