> For the complete documentation index, see [llms.txt](https://help.pagefly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pagefly.io/page-structure-and-elements/shopify-elements/product.md). # Product ### About Shopify Product Elements On PageFly Elevate your Shopify store and watch conversion sour with Product elements! This suite of tools integrates seamlessly with your existing data, ensuring accurate product details like titles, variants, and pricing. Go beyond static descriptions – showcase your products in stunning detail with high-quality images and videos alongside clear variant options. Intuitive navigation guides customers with product lists for browsing, detailed pages for in-depth information, and strategically placed "Add to Cart" buttons for a smooth checkout. Advanced options like product view details and Metafields allow you to cater to specific customer needs and showcase unique product attributes. Mastering PageFly's Product Elements empowers you to showcase products effectively, enhance user experience, and ultimately boost conversions. ### Related Resources * [How to use Shopify App Block element with PageFly section](https://help.pagefly.io/manual/how-to-use-shopify-app-block-element-with-pagefly-section/) * [How to Edit PageFly Content List Element](https://help.pagefly.io/manual/content-list-element-2/) --- # 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://help.pagefly.io/page-structure-and-elements/shopify-elements/product.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.