> 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/knowledge/adding-sources.md).

# Adding sources

**Knowledge** in the admin. A store can hold up to **10 sources**.

<figure><img src="/files/IolHtMb8hlQOPPJx4whS" alt="Knowledge — sources on the left, the test chat on the right"><figcaption><p>Knowledge — sources on the left, the test chat on the right</p></figcaption></figure>

Supported formats: **PDF, Word, text, Markdown, CSV, and HTML** — plus links, and pasted notes. Sources are indexed for retrieval, so the assistant quotes your documents instead of guessing. More formats can be added on request.

{% embed url="<https://vimeo.com/1216097610>" %}
Where sources go, and the test chat beside them
{% endembed %}

{% stepper %}
{% step %}

#### Add a source

Attach a file, add a page, or paste a note. The counter at the top shows how many of your ten you have used.
{% endstep %}

{% step %}

#### Give it time to process

A source has to be processed before the assistant can answer from it.
{% endstep %}

{% step %}

#### Test it

Use the chat on the same screen to ask a question the new source should answer. See [Testing answers](/maker-greatstore/knowledge/testing-answers.md).
{% endstep %}
{% endstepper %}

## Choosing what to add

With only ten slots, spend them on what shoppers actually ask and your catalogue cannot answer:

* [x] Returns and exchanges
* [x] Shipping — destinations, timings, costs
* [x] Sizing and fit guidance
* [x] Care and materials
* [x] Warranty and repairs
* [x] Store locations — the assistant knows the shopper's city from their IP, so a plain list of your stores is enough for it to answer "find the nearest store to me"

{% hint style="info" %}
One well-structured document covering several topics is usually a better use of a slot than several thin ones.
{% endhint %}

{% hint style="warning" %}
An empty knowledge base is not a failure state — the assistant still answers from your catalogue and connectors. It simply cannot answer policy questions.
{% endhint %}

## What the shopper sees

When a shopper asks something your catalogue cannot answer, the assistant answers from these sources instead of guessing or deflecting — this is what powers policy answers on the product page.


---

# 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/knowledge/adding-sources.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.