Skip to content
Interface language: English
Design / Signal

Buy again: an old list is not yet today's order

Design a reorder that accounts for changed packaging, availability and an existing cart.

Article language: English

A woman beside a cup and folded red fabric by the water.
In this article

A “buy again” button promises a pleasant shortcut: last year's list, one click and back to work. The problem begins when a pack now contains eight items instead of ten. The same number in the cart then means a different order, even though the product name looks familiar.

A fictional bicycle rental needs numbered tags, wristbands and small station organisers. The purchaser finds an order from a year ago. Some items still exist, one has changed its packaging and one variant has been discontinued. The design should help reconstruct the needed set without pretending the catalogue stood still.

History is a starting point for a new choice

First let the customer recognise the old order. Date, reference and readable items help more than a button beside a number. The purchaser may remember buying equipment before opening a second location but not the order reference. An available product name and variant help confirm the right list.

Also test failure to retrieve complete order data. A read error does not mean all products were removed. Instead of an empty proposal with an active button, show the limit and a way to retry the read. The customer should distinguish missing purchase data from a confirmed absence of current equivalents.

Separate the historical view from today's cart proposal. History should show what was ordered then; the proposal should show what can be added now. If the old organiser was discontinued, do not silently rename it in history as a current substitute. The person would lose the ability to compare old and new.

Shopify's order-line reference includes quantity and variant identification and option fields. A historical line is more precise than a general model name. That does not mean the variant remains available; establish availability for the new action.

In our rental, the old record identifies a blue tag, a particular fastening and a number of packs. An image of the current version may help with a purchase proposal, but should not replace historical characteristics. On return the customer should see the difference, not wonder if their memory has failed again.

Establish which version of the old purchase underlies the proposal. Its quantity might later have changed or an item been cancelled before fulfilment. The customer may want to reconstruct the original intention or the set actually received. Name the chosen basis and allow inspection instead of deciding from the first number found in history.

Explain the button too. If it moves items into a cart, the message should confirm cart preparation. Repeating a list does not itself place an order. “Reordered” would be premature while the customer must still check current items and complete the purchase.

Three outcomes for old items

Before transferring, identify which items can be reconstructed unambiguously. Three outcomes matter in our example:

  • The blue tag has the same variant and sales unit. The old quantity can be proposed for checking.
  • The wristbands remain available, but the number per pack changed. The old pack quantity requires a new decision.
  • The small organiser was discontinued. Keep it visible as not reconstructed, explain why and provide a route to another product.

This is a design model, not an assumption about every shopping platform. Agree with the implementer which states can actually be recognised. If the shop only reorders whole orders or blocks a reorder when an item is unavailable, design understandable information and a next step matching that behaviour.

A missing item should not disappear in a generic “products added”. Show how many were reconstructed and which require a choice. The customer needs to know whether the list is complete or partial without counting rows against history in another tab.

Distinguish a stockout, a discontinued variant and inability to establish a current equivalent. Communicating an unavailable product (in Polish) requires the right reason and next action. “Unavailable” alone does not explain whether to wait for a return, choose another version or ask support about the data.

Do not match an old item by name alone. A new product may have a similar label while the old identifier no longer leads to an available variant. If the relationship is unconfirmed, leave the item requiring a choice. Acceptance should include that case so an accidental title match is not treated as a product match.

Show a substitute as a proposal. Similar colour and photography do not prove matching fastening or dimensions. For the organiser, the customer should inspect current data and decide. A successor relationship must come from a confirmed catalogue, not similar names.

For a larger selection, comparing specific models (in Polish) helps. Do not immediately open a comparison full of random products. Begin with the old choice's attributes and the missing information needed to replace it. The purchaser wants to resolve one change, not repeat the entire search from scratch.

A packaging change changes the number of pieces

Four old packs of ten meant forty wristbands. Four current packs of eight mean thirty-two. Copying “4” is correct copying of a digit and incorrect reconstruction of the needed quantity. Show both units when packaging affects the decision.

