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 may come back unused and immediately resaleable, or arrive damaged and fit only for spare 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, warranty or write-off.
What returns management is, and what this page does not cover
Returns management is the reverse flow of goods: a customer reports an item, it arrives, someone assesses it, and then a decision is made. That decision is the real work. With a normal order you know in advance what leaves the door; with a return you only know once the box is opened.
This page is about that flow back and the decision per item. If you are mainly looking for a returns form and a better ordering experience at the front end, that belongs under custom webshop development. If it concerns the broader control of purchasing, stock and suppliers, of which returns are only one flow, see supply chain management software. If it concerns customer dissatisfaction, complaints management software is the right page. A customer may return something happily because they ordered two sizes; another may be furious without sending anything back.
Online shops
Volume and the statutory cooling-off period set the rhythm. The question is seldom whether you accept a return, but how quickly a resaleable item is back on the shelf.
Wholesalers and distributors
Returns run on contract, not on law alone: a return number requested in advance, agreements on the condition in which the item comes back, sometimes a buy-back allowance.
Manufacturers and Brands
Here, after assessment, the item often leaves again, back to its own supplier: the start of a second process with its own claim number.
Why returns get stuck in the accounts
The pattern we encounter most often: the return is modelled as an order running in reverse. As soon as the customer registers, the system already books the stock back in and prepares the credit note. From that moment nothing adds up. The item is still on its way, 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 that by hand.
Behind that one word "return" sit four outcomes, each with its own administrative tail. The item goes back into sellable stock unharmed. It goes to repair or repackaging, and is then neither sellable nor written off. It proceeds as a warranty claim, after which the flow of goods and the flow of money separate. 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 rising: transport there and back, receipt, assessment, cleaning or repackaging, photographing again, financial processing. Together these often exceed the margin, and what comes back most often is rarely cheap. You can only steer once the reason is fixed per item. "Did not meet expectations" is not a reason but a summary; the difference between "size ran small", "description was inaccurate", "arrived damaged" and "wrong item delivered" points to four different departments.
Three grounds for a return, three different obligations
A return arrives on one of three grounds, and that determines who pays what, which deadline applies and whether you may refuse. That distinction belongs in the system, not in the head of whoever opens the box.
The statutory cooling-off period applies to distance sales to consumers. According to the Authority for Consumers & Markets, the consumer has a cooling-off period of up to 14 days after the product has been delivered, then 14 days to send it back, and the seller must refund within 14 days. Exceptions apply, including for made-to-measure or personalised products, rapidly perishable goods and opened hygiene products. If you do not inform the customer of the cooling-off period, the ACM says it is automatically extended by a year. The clock therefore runs from the delivery date, and the evidence that you informed the customer correctly must be easy to retrieve.
Warranty follows 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 it to do, and the seller remains accountable for that. A warranty return has no cooling-off clock, but it does have a purchase date, a serial number or batch, and a technical assessment.
Goodwill is the third ground: a more generous arrangement that you set yourself. It rests on your terms, not on the law. You may refuse a goodwill return, attach conditions to it or refund 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 you intended.
For business customers there is no statutory cooling-off period but the contract applies: a return number requested in advance, usually called an RMA, agreements about the condition in which the item comes back, and sometimes a buy-back fee. If you sell to both groups, two sets of rules run side by side.
- Record the ground at registration, do not infer it afterwards
- Calculate deadlines from the delivery date
- Flag exceptions per item or category
- Retain serial number or batch for warranty and recall
- Log who assessed what, when and why
What returns management software must be able to do
These components are linked: the reason given 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 maintain yourself: short enough to be filled in, specific enough to point a department to the cause.
Receipt and identification
The warehouse scans what arrives and matches it against the registration. Discrepancies are more the rule than the exception: a different item, an empty box, two units instead of one.
Assessment with your own grades
Not approved or rejected, but the grades your range requires: unused, opened but complete, signs of use, defective, incomplete. For each grade it is fixed what follows.
Repair and repackaging
An item in cleaning, repair or repackaging cannot be sold for a while and has not been written off. That in-between state deserves its own stock status, or it will surface as a stock discrepancy.
Financial settlement
A credit note linked to the original invoice line, including partial returns and the shipping costs you refund.
Warranty claims to the supplier
If the item is passed on to your supplier, a second case runs with its own claim number and deadline. Without tracking, such a claim can lapse unnoticed.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →The integrations that make a returns process truly add up
Returns management is rarely 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 supplies location and stock status and receives the outcome back, including the in-between state of items under repair. With the carrier you generate return labels and track the shipment, which records when the customer handed over the parcel. Accounting receives the credit note.
For identification across the chain, it helps to connect to 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 development is not the answer
Mature returns portals exist that plug directly into a webshop. They handle the registration, the label, customer communication and the refund, and for the consumer side they often do this very well. If you sell through a single channel and a return is either good or not good when it arrives, such a package is lighter to manage than anything we would build. We would rather say that in the first conversation than halfway through a project.
Custom software pays for itself once the assessment itself is your 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 to be maintained whenever your range, your terms or the law changes. Testing, logging and maintenance of the integrations also fall to you.
Choose a standard package if
- You sell through one channel, with the same terms for everyone
- The assessment comes down to sellable or not sellable
- Repair and repackaging are not a workflow of their own
- Your webshop platform already includes the portal
- You do not need to track warranty claims to suppliers
Custom development pays off if
- The assessment has several grades with their own rules
- Repair or repackaging is a workflow with real capacity behind it
- You apply different terms per channel, country or customer type
- A return also involves a supplier or service partner
- You are locked into the roadmap of your parcel provider
Frequently asked questions about returns management software
A returns form records that a customer wants to send something back. Returns management software starts from there: the item arrives, someone assesses its condition, and that decision determines whether it goes back into saleable stock, goes to repair, proceeds as a warranty claim or is written off. The system links this to the order line and passes the consequences through to stock and accounting.
If you sell through a single channel and a return is always either approved or rejected by you, a returns portal attached to your webshop usually covers the consumer side well, and it is lighter to manage than custom development. Custom development pays off when the assessment itself is your work: multiple quality grades, repair or repackaging as a genuine workflow, different terms per channel, or a chain in which a supplier is also involved.
For distance selling to consumers, there is a cooling-off period of up to 14 days after delivery of the product. Once the contract is dissolved, the consumer has 14 days to return the goods, and the seller must refund within 14 days. There are exceptions, including for made-to-measure or personalised products, perishable goods and opened hygiene products. According to the ACM, if the seller does not inform the consumer about the cooling-off period, it is automatically extended by one year.
The cooling-off period for distance selling is a consumer right. For business buyers, what you agree contractually applies: whether returns are permitted, within what timeframe, in what condition the item must come back and whether you charge a restocking fee. This is usually handled through a return number requested in advance, known as an RMA. Your software needs to recognise that distinction.
This happens more often than most systems can handle. The customer gets their money back, while the item still goes on to the supplier because it is defective. Two flows that run at their own pace: the credit note is processed within a short period, while the supplier's compensation may come much later or not at all. Link them to the same item, but settle them separately.
Before you sign, confirm who owns the source code and the data, and ask for access to the repository and a working export. Getting locked in rarely comes from the technology itself; it usually happens because knowledge isn't written down anywhere. Make sure administrators can adjust 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.
Webshop development
The front end where ordering and return requests begin. Size charts and product information account for a large share of returns.
Supply chain management software
The broader control of purchasing, stock, suppliers and transport, of which returns are one flow. If a return goes to the disposal stage and involves equipment, it affects your WEEE return.
Complaints management software
Registering and following up on complaints. A complaint and a return sometimes overlap, but they are separate processes.
For returns from fashion retailers, with terms per customer and season and assessment per piece, there is our returns processing software for the fashion wholesale sector.
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. We will then assess whether your process fits an existing returns portal or whether custom development makes the difference. You will get that assessment in the first conversation, even if the answer is a package.