UX case study · Speculative concept
Enhancing Nordstrom's Post-Purchase Experience
Improving purchase findability and streamlining the in-store return journey in the Nordstrom mobile app. This project began at the returns counter.
This is a speculative concept project. It is not affiliated with, commissioned by, or endorsed by Nordstrom, and it references no internal data, tools, or customer information.
This project began at the returns counter.
Chapter 01 · Overview
Why this problem matters
Nordstrom has long been recognized for exceptional customer service, and its customer-friendly return policy is one of the brand's strongest differentiators. A seamless return experience builds trust, encourages purchase confidence, and strengthens long-term loyalty.
I work on the Service Experience team at a Nordstrom store, where I process returns every shift. That vantage point gave me a repeated, close-up view of a specific moment: a customer standing at the counter, phone in hand, scrolling through their purchase history to find the order they came in to return — and then, once they find it, hesitating over what to tap next.
The return policy is excellent. The path to it in the mobile app has three points of friction:
- Reaching purchase history takes too many steps. The Purchases page is buried inside the Account section.
- Finding the right order means scrolling. Long purchase histories offer few tools to narrow the search.
- The next step is ambiguous. Once customers find their order, nothing tells them what an in-store return actually needs — so they stall, or start a return flow they don't need.
This speculative redesign addresses all three while staying inside Nordstrom's existing design language.
Scope. The redesign is limited to the digital touchpoints of an in-store return: the Home screen, the Purchases page, and the Order Details page.
A note on method. Everything here is based on the public mobile app and general patterns I noticed in my frontline role. No internal systems, data, or individual customer interactions are referenced.
Chapter 02 · The Problem
Three points of friction
The current journey, screen by screen
Six screens of the app as it stands today, from opening it to reaching the barcode a store associate needs. Two of them are where customers stall.
Home — the starting point
Nothing on the Home screen points toward a return. The journey begins by tapping Account, which is where the app hides everything to do with orders.
Account — Purchases, one level down
Purchases sits inside Account, labelled “Track, manage & return.” It is the gateway to returns, receipts, tracking and reordering, yet it takes two taps to reach.
Purchases — the scroll
This is where the customer is struggling to skim through their orders and find the item that they want to return. They find it very hard to navigate, not finding a proper filter.
The order is found — now what?
When the customer finds their specific purchase, this is where they are confused where to click on to find the details of the order.
Tapping into the order
The order region is tappable, but nothing marks it as the way in. “Start a Return” is the loudest element on screen — and for an in-store return, it is the wrong one.
Order Details — the destination
The barcode and order number the counter actually needs live here, five screens deep, behind a step the customer had to guess at.
fig. 02·1 — the current return journey, recorded on the live app
Friction 1 — Reaching purchase history
The Purchases page is the gateway to returns, receipts, order tracking, online-order pickup, and reordering — yet it sits behind the Account page:
Map — the current journey. Customers spend it stalled at this stop.
Friction 2 — Finding the right order
For customers with large purchase histories, "locate order" is the expensive step. Order cards are large, only a basic date filter is available, and finding an older purchase means scrolling through months of history — often while the counter waits.
Friction 3 — Knowing what to do next
Once a customer locates the right order, its preview presents two competing elements: a banner with a small chevron, and a prominent "Start a Return" button. For an in-store return, the barcode or order number is what the counter actually needs — but nothing on the screen says so. The button reads like the obvious next step, so customers either stall ("do I need to start the return in the app first?") or tap into a flow they didn't need. At the counter, this shows up as hesitation, back-navigation, and phones handed over on the wrong screen.
The combination — unnecessary navigation, unbounded scrolling, and an ambiguous final step — raises the effort of one of Nordstrom's most valued customer experiences.
Chapter 03 · Design Challenge
How might we…
- …make purchase history easier to reach and faster to search, without disrupting Nordstrom's existing navigation patterns?
- …make it immediately clear where the information for an in-store return lives — and what to bring to the counter?
Chapter 04 · Research & Observations
What the counter taught me
Most speculative redesigns start from an app audit. Mine started from watching the same small breakdowns repeat across shifts. Kept at the level of general patterns, three stood out:
- Scrolling at the counter. Customers regularly arrived still searching for their order, scrolling through their history while the return waited on them.
- The "which one?" pause. On the order preview, customers frequently hesitated between the banner and the "Start a Return" button — or asked directly which one they were supposed to use.
- Order numbers as the quiet fallback. When a barcode wouldn't cooperate, the order number saved the interaction — yet it's the least prominent element on the screen.
Auditing the current app
Walking the flow end to end confirmed what the counter suggested:
- The Purchases page is buried inside Account, despite functioning as the entry point for several high-value tasks.
- Customers cross multiple screens before reaching their purchase history.
- The purchase list offers limited tools for narrowing results, so effort scales with the length of a customer's history.
- The order preview gives no guidance about which element serves an in-store return.
Chapter 05 · Goals
What the redesign had to achieve
For customers
- Reach purchase history directly from the Home screen.
- Locate a specific order quickly, even in a long history.
- Understand return eligibility and know exactly what to bring to the counter.
For Nordstrom
- Improve the discoverability of a page that gateways returns, tracking, receipts, pickup, and reordering.
- Reduce friction in post-purchase interactions, supporting the brand's service reputation.
One guardrail throughout: preserve familiarity. Reuse existing Nordstrom interaction patterns and keep visual changes minimal outside the project's scope.
Chapter 06 · Design Exploration
Three ways in
I explored three navigation concepts for surfacing Purchases before selecting a direction.
Header shortcut
A Purchases icon added to the Home page header.
Pros
- Always visible without scrolling
- Fast access
Cons
- Crowds the header
- Inconsistent with existing navigation patterns
Bottom navigation tab
A dedicated Purchases tab in the bottom navigation.
Pros
- Persistent, one-tap access
- Highest discoverability
- Removes the intermediate Account screen
Cons
- Bottom-nav slots are the most contested real estate in the app
- Places a task page alongside browse-and-shop destinations
Account shortcut card
A Purchases shortcut card on the Home page.
Pros
- Minimal visual change, low effort
- Fits existing UI naturally
Cons
- Loses visibility once the user scrolls
- Easy to overlook entirely
Why Concept 2 earns the slot despite the cost. Purchases isn't a niche page — it's the gateway to returns, order tracking, receipts, pickup, and reordering, which are recurring tasks for active customers. Recurring tasks are what persistent navigation is for. The discoverability gain outweighs the cost of the slot, and the pattern is validated by competitors that already promote order history to top-level navigation.
Making room in the tab bar. Adding Purchases means an existing tab gives up its place, and the strongest candidate is the Store tab. Locating a store or checking hours is an occasional, situational task; returns, tracking, and pickup are recurring ones — and persistent navigation should serve the recurring. Store lookup relocates to the Home header, staying one tap away without holding a permanent slot.
Chapter 07 · Final Solution
The redesign
The redesign answers each friction point in turn: a shorter path to Purchases, an order list built for finding, and an order preview that makes the next step obvious.
1 — Reaching Purchases in one tap
Before
Starting an in-store return meant navigating several screens through Account before purchase history even appeared.
After
Purchases is promoted to a primary destination in the bottom navigation: one tap from anywhere in the app, with the intermediate Account screen gone from the journey. A complementary shortcut on the Home screen gives customers heading into a store a direct entry into the return journey — unlike Concept 3, it supplements persistent navigation rather than replacing it.
fig. 07·1 — reaching Purchases in one tap
- Fewer navigation steps
- Faster start to every post-purchase task
2 — Finding the right order faster
Before
Customers scrolled through large order layouts with only a basic date filter, scanning multiple screens whenever they couldn't remember the exact purchase date.
After
Two changes make the history searchable. A more compact order layout: related information is consolidated into a single order preview, so more purchases fit within one screen height and the amount of scrolling drops. More precise filtering: filters for Date, Order Status, and Seller let customers narrow their purchase history before browsing.
Filtering by order status
Separating in-store purchases
The three filters that replace the open-ended scroll
Seller — Nordstrom or Marketplace
Status — in-store purchases
Status — online orders
fig. 07·2 — finding the right order faster
- More orders visible per screen
- Less scrolling
- Faster order identification
3 — Making the next step obvious
Before
Even after finding the correct order, key return information wasn't visible. "Can I still return this?" and "Where do I find the barcode?" were the questions I heard most at the counter.
After
Two changes remove the guesswork. Return eligibility at a glance: each item states its return status on the preview itself — "Return Anytime," "Return by Sep 27" for Marketplace items, "Returned/Refunded" — so customers understand eligibility without opening the order. One destination for everything: the entire order card becomes the entry point to Order Details, where every action and detail for that purchase lives together, including the barcode and order number an in-store return needs. Redundant per-card actions are removed, so "Start a Return" no longer competes for in-store intent.
Status sits on the order, not the item — and the screen scrolls to show two of them.
Every item states its own return window, and a whole order fits without scrolling.
fig. 07·3 — making the next step obvious
- Reduced uncertainty
- Clearer return expectations
- Faster path to the barcode
Map — the redesigned journey. The marker now sits at the destination.
Chapter 08 · Measuring Success
How I'd measure success
Because this is a speculative project, I'm deliberately not claiming outcomes. If this design shipped, these are the measures I would track against the current app as a baseline:
- Time to locate a past purchase — especially orders more than 30 days old, where scrolling costs the most today.
- Taps from Home to the return barcode — the most direct read on navigation effort.
- Task success rate for finding a specific past order without assistance.
- Volume of support conversations about locating purchases, in-app and in-store.
Chapter 09 · Limitations
What this project can't claim
- No access to Nordstrom's data or research pipeline. I couldn't validate against analytics, existing research, or the actual user base.
- A frontline vantage has its own bias. I mostly see customers who already chose to return in store; online-return behavior is less visible to me.
- A moving target. The designs respond to the public app as of mid-2026; the real product evolves.
Chapter 10 · Reflection
What I learned
This project reinforced that good UX isn't always about adding new features. Often the biggest improvements come from reorganizing existing information around users' natural workflow — here, consolidating everything an order needs into one destination instead of scattering actions across the screen.
Working in Service Experience gave me a perspective an app audit alone would not have provided. Standing behind the returns counter made friction visible on both sides of the interaction — the customer's and the associate's — and the redesign aims to relieve both.
Contact