Aeneia conceptual photography

Establish what the customer wants to repeat: the number of packs or individual pieces. If the system can propose conversion, show the result before acceptance. With a different pack size, the exact count may require choosing between surplus and shortage. Present available choices rather than deciding silently.

With eight per pack, five boxes reproduce forty. With twelve per pack, three yield thirty-six and four yield forty-eight. The second option needs a conscious choice; rounding upward does not reproduce the old piece count exactly.

This is not a minor visual detail at the end of the cart. Unit and pack contents belong to the product catalogue data model (in Polish). If the historical record cannot establish them, explain the limit and request a check. Do not guess the old pack contents from today's photograph.

Allow quantity correction even for an unchanged item. The rental may need fewer tags than last year or only replace worn equipment. An old order is a convenient starting point, not an obligation to reproduce all stock. Show selected values and units before adding them to the cart.

If a product sells in specified multiples, explain the permitted quantity during editing. Do not silently change an entered “6” to “10” without showing what changed. A customer may accept the proposal but should understand its effect. The final quantity must also be clear in the summary.

The cart may already contain something

Before reordering, the customer may have added a new station lamp. The action on the old list should clearly state whether it adds items or replaces contents. Do not remove current work while offering a shortcut intended to save time. If a choice between sets is needed, show it before the change.

Adobe describes reordering into a nonempty cart as preserving existing products and adding reordered items. That is one system's behaviour, not a universal rule. A shop's design should name and test its actual combination behaviour.

Establish what happens when the same item is in both sets. If the cart has one pack of tags and history proposes four, the result may depend on the addition rule. The customer should see the final quantity. “Four added” alone may not remind them one was already present.

After transfer, show the current result and information about omitted or changed items. Editing quantities in the cart (in Polish) should work as in an ordinary purchase. Do not turn reordered items into a separate set that cannot be conveniently corrected before the next step.

For partial failure, distinguish added items from those the operation did not include. If the response is interrupted before confirming the result, first show the current cart or let the customer check it. Asking them to retry the whole list without identifying state can add some products twice. The customer should be able to establish the result before another attempt.

Test another click too. A customer may miss the response and press the button again. The design should specify how it shows an ongoing action and its result so it does not encourage accidental quantity multiplication. If deliberate repeated addition is available, the current contents should make its effect visible.

Buying again ends with a new check

Selected items need current data before the next decision. Cost, availability, variant and quantity should match today's offer. Contact details and delivery location may also change. Do not hide them because the previous order was once fulfilled correctly.

Do not automatically carry over old notes that may have concerned a one-off situation. Last year's delivery date or description of a particular event does not become current through copying. If a customer can reuse a note, show its origin and allow conscious reuse or editing. Product data and extra instructions need separate treatment.

If one item still needs choosing, preserve the rest of the prepared set. Returning from a substitute's page should lead to the current cart, with visible information about what is still missing. Losing correctly reconstructed items while finding one organiser defeats the shortcut.

A list of products saved for later (in Polish) differs because this route starts from an actual past purchase. A saved list may contain alternatives; here the customer has a record of a selected set and quantities. Both returns must nevertheless account for catalogue changes rather than automatically opening the first available variant.

For acceptance, prepare one old order containing an unchanged item, changed packaging and a discontinued variant. Add something to the cart beforehand. Reorder, edit quantity and return from a substitute's page. Check whether every number and omitted item has a visible explanation. That reveals more than testing an ideal order from last week.

At Aeneia Design, this route can become a shop design and its states: recognising the old purchase, selecting items, checking changes and the cart result. Historical and current product data must be established with the catalogue owner and system implementer. They determine what can honestly be reconstructed automatically.

The rental employee should end knowing how many wristbands are being ordered, which organiser was selected and what remains of the old list. Then “buy again” saves a catalogue search. Familiar numbers in the cart are not enough if the customer still has to guess how many boxes will arrive and what they contain.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear