> For the complete documentation index, see [llms.txt](https://developer.vario-software.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.vario-software.de/cookbook/onlineshops-and-marketplaces-app/introduction.md).

# Introduction

Shop and marketplace apps connect external e-commerce platforms (Shopify, Shopware, Amazon, etc.) to VARIO ERP. They handle bidirectional data synchronisation between the platform and the ERP.

## Architecture

```
┌──────────────┐    webhooks     ┌──────────────┐    API calls    ┌──────────────┐
│   VARIO ERP  │ ──────────────► │   Shop App   │ ──────────────► │   Platform   │
│              │ ◄────────────── │  (your code) │ ◄────────────── │  (Shopware,  │
│              │   ERP API       │              │   Platform API  │   Shopify…)  │
└──────────────┘                 └──────────────┘                 └──────────────┘
```

**Outbound** (ERP → Platform): ERP webhook → queue entry → fetch from ERP → transform → push to platform

**Inbound** (Platform → ERP): Fetch from platform → transform → MultiPart Import into ERP

## What Makes Shop Apps Special

Unlike other VARIO Cloud apps, shop apps:

* **Create sales channels** — each connected shop becomes a sales channel in the ERP
* **Sync product data outbound** — articles, prices, stock levels, and images flow from ERP to the platform
* **Import orders inbound** — orders placed on the platform are imported into the ERP
* **React to ERP webhooks** — changes in the ERP trigger outbound sync via a queue
* **Store per-channel configuration** — each sales channel has its own API credentials, mapping rules, and transfer toggles

## Documentation Structure

| Section                                                                                                                              | Content                                       |
| ------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------- |
| [Getting Started](https://github.com/vario-software/dev-guides/blob/main/onlineshops-and-marketplaces-app/getting-started/README.md) | Project structure and first-app tutorial      |
| [Core Concepts](https://github.com/vario-software/dev-guides/blob/main/onlineshops-and-marketplaces-app/core-concepts/README.md)     | Sales channels, data flow, queues, webhooks   |
| [Inbound](https://github.com/vario-software/dev-guides/blob/main/onlineshops-and-marketplaces-app/inbound/README.md)                 | Order, product, and customer import           |
| [Outbound](https://github.com/vario-software/dev-guides/blob/main/onlineshops-and-marketplaces-app/outbound/README.md)               | Product, stock, price, and order-status sync  |
| [Configuration](https://github.com/vario-software/dev-guides/blob/main/onlineshops-and-marketplaces-app/configuration/README.md)     | Channel parameters, mapping, transfer toggles |

{% hint style="info" %}
For general app development topics (manifest, authentication, EAV basics, VQL syntax, local development), see the general VARIO Cloud App documentation. This guide covers only shop-specific patterns.
{% 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 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://developer.vario-software.de/cookbook/onlineshops-and-marketplaces-app/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.