> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/ai-store/store-theme-store-settings-and-store-connectors.md).

# Store Theme, Store Settings & Store Connectors

### 1. Store Theme

#### **Step 1: Open Store Theme**

1. Go to **Ecom Store**.
2. Open **Store Theme**.
3. View the **active theme** and storefront preview.

#### Step 2: Configure Store Details

From the top-right section, you can update:

* Store Name
* Domain
* Subdomain
* Currency
* Warehouse Details

#### Step 3: Select or Change Theme

1. Go to **New Theme**.
2. Select a default theme if required.
3. Alternatively, use:
   * **AI Theme Builder**
   * **Classic Editor**

#### Step 4: Customize Using AI Theme Builder

1. Open **AI Theme Builder**.
2. Enter your requirements as a natural-language prompt.
3. Preview the changes.
4. Check the design in both **Web View** and **Mobile View**.
5. Modify the prompt if further changes are required.
6. Save the changes once you are satisfied.

You can customize elements such as:

* Hero section
* Colors and branding
* Store components
* Navigation
* Footer
* Other storefront sections

#### Step 5: Customize Using Classic Editor

The **Classic Editor** allows you to customize the storefront manually.

You can configure:

* Hero section
* Heading and description
* Images and image styles
* Navigation bar
* Colors and branding
* Store components
* Footer
* Privacy Policy
* Checkout type
* Custom CSS

Use the preview to check how your changes will appear on the storefront.

## 2. Store Settings

#### Step 1: Open Store Settings

1. Go to **Ecom Store**.
2. Open **Store Settings**.

#### Step 2: Configure Guest Checkout

1. Find the **Guest Checkout** setting.
2. Enable it to allow customers to place orders without creating an account.
3. Disable it if customers must create an account before placing an order.

#### Step 3: Configure Warehouse

From the **Warehouse Settings**, you can manage:

* Warehouse address
* City
* State
* PIN code
* Country
* Shipping cost configuration

Update these details whenever your warehouse information changes.

#### Step 4: Configure MCP Connection

The **MCP Connection** allows supported AI assistants to connect with your store using the Model Context Protocol.

From this section, you can:

* View the MCP API key
* Copy the MCP connection URL
* Follow the connection instructions
* Regenerate the API key
* Disable the key when required

The MCP connection can be used with supported MCP clients such as **Claude**.

## 3. Store Connectors

#### Step 1: Open Store Connectors

1. Go to **Ecom Store**.
2. Open **Store Connectors**.
3. View the available external platform integrations.

#### Step 2: Connect an External Platform

Available connectors may include:

* WooCommerce
* Shopify
* WhatsApp Business
* Zid

1. Select the required connector.
2. Follow the connection process for that platform.
3. Once connected, the connector status will change from **Not Connected** to the appropriate connected status.

#### Step 3: Synchronize Store Data

Depending on the connector, you may be able to synchronize information such as:

* Products
* Orders
* Inventory
* Store updates

The available synchronization options depend on the specific connector.

{% embed url="<https://www.youtube.com/watch?v=kGnAgV6_DRw>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/ai-store/store-theme-store-settings-and-store-connectors.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.