Vendure Integration
Install the Convertmax Vendure plugin to push products, customers, and orders into Convertmax—so headless catalog and order truth feeds the same first-party revenue and journey reporting as your other connectors.
Vendure is often the system of record for headless storefronts. Convertmax makes that catalog, customer, and order data attributable—so growth and commerce teams can connect campaigns and journeys to real Vendure revenue, not just platform dashboards.
What the integration does
A Vendure 3 plugin with event-driven sync, job-queue reliability, and Admin UI reindex actions for full or single-entity backfills.
Create, update, delete, and reindex products into Convertmax as catalog changes happen in Vendure—including optional variant detail and per-product sync opt-out.
Push customer upserts and deletes when contacts change in Vendure, with email-gated filters and optional address payloads for richer identity linking.
Sync order lifecycle changes—including line items and variant detail—so Vendure commerce revenue can roll into Convertmax reporting alongside other sources.
Sync work runs through the Vendure job queue with configurable retries, timeouts, idempotency keys, and per-entity sync status records for operators.
Trigger Full Sync to Convertmax from product, customer, and order lists, or sync a single record from the detail page when you need a targeted backfill.
Map external IDs, product sync enablement, customer lifecycle stage, and last-synced timestamps onto Vendure entities for round-trip identity and control.
Once products, contacts, and orders land in Convertmax, they participate in the same identity and revenue model used for CRM, payments, and web conversions.
Built for revenue-focused attribution
Headless Vendure stores often split storefront analytics from the commerce backend. Syncing orders and customers into Convertmax closes that gap so paid and organic journeys can be tied to real catalog and order outcomes.
Commerce, marketing, and RevOps get one place to see which campaigns and pages precede Vendure revenue—without rebuilding attribution inside every custom storefront.
How it works
Add @convertmax/vendure-plugin-api-sync to your Vendure 3 project and register ApiAuthSyncPlugin with your Convertmax API URL and credentials.
Use withConvertmaxCustomFields (or equivalent fields) so products, customers, and orders can store external IDs and sync metadata.
Keep the job queue worker running so convertmax-api-sync jobs process create, update, delete, and reindex operations reliably.
Compile ApiAuthSyncPlugin.ui into your Admin UI build to expose Full Sync and Sync This actions for SuperAdmins.
Trigger convertmaxSyncAll or use Admin UI full sync for the initial load—then entity events keep products, customers, and orders flowing automatically.
Vendure commerce data joins Convertmax identity and revenue reporting so teams can attribute storefront performance to the marketing that drove it.
Questions about Vendure plugin setup, endpoint wiring, custom field mapping, or how orders map into Convertmax revenue? Email help@convertmax.io or book time with the team.