> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/pricing-experiences/price-testing-integration-guides/integration-guide-using-duplicate-products.md). # Integration Guide using Duplicate Products Learn how to integrate your Shopify store with Intelligems for a Pricing Test using duplicate products. Before you can run a Price Test with duplicate products, there's a small integration to complete: 1. Add Intelligems JavaScript 2. Tag product prices 3. Hide duplicate products from collections pages (only if Shopify doesn't render your collections) 4. Configure duplicate products 5. QA your integration, and publish your changes {% hint style="info" %} Our team turns on the duplicate products integration for your store. If you've asked us to complete the integration, we'll handle most of these steps for you. {% endhint %} ### **How duplicate products work** When you save a Price Test, Intelligems creates a copy of each tested product for every non-control group. Each copy carries that group's price as its real Shopify price, so your cart, checkout and any app reading the product's price all see the test price. Duplicates are created with Shopify's Unlisted status, so shoppers won't find them in your collections, storefront search or product recommendations. They can still be added to cart. Most stores are set up with a Functions integration and don't need duplicate products. There are certain instances where duplicate products may be necessary, usually because an app on your product page reads the price straight from the product. These include: * Testing subscription prices with most subscription apps, like Recharge or Skio * Testing prices on products that use a bundle or volume discount app on the product page, like Kaching or Shrine * Testing significant product page changes --- # 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.intelligems.io/pricing-experiences/price-testing-integration-guides/integration-guide-using-duplicate-products.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.