Designing an Ecommerce Store for the Second Purchase

By Quincy Samycia

Imagine someone spending an evening choosing a coffee machine. They compare finishes, look closely at the controls, consider where it will sit, and decide whether the price makes sense. The website helps them reach a decision. They place the order.

A few weeks later, that same person returns to buy coffee for the machine or find an answer about using it. They arrive with a different level of knowledge and a more specific task. The relationship has moved forward. Has the website made room for that change?

I think this question belongs in the original ecommerce brief. Designing for the second purchase means considering what the first purchase allows the customer to stop figuring out. It also means understanding what they may need to learn next.

A returning customer should be able to build on an earlier decision. That is a useful design standard whether the next visit leads to another order, a resolved question, or a decision to come back later.

The product determines what comes next

The phrase “second purchase” needs some care. Someone buying coffee regularly has a different relationship with the catalogue from someone choosing a machine they expect to keep for years. The same person can occupy both situations within one brand.

For a frequently consumed product, a useful next visit might involve replenishment. For equipment, it could involve setup, care, compatibility, or support. Designers should understand that ownership cycle before deciding what a returning customer needs to see.

Our work at The Branded Agency for Milton Coffee Co. offers a useful starting point. The project involved refreshing the interface and copy while retaining the existing branding and photography. We developed customized Shopify product templates, supported catalogue migration and organization, and integrated a third-party design-your-own experience for the brand’s customizable coffee machines.

Those decisions establish how products and their differences are explained. When considering how an experience like this could serve an existing owner, I would start with that structure: can the customer return to the details of the product they chose and understand what is relevant to it?

That question gives the designer a more precise assignment. The next useful interaction may be buying a compatible consumable. It may be finding information that helps someone keep using a product they already value. The design should make room for both.

Keep earlier decisions visible

A customer may remember liking a product without remembering its exact name. They may recognize a finish but forget how the catalogue described it. They may know that a previous order worked well without recalling the quantity or configuration.

The interface can help preserve those decisions. A useful order record would show a recognizable image, the product name, the selected options, and what was included. The customer should be able to connect that record to the item they own.

This follows Nielsen Norman Group’s explanation of recognition and recall in interface design: making relevant information visible gives people cues they would otherwise have to retrieve from memory. The principle applies to the content we show as well as the controls we design.

For a returning shopper, this means showing the details needed to identify a previous choice. An order number alone cannot explain whether the customer selected the smaller pack, a particular finish, or an optional attachment.

That also creates a responsibility when the catalogue changes. A renamed product or updated package should remain understandable in relation to an earlier order. If an old variant has been discontinued, the interface should explain that change and identify any suitable alternative clearly.

Continuity depends on these small details remaining legible over time.

Make buying again easy to review

A previous purchase is a useful starting point. It does not settle every decision about the next one.

Someone may want the same product in a different quantity. They may be ordering for a different address or choosing another version for someone else. Their needs may have changed since the last order.

A repeat-order action should assemble a clear, editable selection. Before committing, the customer should be able to see the exact item, current price, quantity, availability, and any choices carried forward. The interface should make it easy to correct an assumption.

This matters especially when the offer has changed. A previous order might have included a temporary discount, a bundle, or a pack size that is no longer available. Reusing that order should never leave the customer to discover the difference only after purchase.

The same thinking applies where subscriptions are appropriate. Frequency, quantity, and the next charge belong close to the controls for managing the arrangement. Someone who needs to delay a delivery should be able to understand what that change will do.

My standard for these interactions is whether the customer can complete the task with confidence. A short path that leaves its consequences unclear still asks the customer to do unnecessary work.

Give ownership a place in the navigation

The customer who already owns a product needs a clear route into the experience. Sometimes that route is an account. Sometimes it is a product page, a search result, or a link saved from an earlier order.

Useful product information should remain accessible when the customer cannot remember where they purchased or how they signed in. Someone who received the product as a gift may need the same care information as the original buyer.

Product guidance should therefore have a sensible public structure, with model names and categories that connect to the products themselves. An account can add context, such as a previous configuration or order, while the underlying information remains findable.

Within the navigation, the distinction should be practical. A person exploring a machine needs help evaluating it. An owner looking for compatible supplies or care instructions needs a direct way to reach those tasks. Both should be able to recognize their route without interpreting internal department names.

