Accessible Returns and Exchanges Before the January Peak
Returns volume peaks right after the holidays. How to make labels, portals, and status updates usable before the rush tests them.
January is the returns peak, and returns are a stressed journey: shoppers are disappointed, deadlines are running, and many are returning gifts they did not choose, without the order details the buyer had. If the returns journey has barriers, January is when they do the most damage.
This guide covers the returns portal, label generation, and status communication, and the gift recipient case that most returns designs quietly ignore.
Design for the gift recipient, not just the buyer
A recipient often has no account, no order email, and sometimes no order number, just the item and maybe a gift receipt. A portal that demands buyer credentials before showing any path forward strands them. Offer a lookup by the details a recipient plausibly has, and a clearly labelled assisted route for the rest.
Instructions need the same treatment. A returns page written for the buyer assumes knowledge a recipient does not have. State what to include in the parcel, what happens to refunds for gifts, and whether credit goes to the recipient or the buyer, in plain steps.
Labels and forms without traps
Label generation should work by keyboard, announce errors in text tied to the field, and never depend on dragging, handwriting style inputs, or a map pin for an address. Drop off options should be listed in text with addresses, not only shown as pins on a map.
If a printable label is offered, also offer a label free option where carriers support it, such as a code shown at drop off. Printers are not universal, and a returns journey that requires one quietly excludes a slice of shoppers every January.
Status updates people can actually follow
A returns tracker that shows status only as a coloured progress graphic leaves many shoppers guessing. State each stage in words: received, inspected, refund issued, with dates. Email and text updates should carry the same words, not a link forcing a portal visit for basic facts.
Refund timing deserves a plain sentence, including that bank processing adds days after the store issues the refund. Most returns anger is uncertainty, and most uncertainty is curable with dated, written status instead of graphics.
Test returns before the peak, with peak cases
Run test returns in November for the awkward cases: gift without an account, exchange for a different size, damaged item, and a return started on a phone. Complete each by keyboard and with a screen reader, and time how long the assisted route takes to reach a human.
Staff the assisted route for January volume. An accessible portal with an overwhelmed support queue behind it still fails shoppers whose case does not fit the form. The route and the staffing are one system, and the peak tests both.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: After the Demand Letter: A Calm, Practical Response Playbook, ADA Risk in Mobile Apps and Loyalty Programs Nobody Audits, and Does Your Insurance Cover an Accessibility Claim?.
Frequently asked questions
Why design returns for gift recipients?
January returns include many recipients who lack accounts, order emails, and order numbers. A portal that requires buyer credentials strands them at the first step. A lookup using details a recipient plausibly holds, plus a staffed assisted route, covers the real caseload.
What makes a returns form inaccessible?
Unlabelled fields, errors shown only in colour, map only drop off information, drag based interactions, and a hard printer requirement for labels. Each has a simple alternative: labels, text errors, listed addresses, standard controls, and a label free drop off option.
How should return status be shown?
In dated words at each stage, received, inspected, refund issued, in the portal and in email or text updates. Graphics can accompany the words but cannot replace them, and refund wording should separate store processing time from bank processing time.
When should returns be accessibility tested?
Before the peak, ideally in November, using awkward cases: gift returns, exchanges, damaged items, and phone started returns, completed by keyboard and screen reader. January volume leaves no time to discover a stranded journey.