> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/pt/apps-integrations/shopify/online-store/cart-verification-script.md).

# Script de verificação do carrinho

As marcações no carrinho podem ficar indisponíveis se outra pessoa reservar primeiro o mesmo horário.

O **Script de verificação do carrinho** verifica a disponibilidade e evita reservas duplicadas ao validar que o horário selecionado ainda está disponível.

{% hint style="info" %}
O que os clientes veem

Uma pequena notificação na loja aparece (no canto inferior esquerdo) quando a Sesami valida a reserva.
{% endhint %}

## Ativar / gerir

{% tabs %}
{% tab title="Temas do Online Store 2.0" %}
Esta definição pode estar disponível como uma opção de definição da loja / integração do tema, dependendo da configuração do seu tema.
{% endtab %}

{% tab title="Temas Vintage" %}
Vá para:

**Sesami → Definições → Validar marcações no carrinho**

Depois, ative a caixa de seleção.
{% endtab %}
{% endtabs %}

## Estilo

Pode personalizar o estilo (cores, fontes, etc.).\
Veja: “Como personalizar os estilos do Cart Verification Script”.


---

# 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.sesami.co/pt/apps-integrations/shopify/online-store/cart-verification-script.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.