Home›Industries›Transport & logistics›Return logistics platform
Industry · Transport & logistics

Custom return logistics platform.

Returns are the most painful link in e-commerce. A custom reverse logistics platform brings the whole path into one environment, from customer portal and carrier label through receiving, grading and refurbishment to resale or recycling. With control over stock, fraud signals and AI prediction of return risk per SKU.

RMA portalCarrier labelsGrading & refurbB-stockReturns fraudWEEE-compliant

Returns are no longer a side issue.

In fashion and electronics, a large share of what your e-commerce channel ships comes back sooner or later. In B2B distribution, sale-or-return agreements with dealers and resellers are the rule rather than the exception. And in every product category with serial numbers, an RMA flow runs alongside the primary order process.

A standard e-commerce stack never fully covers all of this. The webshop knows something about it, the warehouse something, customer service something, and accounting something, but together they rarely form a complete picture. Returns keep snowballing out of control, with their own Excel files and shadow administrations.

A custom return logistics platform brings those fragments back together. It doesn't replace your OMS or WMS, but is the layer that captures the fragmented reality of returns in one coherent flow, with integrations to carriers, marketplaces, finance and stock. Without that layer, you're steering by a blur you can't even see in full.

Three flavours of return platform.

Not every e-commerce organisation has the same returns challenge. For one retailer the pain is in a manual customer desk; for another it's in receiving and grading; for a third it's in resale and financial settlement. In the first conversation, we advise which variant fits.

Compact project · fixed sprint budget

Customer RMA portal with label generator

A secure returns environment where customers register their return, choose a reason from a guided list and immediately receive a PostNL or DHL label via your account or via Sendcloud. Includes a dashboard for your customer service team with open requests, status and an automated email flow. For retailers who finally want to get their returns desk out of Outlook and spreadsheets.

RMA portalPostNL / DHL / SendcloudCustomer service dashboardEmail flow
Mid-sized project · fixed sprint budget

Receiving, grading and B-stock

The portal from the first flavour plus the warehouse side: a scan flow for incoming returns, grading screens (A/B/C/D) with photo capture, automatic routing to a stock location or refurbishment bench, and a B-stock resale channel with a separate stock layer and its own pricing logic. For businesses that want to treat the returns flow as a sales channel rather than a cost item.

Scan receivingGrading A/B/C/DRefurb benchB-stock channel
Larger project · fixed sprint budget

Full reverse logistics platform with AI

The complete flow with marketplace return integrations (Bol, Amazon, Zalando), a warranty and RMA track for serial numbers, recycling and WEEE flows, and an AI layer for return risk scoring per SKU and fraud detection based on customer patterns. Includes integrations with your transport software, ERP and BI. For multi-channel sellers who want to bring scale to their returns chain.

Marketplace returnsRMA / warrantyWEEE / recyclingAI risk scoringFraud detection

What a returns platform really has to offer.

The easiest way to underestimate a returns platform is to think of it as a returns form for the customer. That is at most the front end. Behind it sits a chain of decisions, most of which today are made implicitly or by hand: which returns are accepted (within the statutory withdrawal period, or outside it as a goodwill gesture), which label the customer gets (your own PostNL or DHL account, a Sendcloud aggregator, or a separate returns carrier per country), how the parcel is received (which warehouse location, which team, which priority), who assesses it (grading, photo documentation, possibly a refurb flow), what happens to it (back into A-stock, into B-stock, to repair, to recycling, or back to the supplier), and how the financial settlement works (refund, repair credit, repair invoice, warranty claim with the supplier).

In a good reverse logistics platform, each of those six layers is explicit — not as guidance for an employee in Notion, but as an enforceable flow with validation, an audit trail and integrations with your existing systems. That may sound like a big step, but without that explicit layer your returns data stays fragmented across carrier portals, marketplace back ends, warehouse scanners and accounting export files. Management information is then effectively zero.

