> For the complete documentation index, see [llms.txt](https://docs.fulfillmenttools.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fulfillmenttools.com/documentation/getting-started/quick-implementation-guides.md).

# Quick implementation guides

The guides in this section will take you through how to quickly implement fulfillmenttools into your set up, so you can already start seeing results.

This implementation should take 1-3 weeks.

{% hint style="info" %}
We recommend starting with this set up, then adding more functionality as you go.
{% endhint %}

In these guides, we won't go into full details, you can find more information in the {Whatever} named section.

We'll guide you through connecting your online store and other parts of your infrastructure to fulfillmenttools, including:

1. Adding your first facility
2. Adding your carriers to that facility
3. Importing your inventory and stock
4. Connecting your orders to fulfillmentools
5. Creating a basic routing strategy
6. Testing and go live


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fulfillmenttools.com/documentation/getting-started/quick-implementation-guides.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.