Return Authorization Aging

A customer receives permission to return a device but has not shipped it after two weeks, while another item arrived at the warehouse and waits for inspection. Both cases are aging, but they need different next actions.

Oracle documentation describes return authorisation, merchandise receipt and credit as distinct stages, and its returns guide shows that authorisation does not itself mean the item has been received or refunded. Choose the start event, which could be the authorisation creation date or the date the customer first requests a return, and report which one is used.

Define the end event for each stage, since authorisation-to-shipment, receipt-to-inspection and receipt-to-credit have different owners and one combined age can hide where the delay sits. Group by status, so that waiting for customer shipment, carrier transit, warehouse receipt, inspection and credit are not one undifferentiated queue.

Set a meaningful age: calendar days make total elapsed time visible, while business days may aid staffing review, but use a documented convention. Record deadline rules and the effective dates of policy changes, because a return authorisation may have an expiry or shipping window under company policy, new terms should not silently overwrite those that applied at purchase, and a customer should not be assumed to lose rights merely because an internal clock expired; check applicable law and terms.

Communicate clear instructions as well, since customers need an address, label or collection plan and an authorisation without workable shipping details may be stalled by the business. Watch shipment scans, because a label created is not proof the parcel entered a carrier network, so distinguish printed label, pickup and delivery evidence.

Check partial returns: an authorisation for three items may have only two received, so count line or unit status rather than closing the entire case. Link to the order, as eligibility, payment method and original fulfilment details help resolve a return and a disconnected ticket may duplicate work.

Prioritise by consequence, since a high-value product, expiring return window or customer hardship can warrant prompt review and age alone is not the whole priority. Set an owner for each stage: service can handle customer contact, operations can confirm receipt and finance can issue a credit under controls.

Inspect promptly, because a received item may need condition grading or serial verification and delaying inspection can delay the customer's answer, while hazardous, recalled or damaged items may need special handling that should not be bypassed to speed a return. Separate refund processing, as approval of a credit and settlement to a card or bank account are distinct events, and reconcile balances because an unresolved return may affect revenue estimates, inventory and customer credits.

Report aging bands, counting cases at zero to seven, eight to fourteen and older days if those bands fit operations, and show the oldest cases as well as average age, while avoiding denominator games, since closing an authorisation without a final outcome can make the queue look smaller and explicit cancelled, denied or expired states with reasons are safer. Review bottlenecks (repeated warehouse delays may call for staffing or improved scan routing, and repeated customer non-shipment may signal unclear instructions), send helpful reminders without ignoring previous replies, share only what each handler needs because return cases may include addresses and payment details, and remember that an aging report is a snapshot of open cases while cycle time measures completed cases, so for owners the metric works when each stage has a clear clock and owner.