In short: MEGZO Integrator Vortex connects SAP (S/4HANA) and Favi so your catalog, prices and stock publish from SAP (S/4HANA) to Favi automatically, and every Favi order flows back into SAP (S/4HANA) as one record — on a 5-minute heartbeat, with oversell protection and no double data entry.
Keep SAP (S/4HANA) as your single source of truth and let MEGZO Integrator Vortex sync your catalog, prices, stock and orders to Favi — automatically, both directions, with no double data entry and no overselling.
SAP (S/4HANA)'s fields map to Favi's through database-backed, versioned rules — VAT strip/add, rounding, enum lookups, currency conversion — editable without a deploy.
Stock pushed to Favi with a buffer and reconciled, so a unit can't sell twice across channels.
Every Favi order becomes one record in SAP (S/4HANA) — idempotent by design.
Fulfilment and payment systems plug in alongside this pair — no extra integration project.
Stock flows on a 5-minute heartbeat and on demand, with push (webhook) wake-ups where Favi supports them. It is pushed with an oversell buffer and continuously reconciled, so you never sell the same last unit twice.
No. Order creation is idempotent — keyed on the channel order id with a unique constraint and an order-lock — so a retried or replayed order never creates a second record in SAP (S/4HANA).
From neither — you manage Product, Price, Stock and Order syncing from your MEGZO IV vendor panel. Field mapping between SAP (S/4HANA) and Favi is dynamic and database-backed; a non-developer can remap a field and it takes effect without a deploy.
MEGZO IV fetches the invoice PDF that SAP (S/4HANA) (or your invoicing service) already produced and attaches it to the Favi order where supported. It never generates a fiscal/legal invoice and never submits to e-Factura/ANAF.
SAP (S/4HANA) and Favi share a regional footprint (Global, CZ, SK, HU, RO, HR, BG), so this is a native fit.
We run the sync; you watch it from one dashboard. Tell us your setup and see it live on a 5-minute heartbeat.