> 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** or in **Limio for Salesforce**, they must first be **published**. Publishing creates a **version** of each offer and add-on. This versioning is important because it gives you control over when updates go live. For example, you might make a change in the **Limio Catalog** that you don’t want customers to see immediately. By managing versions, you can decide exactly when those changes become available online or in Limio for Salesforce. Versioning also ensures consistency across Limio features that depend on offers and add-ons, such as **cross-sell** and **upsell** functionality, which require published and up-to-date versions of the relevant offers. There are two ways to publish: directly from the catalog (below), or via a page (Steps 1–2). ## Publish directly from the catalog (Release 116 and later) Offer and add-on pages in the catalog have their own **Publish** and **Unpublish** buttons next to Save. Publishing an item directly creates a new published version immediately — no page rebuild required. The new version is immediately live everywhere that reads published offers and add-ons: **Limio for Salesforce**, **upgrade and downgrade options**, **cross-sells and upsells**, and **purchase links**. {% hint style="warning" %} Shop pages are unchanged: they render the versions bundled at page build time, so a rebuild and republish is still required for changes to appear on shop pages. {% endhint %} ## Step 1: Attach the offer or add-on to a page 1. Open the **Page Builder** in Limio. 2. Add the **offer label** or **add-on label** to a page. 3. Click **Save** to confirm your changes. 💡 If you are only using [Purchase Links](/product/checkout/how-to-configure-purchase-links.md)or want to update offers for Limio for Salesforce, you can create a **dedicated publishing page** (sometimes called a **dummy publishing page**) that contains all offers and add-ons you want to make available. Make sure that this page [is not indexed](https://docs.limio.com/product/seo/how-to-configure-the-seo-metadata-of-your-pages) and behind an [authentication](https://docs.limio.com/product/authentication/authentication-provider-per-page) gate to restrict access. ## Step 2: Publish the page Once the offer or add-on is attached to a 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 will automatically update all offers and add-ons it references, ensuring the latest published versions are available online and in Limio for Salesforce. ## Important: Changes are only live after republishing Edits to a published offer or add-on are not automatically live. For changes to appear on your **shop pages**, you must still **rebuild and republish** a page that contains those offers or add-ons. For Limio for Salesforce, purchase links, cross-sells/upsells and upgrade/downgrade options, you can instead publish the offer or add-on directly from the catalog (Release 116 and later). For example, if you change the price of an add-on and save it in the Catalog but don’t republish the page that includes it, your customers will still see the previous version online and in Limio for Salesforce. ## Summary | Action | Description | | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Publish from the catalog (R116+)** | Publishes the offer or add-on directly — live immediately in purchase links, Limio for Salesforce, cross-sells and upgrades. Shop pages still require a page republish. | | **Attach to a page** | Add the offer or add-on label to a Limio Page. | | **Build and publish** | Makes the offer or add-on live in purchase links and Limio for Salesforce. | | **Republish after edits** | Ensures the latest version is visible to customers. | 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) both allow you to distinguish whether you want to retrieve published offers/add-ons or all offers/add-ons in your catalog. Within the API, a version will be a unique identifier, such as: ```auto version": "4dd34671f26fdbbf240560b78f7f2f54654cde72" ``` ## Related articles: [Publish/Unpublish Pages](/product/page-builder/how-to-publishunpublish-your-pages-online.md) [https://docs.limio.com/support/troubleshooting/i-cant-publish-my-pages](https://docs.limio.com/support/troubleshooting/i-cant-publish-my-pages "mention") --- # 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.