> 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/help-center-live-nl/apps-integrations/shopify/online-store/cart-verification-script.md).

# Script voor winkelwagenverificatie

Afspraken in de winkelwagen kunnen niet meer beschikbaar zijn als iemand anders eerst hetzelfde tijdslot boekt.

De **Script voor winkelwagenverificatie** controleert de beschikbaarheid en voorkomt dubbele boekingen door te verifiëren dat het geselecteerde tijdslot nog beschikbaar is.

{% hint style="info" %}
Wat klanten zien

Er verschijnt een kleine melding in de storefront (linksonder) wanneer Sesami de boeking valideert.
{% endhint %}

## Inschakelen / beheren

{% tabs %}
{% tab title="Online Store 2.0-thema's" %}
Deze instelling is mogelijk beschikbaar als een storefront-instelling / thema-integratieoptie, afhankelijk van de configuratie van je thema.
{% endtab %}

{% tab title="Vintage-thema's" %}
Ga naar:

**Sesami → Instellingen → Afspraken in winkelwagen valideren**

Schakel daarna het selectievakje in.
{% endtab %}
{% endtabs %}

## Opmaak

Je kunt de stijl aanpassen (kleuren, lettertypen, enz.).\
Zie: “Hoe je de stijlen van het Cart Verification Script kunt aanpassen”.


---

# 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/help-center-live-nl/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.