> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryoto.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Marketplace integrations

> Connect Amazon, Noon, Jumia and Trendyol so their orders join your store's queue, or run your own marketplace on OTO, and find out which setup you need.

“Marketplace” means two different things in OTO, and they are almost opposites. One is selling on someone else's marketplace. The other is running your own.

## Selling on a marketplace

Marketplace orders arrive on the same rails as your storefront's, into the same queue, subject to the same [routing](https://docs.tryoto.com/modules/omnichannel-oms/order-routing.md). Operationally there is no separate marketplace process, which is the point.

In the [channel catalog](https://docs.tryoto.com/integrations/sales-channels.md): **Amazon**, **Noon**, **Jumia**, **Trendyol** and **Trendyol International**.

> [!TIP]
>
> **Marketplaces are stricter than your own storefront, and the strictness is the risk**
>
> A marketplace sets the delivery promise and measures you against it. Late dispatch costs a seller rating, and a rating costs placement.
>
> Two things are worth setting deliberately before volume arrives: a realistic [preparation SLA](https://docs.tryoto.com/modules/hubs-management/overview.md) on the hubs that will serve marketplace orders, and [status mapping](https://docs.tryoto.com/modules/sales-channels/updates.md) that reports dispatch promptly — because on most marketplaces the clock stops when you report, not when you ship.

## Running a marketplace

The other sense: you operate the marketplace, and your sellers each need fulfillment. OTO supports this as a **master account with seller sub-accounts**, driven through the API.

| Endpoint | What it does |
| - | - |
| `POST /rest/v2/marketplace/register` | Create a seller sub-account under your master account. |
| `POST /rest/v2/marketplace/clientInfo` | Update a seller's details. |
| `GET /rest/v2/marketplace/clientInfo` | Read them back. |
| `GET /rest/v2/codTransactions` | Track each sub-account's COD wallet — balance, upcoming transfers, withdrawals and history. |

These require a marketplace token to be activated on the account. Mobile number verification for sellers is part of the same flow. See the [endpoint index](https://docs.tryoto.com/developers/rest-api-reference.md).

> [!NOTE]
>
> **COD visibility is what makes the sub-account model work**
>
> A marketplace operator carries a problem an ordinary merchant does not: money collected in cash, on behalf of sellers who each want to know when they are getting paid.
>
> `codTransactions` exposes that per sub-account through the API, which is what lets you answer it in your own seller dashboard rather than by exporting spreadsheets.

## Which one are you?

| If… | Then |
| - | - |
| You sell your own goods on Amazon, Noon, Jumia or Trendyol | Connect it as a [sales channel](https://docs.tryoto.com/integrations/sales-channels.md). Nothing else changes. |
| Other people sell through your platform and you handle fulfillment | The master account and sub-account model above. |
| Both | Both, on one account. They do not conflict. |

## Related

* [Sales channels](https://docs.tryoto.com/integrations/sales-channels.md) — the catalog.
* [Endpoint index](https://docs.tryoto.com/developers/rest-api-reference.md) — the marketplace endpoints in context.
* [Order routing](https://docs.tryoto.com/modules/omnichannel-oms/order-routing.md) — how marketplace orders get assigned.


## Related topics

- [Plans, pricing and add-ons](https://docs.tryoto.com/pricing/plans-and-packaging.md)
- [Integrations overview](https://docs.tryoto.com/integrations/overview.md)
- [Sales channel integrations](https://docs.tryoto.com/integrations/sales-channels.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.