> 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/additional-price-codes.md).

# Additional Price Codes

Show shoppers how each option changes the price, such as +$100 for arms. Learn how to set up additional price codes and turn on price difference display.

The price difference display feature lets you show the price impact of each option directly in the configurator, so end users can see exactly how their choices affect the total price in real time. This feature is available for both **Standard** and **Modular** configurators.

***

## Overview

The price difference is always shown relative to the currently selected option. If a user has **Without arms** selected, switching to **With arms** shows **+$100**. If they switch back, **Without arms** shows **–$100**. The display updates dynamically as the user makes selections, so customers are never surprised by a change in the total.

![Configurator options showing price differences relative to the selected option](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FSmDUUAeyGOQ07CRvqqVa%2Fprice-image-1_11wlwaa.png?alt=media)

**Example use cases:**

* **Upgrades and add-ons:** a chair with or without armrests, a desk with or without a cable management tray
* **Express shipping:** offer standard vs. express delivery, with the surcharge shown immediately on the option (e.g. **+$100** for express)
* **Material or finish upgrades:** standard fabric vs. premium leather, where the premium option shows its upcharge directly on the swatch or button
* **Service add-ons:** extended warranty, white-glove installation, or custom engraving shown as a clear price addition

{% hint style="info" %}
To enable this display, you must use **additional price codes** assigned to each option value. Price code patterns alone are not sufficient. See [Using additional price codes alongside price code patterns](#using-additional-price-codes-alongside-price-code-patterns) for details.
{% endhint %}

***

## Supported widgets

<table><thead><tr><th width="59.16796875">#</th><th>Widget</th><th>Supported</th></tr></thead><tbody><tr><td>1</td><td>Thumbnail (large and small)</td><td>✅ Yes</td></tr><tr><td>2</td><td>Filter (large and small)</td><td>✅ Yes</td></tr><tr><td>3</td><td>Multichoice</td><td>✅ Yes</td></tr><tr><td>4</td><td>Number button</td><td>✅ Yes</td></tr><tr><td>5</td><td>Radio plain text</td><td>✅ Yes</td></tr><tr><td>6</td><td>Radio list box</td><td>✅ Yes</td></tr><tr><td>7</td><td>Radio with thumbnails</td><td>✅ Yes</td></tr><tr><td>8</td><td>Slider</td><td>❌ No</td></tr><tr><td>9</td><td>Color picker</td><td>❌ No</td></tr><tr><td>10</td><td>Number scale</td><td>❌ No</td></tr><tr><td>11</td><td>Input</td><td>❌ No</td></tr><tr><td>12</td><td>Upload texture images</td><td>❌ No</td></tr><tr><td>13</td><td>Text engraved</td><td>❌ No</td></tr><tr><td>14</td><td>Print on demand</td><td>❌ No</td></tr><tr><td>15</td><td>Message</td><td>❌ No</td></tr></tbody></table>

{% hint style="info" %}
Support for some unsupported widgets is planned for a future release.
{% endhint %}

***

## How to set up price difference display

### Prerequisites

Before assigning additional price codes to your options, make sure the codes exist in **Market Cost Prices** under **Pricing**. See [Pricing Overview](/pricing-and-codes/pricing-setup/pricing-overview.md) for details on how to create and import codes.

For example, to show the price difference for a chair's arm options, you might have the following codes in your MCP:

<table><thead><tr><th width="199.7265625">Code</th><th>RRP</th></tr></thead><tbody><tr><td>CHAIR-ARMS</td><td>$100</td></tr><tr><td>CHAIR-NO-ARMS</td><td>$0</td></tr></tbody></table>

{% hint style="info" %}
You can use the same codes already set up as price codes in the **Additional price code** field – you don't need to create separate codes. This is useful when you want to reuse existing codes purely for price difference display without changing how the total price is calculated.
{% endhint %}

![CHAIR-ARMS and CHAIR-NO-ARMS codes set up in Market Cost Prices under Pricing](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FEMLswfuH7AiRjKvzpqW4%2Fprice-image-2_as3loo.png?alt=media)

{% stepper %}
{% step %}

### Assign additional price codes to options

1. Go to **Option Sets** and open the relevant option set.
2. Find the option whose values you want to assign codes to.
3. In the **Additional price code** column, assign the relevant MCP code to each option value.

For the arms example, this would look like:

| Option value | Additional price code |
| ------------ | --------------------- |
| With arms    | CHAIR-ARMS            |
| Without arms | CHAIR-NO-ARMS         |

{% hint style="info" %}
If an option value has no additional price code assigned, Mimeeq automatically treats its price as zero when calculating the difference.
{% endhint %}

![Additional price codes assigned to each option value, with Show Price Difference set to Yes](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FuRTqGxHfTpYAZOTCwI98%2Fprice-image-3_avk7e2.png?alt=media)
{% endstep %}

{% step %}

### Enable price difference display on the widget

1. Open the product configuration.
2. Find the widget for the option you set up.
3. Enable the **Price difference display** setting on the widget.

Once enabled, the configurator will show the price difference next to each option value based on what is currently selected.

![Price difference display across multiple option types](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2F2N4tShuMsSWA2pRVlGmb%2Fprice-image-4_1fee8nr.png?alt=media)
{% endstep %}
{% endstepper %}

***

## Using additional price codes alongside price code patterns

If you already have prices set up using price code patterns (e.g. `{SeatSlider#priceCode}`), you can still use additional price codes purely to drive the price difference display – without affecting the total price.

When both are in use, a toggle controls whether the additional price codes are also added to the total:

<table><thead><tr><th width="59.3046875">#</th><th>Toggle</th><th>Behaviour</th></tr></thead><tbody><tr><td>1</td><td><strong>On</strong></td><td>Additional price codes contribute to both the price difference display and the total price</td></tr><tr><td>2</td><td><strong>Off</strong></td><td>Additional price codes are used only for the price difference display and do not affect the total</td></tr></tbody></table>

This is useful when your pricing is fully handled by price code patterns and you want to add option-level price transparency without double-counting.

{% hint style="warning" %}
**Important:** if you enable price difference display on a widget but the options only have price code patterns – and no additional price codes assigned – nothing will be displayed. The price difference feature compares additional price codes only.
{% endhint %}

![The Include Additional Price Codes in Total Price toggle in the product's Pricing/Codes tab](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FOQhmKzV6K7rMCCcZs4IY%2Fprice-image-5_fmhjwv.png?alt=media)

***

## Troubleshooting

**Price difference is not displaying**

* Check that the option values have additional price codes assigned in **Option Sets**. Price code patterns alone will not trigger the display.
* Verify the codes exist in **Market Cost Prices** under **Pricing**.
* Confirm the **Price difference display** setting is enabled on the widget.
* Check that the widget type is supported – see [Supported widgets](#supported-widgets).

**Price difference shows $0 for one of the options**

* This may be expected behaviour if that option value intentionally has no price difference. However, if this is unexpected, check that an additional price code has been assigned to that option value in the option set.

**Price difference is affecting the total price unexpectedly**

* If you are using additional price codes alongside price code patterns and do not want them added to the total, make sure the **Add additional price codes to total** toggle is turned off. See [Using additional price codes alongside price code patterns](#using-additional-price-codes-alongside-price-code-patterns).

***

## 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>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><tr><td><strong>CSV Templates</strong></td><td>Download templates to import Item Master data and market cost prices.</td><td><a href="/pricing-and-codes/pricing-setup/csv-templates.md">CSV Templates</a></td></tr><tr><td><strong>Promotional Prices</strong></td><td>Show compare prices using promotional price lists.</td><td><a href="/pricing-and-codes/price-codes-and-promotions/promotional-prices.md">Promotional Prices</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/additional-price-codes.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.