Skip to content
Interface language: English
Design / Signal

A gift should surprise its recipient, not reveal itself in a notification

Design a gift purchase that separates the buyer, recipient, delivery notices and the gift message.

Article language: English

Illustration of two people at a table before a large circular structure and mountains.
In this article

A surprise can end before the wrapping begins. A shop sends the recipient “Thank you for your purchase”, names the product in the subject line and leaves the price in an attachment. The wrapping paper is still a mystery; the rest is not.

Buying for someone else requires more than a “different address” field. The buyer makes the decision and wants to control the order. The recipient receives the item and may also need information to collect the parcel. They need not receive the same messages or see the same data.

Consider a fictional album shop. Marta buys an album for Jan and wants it sent directly to him with a gift message. The occasion's timing matters, but the shop does not offer delivery at a selected hour. These are our example's assumptions; the design must preserve the distinction between the buyer's wish and a confirmed service.

Do not begin by multiplying fields

First map the information flow. Marta should receive the purchase confirmation. The parcel address belongs to Jan. The recipient of a carrier notification must be determined for the selected delivery method. The gift message is text for printing; a note about entering from the courtyard is a delivery instruction. Putting both in a “message” field gives fulfilment staff no reliable basis for acting.

Separating user, buyer and payer (in Polish) helps name the roles. For a gift, assign each field its use too. “Order confirmation email - for the buyer” says more than two consecutive fields named “Email”.

Do not copy the recipient's address into the buyer's contact when the delivery option changes. The separation must survive the rest of the cart, summary and messages. A browser may suggest the buyer's own information, too. After completion, show full role names so Marta can notice if her information entered the recipient section.

In an international address form (in Polish), recipient and country affect the required information. A gift does not justify imposing a Polish template on every address. Returning to domestic delivery should not silently mix information retained from a previous choice either.

Ask only for information needed for the selected route. If the shop sends a parcel, the recipient's email need not automatically be mandatory for the shop itself. If a particular service requires it, name the reason and expected message. The buyer should understand what will be sent before supplying someone else's contact.

The same home address does not mean the same role. Marta may live with Jan and still want a surprise. Do not enable gift mode solely because addresses differ, or disable it when they match. The buyer should consciously choose who the purchase is for and which services to select. Inference from shipping data alone cannot replace that choice.

“Gift” also needs explanation. Does it mean hiding the price, special wrapping, a card with a gift message or only information for the packer? A shop may offer some of these. Show specific choices and their scope rather than promising undefined gift handling.

Test returning to an ordinary purchase too. Marta may decide not to send the album to Jan and to give it in person. Turning off the gift option must not leave a hidden instruction to message him. Equally, deleting a written gift message without warning makes another change of mind harder. Separate retaining working text in the form from approving it for fulfilment, and show which version will enter the order.

Separate the surprise from a message needed for collection

Marta may not want the album revealed early. Jan may nevertheless need a collection code or delivery contact. A design should not promise “The recipient will find out nothing” if the chosen carrier sends its own notification. Establish the flow for that method, then show its limits during selection.

Etsy describes a gift teaser: a recipient message with order and delivery information and selected content such as a gift message and product photo. It is a deliberate feature, not the same as a neutral technical parcel notice.

For our shop, prepare separate examples: a confirmation for Marta, a message Jan needs to collect the parcel and a card inside it. Identify who sends each. A shop can decide its own email, but a partner's notification requires checking that partner's actual configuration.

Shop transaction messages (in Polish) should describe confirmed status. For a gift, the design must also choose how much to reveal to each person. The buyer may need the full product and price list; the parcel recipient chiefly needs instructions for their own step.

A digital gift card follows a different path. Shopify describes a separate code message for the recipient and sent confirmation for the buyer, with a future send date in supported themes. This is a feature of the described card, not an automatic scheduling option for every physical product.

Aeneia conceptual photography

Do not combine email send date, parcel dispatch date and estimated delivery in one “Gift date” field. In our example the shop may accept a wish but does not confirm a chosen hour. The screen should say what can actually be selected. A birthday does not turn an estimated delivery into a guarantee.

