> For the complete documentation index, see [llms.txt](https://support.heyamplify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.heyamplify.com/bundles-and-upsell/bundles-upsell.md). # Bundles & Upsell Set up and manage bundling scenarios, including fixed product bundles, frequently bought together suggestions, mix-and-match options, and a variety of other upsell and cross-sell offers on product pages and regular pages. The integration with your Shopify store ensures that inventory is automatically synchronized and discounts are applied smoothly. ### Scenarios
Bundle as Product Bundle as ProductBundle as a Product.png
Build Your Own Bundle Page Build Your Own Bundle PageBuild Your Own Bundle Page.png
Build Your Own Bundle Section Build Your Own Bundle SectionBuild Your Own Bundle Section.png
Quantity Breaks Quantity BreaksQuantity Breaks.png
Upsell PopupUpsell PopupUpsell Popup.png
Frequently Bought Together Frequently Bought TogetherFrequently Bought Together.png
*** ### Other
AnalyticsAnalyticscard-analytics.pngAnalytics
SettingsSettingscard-settings.pngSettings
IntegrationsIntegrationscard-integrations.pngIntegrations
BillingBillingcard-billing.pngBilling
--- # 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://support.heyamplify.com/bundles-and-upsell/bundles-upsell.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.