The gain lies not in any one of those layers, but in how they work together. Only when you can see at SKU level which product is over-represented in the returns flow, which return reason stands out at brand level, and what grading percentage a supplier shows, can you talk to purchasing and to suppliers — not about anecdotes, but about facts. The platform is therefore not just an operational tool; it is the measurement layer for your returns position.

What you have in hand at the end.

A production-ready returns platform plus the organisational hooks to manage and develop it yourself. Ownership of data, code and architecture rests with you.

  • The returns platform itself, in productionProduction and staging environments in your cloud (GCP, AWS, Azure) or with us. With monitoring, a backup strategy, a recovery procedure and a runbook for incidents.
  • Customer RMA portal in your brandA returns environment in your own look and feel — not a white-label SaaS frame with a stray logo. Mobile-first, multilingual where relevant, with a clear status flow for the customer.
  • Carrier integrations for labels and track and tracePostNL, DHL, UPS, DPD and GLS directly, or via Sendcloud as an aggregator. Including automatic label generation, tracking events fed back into the platform, and a switchable carrier choice per country or return type.
  • Marketplace returns integrationsIncoming return notifications from Bol, Amazon, Zalando, Otto, eBay and the marketplace extensions for Shopify, Magento and WooCommerce — automatically matched to the corresponding order in your OMS.
  • Receiving and grading screens for the warehouseScan flow for barcodes and serial numbers, A/B/C/D grading with photo documentation, routing to a stock location or refurb workbench, and an optional AI grading suggestion based on your historical decisions.
  • Resale chain for B-stock and refurbA separate stock layer for B-stock and refurbished items, with its own pricing logic, its own sales channel (own webshop, marketplace or outlet) and a traceable link to the original return.
  • RMA and warranty administrationFor products with serial numbers: warranty status, repair flow, supplier returns and cost allocation between customer, supplier and your own warranty pot.
  • Fraud detection and AI risk scoringPatterns for address clustering, wardrobing, bracketing abuse and returnless refund abuse, plus predictions of return risk per SKU and per customer — built on our broader experience in AI development.
  • Recycling and WEEE flowsFor electronics categories: a WEEE-compliant disposal chain, integration with recycling partners, battery flows and hazardous-substances handling. Plus the registration needed for producer-responsibility reporting.
  • Full codebase, documentation and knowledge transferSource code, build instructions, database schema, architecture overview, integration documentation and knowledge-transfer sessions for your IT team or your managed-services provider. No vendor lock-in: another team can take it over.
  • Optional ongoing management and further developmentMonitoring, backups, security patches and further development for a fixed monthly budget. With multiple response-time tiers, depending on how critical the platform is to your operation.

When a custom returns platform is the right choice.

Six patterns in which retailers, brands and B2B distributors come to us. If you recognise one or more of them, a conversation is usually worthwhile, even if we end up concluding that a SaaS route still does the job for now in your situation.

Fashion · high return rates

Return volume is growing faster than is operationally sustainable

Fashion and clothing categories have return rates seen in no other sector. What still worked with a manual flow falls apart as soon as you scale to multiple channels or multiple countries. A custom returns platform with a guided flow and automatic label generation is then no longer optional.

Electronics & RMA

Defects and RMAs run alongside the primary order process

You sell products with serial numbers and warranty periods. Defect reports, warranty claims, repairs and supplier returns currently live in a shadow administration. A returns platform with an explicit RMA track connects that shadow layer to your OMS and your warranty pot.

Multi-channel · marketplaces

Bol, Amazon and your own webshop are out of sync

Every marketplace has its own returns flow with its own deadlines, labels and reports. Your own webshop has a third. Reconciling them takes manual work every day, and comparing figures per channel is barely possible. A single returns platform with marketplace integrations resolves the fragmentation.

B2B distribution · sale-or-return

Resellers and dealers routinely return part of their stock

In B2B distribution, sale-or-return, consignment and seasonal-return arrangements are the rule rather than the exception. The terms differ per dealer or per supplier. A returns platform with partner contracts as its base layer makes this manageable and visible.

