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

# カート検証スクリプト

カート内の予約は、他の人が同じ枠を先に予約すると利用できなくなる場合があります。

以下の **カート検証スクリプト** 選択した枠がまだ利用可能かを検証することで、空き状況を確認し、二重予約を防ぎます。

{% hint style="info" %}
お客様に表示される内容

Sesami が予約を検証すると、小さなストアフロント通知が表示されます（左下）。
{% endhint %}

## 有効化 / 管理

{% tabs %}
{% tab title="Online Store 2.0テーマ" %}
この設定は、テーマの構成によってはストアフロント設定 / テーマ連携オプションとして利用できる場合があります。
{% endtab %}

{% tab title="Vintageテーマ" %}
次へ進んでください：

**Sesami → 設定 → カート内の予約を検証**

次にチェックボックスを有効にします。
{% endtab %}
{% endtabs %}

## スタイリング

スタイル（色、フォントなど）をカスタマイズできます。\
参照：「カート検証スクリプトのスタイルをカスタマイズする方法」。


---

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