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

# Cart Verification Script

The Cart Verification Script helps prevent invalid bookings by checking appointment availability and quantity in the cart before the customer proceeds to checkout.

Appointments added to the cart can become unavailable while a customer is browsing or completing checkout. Another customer may book the same slot first, the [reservation period](https://help.sesami.co/booking/availability/reservation-period.md) may expire, or the selected quantity may no longer be available.

### What does the Cart Verification Script check?

The script validates appointments in the cart to make sure:

* The selected appointment slot is still available.
* The selected quantity is valid and available.
* The [temporary reservation](https://help.sesami.co/booking/availability/reservation-period.md) for the appointment has not expired.

If an appointment is no longer available or the selected quantity is invalid, Sesami prevents the customer from proceeding to checkout until the issue is resolved.

### What does the customer see?

When Sesami detects an invalid appointment or quantity in the cart, a notification appears at the bottom of the page.

<figure><img src="https://934599958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnDgiM1CWSLWRIbhORANO%2Fuploads%2Fw6CHoTiWlzzKMqmfxJNA%2FScreenshot%202026-11-06%20at%2010.51.15.png?alt=media&amp;token=89bd92b5-b3ab-4cfb-8b91-9b531739297f" alt=""><figcaption></figcaption></figure>

## Enable/manage it

{% tabs %}
{% tab title="Online Store 2.0 themes" %}
The Cart Verification Script is enabled through the Sesami Theme App Extension. Make sure the required Sesami app block is added and enabled in your theme.

<figure><img src="https://934599958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnDgiM1CWSLWRIbhORANO%2Fuploads%2FD0ovG3dlB5XXCv5wzdHO%2FScreenshot%202026-11-06%20at%2011.02.18.png?alt=media&amp;token=5d0e4642-16e0-402d-8ce6-0f57f7d89b73" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Vintage themes" %}
Themes that do not support app extensions require manual storefront integration.

The Cart Verification Script is included with [Sesami manual integration](https://help.sesami.co/apps-integrations/shopify/online-store/manual-install.md)
{% endtab %}
{% endtabs %}

## Styling

The Cart Verification notification supports customization of its colors, fonts, and other styling options. However, the notification text cannot be modified.

See: “[How to customize the styles of the Cart Verification Script](https://help.sesami.co/apps-integrations/shopify/online-store/customize-cart-verification-script-styles.md)”.


---

# 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/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.
