> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-greatstore/readme.md).

# Introduction

GreatStore is an AI shopping assistant you embed on your storefront: configure it, teach it, connect it to your catalogue, and drop in one script tag.

***

## The two halves

{% columns %}
{% column width="50%" %}
**The admin**, where you set things up. Brand and persona, the documents the assistant can answer from, the connectors it searches, the apps it can render, and the metrics that come back.
{% endcolumn %}

{% column width="50%" %}
**The storefront**, where shoppers meet it. A chat panel on your own site that can search, compare, answer policy questions, and hand off to checkout.

See [Overview](/maker-greatstore/storefront/storefront.md).
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
Every setting in the admin has a shopper-visible consequence. Configuration pages in these docs carry a **What the shopper sees** section so you can check the result without switching context.
{% endhint %}

## Your store, your admin

Manage your store at [**my.greatstore.ai**](https://my.greatstore.ai). Sign in with your **Maker account**, and if you manage more than one store you'll pick which to open. Anyone in the store's organization in Maker can reach its GreatStore admin; adding or removing teammates happens through Maker's organization management, not in GreatStore itself.

{% hint style="info" %}
No store yet? Sign in at [my.greatstore.ai](https://my.greatstore.ai) and make one; see [Create your store](/maker-greatstore/get-started/create-your-store.md). You'll need Maker's Ultra plan on your organization. That's the plan GreatStore comes with, and its credits are what your store spends.
{% endhint %}

## What the assistant can draw on

| Source       | Gives it                                                        | Set up in                                                                 |
| ------------ | --------------------------------------------------------------- | ------------------------------------------------------------------------- |
| Connectors   | Products it can search and look up                              | [Overview](/maker-greatstore/connectors/connectors.md)                    |
| Knowledge    | Policies, shipping, sizing, care: anything not in the catalogue | [Adding sources](/maker-greatstore/knowledge/adding-sources.md)           |
| Apps         | Interactive experiences it can render instead of plain text     | [Overview](/maker-greatstore/apps/apps.md)                                |
| Page context | What the shopper is looking at right now                        | [JavaScript API](/maker-greatstore/developer-reference/javascript-api.md) |

## Start here

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-rocket-launch" style="color:$primary;">:rocket-launch:</i></h4></td><td><h4>Get started</h4></td><td>Go from an empty store to a live assistant, following the setup checklist.</td><td><a href="/maker-greatstore/get-started/quickstart.md">Quickstart</a></td></tr><tr><td><h4><i class="fa-sliders" style="color:$primary;">:sliders:</i></h4></td><td><h4>Configure</h4></td><td>Brand, appearance, and the origins your chat is allowed to load from.</td><td><a href="/maker-greatstore/configure/brand-basics.md">Brand basics</a></td></tr><tr><td><h4><i class="fa-plug" style="color:$primary;">:plug:</i></h4></td><td><h4>Connectors</h4></td><td>MCP servers that give the assistant something to search.</td><td><a href="/maker-greatstore/connectors/connectors.md">Overview</a></td></tr><tr><td><h4><i class="fa-code" style="color:$primary;">:code:</i></h4></td><td><h4>Developer reference</h4></td><td>The embed script, the JavaScript API, and MCP access for agents.</td><td><a href="/maker-greatstore/developer-reference/javascript-api.md">JavaScript API</a></td></tr></tbody></table>

## By what you're trying to do

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th><th data-type="content-ref"></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td><h4>Set it up</h4></td><td><a href="/maker-greatstore/get-started/quickstart.md">Quickstart</a></td><td><a href="/maker-greatstore/get-started/installation.md">Installation</a></td><td><a href="/maker-greatstore/configure/appearance.md">Appearance</a></td></tr><tr><td><h4>Make it smarter</h4></td><td><a href="/maker-greatstore/knowledge/adding-sources.md">Adding sources</a></td><td><a href="/maker-greatstore/connectors/connectors.md">Overview</a></td><td><a href="/maker-greatstore/apps/apps.md">Overview</a></td></tr><tr><td><h4>See how it's doing</h4></td><td><a href="/maker-greatstore/insights-and-usage/chats.md">Reading chats</a></td><td><a href="/maker-greatstore/insights-and-usage/weekly-insights.md">Weekly insights</a></td><td><a href="/maker-greatstore/insights-and-usage/usage.md">Usage</a></td></tr></tbody></table>

## What you get back

Conversations are recorded under **Chats**, summarised into weekly insights, and metered under **Usage**: credits, conversations, shoppers, messages, and voice minutes.

See [Reading chats](/maker-greatstore/insights-and-usage/chats.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.maker.co/maker-greatstore/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.