Integrations
Your platform, already supported.
MelQart connects through each platform’s official APIs with scoped credentials, encrypted at rest. It reads your catalog to build the market picture — and writes back exactly one thing: price changes you approved.
| Platform | Connection | Catalog sync | Approved price updates | Notes |
|---|---|---|---|---|
| Shopify | OAuth | Yes | Yes | |
| WooCommerce | API keys | Yes | Yes | |
| Salla | OAuth | Yes | Yes | |
| Zid | API token | Yes | Yes | |
| Vendure | API token | Yes | Yes | |
| Magento | API token | Yes | Planned | Catalog sync today; price updates on the roadmap. |
| Amazon | — | Planned | Planned | Marketplace coverage on the roadmap. |
| noon | — | Planned | Planned | Marketplace coverage on the roadmap. |
This table states exactly what ships today. If a cell says planned, it is a roadmap item, not a promise with a date.
How a connection behaves
Read broadly. Write narrowly.
A connected store syncs its catalog on a schedule, so your market picture stays current without you driving it. Writes are different: the only write MelQart ever performs is an approved price change, confirmed after it lands and reversible in one click.
Disconnect at any time. Your credentials are scoped to the platform’s own permission model and removed when you delete the integration.
Before you connect anything
See what MelQart sees — no connection required.
The free audit reads your public storefront only. Your live price ladder in about a minute, before you share a single credential.