Fraud pressure

Wardrobing and returnless-refund abuse are on the rise

Patterns such as wardrobing, bracketing, carrier switching and address clustering weigh more heavily as your volume grows. Classic fraud rules are quickly exhausted; a custom scoring model trained on your historical data picks up more subtle signals with fewer false positives. The underlying AI approach fits within our broader AI practice.

Sustainability & compliance

WEEE, recycling and CSRD require demonstrable flows

For electronics, the WEEE directive requires demonstrable disposal and recycling flows; for fashion and electronics categories combined, CSRD reporting becomes relevant. A returns platform with explicit destination tracking (refurbishment, resale, recycling, scrapping) provides the basis for those reports without a second administration.

How a returns platform project works.

1

Introduction and quick scan of your returns flow

An initial conversation in which we learn which channels you run (own webshop, marketplaces, B2B), what return volumes and categories you have, and where the pain is greatest today. This is followed by a short scan of your existing tooling (OMS, WMS, carrier portals, possibly a SaaS returns tool) and a first idea of scope and architecture.

2

Discovery with operations, customer service and the warehouse

A workshop with your teams plus daily shadowing sessions in the warehouse and in customer service. We map the actual returns flow, including all the exceptions, and where needed interview your key suppliers and your marketplace account manager. At the end: scope, planning, screen flows for the first tier and the architecture choice for the OMS/WMS integrations.

3

Building in sprints with a parallel pilot

A working build every two weeks. We start with the channel or flow where the pain is greatest, often the customer portal plus the first carrier integration, or receiving and grading for your busiest warehouse location. Your people test alongside us, and ideally a pilot group runs real returns on the new environment before everyone else switches over.

4

Integration with OMS, WMS and marketplaces

In parallel with the build, we work on the integration layer: stock movements back to your OMS, warehouse events towards your WMS, incoming marketplace return events, and financial settlement towards your accounting system. For companies on an Omniful stack, we connect directly through the Omniful integration; for other stacks, we build the integrations via API or through an aggregator.

5

AI layer for risk scoring and fraud

Once the core platform is running stably and enough historical return data is available, we build the AI layer: return risk scoring per SKU and per customer, fraud detection with human-level advisory output, and optionally a grading suggestion model based on the photo set. Deliberately not earlier, because an AI model running on opaque data is an asymmetric risk.

6

Rollout, training and ongoing maintenance

A phased rollout to the remaining channels, locations and categories, training for customer service, warehouse and operations, and a choice: run it in-house, with your existing maintenance partner, or under a further-development contract with us. The environment grows with your returns strategy.

Compliance: what a platform needs to handle.

The legal framework around e-commerce returns is broader than many retailers recognise in their working processes. The GDPR touches almost every return record: you process personal data of customers and, in the returns flow, often also of recipients and drivers. A platform should provide role-based access, encryption and an immutable audit log as standard, not as an option but as a baseline.

The right of withdrawal under Book 6 of the Dutch Civil Code gives consumers in the EU an unconditional fourteen-day right to return distance purchases, with a few exceptions for custom-made, hygiene and digital products. That period must be hard-wired into your platform's status flow, not left as a manual check by customer service. Warranty periods under Book 7 of the Dutch Civil Code run alongside it for non-conformity, often combined with your own extended warranty policy; in a good platform these are tracked explicitly, not implicitly.

For electronics, WEEE (Waste Electrical and Electronic Equipment) also applies, with a demonstrable collection and processing chain for discarded equipment and separate streams for batteries. For multi-channel sellers who sell across borders, import VAT also comes into play with international returns: a return from a foreign warehouse requires the correct adjustment in your VAT return and in the carrier flow for customs. Finally, ePrivacy affects your customer RMA portal through cookies, trackers and any email tracking you use in return confirmations.

A platform that takes this into account explicitly saves a lot of trouble later: you can report when an auditor or regulator asks, you are in a strong position in disputes, and you don't make your operations team dependent on a manual "compliance check" that is sometimes carried out and sometimes not.

