> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/pricing-and-codes/price-codes-and-promotions.md). # Price Codes & Promotions Set up one-time charges, order quantity rules, promotional prices and extra price codes for your products. These articles cover pricing rules that sit on top of your base price list. Use them to add fixed charges, quantity limits, promotions and API-driven prices.
Cover imageCover image (dark)
One-Time PricesAdd fixed charges that don't multiply with quantity.One-Time Prices01-price-codes-one-time-prices.svg01-price-codes-one-time-prices-dark.svg
MOQ & IOCSet minimum and incremental order quantities for products.MOQ & IOC02-price-codes-moq-and-ioc.svg02-price-codes-moq-and-ioc-dark.svg
Promotional PricesShow compare prices using promotional price lists.Promotional Prices03-price-codes-promotional-prices.svg03-price-codes-promotional-prices-dark.svg
Pricing APIConnect external systems to calculate prices dynamically.Pricing API04-price-codes-pricing-api.svg04-price-codes-pricing-api-dark.svg
Additional Price CodesShow price differences between options in the configurator.Additional Price Codes05-price-codes-additional-price-codes.svg05-price-codes-additional-price-codes-dark.svg
--- # 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.mimeeq.com/pricing-and-codes/price-codes-and-promotions.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.