One source of truth.
Every channel.
Zero double entry.
MEGZO Integrator Vortex keeps your ERP as the single source of truth and auto-syncs products, prices, stock and orders across every marketplace, shop, courier and invoicing system — and any system with a REST API, including your own. Both directions, every few minutes, from one dashboard.
The daily tax of selling everywhere — gone.
No double data entry
Change a product, price or stock level once in your ERP. MEGZO IV pushes it to every connected channel automatically.
Never oversell
Stock is pushed with a safety buffer and continuously reconciled, so two channels can't sell the same last unit.
Orders land by themselves
A marketplace or webshop order becomes a Sales Order in your ERP, once, never twice — even if the channel sends it again.
Invoices & tracking flow back
The invoice PDF your ERP produced is attached to the order; the courier's tracking number is pushed to the buyer.
Business intelligence built in
Every channel flows through one shared data layer, the natural place to see orders, stock-at-risk, price spreads and returns across all of them.
Expand in days, not months
Adding a sales channel is a configuration step, not a project. The same engine, a few settings, live.
Bring your own API
Beyond the catalogue, the universal connector points at any REST endpoint — map the fields in the panel and sync catalog, orders, price and stock. No API at all? We pull catalog and price data by scraping.
One shared data layer. Every flow runs through it.
MEGZO IV connects to the APIs of your ERP and your channels and runs the sync in the cloud. Field mapping is dynamic: a non-developer remaps a field in the panel and it takes effect right away, with no code change.
88 live. 4 validated against real instances.
ERP — systems of record
22Marketplaces & feeds
43E-commerce
8Invoicing
8Couriers
7Payments
16Next: the global expansion — the top ERP, marketplace and e-commerce systems of the US, Asia, Africa, New Zealand, Switzerland, Norway and Denmark — added the same way, with zero engine changes.
Pay for the work we do. Watch every dial.
Starter
One channel, live and reliable.
- 1 active connector instance included (then €19 / connector / mo)
- 1,000 propagations / mo included, then €0.020 each
- 0.1% NET-GMV toll above €10,000 / mo
- Oversell-safe stock, idempotent orders, daily reconciliation
- One OpenTelemetry trace per flow; replayable dead-letter queue
Growth
Several channels, one dashboard.
- 3 active connector instances included (then €15 / connector / mo)
- 10,000 propagations / mo included, then €0.015 each
- 0.1% NET-GMV toll above €50,000 / mo
- Everything in Starter, at a lower marginal rate as you scale
- Dynamic field mapping — remap it yourself, live right away
Scale
High volume, unlimited connectors.
- Unlimited active connector instances
- 50,000 propagations / mo included, then €0.010 each
- 0.1% NET-GMV toll above €100,000 / mo
- Priority support; the lowest marginal rate at scale
- Multi-tenant isolation; per-tenant sealed credentials
Hybrid: a per-connector monthly base (the floor) + propagation overage beyond the tier quota + a 0.1% NET-GMV toll above a per-tier toll-free threshold. You meter the work we do, not a number you can't see.
Feed / comparison channels
Feed and comparison channels (Google Merchant, Favi, Compari, Price.ro, Skroutz's catalog half) carry no orders, so they bill on a fixed monthly fee by listings + attribute richness — a single-channel add-on, not propagations.
Four dials. Every one visible on your dashboard.
The 0.1% is a toll for value carried across our infrastructure — not a marketplace commission. You already own your channels; we move the data. It is deliberately 10–50× below marketplace commissions, taken only above your tier's toll-free threshold, and only on NET (refunds are credited back).
Propagations
per propagation
One order landing in a destination — the honest unit of the work we do. 1 order × N channels = N propagations.
NET GMV
0.1% toll, above threshold
Order value propagated, minus refunds and cancellations. The thin value-aligned toll is taken only on what stuck, only above your tier's threshold.
Active connectors
per connector / mo
Each live connector instance with at least one enabled flow. Bundled by tier; extras bill per connector, prorated daily.
Feed listings
fixed monthly by tier
Products × attributes in a feed channel — the dial behind the separate Feed S/M/L track.
Beyond the managed plan
The managed Vortex is the default. When the API path isn't enough — a system with no usable API, a channel not yet in the catalog, a storefront to build, or a migration off BaseLinker — we scope it and quote it.
Managed integration, built on a platform core.
Who it's for
Growing retailers and brands on Acumatica, SoftOne, Dynamics, SAP, Odoo and more, selling on eMAG, Amazon, Allegro, bol, Shopify, WooCommerce and beyond.
How we work
A managed monthly service per tenant. You configure mappings in your vendor panel; we operate the sync, the reliability and the observability. Custom in-house modules on request.
Talk to us
Tell us your ERP and your channels and we'll show the exact sync running live. office@megzo.biz
Built for IT to trust.
Secure by design
Credentials encrypted at rest (AES-256-GCM), decrypted only in-memory, never logged. Every webhook HMAC-verified.
Reliable by invariant
Idempotent order creation, oversell protection, backoff retries, daily reconciliation, a dead-letter queue with alerts.
GDPR data processor
Data minimisation, encryption in transit and at rest, a retention policy and a DPA per client. Business data stays in your ERP.
Cloud-native runtime
TypeScript on Cloudflare Workers, Postgres via Hyperdrive, R2, Queues, Durable Objects, Cron heartbeats. No boxes to patch.
Questions sellers ask before they switch
What does MEGZO Integrator Vortex actually do?
It keeps your ERP and your sales channels in sync, both ways, on a 5-minute heartbeat. Your ERP stays the single source of truth: catalog and prices publish out to each marketplace, stock pushes out with an oversell buffer, and marketplace orders land back in the ERP as sales orders — no second system to maintain, no copy-paste.
Which systems does it connect?
On the ERP side: Acumatica, SAP, Microsoft Dynamics 365, Odoo, SoftOne and the main Romanian systems. On the channel side: eMAG, Amazon, Trendyol, Allegro, eBay and more, plus WooCommerce, Shopify and Magento storefronts, price-comparison feeds, and Romanian invoicing and courier APIs. Every system is a connector on one engine, so a new one is configuration, not a rebuild.
How is this different from BaseLinker?
BaseLinker is the hub that holds your catalog. We don't — your ERP holds it, and MEGZO syncs it outward, so stock, price and orders reconcile against the system your finance team already trusts instead of a separate copy. If you don't run an ERP, BaseLinker may be the better fit; if you do, the ERP-anchored model is the difference that matters.
Does MEGZO issue invoices or submit e-Factura to ANAF?
No. MEGZO never generates a fiscal invoice and never submits to e-Factura or ANAF — your ERP or invoicing software owns that. When a channel needs the invoice attached to an order, we fetch the PDF your system already produced and attach it. That boundary is deliberate: we move data, we don't create fiscal documents.
How does it stop overselling?
Stock publishes with a safety buffer — the channel sees available minus a margin you set — and a reconciliation pass re-checks the channel against the ERP on a schedule, so a missed webhook can't quietly drift you into selling stock you don't have. Overselling is the failure mode that costs the most, so it's protected by default, not as an add-on.
Is it actually live, or just a roadmap?
Live. A Romanian eMAG seller runs catalog, stock, orders, invoice attach and AWB on this exact engine today. The broader connector catalogue is tested and beta-ready; four are validated against real production instances. We tell you which tier a connector is at before you switch.
Stop re-keying.
Start scaling.
Tell us your ERP and the channels you sell on. We'll show you the exact sync running on a 5-minute heartbeat — and what it does to your team's workload.