Custom returns management software development
A return is not an order running in reverse, but an assessment whose outcome is unknown in advance: the same item can come back unused and be immediately sellable, or arrive damaged and be good only for parts. Each outcome affects a different set of records. Appfront builds returns management software that records that decision and passes it on to stock, credit notes, warranty or write-offs.
What returns management is, and what this page is not about
Returns management is the reverse flow of goods: a customer registers an item, it arrives, someone assesses it and then a decision is made. That decision is the real work. With a regular order you know in advance what leaves the door; with a return you only know once the box is open.
This page is about that return flow and the decision per item. If you mainly want a returns form and a better ordering experience at the front end, that belongs under a custom webshop. If you are looking at the broader management of purchasing, stock and suppliers, where returns are only one of the flows, look at supply chain management software. If it is about customer dissatisfaction, complaints management software is the right page. A customer can return something contentedly because they ordered two sizes; another can be furious without sending anything back.
Webshops
Volume and the statutory cooling-off period set the rhythm. The question is rarely whether you accept a return, but how quickly a sellable item is back on the shelves.
Wholesalers and distributors
Returns run on contract, not on statute: a return number requested in advance, agreements on the condition in which the item comes back, sometimes a take-back fee.
Manufacturers and brands
Here, after assessment, the item often goes out of the door again, to your own supplier: the start of a second process with its own claim number.
Why returns get stuck in the administration
The pattern we come across most often: the return is modelled as an order running in reverse. As soon as the customer registers, the system books the stock back in and prepares the credit note. From that moment on, nothing adds up. The item is still in transit, may be damaged or different from what was registered, and sometimes nothing arrives at all. Sales sees stock that isn't there; the warehouse corrects it by hand.
That one word, "return", covers four outcomes, each with its own administrative tail. The item goes back into sellable stock undamaged. It goes to repair or repackaging, and is then neither sellable nor written off. It continues as a warranty claim, after which the flow of goods and the flow of money diverge. Or it is written off. Software that only knows "approved" and "rejected" squeezes those four outcomes into two boxes.
Meanwhile, the handling cost per return keeps adding up: transport both ways, receipt, assessment, cleaning or repackaging, re-photographing, financial settlement. Together, that regularly exceeds the margin, and what comes back most often is rarely cheap. You can only steer once the reason is recorded per item. "Did not meet expectations" is not a reason but a summary; the difference between "size came up smaller", "description was inaccurate", "arrived damaged" and "wrong item delivered" points to four different departments.
Three grounds for a return, three different obligations
A return comes in on one of three grounds, and that determines who pays what, which deadline applies and whether you may refuse it. That distinction belongs in the system, not in the head of whoever opens the box.
The statutory cooling-off period applies to distance selling to consumers. According to the Dutch Authority for Consumers & Markets (ACM), the consumer has a cooling-off period of 14 days after the product is delivered, then 14 days to send it back, and the seller must refund within 14 days. There are exceptions, including made-to-measure or personalised products, perishable goods and opened hygiene products. If you do not inform the customer about the cooling-off period, the ACM says it is automatically extended by a year. So the clock is tied to the delivery date, and the proof that you informed the customer correctly must be traceable.
Warranty follows a different logic. The ACM explains that the statutory warranty is not tied to a fixed number of years: you are entitled to a product that does what you could reasonably expect, and the seller remains accountable for that. A warranty return has no cooling-off clock, but it does need a purchase date, a serial number or batch, and a technical assessment.
Goodwill is the third ground: a more generous arrangement that you operate yourself. It rests on your terms, not on the law. You may refuse a goodwill return, attach conditions to it or compensate it differently; you may not do so for a withdrawal within the statutory cooling-off period. Handling both under the same button gives away more than intended.
For business customers there is no statutory cooling-off period, only the contract: a return number requested in advance, usually called an RMA, agreements on the condition in which the item comes back, sometimes a take-back fee. If you sell to both groups, two sets of rules run side by side.
- Record the ground at registration, don't infer it afterwards
- Calculate deadlines from the delivery date
- Flag exceptions per item or category
- Retain the serial number or batch for warranty and recalls
- Log who assessed what, when and why
What returns management software must be able to do
These components are interdependent: the stated reason drives the assessment, the assessment drives the financial settlement, and that determines what you see in the figures.
Registration with a reason per item
The customer selects a reason per line, not per order, from a list you manage yourself: short enough to be filled in, specific enough to point to a department.
Receipt and identification
The warehouse scans what arrives and matches it against the registration. Discrepancies are more rule than exception: a different item, an empty box, two units.
Assessment with your own grades
Not approved or rejected, but the grades your range needs: unused, opened but complete, signs of use, defective, incomplete. For each grade, what follows is predefined.
Repair and repackaging
An item in cleaning, repair or repackaging is unsellable for a while, yet not written off. That in-between state deserves its own stock status, otherwise it shows up as a stock discrepancy.
Financial settlement
A credit note linked to the original invoice line, including for partial returns and the shipping costs you refund.
Warranty claims to the supplier
If the item goes on to your supplier, a second case starts there with its own claim number and deadline. Without monitoring, such a claim expires unnoticed.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →The integrations that make a return watertight
Returns management is almost never a standalone system. The original order comes from your webshop or ERP, because without the item, price, delivery date and customer type there is nothing to assess. The warehouse system provides location and stock status and receives the outcome back, including the in-between state of items under repair. With the carrier, you retrieve return labels and track the shipment, which records when the customer handed over the parcel. Your accounting system receives the credit note.
For identification across the chain, it helps to align with what you already use: the GS1 standards with the GTIN at item level, the SSCC for a logistics unit and the GLN for a location.
When custom isn't the answer
Mature return portals exist that plug straight into a webshop. They handle registration, the label, communication with the customer and the refund, and on the consumer side they often do that very well. If you sell through a single channel and a return either comes back fine or it doesn't, a package like that is lighter to manage than what we build. We'd rather tell you that in the first conversation than halfway through a project.
Custom software pays for itself once the assessment itself is your core work, or when a return involves more parties than just you and your customer. Do bear in mind that you become the owner of the decision rules, and these need maintaining whenever your range, your terms or the law change. Testing, logging and maintaining integrations also become your responsibility.
Choose a standard package if
- You sell through a single channel, with the same terms for everyone
- The assessment comes down to sellable or not sellable
- Repair and repackaging are not a workflow in their own right
- Your webshop platform already includes the portal
- You don't need to monitor warranty claims to suppliers
Custom software pays off if
- The assessment has multiple grades, each with its own rules
- Repair or repackaging is a workflow that needs capacity
- You apply different terms per channel, country or customer type
- A return also involves a supplier or service partner
- You are stuck on your package vendor's roadmap
Frequently asked questions about returns management software
A return form records that a customer wants to send something back. Returns management software starts after that: the item arrives, someone assesses its condition, and that decision determines whether it goes back into sellable stock, goes to repair, continues as a warranty claim or is written off. The system links this to the order line and passes the consequences on to stock and accounting.
If you sell through a single channel and a return is always simply approved or rejected, a return portal from your webshop platform usually covers the consumer side perfectly well, and is lighter to manage than custom software. Custom software pays off when the assessment itself is your core work: multiple quality grades, repair or repackaging as a real workflow, different terms per channel, or a chain in which a supplier is involved too.
For distance sales to consumers, there is a cooling-off period of up to 14 days after the product has been delivered. After withdrawal, the consumer has 14 days to send the goods back, and the seller must refund within 14 days. There are exceptions, including made-to-order or personalised products, fast-perishable products and opened hygiene products. If the seller fails to inform the consumer about the cooling-off period, the ACM (the Dutch consumer authority) says it is automatically extended by a year.
The cooling-off period for distance sales is a consumer right. For business customers, what applies is whatever you agree in the contract: whether returns are allowed, within what period, in what condition the item must come back and whether you charge a restocking fee. This usually runs through a return number requested in advance, known as an RMA. Your software needs to know that distinction.
This happens more often than most systems can handle. The customer gets their money back, while the item goes on to the supplier because it is defective. These are two flows with their own pace: the credit note runs within a short period, while the supplier's compensation may come much later or not at all. Link them to the same item, but process them separately.
Before you sign, establish who owns the source code and the data, and ask for access to the repository and for a working export. Lock-in rarely comes from the technology itself and usually arises because knowledge is documented nowhere: make sure administrators can change the return rules themselves, ask for documentation of the integrations, and keep integrations on published interfaces.
Related services
If your question is closer to one of these, start there.
Custom webshop development
The front end where ordering and return requests begin. Size charts and product information largely determine the number of returns.
Supply chain management software
The broader management of purchasing, stock, suppliers and transport, in which returns are one of the flows. If a return goes to the waste stage and involves electrical equipment, it affects your WEEE reporting obligation.
Complaints management software
Recording and following up complaints. Complaints and returns sometimes overlap, but they are different processes.
For returns from fashion retailers, with terms per customer and season and assessment per item, there is our returns processing software for fashion wholesalers.
If you handle returns from fashion retailers, take a look at our returns app for fashion wholesalers.
Walk through your returns process with someone who knows the trade
Tell us what comes in and what happens to an item once the box is opened. Then we will look at whether your process fits an existing returns portal or whether custom development makes the difference. You get that assessment in the first conversation, even if the answer is an off-the-shelf package.