> 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/get-started/the-shopper-experience.md).

# The shopper experience

Everything you configure in the admin surfaces here. This page walks the storefront side end to end, using [store.design](https://store.design) — the reference storefront running Greatstore — as the example.

{% embed url="<https://vimeo.com/1216097592>" %}
The desktop flow on the reference storefront — search, the concierge, an in-chat comparison
{% endembed %}

## The flow

{% stepper %}
{% step %}

#### Search

The shopper searches your catalogue. Results resolve to real product cards — image, name, seller, price.

What powers it: whichever connectors are enabled. See [How connectors work](/maker-greatstore/connectors/how-connectors-work.md).
{% endstep %}

{% step %}

#### The concierge

The assistant can search on the shopper's behalf, narrow a long list, and explain its reasoning. On the reference storefront it's named **M.** — that's the assistant name from **Configure → Basic**.

It appears as a panel on the side, or a compact input at the bottom on mobile, depending on your **Desktop panel side** and **Mobile bottom bar** settings.
{% endstep %}

{% step %}

#### Comparison and product detail

When a shopper is weighing up options, the assistant can render an in-chat comparison rather than describing differences in prose. Product cards show live price, variants and availability.

These are apps. See [App library](/maker-greatstore/apps/library.md).
{% endstep %}

{% step %}

#### Questions the catalogue can't answer

Returns, shipping, care, sizing. The assistant answers from the documents you added under **Knowledge**, and can cite them.

See [Adding sources](/maker-greatstore/knowledge/adding-sources.md).
{% endstep %}

{% step %}

#### Bag and checkout

The shopper adds to bag and checks out. Where a storefront aggregates multiple merchants, checkout hands off per seller and completes on the seller's own site.
{% endstep %}
{% endstepper %}

## On mobile

The panel becomes a bottom bar rather than a side panel, and the concierge stays reachable while the shopper browses.

{% embed url="<https://vimeo.com/1216181217>" %}
The mobile flow on the reference storefront — search, concierge, product, bag
{% endembed %}

## Where each part comes from

| What the shopper sees                             | Where you set it                            |
| ------------------------------------------------- | ------------------------------------------- |
| Store name in the chat header                     | Configure → Basic → Brand name              |
| The assistant introducing itself by name          | Configure → Basic → Assistant name          |
| Panel colours, fonts, corner style                | Configure → Appearance                      |
| Panel on the left, right, or floating             | Configure → Appearance → Desktop panel side |
| The bottom bar on mobile                          | Configure → Appearance → Mobile bottom bar  |
| The "AI can make mistakes" line                   | Configure → Appearance → AI disclaimer      |
| Which products it can find                        | Connectors                                  |
| Policy and FAQ answers                            | Knowledge                                   |
| Comparison tables, catalogue grids, product cards | Apps                                        |

{% hint style="info" %}
The reference storefront is built on Shopify's Global Catalog MCP, which lets it search across many merchants. Your own store will typically point at your own catalogue instead — the shopper-facing behaviour is the same.
{% endhint %}


---

# 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/get-started/the-shopper-experience.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.