lexoffice + Amazon (SP-API) integration
In short: MEGZO Integrator Vortex connects lexoffice and Amazon (SP-API): every Amazon (SP-API) order flows into lexoffice as one idempotent record, and the lexoffice invoice attaches back to the Amazon (SP-API) order automatically.
Keep lexoffice as your invoicing system of record: MEGZO Integrator Vortex routes each Amazon (SP-API) order in and attaches the matching lexoffice invoice back to the order.
What syncs between lexoffice and Amazon (SP-API)
Channel specifics: price & stock update your existing listings (listing creation stays with you) · prices are published VAT-inclusive.
Why lexoffice + Amazon (SP-API) on MEGZO IV
Dynamic field mapping
lexoffice's fields map to Amazon (SP-API)'s through editable rules you control (VAT strip/add, rounding, value lookups, currency conversion), and changes take effect right away, with no code change.
Never oversell
Stock pushed to Amazon (SP-API) with a buffer and reconciled, so a unit can't sell twice across channels.
Orders, once
Every Amazon (SP-API) order becomes one record in lexoffice — idempotent by design.
Works with your couriers & payments
Fulfilment and payment systems plug in alongside this pair — no extra integration project.
Couriers — AWB & tracking to Amazon (SP-API)
Payments — via the official plugin or a custom integration
lexoffice + Amazon (SP-API) — FAQ
Does MEGZO IV sync stock between lexoffice and Amazon (SP-API) in real time?
Stock flows on a 5-minute heartbeat and on demand, with push (webhook) wake-ups where Amazon (SP-API) supports them. It is pushed with an oversell buffer and continuously reconciled, so you never sell the same last unit twice.
Will a Amazon (SP-API) order create a duplicate in lexoffice?
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 lexoffice.
Do I manage this from Amazon (SP-API) or from lexoffice?
From neither — you manage Product, Price, Stock and Order syncing from your MEGZO IV vendor panel. Field mapping between lexoffice and Amazon (SP-API) is dynamic; a non-developer can remap a field and it takes effect right away, with no code change.
Can MEGZO IV handle invoices for Amazon (SP-API)?
MEGZO IV fetches the invoice PDF that lexoffice (or your invoicing service) already produced and attaches it to the Amazon (SP-API) order where supported. It never generates a fiscal/legal invoice and never submits to e-Factura/ANAF.
Is lexoffice ↔ Amazon (SP-API) a good regional fit?
lexoffice and Amazon (SP-API) share a regional footprint (DE, BE, NL, FR, IT, ES, AE, SG), so this is a native fit.
Related integrations
More channels for lexoffice
More systems that sync to Amazon (SP-API)
Guides
Connect lexoffice to Amazon (SP-API)
We run the sync; you watch it from one dashboard. Tell us your setup and see it live on a 5-minute heartbeat.