During a delay, show Marta the current state and available way to agree next steps. Do not withhold information Jan needs for collection merely to preserve a surprise promise. The shop should establish beforehand which notices are necessary for receipt. If a change needs the buyer's decision, the message should go to her with the matter named and a response deadline grounded in actual support arrangements.

For delivery and in-person collection (in Polish), distinguish buyer from the person authorised to collect. Asking Jan to collect may require a different route from sending the parcel to his address. The rule must come from the shop's confirmed operation.

If the chosen method sends the collection code to Marta, show that she will need to pass it to Jan. Do not promise independent collection if necessary information reaches only the buyer. If Jan receives contact, warn Marta that a notification may disclose the shop sender. Recipient selection has a practical effect, not just a database-organising role.

A gift message is not a warehouse note

Preview the gift message as it will be printed. Preserve line breaks, signature and length limit. A separate signature field can prevent a card ending with warm wishes but no indication of the sender. Do not automatically add the buyer's name if that was not selected.

Marta may want a joint family signature different from the order details. The card preview should preserve it. If the shop offers a gift without revealing the buyer, also check the sender visible on the label, message and collection page. An empty signature does not establish anonymity across the whole route. Our basic example makes no such promise.

Name the fulfilment note separately. “Do not put a gift message here” may help when migrating an old form, but a clear pair of fields is better: card text and shop instruction. Show both in their actual roles in the summary. A warehouse worker should not have to guess whether “For Jan, do not bend” is practical poetry.

WooCommerce describes sending a customer note email when a note is marked Note to Customer. This is a specific example of a field connected to communication, not proof that every gift note behaves the same. Implementation must trace the actual field in which the text is stored.

Etsy distinguishes the packing slip for a shipment from the order receipt for the seller and says neither is an invoice for the buyer. For orders marked as gifts, the packing slip omits the breakdown of what the buyer paid. When designing your own parcel, name the specific document. “No receipt” should not replace determining which printout enters the parcel and where the buyer receives their information.

Inspect the actual set: shipping label, document inside the parcel, card and messages. An attractive web preview of a gift message does not confirm what the warehouse system prints. With several order items, establish whether the card concerns the entire parcel or a specified album.

The cart may contain an album for Jan and a notebook Marta buys for herself. Marking the whole order as a gift does not resolve the division. The shop should clearly show whether it can split parcels and attach the gift message to the right item. If it supports only one shared address and card, explain that scope before confirmation. Marta should be able to separate purchases rather than rely on a packer's guess.

Two views of the same order

Before ordering, show Marta a separate summary: her contact, Jan's address, selected services and gift message. Recipient information belongs by delivery, not only in a distant account section. If one value changes, the others must not silently return to defaults.

When correcting contact after purchase, show what the change covers. A new email may be used for a later notification but cannot recall a message already sent. In our example, support confirmation should separate saving the correction from applying it to the prepared parcel. Once a label is printed or shipment handed over, a confirmed support step is needed, not merely a green mark beside an edited address.

A project with Aeneia Design can cover the route from cart through messages and materials for both people. Start by mapping what the shop and its partners actually support. That can inform the form, summary and specific error states.

Test with separate test contacts, not a real recipient. Inspect not only the main email but also the subject, attachment and page opened by the button. In an HTML email template (in Polish), what a recipient sees without downloaded images matters too. Hiding a price in a graphic does not remove it from other parts of the message.

Follow Jan's message link too. If it leads to Marta's entire order page, it may reveal her notebook, prices or information intended only for the buyer. The recipient's view should show the necessary parcel scope. A later review request also needs an identified recipient: the person who bought an album and the person using it may answer different questions.

Finally, have a test participant acting as Marta check what she is buying and to whom the parcel goes. Then have them open Jan's route and do only what a recipient should be able to do. A good gift order joins these two flows while preserving different tasks and information scopes. The album may be a surprise; how to receive it should be clear.

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