Conversion and checkout · UX/UI pattern guide

Wishlist and save for later

Wishlist and save-for-later patterns let users preserve interesting objects without making an immediate purchase or commitment.

Browse all patterns Scope this pattern

At a glance

What the pattern is designed to accomplish

Saved items, heart states, reminders, account sync, and cart recovery moments.

Wishlist and save for later interface pattern illustration

Planning price

€700

A starting budget anchor before discovery and technical scoping.

Typical effort

2-4 days

The implementation range depends on states, data, and integrations.

Pattern family

Conversion and checkout

Use the family to find adjacent patterns that support the same journey.

Use cases

When this pattern is a strong fit

Use the pattern when it removes a real decision or interaction burden, not simply because users recognize its visual form.

Best suited to

Long-consideration shopping, travel, property, media, and research
Products where users compare across sessions or devices
Flows that benefit from reminders, sharing, or later cart recovery

Anatomy

The essential parts of wishlist and save for later

The visual treatment can change, but these responsibilities need to remain clear.

Part 1

A clear save control with visible saved state

Define this part explicitly in the design and test it with realistic content and states.

Part 2

A durable collection that can be reviewed and edited

Define this part explicitly in the design and test it with realistic content and states.

Part 3

Useful status changes such as price, availability, or deadline

Define this part explicitly in the design and test it with realistic content and states.

Part 4

A simple route from saved intent to the next action

Define this part explicitly in the design and test it with realistic content and states.

Implementation

Design and delivery guidance

The pattern works when interaction rules, content, data, and edge cases support the same user goal.

Recommended approach

Explain whether saving requires an account and what persistence users receive.
Keep saves reversible and synchronize state reliably.
Use reminders only with explicit preference and meaningful change.

Common failure modes

Using save as a disguised email-capture mechanism
Losing anonymous saves during sign-in or account creation
Sending urgency messages when nothing relevant changed

Accessibility

Inclusive design requirements

Accessibility is part of the pattern's behavior and content model, not a visual pass added after implementation.

Minimum considerations

Expose saved state with pressed or selected semantics and text.
Announce save and removal without shifting focus.
Give repeated save buttons object-specific accessible names.

History

How wishlist and save for later emerged and who popularized it

Interface patterns usually evolve through several technologies and products. The distinction below avoids assigning a single inventor where the evidence points to gradual adoption.

Origins

How the pattern came about

Wish lists existed in gift registries, mail-order catalogs, and personal shopping notes before ecommerce. Online accounts made those lists persistent, searchable, and shareable.

Popular adoption

Who helped make it mainstream

Amazon's Wish List was already prominent alongside 1-Click by 1999 and helped establish saving as a core ecommerce account feature. Pinterest later expanded the behavior beyond shopping by making visual saving and collection-building the product itself.