> 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/sesami-and-shopify.md).

# Sesami and Shopify

Sesami integrates directly with your Shopify store to add booking and appointment functionality alongside your existing products.

## How Sesami Works with Shopify

Sesami uses Shopify's product system to power bookings:

* **Products become services** — you create a Shopify product with a "Duration" variant, then link it to Sesami as a bookable service
* **Orders track bookings** — when a customer books, a Shopify order is created, keeping all your revenue and reporting in one place
* **Checkout handles payment** — bookings go through Shopify's native checkout (or use Instant Booking to skip it)

## Shopify Requirements

{% hint style="warning" %}
Sesami requires one of the standard Shopify plans: **Basic**, **Shopify**, **Advanced**, or **Shopify Plus**.

The **Shopify Starter plan is not compatible** — it doesn't include an online store.
{% endhint %}

## What's Supported

| Shopify Feature         | Sesami Support                      |
| ----------------------- | ----------------------------------- |
| Online Store 2.0 themes | App embed — no code needed          |
| Legacy themes           | Supported (may need manual install) |
| Shopify POS             | Book and view appointments in-store |
| Shopify Plus            | Recommended with Premium plan       |
| Shopify Flow            | Automate tagging, workflows         |
| Shopify Markets         | Multi-language storefront support   |

## Installing Sesami

1. Go to the [Sesami page on the Shopify App Store](https://apps.shopify.com/sesami) or enter your store URL at sesami.co
2. Click **Add app** and approve permissions
3. Choose a plan — your **10-day free trial** starts immediately
4. Follow the [Quickstart Guide](https://github.com/sesamiapp/gitbook/blob/master/apps-integrations/quickstart.md) to configure your first service

## Omnichannel: Online + In-Store

Sesami bridges online and in-store experiences:

* Customers book online through your Shopify storefront
* Staff can book and manage appointments via Shopify POS
* All bookings sync to a unified calendar

This lets you convert online visitors into in-store appointments and manage everything from one platform.

## Related

* [Quickstart Guide](https://help.sesami.co/get-started/quickstart.md) — set up your first bookable service
* [Shopify POS](https://help.sesami.co/apps-integrations/shopify/pos.md) — using Sesami with Point of Sale
* [Pricing](https://help.sesami.co/get-started/about-sesami/pricing.md) — plans and pricing


---

# 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/sesami-and-shopify.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.
