> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/equipme/offer-management/service-portfolio/create-an-option.md).

# Create an option

{% @arcade/embed flowId="FWcktaEkeQCsfJlD8uyi" url="<https://app.arcade.software/share/FWcktaEkeQCsfJlD8uyi>" %}

#### Options and variants

Options allow you to offer the same service in different configurations without creating multiple services.

An option describes *what can vary* within a service, for example color, storage size, or performance level. Each option contains one or more variants, which represent the actual selectable values.

This makes it possible to keep your service portfolio clean while still offering flexibility where it matters.

***

#### Mapping configuration

<figure><img src="/files/Rjl2er5jLeVuDMltSf9i" alt=""><figcaption></figcaption></figure>

The mapping configuration defines how an option behaves within the service setup.

Some options belong together and describe different aspects of the same configuration. Others represent independent additions that can be added on top of a service.

Options of type **Combination** are used for variations that belong together, such as color, memory, or storage. Selected variants are treated as one combined configuration.

Options of type **Additive** are used for independent additions, such as accessories or additional services. These options do not depend on other selections and can be added individually.

Choosing the right mapping configuration helps you model real-world setups accurately while keeping services easy to maintain.

***

#### Display type for options

<figure><img src="/files/5XEm3nAlbMo13pc1cfn5" alt=""><figcaption></figcaption></figure>

When an offer contains options with multiple variants, you can control how these variants are displayed in the marketplace.

The display type does not change the logic or pricing of an option. It only affects how variants are presented to the user during selection.

***

#### Standard view

In the **Standard** view, variants are displayed as individual selection cards.

This layout is ideal when:

* the number of variants is small
* variants are visually or conceptually distinct
* you want users to compare options at a glance

The standard view works especially well for options like colors, editions, or clearly differentiated configurations.

<figure><img src="/files/Oqo2fevFtOkJM1IxqCOv" alt=""><figcaption></figcaption></figure>

***

#### Compact view

In the **Compact** view, variants are displayed inside a dropdown menu.

This layout is helpful when:

* there are many variants
* variants are similar in nature
* screen space should be kept minimal

The compact view keeps the interface clean and prevents long lists from overwhelming the user.

<figure><img src="/files/oiGUFN4WHTRPmH3hS98P" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hub.equipme.io/equipme/offer-management/service-portfolio/create-an-option.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.