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

# Getting Started

Start your business with OPT OnDemand

This page provides the detailed step-by-step manual for setting up your business with OPT OnDemand. Our sales representatives will guide you through the entire process. In case you don't have any associated account manager, send an inquiry to **<ecom-sales@optondemand.com>**.&#x20;

## 1. Decide on the integration method

Depending on your business needs, we will assist you in selecting the most suitable integration method. For standard e-commerce projects, we offer integration with the Shopify platform. For larger projects or ERP system connections, our API is an ideal solution. Alternatively, you can manually import orders via CSV files or utilize third-party software such as OrderDesk.&#x20;

[Integrations & Apps](/integrations-and-apps/rest-api.md)

## 2. Select products from our portfolio

An OPT sales representative will guide you through the diverse range of garment and non-garment products, assisting you in building your portfolio. You will be provided with a list of products along with SKUs and agreed prices.&#x20;

## 3. Add your products to the warehouse

In case you want to sell your own products, you can send them to us and we’ll store them in our warehouse. This may include special blank articles you want us to print on, or other products that we will pick, pack, and ship on your behalf.

[Fulfilment](/services/fulfilment.md)

## 4. Select production technologies

The production technology differs from selected blank articles in the previous steps and the type of design you intend to print. Basic garment articles support more production technologies, and you can decide the most suitable for you.

[Print production](/services/print-production.md)

## 5. Create products

Now it’s time to define what will be printed and where. We’ll need your print-ready files (the required format depends on the production technology selected in the previous step) along with the desired print placement on the chosen blank article. You can also add metadata to the products and select a template for generating previews.

{% hint style="info" %}
This step is ideal for all e-commerce projects. For API integration it’s not required — the final product details can be specified at the time the order is submitted.
{% endhint %}

## 6. Define the shipping

We offer tracked, untracked, and express shipping options globally, partnering with the world's leading delivery companies to ensure reliable service. Chose the most suitable options for you.&#x20;

[Shipping](/services/shipping.md)

## 7. Order processing

Everything is now ready to complete the integration. Order processing depends on the type of integration selected in the first step. For detailed information, please refer to the guides for each integration type.

## Have any technical question?

{% hint style="info" icon="phone" %}
Schedule a talk with CTO <https://meetings-eu1.hubspot.com/michal-kejzlar>
{% 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 by asking a question.

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

```
GET https://docs.optondemand.com/getting-started.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.
