> 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/one-time-prices.md).

# One-Time Prices

Add fixed charges that stay the same however many units a customer orders. Learn how the Ignore Product Quantity toggle works and when to use it.

The **Ignore Product Quantity** toggle, found in the **Pricing and Codes** tab, is a special pricing feature. It applies a one-time charge to your configuration, regardless of how many units of the product are ordered.

***

## How it works

When this option is checked for a specific price component:

* The charge will be added to the total only once per order
* The charge will not multiply when the customer orders multiple configurations
* For multiple-configuration orders, the system automatically distributes this one-time cost across all units

***

## Real-world example

**Scenario: custom colour upcharge for furniture**

Let's say you're configuring a chair with these components:

* **Base chair:** €1,000
* **Special paint option:** €100 with **Ignore Product Quantity** enabled

### When ordering 1 unit

* **Total price:** €1,100 (€1,000 + €100)
* **Price per unit:** €1,100

### When ordering 20 units

* **Standard calculation without this feature:** €22,000 (20 × €1,100)
* **With Ignore Product Quantity enabled:** €20,100
  * **Base chairs:** €20,000 (20 × €1,000)
  * **One-time paint charge:** €100 (applied only once)
* **Price per unit:** €1,005 (€20,100 ÷ 20)

***

## When to use this feature

This feature is ideal for:

* **Setup fees** that shouldn't scale with quantity
* **Special customisation costs** that only need to be paid once
* **Administrative charges** that apply to the entire order

***

## Benefits

* More accurately reflects true costs of certain customisations
* Provides more competitive pricing for larger orders
* Simplifies pricing for one-time services associated with the product

***

## User interface note

When the **Ignore Product Quantity** feature is used, the system displays an informational message on the finish screen:

{% hint style="info" %}
This product contains one-time extra charges of \[amount].
{% endhint %}

This message helps customers understand why the total price doesn't increase at a strictly linear rate when ordering multiple units. It provides transparency about the pricing structure and prevents confusion when customers change quantities.

***

## Related articles

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>MOQ &#x26; IOC</strong></td><td>Set minimum and incremental order quantities for products.</td><td><a href="/pricing-and-codes/price-codes-and-promotions/moq-and-ioc.md">MOQ &amp; IOC</a></td></tr><tr><td><strong>Additional Price Codes</strong></td><td>Show price differences between options in the configurator.</td><td><a href="/pricing-and-codes/price-codes-and-promotions/additional-price-codes.md">Additional Price Codes</a></td></tr><tr><td><strong>Pricing Overview</strong></td><td>Set up currencies, markets, price lists and quantity breaks.</td><td><a href="/pricing-and-codes/pricing-setup/pricing-overview.md">Pricing Overview</a></td></tr></tbody></table>


---

# 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/one-time-prices.md?ask=<question>&goal=<user_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.