Returns Management Software: Build vs Buy
Buy if you run one fulfilment node, process under roughly 2,000 returns a month, and can fit your real policy on one page. Loop, Happy Returns and AfterShip Returns do that job well and no build recovers its cost at that volume.
On this page
Buy if you run one fulfilment node, process under roughly 2,000 returns a month, and can fit your real policy on one page. Loop, Happy Returns and AfterShip Returns do that job well and no build recovers its cost at that volume. Build the operational layer behind the portal once grading, disposition and reconciliation have moved into spreadsheets.
What Loop, Happy Returns and AfterShip actually do well
The customer facing portal is a commodity, and that is a compliment. Loop Returns handles the shopper side competently: a reason code, a prepaid label, an exchange or store credit offered before a refund, and a decent conversion from refund to exchange that pays for the subscription on its own. Happy Returns adds physical drop off points and box free returns, which removes packaging friction that no software fixes. AfterShip Returns covers the same ground with tracking already attached.
If you run one node, process under about 2,000 returns a month, and your written policy fits on a page, buy one of them and stop reading. A build at that volume is capital spent on a problem you do not yet have, and we say so to founders who ask us to quote it.
They also carry things a build never gives you free. Somebody else keeps the carrier label integrations current when rates and services change. Somebody else supports the shopper who cannot print a label on a Sunday. Somebody else has already tuned the exchange offer that lifts your retention.
So keep the front door. The rest of this page is about the building behind it.
Where they stop: what happens after the label scan
The portal's lifecycle effectively ends at received. Your profit and loss statement starts there.
It is the Tuesday after a holiday weekend and your returns coordinator is at the dock with a scan gun in one hand and a phone in the other. The portal says 412 packages are inbound this week. Carrier scans show 371 delivered. The warehouse spreadsheet, the one with fourteen tabs and three owners, shows 340 processed. The customers sitting in the gaps between those numbers are opening tickets that all ask the same question.
A returned jacket gets scanned, dropped in a container and graded whenever the inspection bench clears its backlog. If that takes five weeks in October it misses the season and goes to outlet at a fraction of full price. Nobody decided that. Restock, refurbish or liquidate is decided by whoever is on the bench that day, with no photo record and no consistency between your own warehouse and your third party logistics provider.
Then there is refund timing. To keep customers calm most brands refund on carrier scan, and serial abusers know it. The box arrives empty, or holds a worn item, or a cheaper substitute, or an identical model with a different serial number. By the time the bench catches it the refund cleared a fortnight ago. Portals offer broad refund timing settings. They have no memory of the customer who returned nineteen orders in twelve months with four inspection mismatches, because the customer history that matters lives in your order data rather than in theirs.
The last gap is routing. Most brands configure one return address, so a west coast customer ships a B grade fleece across the country to a dock where it waits to be trucked back toward the outlet partner it was always destined for. You paid freight twice on an item you had already decided not to resell at full price.
The arithmetic: cost per return versus a build
Returns platforms price per return, or on a monthly plan banded by return volume, which comes to the same thing. Take your per return cost, multiply by monthly volume, multiply by 36 months. That is the visible side and it is the smaller half.
Now price the invisible side. Take your monthly return volume and your average order value and write down the refund liability and recoverable inventory moving through that spreadsheet every month. Then estimate the share mishandled: a double refund here, a restocked unit never relisted there, a grade A item sent to liquidation. Even a low single digit percentage of that flow is a monthly number larger than the subscription, and unlike the subscription nobody invoices you for it.
Add the labour. The headcount whose actual job is reconciling three systems. The support tickets that exist only because the portal cannot express your policy, which a support agent then resolves by judgement at ten to five on a Friday, and agent judgement drifts generous over time.
The crossover in our delivery experience arrives near 5,000 returns a month, or at the second receiving node, whichever comes first. Below 2,000 a month on one node, buy. Between those numbers the deciding factor is usually recovery value: if a meaningful share of returned units could be resold at close to full price and are not, the build pays for itself out of inventory rather than out of software savings.
What a custom returns build actually costs
Bands, from delivery experience. A focused first release covering the policy eligibility engine, receiving and grading with photo capture, unit level disposition, refund release control and integration with your commerce platform plus one warehouse system runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding multi node routing at label creation, customer level abuse scoring, automated posting to your accounting system, outlet and liquidation flows and portal replacement runs $150,000 to $400,000 phased over 6 to 12 months.
Data migration adds 10 to 25 percent. Open returns move with their state intact, and spreadsheet history gets normalised into the new ledger, which means somebody who knows the business resolving inconsistent columns on older rows. Validate migrated totals against past refund journals before anyone trusts a report.
Year two runs 15 to 20 percent of build cost annually. Commerce platform interfaces version, carriers change services, and every new sales channel brings its own return path.
What pushes it up: the count of physical nodes and distinct warehouse systems, since each receiving integration is its own project. Grading stations with hardware, because scanners and cameras behave differently on a concrete floor than in a demonstration. Accounting depth, since multi entity or multi currency posting roughly doubles the finance work. And cross border returns with duty in play.
What keeps it down: keep the portal, build the ledger, and integrate one warehouse first.
The four situations where building wins
- Regulatory fit. Returns sit on top of three separate rule sets that pull in different directions. Refunds must route back through your existing payment processor to the original tender, which keeps the new system out of Payment Card Industry Data Security Standard scope because it never touches card numbers, and that design decision has to be made deliberately rather than discovered in an audit. Several states set refund disclosure duties, with California Civil Code section 1723 requiring a conspicuously posted policy, and the European Union grants a 14 day right of withdrawal under the Consumer Rights Directive. Meanwhile deletion rights under the General Data Protection Regulation and the California Consumer Privacy Act collide with retention duties on financial records, so identity has to be separable from the ledger. And if you import, duty drawback under 19 U.S.C. 1313 lets you recover duty on goods that are exported or destroyed, which requires unit level records most brands never keep.
- Scale economics. A per return fee grows with the volume you are trying to reduce, and it grows fastest in the months your operations team is already stretched.
- A workflow that is your competitive advantage. If recovery value is real for your category, the disposition decision is the business. Grade A back to sellable stock with an inventory adjustment, grade B to refurbishment or outlet, grade C to liquidation, grade D written off, each with a photo and a named grader.
- Integration sprawl across three or more systems. The portal, the commerce platform, the warehouse system, the help desk, the accounting ledger and a spreadsheet holding the truth. Month end closes from three sources that never agree, which is why your return reserve is an estimate your auditors keep asking about.
Two of those true is a build. One of them is a better plan with your current provider.
How to decide in a week, with three numbers
Everything here uses data you already have and none of it needs a vendor.
Monday: pull last month's inbound count from the portal, delivered scans from your carriers, and units actually processed at the dock. Those three should match. The gaps are refunds owed, tickets opened and inventory unaccounted for.
Tuesday: take a hundred returned units received last month and measure the days between carrier delivery and a grading decision. Sort them. The tail is where seasonal value died.
Wednesday: pull the twenty highest value units returned last month and check what actually happened to each. Count how many could have gone back to full price stock and did not.
Thursday: pull every return exception ticket from last month and group by cause. Policy the portal could not express. Refund already issued. Item not as described. One cause usually dominates and it names your first release.
Friday: price it. Recovery value lost, plus double refunds and unreconciled units, plus the reconciliation headcount, plus three years of per return fees. Under roughly $120,000 a year, tighten the process and negotiate your plan. Above it, build the ledger, disposition and routing layer, keep the portal as the front door, and replace it later only if the per return fees justify it.
If it points to build, start with a paid discovery rather than a proposal. Two to three weeks, fixed fee, and the deliverable is a signed product requirements document covering the unit level data model, the eligibility rules, grading and disposition states, refund release logic, accounting postings and acceptance criteria. You keep that document whoever builds from it.
We are wrong for you if you run one node under 2,000 returns a month, if converting refunds into exchanges is your main objective, or if you are choosing on hourly rate. Where Digital Heroes fits: more than fifty specialists, over 2,000 projects, our own products including ShopScore, HeroCheckout and Section Vault, and India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law. You meet the named team before signing, full source and deployment pipelines are handed over at delivery, and our record is checkable on Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S listing.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Google-commissioned research (conducted by Deloitte and 55) analyzing over 30 million user sessions across 37 leading European and American brand sites found that faster mobile site speed correlated with improved funnel progression, conversions, and average order value across retail, travel, luxury, and lead-generation verticals. Source: web.dev (Google Chrome team) / Milliseconds Make Millions (2020) →
- The average documented online shopping cart abandonment rate is 70.22% (based on 50 studies), and large ecommerce sites can achieve a 35.26% increase in conversion rate through better checkout design. Source: Baymard Institute (2024) →
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
- Only about 30% of digital transformations succeed at meeting their objectives, but getting six critical success factors in place (leadership commitment, talent, agile culture, progress monitoring, clear strategy, and a modernized platform) raises the odds of success from 30% to 80%. Source: Boston Consulting Group (BCG) (2020) →
Frequently asked questions
How long does a first release take and what should be in it?
Twelve to sixteen weeks, covering the eligibility engine, receiving and grading with photo capture, unit level disposition, refund release control and integration with your commerce platform plus one warehouse system. Multi node routing, abuse scoring and accounting automation extend the programme to six to twelve months, released in phases so the dock never waits on a single large launch.
Who owns the returns data if an agency builds the platform?
It should be contractual and unambiguous before kickoff: you own the repository, the infrastructure accounts and the data. Your returns ledger feeds your reserve calculation, your chargeback responses and your buying decisions, so it cannot live somewhere you need permission to query. At Digital Heroes the client owns the source, the deployment pipelines and the documentation from the first commit.
What happens if a customer disputes a refund we held for inspection?
You respond with evidence rather than a policy quote. Grading photos captured at the bench, the carrier scan timeline, the weight recorded at receipt and the inspection notes attach to the response in the format the processor expects. Brands lose these disputes when their only record is a spreadsheet row, which is also why holding refunds without evidence capture is worse than refunding on scan.
Can we keep Loop as the front door and build only the warehouse side?
Yes, and that is the sequence we recommend most often. Loop keeps the shopper experience and the exchange conversion, while the custom layer owns receiving, grading, unit level disposition, refund release timing and accounting postings. It is a smaller footprint, it addresses the part that leaks money, and it leaves the option of replacing the portal later if per return fees justify it.
Should a brand doing 1,500 returns a month build custom software?
No, and we would say so before quoting. At one node and that volume, a portal plus a disciplined grading procedure and a weekly reconciliation will beat a build on cost and on risk. The case appears when a second receiving node opens, when recovery value is real and unrealised, or when somebody's actual job has become reconciling three systems that disagree.
What is the difference between a returns portal and a returns platform?
A portal manages the shopper: reason codes, labels, exchanges and status emails. A platform manages the unit: where it physically is, what grade it received, which channel it should go to, when the refund releases and how the money posts to your ledger. Most brands buy the first and improvise the second, which is why the dock and the finance close disagree every month.
How much does adding a second warehouse or third party logistics provider cost?
Treat each receiving integration as its own project, because warehouse systems differ in what they expose and how they confirm receipt and restock. The larger question is routing: once a second node exists, the label decision itself has to become intelligent, choosing a destination by item category, likely grade and carrier zone cost at the moment the label is created rather than as a fixed setting.
Can returns data improve what we buy next season?
Yes, and reason codes are the cheapest product research available to you. Held at style and size level rather than exported to a file nobody opens, they show which fits, colours and descriptions drive returns, and cohort views show whether a size guide change moved the number. The planning team buying next season's version of a heavy returning style is a preventable and expensive habit.
What happens to open returns during a migration?
Run the new receiving flow in shadow alongside the current one for a few weeks, migrate open authorisations with their states intact, and cut over one node at a time. Volume never stops in this operation, which is why a single cutover weekend is the wrong plan. Validate migrated totals against past refund journals before anyone reports from the new ledger.
How do we handle cross border returns without losing the duty?
Keep unit level records tied to the original import entry, because duty recovery on goods later exported or destroyed depends on being able to trace the specific units rather than a quantity. Most brands cannot, so the duty is quietly written off. Decide early whether drawback is worth pursuing for your margins, because it changes what the grading bench has to record at receipt.
Should I install a Shopify app or have the feature built custom?
Do the subscription math. An app at $50 a month is $3,000 over five years and ships tomorrow, so apps win for standard problems like reviews, email, and loyalty; custom wins when you would need three apps fighting over the same cart or the feature is your competitive edge. Watch total stack cost too: we regularly see $500 to $800 a month in app fees on mature stores, and replacing two or three overlapping apps with one custom feature is often cheaper by year two.
Should I just buy a premium Shopify theme instead of paying for custom development?
Buy the theme if you have under roughly 500 SKUs, standard shipping rules, and no back-office systems to integrate; a $300 Theme Store theme plus a few days of configuration is the right call at that stage. Custom development earns its cost once you need wholesale pricing, product bundles, subscription logic, or an app stack that stock themes fight with. The honest test: if your requirements fit inside theme settings, do not pay someone to rebuild them.
Do I need Shopify Plus, and at what point is it worth the money?
Shopify Plus starts at $2,300 a month on a three-year term, and the usual crossover is $1M to $2M in annual sales, or earlier if you specifically need checkout customization, built-in B2B wholesale features, or expansion stores for international markets. Below that, the Advanced plan at $399 a month covers most growing brands. Upgrade for a named capability you will actually use, not for prestige.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
Can I launch on Shopify's free Dawn theme and customize it later?
Yes, and for many stores that is the smartest first move. Dawn is Shopify's free reference theme, built on Online Store 2.0 with fast performance out of the box, and a developer can extend it with custom sections instead of starting from zero. Most custom builds we deliver under $10,000 start from Dawn rather than a blank theme because it cuts both cost and risk.
Who can build a custom Shopify development system?
Digital Heroes builds custom Shopify development systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other Shopify development companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Sienna.
Director of Design · APAC · Sydney · 2 posts on the site
Published · Last updated .
