Create return form — capture returns in a structured way

A return form structures the return request from customers. Instead of formless emails or phone calls, it captures all relevant information in a defined path: order number, affected items, return reason, desired solution. For online shops it is mandatory — not legally but operationally. Anyone processing returns without structure loses overview, money and patience.

Besides efficiency, a return form brings a second advantage: data. If you capture return reasons systematically, you see patterns — which products come back especially often, which sizes fit poorly, which descriptions raise wrong expectations. These insights flow into assortment, product descriptions and image selection and reduce the return rate long-term. Ideally, the return form is not just a service tool but a continuous improvement loop.

Three fields are mandatory: order number, item selection and return reason. The order number is the bracket around all processing — without it, mapping to the original order is manual searching. Validate the format directly in the form (e.g. number of digits, allowed characters), this saves callbacks later. The return reason should be a single-choice with five to eight options, plus optional free text for special cases.

Further useful fields depending on industry: photo upload for damaged goods (proof and damage analysis in one), desired solution (refund, exchange, voucher), contact info for callbacks. Conditional logic shows fields situationally — anyone choosing "damaged" sees the photo upload, anyone choosing "does not fit" sees a size follow-up. Keep the form lean: more than seven or eight fields raise the abandonment rate without substantially improving processing quality.

After successful return registration, the second part begins: the package must come back. A professional solution automatically generates a shipping label after form submission — either prepaid (at the shop’s expense) or as an instruction for the customer. Via webhook the form can connect to shipping providers like DHL, DPD or Sendcloud so the label is immediately available as PDF.

The link between return ID and shipping tracking matters. As soon as the package arrives at the shipping provider, the status should automatically update in the internal system — "label created" → "package handed over" → "in transit" → "received". This way both the customer service team and the customer always know what phase the return is in. A simple tracking link in the confirmation email saves enormous numbers of follow-up tickets because impatient customers can check themselves.

After arrival at the warehouse, the decisive workflow begins: check goods receipt, assess condition, release refund. Define clear criteria — what counts as "like new", what as "signs of use", what as "damaged"? This classification decides whether the full refund is given, whether deductions apply or whether the return is rejected. Transparent rules communicated upfront (in the terms and in the return form) prevent disputes.

The refund itself should happen on a binding timeline — within 14 days after goods receipt is the legal standard, faster is service. Via Stripe or another payment provider, the refund can be triggered with one click. The customer notification at every step matters: "We have received your return", "We have triggered the refund", "The money is on its way to you". Silence is the conversion killer for repeat purchases — whoever is treated well in the return process buys again at the same shop with higher probability.