Returns Authorisation

A customer says a device is faulty and wants to send it back, so the seller checks the order and gives a reference with return instructions, which lets staff connect the arriving package to the right customer and reason without guessing. Shopify describes an RMA process for approving, tracking and resolving returns, often using a unique number, and Oracle documentation shows how return authorisations can connect intake with later processing.

Software workflow should be adapted to the seller's legal duties and policy. Begin with the request by recording the original order, item, quantity, purchase date, reason and desired outcome, noting that the customer may ask for a refund, replacement, repair or store credit but available rights depend on law and the transaction.

Check eligibility under both law and policy, because a store's ordinary change-of-mind period may differ from rights for a defective product, and an expired voluntary window is not a blanket reason to reject a valid statutory claim. An RMA number helps match a returned parcel to the request and can appear on the label or inside the package.

Provide clear instructions on where and how to send goods, packaging, deadlines and any agreed shipping cost, since confusing instructions can increase damage or cause a parcel to arrive without an identifiable owner. Some returns are resolved without sending the item back, such as a low-value defective item under an agreed policy, and the authorisation may still record the decision.

On receipt, confirm the item and its condition, match serial numbers or quantities where relevant and document what was found, because a mismatch might be a packing error and not automatically customer fraud. Inspection supports the correct remedy and inventory disposition: a sealed, resalable item may return to stock, while a damaged or unsafe one should not, and products needing testing or supplier assessment should be quarantined.

Refund timing must follow the applicable law and payment rules, and a blanket instruction never to refund before goods are received is too strong, since in some situations an advance refund is valid or required while other cases need inspection first. Track statuses such as requested, authorised, in transit, received, inspected and resolved so the customer can learn where the case stands, because an authorisation that stays open for weeks without action is a service problem.

Link financial entries to the actual outcome, since a refund, credit note or replacement can have different tax and inventory treatment and finance should ensure the original sale, return and any new shipment reconcile. Collect reasons systematically, because a high return rate for one size may indicate misleading product information while defective batches call for quality action.

An illustrative return rate is units returned divided by units sold in a defined period, so 300 returns from 10,000 sold gives 3%, and timing should be aligned when returns arrive after the original sale period. Fraud controls should be proportionate, as serial-number checks and transaction history can prevent duplicate refunds, but a process that treats every customer as suspect can undermine legitimate rights and trust.

A return may come through a store, courier or marketplace, so coordinate channels so the same item is not refunded twice, and review open RMAs by age so cases do not disappear after the first approval. For an owner, a returns authorisation makes a messy reverse journey traceable by helping customers exercise legitimate rights and helping the business understand what came back, what remedy was given and what caused the return.