> 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/pricing/how-to-manage-offers-and-add-ons-versions-with-publish.md). # Manage Versions with Publish For offers and add-ons to appear in **purchase links**, in **Limio for Salesforce**, or to the **AI agent**, you must publish them first. Publishing creates a **version** of the offer or add-on. This versioning gives you control over the moment an update goes live. For example, you can make a change in the **Limio Catalog** that customers must not see yet. With versions, you decide when that change becomes available. Versions also keep the features that read offers consistent, such as **cross-sell** and **upsell**. These features need a published and current version of each offer. ## Which method to use There are two ways to publish an offer or an add-on. | Method | Use this method when | | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [**Publish from the catalog**](#publish-from-the-catalog) (recommended) | You sell through Limio for Salesforce, the AI agent, purchase links, cross-sells or upgrade options. Also use it when you do not build your pricing pages in Limio. | | [**Publish through a page**](#publish-through-a-page) | You use Limio pages for your pricing, or you publish many offers and add-ons at one time. | Publishing from the catalog creates a new version of one item immediately. Publishing through a page publishes every offer and add-on on that page together, which makes it the better method for a bulk change. ## Publish from the catalog Offer and add-on pages in the catalog have their own **Publish** and **Unpublish** buttons next to **Save**. This method is available in Release 116 and later. 1. Open the offer or the add-on in the **Limio Catalog**. 2. If you have unsaved edits, click **Save**. Limio publishes what the catalog holds, so you must save an edit before you publish it. 3. Click **Publish**. The new version is live immediately in: * **Limio for Salesforce** * **upgrade and downgrade options** * **cross-sells and upsells** * **purchase links** * the **AI agent** No page rebuild is necessary. {% hint style="warning" %} Shop pages do not change. A shop page shows the versions that it held at build time. To show a new version on a shop page, rebuild and publish that page. {% endhint %} ### Publish status The offer or add-on page shows one of three statuses next to the item name. | Status | Meaning | | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Draft** | The item has no published version. The channels that read published items cannot see it. | | **Published** | The published version is the same as the saved item. | | **Unpublished Changes** | The item has a published version, and you saved an edit after that. The channels still show the previous version. Click **Publish** to make your edit live. | ### Unpublish an item **Unpublish** removes the published version. The offer or add-on stays in your catalog, but the channels that read published items can no longer see it. To delete a published offer or add-on, unpublish it first. {% hint style="info" %} Your role needs the catalog publish permission. If you cannot see the **Publish** button, ask your Limio administrator. Learn more at [how-to-create-and-manage-users-teams-and-permissions](https://docs.limio.com/support/user-permissions-and-administration/how-to-create-and-manage-users-teams-and-permissions). {% endhint %} ## Publish through a page A page publish sets the version of every offer and add-on that the page holds. Use it for your pricing pages, and for a bulk change across many items. ### Step 1: Attach the offer or add-on to a page 1. Open the **Page Builder** in Limio. 2. Add the **offer label** or the **add-on label** to a page. 3. Click **Save** to confirm your changes. ### Step 2: Publish the page 1. Click **Build** > **Rebuild** to generate the latest version of the page. 2. Click **Publish** to make it live. The most recent published version of the page updates all the offers and add-ons that it references. To publish many pages together, see [Mass Build and Publish Pages](/product/page-builder/how-to-publishunpublish-your-pages-online/mass-build-and-publish-pages.md). {% hint style="info" %} Before Release 116, a dedicated publishing page was necessary for some customers. It held every offer to publish, and it is sometimes called a dummy publishing page. Customers that use only [Purchase Links](/product/checkout/how-to-configure-purchase-links.md) or Limio for Salesforce no longer need this page, because they can publish each item from the catalog. It stays useful for a bulk publish. If you keep such a page, make sure that it [is not indexed](https://docs.limio.com/product/seo/how-to-configure-the-seo-metadata-of-your-pages) and that it sits behind an [authentication](https://docs.limio.com/product/authentication/authentication-provider-per-page) gate. {% endhint %} ## Changes are live only after you publish again An edit to a published offer or add-on is not live automatically. The item moves to the **Unpublished Changes** status, and the channels continue to show the previous version. For example, you change the price of an add-on and save it in the catalog. If you do not publish the add-on again, your customers still see the previous price. To make the edit live, publish the item from the catalog. For your shop pages, rebuild and publish the pages that hold the item. ## Versions in the API Our Limio [Get Offers v2 API](https://docs.limio.com/api/catalog-api/catalog#get-offers-v2) and [Get Add-ons API](https://docs.limio.com/api/catalog-api/catalog#get-add-ons) can return the published items only, or every item in your catalog. Within the API, a version is a unique identifier, such as: ```auto version": "4dd34671f26fdbbf240560b78f7f2f54654cde72" ``` ## Related articles: [Publish/Unpublish Pages](/product/page-builder/how-to-publishunpublish-your-pages-online.md) [Can't Publish Pages](https://docs.limio.com/support/troubleshooting/i-cant-publish-my-pages) --- # 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/pricing/how-to-manage-offers-and-add-ons-versions-with-publish.md?ask=&goal= ``` `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.