Technology choices along the way.

The choice of platform foundation depends on what you already run and how fast you need to develop further. If a mature order management system and your own WMS are already in place, we build the returns platform as a separate service within the same stack, often Node.js or Python on the back end, Postgres as the data layer and React, Vue or Astro for the customer portal and the operational screens. The platform talks to your OMS and WMS via API and never sits in their database.

For carrier integrations, we default to direct integrations with PostNL, DHL, UPS, DPD and GLS where volume and reliability justify it, and to Sendcloud as an aggregator when you want to switch quickly between carriers by country or by type of return. Track-and-trace events flow back into the platform via webhooks, with retry logic for unreliable carrier APIs.

For marketplaces, we use the official returns APIs of Bol, Amazon, Zalando and Otto, with a normalisation layer on top so that marketplace-specific status codes become a single, common set of statuses in your platform. For the marketplace connector in an Omniful environment, we use the existing Omniful integration as a direct bridge, which saves two to three sprints of integration work in a typical multi-marketplace setup.

For AI components, we separate models into their own service with versioning, monitoring and a human-in-the-loop design. Risk scoring almost always works well with classic gradient-boosted models trained on your own returns history; photo-grading suggestions run on a fine-tuned visual classifier; fraud detection combines rules and scores. We don't use an LLM where a solid classic model achieves the same or a better score: lower costs, and easier to explain in a DPIA.

For reporting and BI, the platform connects to your existing BI stack (Power BI, Metabase, Looker Studio or a data warehouse) via a daily export or a streaming event bus. Operational dashboards (open returns, grading throughput, refurbishment workload) live in the platform itself; strategic dashboards (return rate by brand, by SKU, by channel, by supplier) live in your BI tool.

Who this is relevant for.

Our typical client falls into one of six profiles. E-commerce retailers in fashion and lifestyle, where the return rate is structurally higher than in other categories. Electronics retailers and brands with RMA flows, where serial numbers, warranty claims and supplier returns run alongside the primary order process.

Multi-channel sellers and marketplace players with their own web shop plus a presence on Bol, Amazon, Zalando and sector-specific marketplaces. This is where fragmentation between return flows is greatest and the gain from consolidation is clearest. Marketplaces and platforms themselves, which need to provide a returns flow for their selling parties as part of their proposition.

B2B distributors and wholesalers with sale-or-return or consignment arrangements with dealers, intertwined with partner contracts and finance flows that don't fit in a standard tool. And brands with their own warranty or repair desk, where the returns flow is primarily RMA-oriented.

In every profile, the trade-off between a SaaS returns tool and your own platform plays a role. For the first phase of a webshop, SaaS is almost always the right answer. From a certain scale, when integrations with your own OMS, WMS and BI no longer fit, the balance tips towards custom.

Frequently asked questions.

What clients usually want to know before we start.

