> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/legacy-features/how-to-configure-legacy-offers-legacy.md).

# Configure Legacy Offers (Legacy)

| **⚠️ Limio now supports Offers as a standalone object. This is particularly useful if you manage a lot of Offers. See** [**How to create Decoupled Offers (Beta Feature)**](https://docs.limio.com/product/pricing/how-to-create-offers-and-add-ons-to-attach-to-pages#attaching-offers-to-pages-via-an-offer-label)**.** |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

An offer defines how a product will be sold to the customer. It will include the price but also presentational and marketing information. Offers are powerful ways to sell any kind of physical or digital product, whether by subscription or as a one-time transaction. Here is how to configure your offers in Limio.

**Offer Tabs:** Each offer will have the following tabs: attributes, products, attachments and associations.

## Attributes:

Some of the key fields to configure are:

* **Display Name:** how the Offer will be displayed to the customer on the Limio Shop; also visible on Checkout.
* **CTA:** the CTA displayed to the customer on the Limio Shop.
* **Offer Features:** the list of features displayed to the customer on the Limio Shop.
* **Display Price:** the price displayed to the customer on the Limio Shop; also visible on Checkout.
* **Detailed Display Price:** the fine print of the price displayed to the customer on the Limio Shop.
* **Payment Types:** the payment methods available for an offer and displayed to the customer on the Limio Shop Checkout, e.g. Credit Card, Direct Debit, Apple Pay/Google Pay, PayPal (only available for one-off products).
* **Description:** Optional, used for the 'Learn More' part of the offer component.
* **Group:** Optional, used if you'd like to bucket offers together on the offer component.

Subscription fields, such as pricing and term fields, will be driven by the billing system, such as Zuora. Read more on [https://docs.limio.com/integrations/zuora-integration/manage-your-pricing/how-to-configure-subscriptions-in-limio-offers-with-initial-price-and-zuora-rate-plans](https://docs.limio.com/integrations/zuora-integration/manage-your-pricing/how-to-configure-subscriptions-in-limio-offers-with-initial-price-and-zuora-rate-plans "mention").

| **How the Offer is set up in Limio**                                                                         | **How it would be displayed on the Limio Shop**                                                              |
| ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
| ![Screenshot\_2019-10-25\_at\_11.37.14.png](https://limio.zendesk.com/hc/article_attachments/11707030934173) | ![Screenshot\_2019-10-25\_at\_11.37.26.png](https://limio.zendesk.com/hc/article_attachments/11707030935325) |

**Reminder**: Custom fields can be added via **Config > Templates** (see [Templates and Custom Attributes](/product/settings/config-settings/templates-and-custom-attributes.md))

## **Products**

A product is what marketers intend to sell, the raw material, it can be a physical product or a service. It is then used either for one-off or subscription offers. It has its own set of Attributes based on the Product’s Template.

Product will typically be mapped to a product or SKU in the billing system. If you are using Zuora, read more on [https://docs.limio.com/integrations/zuora-integration/manage-your-pricing/how-to-configure-zuora-product-code-sku-in-limio](https://docs.limio.com/integrations/zuora-integration/manage-your-pricing/how-to-configure-zuora-product-code-sku-in-limio "mention")

Products now also references rate plans from the billing system. See [https://docs.limio.com/integrations/zuora-integration/manage-your-pricing/how-to-configure-subscriptions-in-limio-offers-with-initial-price-and-zuora-rate-plans](https://docs.limio.com/integrations/zuora-integration/manage-your-pricing/how-to-configure-subscriptions-in-limio-offers-with-initial-price-and-zuora-rate-plans "mention")

## **Attachments:**

Here you can add any images to display on the offer (see [Add Images to Offers (Legacy)](/product/legacy-features/how-to-configure-legacy-offers-legacy/how-to-add-images-to-offers-and-display-them-on-the-page.md)).

## **Associations:**

| **⚠️ Note:** Associations are set to be retired and replaced by Campaigns and Journeys (see for example: [Create Personalised Switch Experience](/product/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account/how-to-create-a-personalised-switch-upgrade-or-downgrade-experience.md). If you plan on using Associations, please contact <support@limio.com>. |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

Here you can add any link you want to create between offers (e.g. rescue, upsell, cross-sells).

This guide is meant to quickly show you how to configure your offers - for more tips on offers and to learn more about enhanced features visit our [Offers User Guide section](https://docs.limio.com/product/legacy-features/page-builder-v1-overview-of-key-features-components-style-fonts-references-legacy).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.limio.com/product/legacy-features/how-to-configure-legacy-offers-legacy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.