> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/faq/cart-and-checkout/how-do-i-let-customers-send-a-gift-card-to-someone-else.md).

# How do I let customers send a gift card to someone else?

Turning on the gift card recipient form in Volume so customers can send a gift card by email with a message.

Shopify can email a gift card straight to a recipient, with a personal message and a delivery date — but only if the theme renders the recipient form. In Volume that form is a checkbox on the **Buy buttons** block, not a block of its own, and it is **off by default**.

{% stepper %}
{% step %}

### Open the Buy buttons block

In **Customize**, open the product template, expand the product section and select the **Buy buttons** block.
{% endstep %}

{% step %}

### Tick "Show recipient information form for gift card products"

The theme's own hint explains it: "Gift card products can optionally be sent direct to a recipient along with a personal message." The form only renders on gift card products, so leaving it on changes nothing for your regular products.
{% endstep %}

{% step %}

### Check a gift card product

On the storefront you should now see a checkbox reading **I want to send this as a gift**. Ticking it opens four fields: **Recipient email** (required), **Recipient name**, **Message** (200 characters maximum) and **Send on (optional)**, which takes a date in YYYY-MM-DD form.
{% endstep %}
{% endstepper %}

### Changing the wording

All of those labels come from the theme's default content, not from the theme editor. Edit them under **Online Store → Themes → … → Edit default theme content** and search for "recipient". Every language you sell in needs its own translation.

{% hint style="warning" %}
With the recipient form enabled, Volume hides the dynamic checkout buttons on gift card products even if **Show dynamic checkout buttons** is ticked. That is deliberate: **Buy now** and Shop Pay skip the product form, so the recipient details would be lost. The gift card still adds to the cart normally.
{% endhint %}

{% hint style="warning" %}
The form appears only on products created as gift cards in Shopify. A regular product sold as a gift voucher will not show it, and neither will a gift card product on a template whose **Buy buttons** block still has the setting off — see [I added a block but it does not show on the product page](/docs/volume-themes/faq/products-and-variants/i-added-a-block-but-it-does-not-show-on-the-product-page.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staylime.com/docs/volume-themes/faq/cart-and-checkout/how-do-i-let-customers-send-a-gift-card-to-someone-else.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.