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

# Introduction

**Flow Retail offers a range of extensions that add specialized functionality tailored to specific business needs.**

Whether you need customer counting, subscription billing, loyalty programs, or shipping integrations, extensions let you expand Flow Retail's capabilities without building custom solutions.

**Most extensions are quick to configure and can be activated within hours.**

They typically include a one-time setup fee and ongoing monthly costs, though pricing varies by extension type and usage. If pricing information isn't listed on a specific extension page, contact Flow Retail for details.

For more details, get in touch at <https://www.flowretail.com/contact>


---

# 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.flowretail.com/docs/extensions-addons/introduction.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.