This does not require guessing the intent of every visitor. A repeat visit alone tells us little about what someone owns or wants. Clear labels and useful paths allow people to express that intent themselves.

The design challenge is to give discovery and ownership appropriate space within the same experience.

Extend the design system into everyday interactions

Once ownership is part of the brief, the scope of the interface becomes more concrete. Order details, account navigation, product guidance, and repeat-order states deserve considered layouts and content.

Including representative examples of these screens in design reviews reveals whether the typography, spacing, language, and interaction patterns can support ordinary tasks as convincingly as the main product presentation.

An order detail page, for example, has to establish a hierarchy between the product, its selected options, delivery information, and available actions. A help page has to connect a question to the right product. A subscription screen, where relevant, has to distinguish an upcoming order from the settings that govern future ones.

These are substantial design decisions. Their value comes from making the relationship easier to manage, and they deserve attention before their appearance is determined by whichever component happens to supply them.

The underlying product information matters just as much. Names, images, selected options, and compatibility details need to mean the same thing wherever they appear. A visual system can make a clear structure easier to use; it cannot supply product relationships that the team has never defined.

For me, this is a reason to involve the people responsible for the catalogue and customer support while the interface is being shaped. They can help identify which details must survive across a purchase and which questions the design needs to answer.

Choose a specific return journey to improve

There is a practical limit to what any project can address. Designing for an ongoing relationship does not require building every possible account feature or retention mechanism at launch.

I would begin with a specific situation that matters for the product. A customer wants to find the exact item they bought. An owner needs compatible supplies. A subscriber needs to change an upcoming delivery. Each situation gives the team a task it can investigate and a result it can assess.

The next question is what makes that task difficult today. The answer might be a missing product detail, an unclear label, or a page that cannot be reached from the place someone expects. It could also require a deeper change to product data or the account experience.

That sequence makes feature decisions more disciplined. A proposed shortcut has a clear purpose. A new tool has to help complete an identified task. The team can also explain why some work should happen now and some should wait.

Review the experience with someone who already owns the product

The strongest review of a return journey includes people who bring the knowledge the design is meant to support. Usability testing provides a way to observe how those people complete meaningful tasks and use the difficulties they encounter to guide revisions.

For this work, I would make ownership part of the test. Ask someone to identify a product they previously purchased, check whether a related item is suitable, or change a choice before ordering again. Where possible, use the real details they remember and a realistic record of their earlier purchase.

Observe the moments when they have to reconstruct information. Do they leave the page to check a confirmation email? Can they tell which version they own? Do they understand what will happen after selecting an action? Can they reach the information they need without assistance?

The inconvenient situations deserve attention too. Test a past item that is unavailable, an unfamiliar product name, and a customer arriving without an account. Those conditions show whether the design supports an ongoing relationship when the ideal path breaks down.

After launch, I would assess the tasks the team intended to improve: whether people can complete them, where errors occur, and what questions remain unresolved. Repeat purchasing can be part of that assessment, but it also depends on the product, the customer’s needs, price, availability, and service. A visual refresh alone does not establish why someone returned.

For an equipment owner seeking guidance, finding the right answer may be the successful outcome of that visit.

Give existing customers a clear place to continue

I want ecommerce design briefs to account for the knowledge a customer brings back. Their first purchase has already involved time, attention, and a set of choices. The next interaction should make that effort useful.

This changes which details deserve space in the design process. A recognizable order record, a relevant piece of product guidance, or an editable repeat purchase can become an important part of how the brand is experienced.

A good product gives someone a reason to return. The website has a responsibility to help them continue when they do.

Before calling an ecommerce experience complete, I would walk through it from the owner’s side. The person who has already chosen the brand should have a clear place in its design.

Quincy Samycia is co-founder and Head of Brand & Growth at The Branded Agency, where he works with teams on brand strategy and digital experiences.

 ⁠

Find more Community stories on our blog Courtside. Have a suggestion? Contact stories@dribbble.com.

内容来自 Dribbble,版权归原作者所有。

阅读原文 ↗

用 HomepageTab 新标签页关注 RSS,打开浏览器就能看到更新。

安装 HomepageTab