Wishlist patterns
A saved-items list can be a private parking lot, a public manifesto, or a coordinated registry. The pattern depends on whether shoppers are saving for themselves, sharing for influence, or organising other people to buy on their behalf.
Retailer default
Grid with quick-add to cart
A standard product grid filtered to the shopper's saved items, with stock and sale state baked into each tile and a coral add-to-cart button per card. The dominant pattern at large fashion and marketplace retailers.
> what's good
- +Familiar product-grid mental model, no learning curve.
- +In-stock, sale, and back-in-stock states drive timely conversion.
- +Add-to-cart on the tile turns the wishlist into a checkout shortcut.
> what's risky
- ·Without notifications the wishlist is a graveyard, items sit forever.
- ·Stock state must be live, stale data drives abandoned carts.
- ·Empty state is brutal, no room for browsing or recovery copy.
Registry default
Registry with priorities and contributors
A registry list with priority labels per item, claim and chip-in flows for guests, and a progress meter at the top. Contributors stay anonymous to each other but visible to the couple or organiser. Used by wedding, baby, and milestone registries.
> what's good
- +Priorities and group-funding remove awkwardness from gift-giving.
- +Claim and chip-in mechanics prevent duplicates without manual coordination.
- +Progress meter creates urgency near the event date.
> what's risky
- ·Priority labels are loaded social signals, easy to set wrong tone.
- ·Group-funded items need careful refund logic if the event is cancelled.
- ·Anonymous-to-guests expectations must be enforced server-side, not just hidden in UI.