ERP integration and marketplace integration in one engine — keep your ERP as the single source of truth and sync it, both ways, with 88 connectors across marketplaces, e-commerce platforms, couriers, invoicing systems and price feeds. Multichannel inventory sync with oversell protection and idempotent order ingestion. Connectors for Acumatica, eMAG, Trendyol, Amazon, Shopify and more.
Request a demo or an integration → office@megzo.biz · Live catalogue → vortex.megzo.biz · Connectors · Architecture
One source of truth. Every channel. Zero double entry.
About this repository. This is the public overview of MEGZO Integrator Vortex — the catalogue, the architecture, and how the platform is organised. It is intentionally a documentation-only repository: it ships the connector inventory and high-level documentation, not the connector implementations, engine internals, or any credentials. MEGZO IV is a managed commercial service, not an open-source product. To evaluate or onboard, contact office@megzo.biz.
If you sell on more than one channel, your team re-keys the same data in two places. A price changes in the ERP — someone updates eMAG, Trendyol, the webshop, the price feed. An order lands on a marketplace — someone types it into the ERP as a sales order. Stock drifts, you oversell, and a refund (plus a reputation hit) follows.
Middleware that "connects everything" usually hardcodes each pair, so every new channel is a new project, and the integration logic rots as the channels evolve.
MEGZO IV treats every system — your ERP, every marketplace, every courier, every invoicing provider — as a connector that declares its capabilities behind one interface. The engine never knows it is talking to "an ERP" or "a marketplace"; it only knows capabilities (read a catalogue, ingest an order, publish an offer, sync stock, push an AWB, render a feed…). A tenant's integration is then configuration, not code: a set of flows wiring one connector's source capability → a canonical model → another connector's sink capability.
┌────────────┐ canonical model ┌────────────┐
│ SOURCE │ ──────────────────────▶ │ SINK │
│ connector │ (offer / order / │ connector │
│ (e.g. ERP) │ stock / shipment) │ (e.g. eMAG)│
└────────────┘ └────────────┘
▲ │
└────────── one engine, per-tenant ─────┘
mapping + flow config
The payoff: adding a new system is a manifest + an adapter + a catalogue row + a passing conformance test. No engine changes. Every marketplace's orders pour into the same ERP sink. That is why the catalogue below keeps growing without the core moving.
- Offers & pricing — publish products and prices from the ERP to each channel, with per-tenant pricing rules.
- Stock sync with oversell protection — push availability with a safety buffer; reconcile drift. Mandatory, not optional.
- Order ingestion — channel orders become ERP sales orders, idempotently (never a duplicate order).
- Invoice attach — fetch an already-produced invoice PDF and attach it to the channel order (we never generate fiscal documents).
- AWB / tracking hand-off — the courier-minted tracking number flows back to the channel.
- User-configurable field mapping — remap any field between a connector and the canonical model in the admin UI, versioned, no deploy.
88 production connectors (+16 payment integrations available on request) across ERP, invoicing/accounting, e-commerce, marketplaces, feeds and couriers — spanning the Americas, all of Europe + the Nordics + Switzerland, the Gulf/UAE, Africa, South/South-East/East Asia, India and Oceania.
➡️ Browse the full connector catalogue
| Category | Count | Examples |
|---|---|---|
| ERP — systems of record | 22 | Acumatica, SAP S/4HANA, Dynamics 365, Odoo, SoftOne |
| Marketplaces | 39 | eMAG, Altex, Cel.ro, Trendyol, Amazon, Allegro, noon, Coupang |
| Invoicing / accounting | 8 | SmartBill, Oblio, FGO, Xero, Zoho Books, Sage |
| E-commerce | 8 | WooCommerce, Shopify, Magento, PrestaShop, any REST API |
| Couriers | 7 | DPD, FAN Courier, Cargus, Sameday, DHL |
| Feeds | 4 | Favi, Compari, Price.ro, Apify (scraping) |
(+ 16 payment gateways — Stripe, PayPal, Adyen, Netopia, PayU, Revolut Pay and more — integrated on request via the official plugin or custom code.)
This overview repo mirrors the shape of the product so you can see how it is organised. Each folder has a README describing what lives there — the implementations themselves are private.
megzo-integrator-vortex/
├─ CONNECTORS.md # the full generated connector catalogue
├─ ARCHITECTURE.md # runtime, the connector model, flows, reliability & security
├─ data/connectors.json # the public connector inventory (drives the catalogue + the website)
├─ scripts/ # the catalogue generator
├─ packages/ # platform core — shared, core, connector-sdk, telemetry, egress, db
├─ connectors/ # the connector fleet (manifests + adapters, private)
├─ workers/ # the edge runtime — ingress, pollers, consumers, control API, feeds
├─ apps/admin-ui/ # the configurator + mapping UI
└─ docs/ # high-level documentation
TypeScript on Cloudflare Workers · Postgres (control plane) behind Hyperdrive · R2 (blobs) · Cloudflare Queues (async) · Durable Objects (coordination, rate-limit, cursors, locks) · Cron Triggers (schedules & reconciliation) · OpenTelemetry (one trace per flow, source → hub → sink) · React admin UI behind Cloudflare Access.
The platform core and the connector fleet are built and conformance-tested; the marketing catalogue is live at vortex.megzo.biz. Each connector goes live per tenant once its credentials and channel access are in place.
MEGZO IV is sold as a managed service (monthly fee per tenant). For a demo, an integration request, or to add a system to the catalogue:
office@megzo.biz · vortex.megzo.biz
© MEGZO. All rights reserved. This repository is a public overview; it does not grant a licence to the MEGZO IV software. See LICENSE.