> 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/support/known-issues/known-issue-limio-catalog-sync-and-editing-product-or-rate-plan-names-in-zuora.md). # Limio Catalog Sync and Editing Product or Rate Plan Names in Zuora **Situation:** Limio Catalog Sync helps to bring your Zuora Catalog in Limio ([https://docs.limio.com/integrations/keeping-zuora-and-limio-in-sync/sync-between-limio-catalog-and-zuora-catalog](https://docs.limio.com/integrations/keeping-zuora-and-limio-in-sync/sync-between-limio-catalog-and-zuora-catalog "mention")). Once in Limio, it is then possible to use the Zuora Product SKU and the Zuora Rate Plan Name on Limio Products and Limio Offers. The sync is based on the name, not the ID. This is to facilitate the setup of catalog across different environments (Dev, SIT, UAT, PreProd, Prod etc...) by using consistently the name (which doesn't change across environments) There is currently a known issue **if you edit the name of the Zuora Product SKU or the Zuora Rate Plan, then the Catalog Sync will stop working.** **Workaround:** * If you need to change the name of a rate plan: * Please duplicate the rate plan in Zuora * Make the necessary change on the new duplicated rate plan name * Trigger the Limio Sync * Change the Limio Offers to use the new duplicated rate plan * I've already edited the name of a Zuora Rate Plan - what can I do? * Please reach out to and Limio Support will manually modify the data in the Limio back-end. --- # 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.limio.com/support/known-issues/known-issue-limio-catalog-sync-and-editing-product-or-rate-plan-names-in-zuora.md?ask=&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.