> For the complete documentation index, see [llms.txt](https://docs.bogos.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bogos.io/quick-start-guide/understanding-basic-terms.md). # Understanding basic terms Get used to these basic terms in BOGOS before creating offers ## On this page * [Gift product](#gift-product) * [Cart value condition](#cart-value-condition) * [Cart quantity condition](#cart-quantity-condition) * [Specific product condition](#specific-product-condition) ## Gift product Gift product is the free/discounted product your customers will receive when their carts meet the conditions of your offer. How it is created: * When you select a product to be the gift, the app will clone a new product from your original product. That product will be sent to your customer once they meet the condition of your offer. * The gift product will be hidden on the online store. ## Cart value condition This condition requires customers to reach a certain cart value to get gifts. > Buy $100 to get gift ## Cart quantity condition This condition requires customers to have a certain cart quantity to get gifts. > Buy 5 products to get gift ## Specific product condition This condition requires customers to purchase specific products to get gifts. > Buy product A to get gift B You can start installing BOGOS and create new gift campaigns for your store now! --- # 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.bogos.io/quick-start-guide/understanding-basic-terms.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.