Do you build a return logistics platform from scratch or on top of an existing system?
Either is possible, and the choice depends on what is already in place. For retailers with a mature OMS or WMS, we build the returns platform as a separate module on top of what exists, with API integrations for stock movements, label requests and order status. For organisations that don't yet have a mature back office, we more often opt for a combined project in which the returns flow, OMS and WMS are designed together. In the quick scan, we can tell you what is realistic for your situation.
Which carriers and marketplaces are supported as standard?
For labels and track and trace, we integrate with PostNL, DHL, UPS, DPD, GLS and the Sendcloud aggregator. For marketplaces, we support the returns flows of Bol, Amazon, Zalando and Otto, plus the marketplace extensions of Shopify, Magento and WooCommerce. We generally build other carrier or marketplace integrations within a single sprint, as long as a clean API or a SOAP/EDI feed is available. For an Omniful environment, we use the existing Omniful integration directly.
How do you handle GDPR, EU return rights and warranty legislation?
GDPR is the baseline: encryption in transit and at rest, role-based access following the principle of least privilege, data processing agreements with carriers and marketplaces, and an immutable audit log for every return record as standard. The right of withdrawal under Book 6 of the Dutch Civil Code (fourteen days for consumers) is built firmly into the set of return reasons and the status flow, including the statutory exceptions for hygiene products, custom items and digital products. For warranty and RMA, we follow the Book 7 Dutch Civil Code terms plus your own extended-warranty policy; for WEEE and battery recycling flows, we integrate with the established recycling partners. We carry out a DPIA when the scope warrants it.
Can AI help with fraud detection and risk scoring on returns?
Yes, and at several levels. Patterns that would otherwise take manual work to spot — address clustering, carrier switching, returnerless abuse, bracketing in fashion — are easy to detect with classic machine learning on your own historical data. Risk scoring per SKU helps purchasing and merchandising make well-founded decisions. A grading suggestion model based on photos speeds up receiving without replacing your staff. For the AI side, we draw on our wider practice in AI development and build scores in as an advisory rule at approval; the final decision stays with your returns team.
How do grading and B-stock resale work?
Grading is a screen flow in the receiving module: the returns employee photographs the item, assesses it and assigns a grade — A new, B light signs of use, C refurbishment candidate, D recycling. That grade automatically determines the resale destination: back into A stock, to the B-stock channel, to refurbishment, or to recycling. The photo set can optionally pass through an AI grading layer that proposes a grade based on earlier decisions. B-stock sits as a separate inventory layer in your OMS with its own pricing logic and its own sales channel — a dedicated webshop segment, a dedicated marketplace, or an outlet.
What if we already run a SaaS returns tool?
That's not unusual. In that case we start with an honest assessment: a SaaS route is often exactly what a webshop needs in its first phase, and the balance only tips when you run into specific limits — integrations with your own stack that don't fit, B-stock channels that aren't supported, AI components the tool doesn't offer, or an operational scale that pushes SaaS costs past the tipping point. Sometimes migrating to a custom solution is the right step; sometimes a hybrid that keeps the SaaS for the customer portal works perfectly well. We give you that assessment honestly, even if it doesn't work in our favour.
How does this link to your transport software practice?
For retailers who run their own deliveries or work closely with a carrier, the returns platform connects to your transport software: collection routes for returns, dock planning for incoming return batches, and integrations with your own TMS where relevant. For companies that rely entirely on external carriers, this is limited to label and track-and-trace integrations via the carrier layer.
What does a project like this cost?
That depends on the size of your returns flow, the number of channels and marketplaces, the complexity of your OMS and WMS integrations, and the scope of the AI layer. We work with a fixed sprint budget so you can adjust scope sprint by sprint, and we give an indicative total in the quote — never an empty figure before we've mapped your actual returns flow. A compact RMA portal is a considerably lighter project than a full multi-channel platform with an AI layer.
How long will it take before we can go live?
Too dependent on your scope to put a number on it without understanding your situation. For a compact customer RMA portal with a single carrier integration, we're talking about a project of a few sprints. For a full reverse-logistics platform with multiple marketplaces, receiving and grading, a refurbishment flow and an AI layer, we plan for several consecutive sprints, delivered in phases. The first tier is usually live before the last tier comes into scope, so your operation sees value early.
Do you work with our own IT department or an external managed-services provider?
Almost always. We deliver the codebase, deployment instructions, an architecture overview and an incident runbook so that an external managed-services provider can take over. That is a deliberate design choice to avoid vendor lock-in. During the project, we run a knowledge transfer in the final sprint. Sometimes we stay on under a maintenance or further-development contract; sometimes an external party is the better fit for maintenance. We advise on what suits you, even if that means another team takes over.

Talk to us about your returns flow.

A no-obligation introductory call of half an hour. We listen to your current flow across your channels, marketplaces and warehouse, ask targeted questions, and give you direction you can actually use, even if we conclude that a SaaS route is still sufficient for your situation for now.

Fabian van Dijk Business developer · Appfront
Share LinkedIn Email

Edit content