Restocking Fee Calculator: Apply the Policy the Same Way Every Time

The problem this kills

Two customers return the same product in the same shape, three days apart — and somehow one gets charged a 15% restocking fee and the other gets it waived. A CSR eyeballs the policy PDF, does the math in their head, fat-fingers the percentage, and applies it to the wrong subtotal. AR finds out weeks later when the customer disputes the credit, and now you're refunding the difference and apologizing.

Restocking fees are supposed to be simple: a percentage that depends on why the item came back, what condition it's in, and how long the customer took. But when that lives in a policy document and a calculator app, every return becomes a judgment call, and judgment calls drift. The result is inconsistent fees, frustrated customers, chargebacks, and a returns team that dreads the math. The fix isn't a stricter memo — it's a tool that reads the fee straight off your policy table the same way every single time, and forces a human to sign off before anything hits the credit. You don't need to be a developer to build it.

What you'll build

A simple internal web tool for your returns team, CSRs, and AR. You import your restocking-fee policy as a table (fee % by reason, condition, and time window). For each return, you enter the details — order/RMA, item value, return reason, condition, and how many days since delivery — and the tool computes the fee straight from the policy, shows exactly which rule it matched and why, and previews the net credit. Then an agent approves the fee or records a waiver (with a required reason) — and only after that approval is the credit number finalized and logged. Every return ends with a clean record: the inputs, the rule that applied, the fee, any waiver and its reason, and the net credit, ready to export to your refund/credit process.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — your current returns process and who owns it, the systems and spreadsheets you use, the exact way your policy is structured (your real reasons, condition grades, and time windows), how you name orders and RMAs, your typical and peak return volumes, who's allowed to waive a fee, and your messy edge cases. It reads a short spec back to you for a thumbs-up, then builds the tool around your policy instead of a generic template. From there it walks the agent through the data model, the policy import, the fee-calculation engine, the approve/waive gate, the net-credit math, and the export and log. Every step ends with a ready-to-copy prompt.

The governance it includes (this is the point)

This isn't a toy calculator. The plan builds in the controls a real returns and AR function needs: login so only your team can use it, row-level security so people only see their own organization's returns, a complete audit trail of every calculation, approval, and waiver (who, what, when, and the reason), a hard human-approval gate so no fee is applied to a credit until a person signs off, and a duplicate guard keyed on RMA + fee calculation so the same return can't be processed and credited twice. Every waiver is logged with a reason — so when a customer or auditor asks "why was this fee dropped?", you have the answer in one click.

Who it's for

Returns teams, customer-service reps, and accounts-receivable staff who apply restocking fees and are tired of inconsistency, disputes, and after-the-fact corrections. If you can describe your fee policy as "this percentage for this reason, in this condition, within this many days," you can build this.

You've got this — open the plan, paste the first prompt, and you'll be calculating your first consistent, signed-off restocking fee this afternoon.