> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-design/design/offer.md).

# Offer

What is specific to an offer pass template: time-bound coupon, single use, Google provider and redemption channel, and the offer pass used by benefits.

Use an offer when the pass is a coupon: a one-time or time-bound discount, redeemed with a barcode or a code at the point of sale or at checkout, with an expiration date and conditions. Campaign messages can be pushed during the life of the offer.

If the pass represents stored value, use [Gift card](https://docs.thewalletcrew.io/guides-design/design/gift-card.md) instead.

This page covers only what is specific to this type. Every setting is described in the [pass template editor](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration.md), which also explains how to save and push changes.

An offer template is also what builds the separate pass of a benefit that shows an **Add to Wallet** button: see [Where the customer finds it](https://docs.thewalletcrew.io/guides-animation/engage-and-animate/benefit-templates.md#where-the-customer-finds-it).

<details>

<summary><strong>Real-world examples</strong></summary>

* A retailer sends a "20% off any t-shirt" coupon valid for two weeks, redeemed once at the till.
* A brand adds a coupon to the wallet from the benefits page, through a benefit with an **Add to Wallet** button.
* A shop announces a seasonal offer with a notification sent by an [automation](https://docs.thewalletcrew.io/guides-animation/engage-and-animate/automatisation.md).

</details>

## Layout of the two wallets

{% tabs %}
{% tab title="Apple" %}

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Fgit-blob-ec9a625653e970689cc1295399b90fef7aa09335%2Foffer-apple-architecture-editor.png?alt=media" alt="Apple tab of the offer template editor with its collapsed sections and the pass preview"><figcaption><p>Apple offer layout.</p></figcaption></figure>
{% endtab %}

{% tab title="Google" %}

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Fgit-blob-08f0a6712496c8998ad3a47f17766e68c761be47%2Foffer-google-architecture-editor.png?alt=media" alt="Google tab of the offer template editor with its collapsed sections and the pass preview"><figcaption><p>Google offer layout.</p></figcaption></figure>
{% endtab %}
{% endtabs %}

Reference documentation: [Apple Wallet passes](https://developer.apple.com/documentation/walletpasses) and the [Google Wallet offer template](https://developers.google.com/wallet/retail/offers/resources/template).

## What is specific to an offer

### On Apple Wallet

* **Discount in the header.** Put the discount or the amount left in the header fields, the only ones visible when offers are stacked.
* **Single use.** The **Voided** option of the General section marks a pass as void, for example a one-time coupon already redeemed. Set the **Expiration date** for time-bound offers.

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Fgit-blob-f6e2dcefb329003b5e3723e90655a378fff49d84%2Foffer-apple-header-fields-single-frame.png?alt=media" alt="Header fields section of the Apple tab for an offer template, with the expiry field"><figcaption><p>Header fields stay visible when offers are stacked.</p></figcaption></figure>

### On Google Wallet

* **General.** Issuer, Title (for example "20% off any t-shirt"), State, Provider and Redemption channel. The fields are listed in the [Offer settings](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/google-tab.md#offer) of the Google tab.
* **Provider.** The offer provider: the aggregator name or the merchant name.
* **State.** Set it to Completed once the offer is redeemed: Completed passes go to the archived passes.
* **Valid time interval.** The start and the end of the offer.

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Fgit-blob-49ed92f3af5fe9756be82570d06f512c5d9b7baf%2Foffer-google-general-single-frame.png?alt=media" alt="General section of the Google tab for an offer template, with the Provider and Redemption channel fields"><figcaption><p>Check that the General fields are completed, including Provider and Redemption channel.</p></figcaption></figure>

## FAQ

<details>

<summary><strong>Should an offer use an app link or locations?</strong></summary>

Only when they help. App links take customers to an app and locations surface the pass near a store: see the Other common sections of the [Google tab](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/google-tab.md). When there is no app, keep the app links empty and use standard links in the pass instead. Start with a few store locations and check the result on real devices before rolling out to all stores.

</details>


---

# 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://docs.thewalletcrew.io/guides-design/design/offer.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.
