Around 71% of UK online shoppers return something they have bought, and January alone, “Returnuary”, drives roughly £1.5 billion of returns. For a retailer or wholesaler, that is not an edge case. It is a core process that touches customer service, the warehouse, finance, and your suppliers. When it runs on spreadsheets and email chains, refunds drag, stock counts drift, and a fifth of your support tickets end up being “where’s my refund?”
At ByteGears, we build custom return and refund management systems designed around your existing workflows, so your team keeps working the way it already does. You pay once, you own the software, and there are no per-return or per-user fees. We are a London-based consultancy focused on practical automation for UK SMEs.
Why off-the-shelf returns software falls short
Most businesses start with a returns SaaS app and run into the same walls:
- Pricing scales against you. Subscription tiers run from roughly £150 to £450+ a month, and per-return pricing spikes exactly when you are busiest, during the January peak. Carrier label fees and overage charges are easy to miss until the invoice lands.
- It is built for one channel. Many platforms are Shopify-first. If you also sell on WooCommerce, Magento, Amazon, eBay, or in a physical shop, you end up with gaps or a second subscription.
- The integrations are shallow. Returns sync to inventory and accounting through Zapier or batched API calls, so stock can lag 24-48 hours and refunds do not always post to the right GL code. Month-end reconciliation then becomes a manual job.
- The workflow is rigid. Most tools only do “approve or reject”. They cannot hold a “changed mind” return for a cooling-off window, fast-track defects, apply a restocking fee, or require sign-off above a value threshold.
- It is US-centric. Many vendors treat Evri, Royal Mail, and Whistl as afterthoughts, and store customer data outside the UK.
- Warranty and B2B returns get ignored. SMB tools rarely handle warranty repair routing, purchase-order-linked returns, or credit notes instead of cash refunds.
So people end up back in spreadsheets, customers wait too long, and the software you are paying for sits half-used.
To be clear, returns SaaS is the right answer for plenty of businesses. If you sell uniform products from a single warehouse, run a straightforward “accept or reject” process, and spend under a few hundred pounds a month, an off-the-shelf app will serve you well. A custom build earns its place when your returns process is genuinely your own: proprietary policy rules, tight ties to in-house ERP or accounting, multiple brands or warehouses, high volume that makes per-return pricing painful, or warranty and B2B workflows that templates cannot bend around.
What we build instead
We start with your process, not a template
Before any code is written, we map how returns actually move through your business: how they are requested, authorised, shipped back, inspected, graded, and resolved. The software fits that, rather than forcing your team into someone else’s idea of a returns flow.
You pay once and own it
No monthly subscription, no per-return fee, no per-user licensing as you hire. You get the source code, the database, and the infrastructure. That removes the vendor lock-in risk too: you are not exposed to a price hike, a feature being moved to a higher tier, or the platform being acquired and shut down.
It connects properly to what you already use
Returns only work when they connect well. We build direct integrations to:
- E-commerce platforms: Shopify, WooCommerce, Magento, BigCommerce, plus marketplaces like Amazon and eBay
- Accounting software: Xero, QuickBooks, Sage, with refunds posting to the correct GL codes
- Carriers: Royal Mail, Evri, DPD, DHL, and UPS for label generation and tracking
- Payment processors: Stripe, PayPal, and others for refund processing
- Warehouse and ERP systems for two-way inventory sync
We pay particular attention to the integrations that usually fail in off-the-shelf tools: real-time inventory updates so you do not oversell returned stock, and refund reconciliation so finance is not patching the GL by hand at month-end.
UK compliance is built in
The system is built around UK rules from the start:
- Consumer Rights Act 2015 and the 14-day distance-selling withdrawal right
- Correct VAT treatment of refunds and credit notes
- UK GDPR and the Data Protection Act 2018, with UK or EU data residency
- A complete audit trail for HMRC and financial audit, with retention rules you can configure
- Where relevant, sector rules such as WEEE for electronics or hygiene handling for health and beauty
What a returns system includes
The right scope depends on your business, but most builds cover:
- Self-service returns portal — branded request page, RMA number generation, and a status page so customers stop opening “where’s my refund?” tickets
- Policy engine — your real rules: return windows by product category, condition requirements, restocking fees, exchange-only or store-credit-only items
- Approval workflows — auto-approve where rules allow, hold or escalate where they do not, with multi-level sign-off for high-value returns
- Routing logic — returns directed to the right warehouse, department, or repair team based on product, value, condition, or reason code
- Multi-channel handling — online, marketplace, retail, and B2B returns in one system
- Carrier labels and tracking — prepaid or pay-on-return labels and live status pulled from carrier APIs
- Condition and inspection records — digital QC with photo uploads, item grading, and disposition (restock, refurbish, resell, discard)
- Flexible resolutions — original-payment refund, store credit, exchange, or repair
- Supplier chargebacks and credit notes — claims generation for defective or mis-shipped goods, and B2B credit notes against the original purchase order
- Inventory sync — stock levels updated across connected systems as items are received
- Reporting dashboard — processing times, reason codes by SKU and category, return rates, exchange conversion, and seasonal trends
- Fraud signals — flags for serial returners and wardrobing patterns, tuned to your product mix
- Mobile-friendly staff access — warehouse and operations staff can process and grade returns from a handset, not just a desktop
- Granular permissions — separate access for finance, customer service, and warehouse roles
How delivery works
We usually build in two stages so you get a working system quickly, then layer on the harder features.
1. Discovery and planning (1-2 weeks)
We run workshops with your team to document the current returns process, the integrations you depend on, your policy rules, and where things break today. The biggest risk in any returns project is underestimating integration effort, so we get detailed specs for your e-commerce, accounting, and carrier systems up front.
2. Phase one build (6-8 weeks)
We build the core system: branded returns portal, RMA tracking, carrier label generation, customer notifications, refund processing, and your first e-commerce integration. The aim is a system that handles the bulk of your returns end to end.
3. Phase two build (8-12 weeks, scoped to your needs)
This is where the proprietary work happens: exchange flows, accounting integration with GL posting, multi-warehouse routing, repair and resale workflows, fraud rules, approval chains, and additional channels.
4. Testing and go-live
We test alongside your team rather than over a wall:
- Real return scenarios run end to end
- Integration testing against live e-commerce, accounting, and carrier accounts
- Load testing for peak periods, so January volume does not break the system
- A pilot phase running in parallel with your current process before full cutover
- User acceptance sign-off
5. Training and support
Customer service, warehouse, and finance teams each get role-appropriate training and documentation, plus a period of support after launch. Most clients keep us on a small retainer for changes as their returns process evolves.
What it costs
A custom build costs more upfront than signing up to a SaaS app. The picture changes once you look at total cost of ownership.
- Returns SaaS: roughly £150-£450+ a month for the subscription, before carrier label fees, integration work, and per-return charges that spike in January. Enterprise platforms run into tens of thousands a year, often with six-month implementations and separate professional-services fees.
- Custom build: a one-off project, typically £15,000-£60,000 depending on complexity. A simple Shopify-only system sits at the lower end; a multi-channel build with accounting integration and fraud rules sits in the middle; multi-entity work with legacy ERP integration sits at the top.
- After launch: hosting plus a maintenance retainer, with no per-return or per-user fees as you grow.
For a business with steady, meaningful return volume, the total-cost picture usually favours a custom build by year two or three. For high-volume operators paying enterprise SaaS rates, it can favour a build sooner. We will be honest with you about where your numbers actually land, including the cases where SaaS is the cheaper choice.
Beyond cost, a system built around your process tends to mean faster refunds, cleaner stock counts, fewer support tickets tied to returns, and clearer accountability when goods come back defective or mis-shipped.
Industries we build for
If your business handles physical goods coming back, a custom returns system can make sense. The detail differs a lot by sector:
- Fashion and apparel — 30-50% return rates, size and fit exchanges, return data fed back to sizing and sourcing, and B-grade stock routed to outlet or resale channels
- Electronics — warranty claims split from customer returns, defect aggregation flagged to quality teams, secure data wiping and WEEE-compliant disposal, and grading for refurbished resale
- Home and furniture — bulky-item collection scheduling, professional inspection workflows, refurbishment cost tracking, and routing to showrooms or clearance
- Automotive and parts — core returns, warranty claims tied to serial numbers and VINs, B2B credit notes, and cross-border returns post-Brexit
- Wholesale and B2B distributors — purchase-order-linked returns, multi-level approvals on large credit notes, contract-specific return terms by customer tier, and batch or lot tracing for manufacturing defects
- Luxury and high-value goods — authentication before resale, VIP concierge returns, and stronger fraud and wardrobing controls
- Health and beauty — hygiene rules on returned products and strict segregation
- Subscription and rental — damage assessment, wear-and-tear depreciation, and automated late-fee or damage billing
- Food and beverage — short shelf-life products, cold-chain checks, allergen segregation, and HACCP documentation
Common Questions About Custom Return & Refund Management Systems
How does a custom build compare on cost to returns SaaS?
SaaS looks cheap until you add it up. Subscription tiers run from roughly £150 to £450+ a month, and per-return pricing climbs sharply during the January returns peak. Then there are carrier label fees, integration work, and overage charges. A custom build is a fixed one-off project cost, typically £15,000-£60,000 depending on complexity, after which you pay only for hosting and maintenance. For mid-market retailers with steady return volume, the total cost of ownership usually tips in favour of a custom build by year two or three.
What's the typical development timeline?
A working MVP, covering the returns portal, RMA tracking, label generation, refunds, and one e-commerce integration, usually takes 6-8 weeks to build plus a couple of weeks of testing. Phase two work such as exchange flows, accounting integration, fraud rules, and resale routing adds 8-12 weeks. We can sequence delivery so the core system is live before a peak period like January.
Can you integrate with our existing systems?
Yes. We connect returns systems to e-commerce platforms (Shopify, WooCommerce, Magento, BigCommerce), accounting software (Xero, QuickBooks, Sage), carriers (Royal Mail, Evri, DPD, DHL, UPS), payment processors (Stripe, PayPal), and warehouse or ERP systems. We pay particular attention to two-way inventory sync and refund posting to the correct GL codes, since these are where off-the-shelf integrations tend to break.
How do you handle updates and changes?
You own the source code, so there are no forced upgrades. Projects include a period of support after launch, and most clients keep us on a small retainer for changes and new features. Because the code is yours, you can also take it to another developer.
What about data security and compliance?
Returns systems hold customer contact details, purchase history, and payment references, so they fall squarely under UK GDPR and the Data Protection Act 2018. We build with: - UK or EU data residency, so customer data does not have to leave the country - Role-based access for finance, customer service, and warehouse staff - A full audit trail of every approval, refund, and status change for HMRC and financial audit - Configurable retention rules (typically 6 years for return records, shorter for personal data) - Encrypted data transmission and regular security testing
Can it handle our return policy rules and warranty claims?
Yes, and this is often the main reason businesses move off SaaS. We build your exact logic: auto-approve defects, hold "changed mind" returns for a cooling-off window, require sign-off above a value threshold, apply restocking fees, or route warranty claims down a separate repair workflow. B2B returns can be tied to the original purchase order with credit notes instead of cash refunds.