Build or Buy Returns Grading and Restock on Shopify?
Returns grading and restock-to-sellable is a CUSTOMIZE on Shopify: keep the returns portal you already pay for and build the grading layer none of them ship. Loop, Narvar and Happy Returns run the RMA, the label and the refund, and not one grades physical condition or routes a unit to refurb or liquidation. ReturnPro's listing does, at $79.99/month on eCommerce Lite (verified Sep 2026), with 1 review behind it.
Your profile — see how the verdict shifts
- Confidence
- High — Checked the three returns apps mid-market merchants actually run, Loop, Narvar and Happy Returns, against this decision: none of them records a physical condition grade or routes a unit to resale, refurb or liquidation, and all three were dropped as poor fits. ReturnPro is the one App Store listing that advertises inspect, test, clean, grade and refurbish, and it carries 5.0★ from 1 review (verified Sep 2026). Optoro, the established grading and dispositioning platform, publishes no pricing and does not mention Shopify anywhere on its returns-processing page. A category carried by a single one-review listing is vendor risk, not a safe buy.
- Reference scenario
- $20M–$100M GMV · apparel or footwear · 25–30% return rate · own warehouse or a 3PL that will run your rules · a returns portal already installed · agency dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Under 300 returns/month | WAIT | At ten returns a day the grading rule fits on a laminated card and a second inventory location. Systematizing costs more than the recovery it adds. |
| 300 – 1,500 returns/month | CUSTOMIZE | Grading belongs in the system rather than in one supervisor's head. A scan-to-grade step plus condition-graded inventory is a small build on top of the portal you already pay for. |
| 1,500 – 8,000 returns/month | CUSTOMIZE | Every day a sellable unit sits ungraded is a day it misses the demand curve it was returned into. Owning the grade-to-relist path is worth more than the subscription it replaces. |
| 8,000+ returns/month, or a 3PL that won't run your rules | DEPENDS | Two honest answers: outsource the whole leg to a returns-processing network and pay per unit, or build grading into the WMS. The deciding question is whether you want to own returns labor at all. |
What Returns grading and restock-to-sellable Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | A unit graded and relisted within 48 hours sells into the demand that returned it; the same unit graded three weeks later sells at markdown or not at all. |
| Operational efficiency | High | A scan-and-grade step replaces a judgment call made by whoever is on shift, which is what turns returns processing from a bottleneck into a repeatable station. |
| Data & insight | Medium | Condition by SKU and return reason separates products that genuinely fail from products customers simply changed their mind about, which changes what you buy next season. |
| Customer experience | Medium | A B-grade unit restocked as new produces a second return and a one-star review; a graded open-box listing sets the expectation before the box ships. |
Spend ceiling: Size the spend to the margin gap between grades, not to the return count. Multiply annual returns by the difference between a sellable unit's margin and a liquidated unit's recovery. That number is the ceiling, and for most apparel brands it is far larger than any build quote.
What buying enables (top apps)
- + A receiving network with trained labor that inspects, tests, cleans, grades and refurbishes, so peak-season return spikes are somebody else's staffing problem
- + Automatic relisting back to your store or resale across 20+ marketplaces, per ReturnPro's listing (verified Sep 2026)
- + No capex, no warehouse bench, no scanner hardware, so the whole leg becomes an operating line
- + Configurable grading built to reduce subjectivity, which is exactly the failure the warehouse floor produces
What building additionally unlocks
- + Grade definitions written around how your products actually fail, instead of a network's generic A/B/C scale
- + Condition-graded units that stay in your catalog, your inventory counts and your own open-box URLs
- + Disposition tied to your margin math: the discount that makes a B-grade unit worth relisting is your number, not a vendor's
- + Condition-by-SKU-by-reason data feeding buying decisions, supplier conversations and product fixes
Find Your Verdict in 3 Questions
Do you control the receiving bench, either your own warehouse or a 3PL that will run rules you write?
Yes: Go to question 2.
No: Your verdict: BUY — route returns to a processing network that grades and relists, and accept its standard grades.
Do more than 300 units a month come back needing a condition judgment?
Yes: Go to question 3.
No: Your verdict: WAIT — a written two-grade rule and a damaged-stock location recover most of the value at this volume.
Is the margin gap between a sellable unit and a liquidated one worth more than $50,000 a year to you (illustrative)?
Yes: Your verdict: CUSTOMIZE — keep the returns portal, build scan-to-grade, condition inventory and disposition routing behind it.
No: Your verdict: CUSTOMIZE — build the minimum version: two grades, one open-box collection, no refurb queue.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | A processing network onboards in weeks and needs your return routing changed; the grading layer is an estimated $25,000–$60,000 build across scanning, condition inventory and relist rules (Deploi estimate, illustrative). | ||
| Recurring fees | ReturnPro's eCommerce Lite runs $79.99/month (verified Sep 2026) and the per-unit processing fee is not published on the listing, which is the line that scales; the build has upkeep and no subscription. | ||
| Maintenance & upgrades | The vendor maintains its own grading tooling; a built layer needs its grade rules revised whenever the product mix changes, which is merchandising work more than code. | ||
| Switching & exit | Leaving a processing network means moving physical inventory and rebuilding a receiving process; leaving a build means nothing, because the grade history sits in your own catalog. | ||
| Risk | |||
| Vendor risk | One App Store listing with 1 review carries the whole category, and the enterprise alternative has no Shopify integration at all; the build has no vendor to lose. | ||
| Security & compliance surface | Outsourced processing hands a third party your customer returns and their contents; a built layer keeps condition data inside Shopify and your WMS. | ||
| Platform-deprecation exposure | Condition-graded variants, inventory locations and the returns API are stable Shopify primitives; a young listing's roadmap is the less predictable dependency. | ||
| Value | |||
| Fit to requirement | Grade definitions are product-specific, since a scuffed sneaker sole and a cracked device screen fail differently, and a network's standard grades rarely match your merchandising. | ||
| Time to market | Rerouting returns to a processing network starts in weeks; the grading build runs an estimated 6–10 weeks before the first unit is scanned (Deploi estimate, illustrative). | ||
| Performance & scale | A network absorbs peak-season return spikes with its own labor; a built layer scales with the receiving staff you hire, which is a January problem in apparel. | ||
| Data ownership & AI-readiness | Condition-by-SKU-by-reason is the dataset that tells you which products come back broken and which returns were never damaged at all; outsourced, you see a summary. | ||
| Focus & opportunity cost | Reverse logistics is real work nobody wants; buying it back is a defensible use of budget when returns are not part of your brand promise. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| ReturnPro Returns Portal | Live — flagged — 5.0★, 1 review; young listing carrying an entire category. The listing describes a network of returns warehouses that receive, grade and automatically relist items to your store or resell across 20+ marketplaces, with end-to-end processing that inspects, tests, cleans, grades and refurbishes. 60-day free trial on the Marketplace Seller and eCommerce Lite plans. | Shopify Seller free to install; Marketplace Seller $29.99/month; eCommerce Lite $79.99/month (verified Sep 2026). Per-unit processing fees are not published on the listing. | Outsourcing the entire reverse-logistics leg (receiving, grading and resale) rather than running it yourself |
| Optoro Returns Processing | Live — Platform integration; no App Store listing. Optoro describes configurable grading built to reduce subjectivity and paper processes, plus intelligent dispositioning that routes returns to restock, resale, donation or destruction. Acquired by Blue Yonder. The returns-processing page does not mention Shopify anywhere, so any connection is integration work you scope and pay for. | Quote-based; pricing not listed | Enterprise reverse-logistics operations already running a warehouse management system worth integrating to |
| Customer-facing returns portals (Loop, Narvar, Happy Returns) | Category — The returns apps most mid-market merchants already run. They cover the customer side well: self-serve RMA, prepaid labels, exchange-first flows, refund rules and drop-off networks. None of them records a physical condition grade, and none routes a unit to resale, refurb or liquidation. The grading decision happens after the box is opened, which is where these apps stop. | Monthly subscription tiers; confirm current pricing on each listing | The customer-facing return experience: keep it, and build the grading layer behind it |
| Grading and disposition layer (custom) | Build lane — Condition grades modeled as variants or dedicated inventory locations, a scan-and-grade step at receiving, and rules that relist, discount, route to refurb or send to liquidation. Sits behind whatever returns portal you already run and writes back to Shopify inventory. | $25,000–$60,000 one-time (Deploi estimate, illustrative) | Merchants who control receiving and want grade rules that match how their own products actually fail |
The Build Path
- Condition grades as first-class inventory: Model A/B/C grades as variants or as dedicated inventory locations so a graded unit is sellable stock with its own price, not a note in a spreadsheet. Shopify's returns flow gives you a restock toggle; the grade is what turns that toggle into a merchandising decision.
- Scan-and-grade at receiving: A tablet or scanner step at the returns bench: scan the RMA, answer three to five product-specific condition questions, get a grade and a disposition instruction printed on the tag. The rules live in config so merchandising can change them without a deploy.
- Disposition routing and automated relist: Grade A restocks to the main location, grade B publishes to an open-box collection at a set discount, grade C queues for refurb, grade D batches for a liquidation manifest. The relist is the revenue step and the one the customer-facing portals never reach.
- Effort band
- $25,000–$60,000 build — Deploi estimate (illustrative); lands in the $25–75K contact-form band
- Typical timeline
- 6–10 weeks for scan-to-grade plus condition inventory; add 3–4 weeks for automated relisting and a liquidation manifest (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $4,000–$12,000/yr (Deploi estimate, illustrative) to revise grade rules as the product mix changes, keep the WMS or 3PL integration current, and absorb Shopify API version bumps. There is no subscription line.
- What you own — and what you take on
- You own: the grade definitions, the condition data by SKU and return reason, the disposition rules and the open-box channel. You take on: training the receiving bench, keeping grade rules honest as products change, and the judgment calls on units that sit between two grades.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $2,000–$6,000 | $25,000–$60,000 |
| Years 1–3 (recurring) | $36,000–$120,000 (subscription + per-unit processing) | $12,000–$36,000 (upkeep) |
| 3-year total | ≈$38,000–$126,000 | ≈$37,000–$96,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column: ReturnPro eCommerce Lite at $79.99/month (verified Sep 2026) plus per-unit processing at an illustrative rate, since the listing does not publish one; roughly 1,500 returns a month.
- † Build column: scan-to-grade, condition inventory and disposition routing on your own receiving bench; your existing returns portal subscription continues in both columns and is excluded from both. Three-year horizon.
What the Sticker Price Hides
On the buy path
- — Per-unit processing fees are the real cost and ReturnPro's listing does not publish them; get the per-unit rate in writing before rerouting a single box
- — A one-review listing is the entire buyable category here, so price the risk of the vendor changing terms once your returns flow through it
- — Outsourced grading uses the network's grade definitions, not yours, so an item you would sell as open-box may come back liquidated
- — Physically rerouting returns to a processing network is a change to your return labels and your customer's experience, not just a software switch
On the build path
- — Grade rules are the hard part, not the code: expect two or three revisions in the first season as the bench argues about edge cases
- — The 3PL integration is where builds stall; confirm the provider will run a custom receiving step before you scope anything
- — Open-box inventory needs its own merchandising owner or it sits unsold, which converts a grading win into dead stock
- — ~$4,000–$12,000/yr upkeep (Deploi estimate, illustrative) for rule revisions and integration maintenance
What Merchants Say
Operations leads describe the same failure: a returned unit sits in a tote for three weeks, gets restocked as new, ships to the next customer with a crease in the box and comes straight back: two shipping legs and a refund to recover nothing.
The recurring complaint about returns apps is scope rather than quality: the portal works, the customer is happy, and the warehouse still grades by whoever is on shift because no app ever asked what condition the item came back in.
If You Change Your Mind Later
If you bought and outgrow it
Exit means moving physical inventory, not exporting a database. Returns are routed to the vendor's warehouses, so leaving requires new return labels, a rebuilt receiving process and somewhere to put the units in transit on the day you switch. Ask for grade-level history in an export before signing, and plan a full season of overlap.
If you built and want out
Nothing strands. Condition grades live as variants or locations in your own catalog, the grade rules are config you own, and the history sits in Shopify. If you later outsource to a processing network, that history is exactly the file they need to match their grades to yours.
When This Answer Changes
We're watching for:
- ▸ ReturnPro's listing accumulating real review volume, since at 1 review (verified Sep 2026) the category has no track record to buy on
- ▸ Loop, Narvar or Happy Returns adding a condition grade and disposition routing to their receiving flow, which would move this to BUY
- ▸ Shopify adding a condition field to the native returns flow beyond the current restock decision
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Do Loop, Narvar or Happy Returns grade returned items?
No. Loop, Narvar and Happy Returns cover the customer-facing side (RMA, label, exchange, refund) and stop at the loading dock. None of the 3 records a physical condition grade, and none routes a unit to resale, refurb or liquidation. ReturnPro is the one App Store listing that advertises inspect, test, clean, grade and refurbish, and it carries 5.0★ from 1 review (verified Sep 2026).
What does a returns grading build actually cost?
A grading and disposition layer costs an estimated $25,000–$60,000 one-time and runs 6–10 weeks (Deploi estimate, illustrative), covering scan-to-grade at receiving, condition-graded inventory and disposition routing. Upkeep lands near $4,000–$12,000/yr (Deploi estimate, illustrative) to revise grade rules as products change. ReturnPro's eCommerce Lite plan is $79.99/month (verified Sep 2026) plus per-unit processing the listing does not publish.
How do you sell graded returns without damaging the brand?
Sell graded returns as a named open-box or second-quality collection with the condition stated on the product page and a price gap of 15–30% (illustrative). Condition-graded variants keep those units in your own catalog, in your own inventory counts, on your own URLs. The alternative, quietly restocking a B-grade unit as new, produces a second return and a bad review.
Your Next Steps
If you're going with CUSTOMIZE(matches your selected profile)
- Pull 90 days of returns and sort them by what actually happened: restocked as new, discounted, refurbished, written off
- Write the grade definitions with merchandising and the receiving lead in the same room, with three to five product-specific questions per grade
- Model grades as variants or dedicated inventory locations before writing any code
- Ship scan-to-grade first; add automated relisting and the liquidation manifest in a second phase
- Track days-from-receipt-to-sellable weekly, since that number is the entire return on this build
If you're going with BUY
- Get the per-unit processing rate in writing, since the listing publishes only the monthly plan price
- Compare the network's standard grade definitions against how your own products fail
- Confirm what grade-level data comes back to you and in what format
- Pilot one product category for a season before rerouting all returns
- Keep your customer-facing returns portal: the network replaces the warehouse leg, not the RMA
Official Docs & Sources
- Returns and refunds (Shopify) — Shopify Help Center
- Inventory management (Shopify) — Shopify Help Center
- Customer accounts — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy a Returns Portal on Shopify?
A returns portal splits by return economics: WAIT on native for simple flows, BUY exchange-first in the mid-market, BUILD at 3PL scale.
Should You Build or Buy Exchange-First Return Flows on Shopify?
Exchange-first flows are a buy once refund volume matters: steering optimization is the vendors' product, not a feature you rebuild.
Should You Build or Buy Refund-to-Store-Credit on Shopify?
Refund-as-store-credit is a customize-on-native play: the mechanic ships with Shopify, so build the small offer layer instead of renting the wallet.
Should You Build or Buy Return Rules & Automation on Shopify?
Return rules and automation is a customize verdict: Flow plus native returns express simple-but-specific rules; platforms earn their fee on exchange tooling.
Should You Build or Buy a Helpdesk on Shopify?
Buying a helpdesk wins for mid-market Shopify stores; build only the integration glue.
Ready to stop guessing at the returns bench?
Grading is a rules problem, not a personnel problem. We build the scan-to-grade step, the condition inventory model and the relist routing that turns a returned unit back into sellable stock in days instead of weeks.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.