> For the complete documentation index, see [llms.txt](https://design.mirakl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://design.mirakl.com/design/components/structure/panel/totalizer-panel.md).

# Totalizer Panel

A component to present important figures to the user.

<figure><img src="https://1297765105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMoZPkWOmnKvoMWGW4aeM%2Fuploads%2F9CqQ2dGK9u3PBWKO3aZ8%2FTotalizer%20Panel%20Hero.png?alt=media&amp;token=8009d0af-338d-47af-adc9-de3be94a348c" alt=""><figcaption></figcaption></figure>

## Overview

Totalizer panels are used to show and consolidate important figures for operators and sellers. It usually displays numbers that the user wants to access quickly in order to make informed decisions.

Totalizer panels are composed of a background icon and a title (mandatory) and can have a Link Button, a subtext, and a tooltip (optional). Each of them has its own loading strategy.

## Guidelines

Totalizer panels must be used within a group of 2 minimum, either above the overall content or within a sidebar.

Use a [Link Button ](/design/components/actions/buttons.md#link-button)to help users in making quick actions related to your totalizer content.

{% hint style="info" %}
A totalizer panel cannot be used within another panel.
{% endhint %}

Be consistent in using totalizers: avoid mixing different Totalizer variants within the same Totalizer group

If data isn't available, display the totalizer card in red with a dash.

## Content

Totalizer panel content should follow our [content guidelines](/content/writing-for-mirakl.md).&#x20;

The totalizer subtext should be written in noun form.


---

# 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://design.mirakl.com/design/components/structure/panel/totalizer-panel.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.