> For the complete documentation index, see [llms.txt](https://replai-1.gitbook.io/replai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://replai-1.gitbook.io/replai-docs/use-cases/e-commerce.md).

# E-commerce

## E-commerce

E-commerce teams use Replai for product, policy, and order questions.

The best setups combine approved content with a small set of approved actions.

### What should you connect first

Start with the content customers ask for most:

* Shipping pages
* Return policies
* Product and catalog content

Then add actions only where customers need live account or order data.

### Which tier fits best

Use **Agent** for self-serve operations.

Use **Live** when high-value orders should escalate to people.

### Which action is ready to use

**Check order status** is the shipped template.

Shipping, tracking, and returns actions are examples of custom workflows.

{% hint style="warning" %}
Keep visitor confirmation on for any action that changes data.
{% endhint %}

### Related links

* [Agent tier](/replai-docs/features-by-tier/agent-tier.md)
* [Live tier](/replai-docs/features-by-tier/live-tier.md)
* [Support deflection](/replai-docs/use-cases/support-deflection.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://replai-1.gitbook.io/replai-docs/use-cases/e-commerce.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.