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

# Vendo

Overview of Violet's Vendo integration for channel developers

Vendo is a hosted, multi-vendor ecommerce platform built on top of Spree Commerce. Because Vendo is a managed Spree variant, the connection process and integration behavior are nearly identical to Spree with a few minor differences.

## Connection

Merchants provide a **Client ID** and **Client Secret** from an OAuth application, along with their **Store URL**. The OAuth application must be created with the `admin write` scope — the same requirement as Spree.

## Differences from Spree

| Feature                | Spree                              | Vendo                  |
| ---------------------- | ---------------------------------- | ---------------------- |
| Product categorization | `taxons`                           | `categories`           |
| Checkout flow          | Requires explicit step advancement | Advances automatically |

## Webhooks

Webhook behavior is the same as Spree — webhooks are registered automatically. Violet-originated orders are tagged with `channel = "Violet"`.

## Notable Behavior

All other behavior (discount support, API format, order submission flow) is the same as [Spree](/ecom-platforms/spree.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 by asking a question.

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

```
GET https://docs.violet.io/ecom-platforms/vendo.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.