From a vast rewards catalog to a more legible path to an item.

My focus was a clearer route through categories and a responsive shopping experience. The story begins with narrowing a large catalog, then moves through item evaluation, mobile hierarchy and cart review.

The available evidence is a set of archived demonstration-program screens and implementation notes, supported by a later audit. Those sources let me discuss specific interface choices; they do not establish a before-and-after conversion result.

My focus was a clearer route through categories and a responsive shopping experience. The archived search view shows the relationship between the query, department filters, sorting and item cards.

The menu was redesigned as a drill-in pattern. This capture does not show that menu open, so I am not presenting a reconstructed drawer as evidence.

A product page has to support a decision, not just display a product. This archived view keeps the points cost, description and quantity close to the item.

The capture also exposes a tradeoff worth discussing: a nested description area on desktop can hide detail. I would test its discoverability rather than assume that a compact page is always easier.

On a narrow screen, the product image, title and points price stack in reading order. This is a crop of the actual mobile capture, not a desktop screen placed inside a phone mockup.

The long description still deserves scrutiny: responsiveness is the beginning of a usable mobile experience, not the end of it.

The cart separates editable item choices from the order summary. Quantity, removal and the wish list sit with the item; the total and checkout action form a second clear group.

These screens support an interaction walkthrough, not a before/after comparison. I would measure search refinement, item-to-cart progression and checkout abandonment in a future evaluation.

Someone may save an item, empty a cart, lack enough points or leave before confirmation. Those are product journeys too—not exceptions to a single ideal funnel.

The map combines the implementation notes with a later demonstration-program audit. It distinguishes recorded paths from audit observations and unverified recovery behavior; it does not present recommendations as shipped improvements.

The audit records a blocked checkout with two ways forward: return to the cart or continue shopping. It also documents policy acknowledgment before confirmation. These are useful seams for small, focused tests.

The new reference model tests a one-point shortfall, exact balance, missing acknowledgment and unknown data. Passing these checks does not place an order or establish tax, stock or fulfillment eligibility.

The archived screens show a consistent path through search results, item details and cart review, including a real mobile capture. They make the design choices tangible without substituting newly generated UI for the historical product.

The journey reconstruction, prototype explorations and rule tests provide ways to examine that flow today. They are labeled separately from the historical interface. No conversion, revenue or checkout-completion improvement is attributed to this work.

Keeping the item, points cost and action close together is a useful design principle, but compactness is not automatically usability. The nested desktop description and long mobile content are places where I would test whether important information is actually found.

I would carry the same scrutiny into recovery: insufficient points, an empty cart and an interrupted checkout should have understandable next steps. Those remain evaluation priorities, not claims of completed improvements.