Two-way sync
Changes in Magento or Navan instantly reflect in both systems. No stale data, no manual imports.
Keep Magento and Navan in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Magento runs the storefront — the catalog, the orders, and the buyers placing them. Navan records the money behind those orders — invoices, revenue, payments, and the ledger the business closes on. The overlap is every customer, order, and product both sides need to agree on, and when that overlap is bridged by CSV export or an overnight batch, finance reconciles against stale numbers while the store quotes prices or stock the books no longer recognize.
Stacksync syncs Connect Transactions, Manual Transactions, Bookings, Custom Fields in Navan with Customers, Inventory source items (MSI), Invoices, Shipments in Magento field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Magento, its paid-or-overdue state from Navan — and Stacksync keeps every copy consistent and resolves conflicts by the rules you set.
The result is one shared record of who bought what and whether it has been paid, so the storefront, support, and the finance team all read from the same current data instead of re-keying it between systems.
A new or updated order in Magento creates or updates the matching invoice or revenue record in Navan, so billing and reporting start without re-entry.
Paid, overdue, and refunded state from Navan lands on the order or account in Magento, so the store and support see what has actually been collected.
Where both systems keep customer or buyer records, an edit in either propagates to the other, ending duplicate accounts and mismatched contact details.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Magento objects | Navan objects | How this pairing syncs | |
|---|---|---|---|
| Inventory source items (MSI) Per-source stock quantities under Multi-Source Inventory; written from a WMS/ERP so storefront stock matches the warehouse. | Repayments, Fees, and Adjustments Money-movement records including repayments, FX and platform fees, and credit or debit memos; read-only for reconciliation ledgers. | Inventory source items (MSI) is specific to Magento and Repayments, Fees, and Adjustments to Navan — each maps to any object or custom field on the other side. | |
| Invoices Invoice documents tied to orders; read out for finance and revenue recognition, or created via the sales API when billing downstream. | Users Employee and cardholder records referenced by every transaction; usually provisioned from an HRIS and used to map spend to people and departments. | Invoices is specific to Magento and Users to Navan — each maps to any object or custom field on the other side. | |
| Shipments Shipment and tracking records against orders; created or read to drive fulfillment status between Magento and a 3PL/WMS. | Card Transactions Navan physical and virtual card spend; read via GET, then GL codes, cost centers, and ERP sync status are written back per transaction through the transaction update endpoint. | Shipments is specific to Magento and Card Transactions to Navan — each maps to any object or custom field on the other side. | |
| Carts / quotes Active and guest carts (quotes) with items and totals; read for abandoned-cart analysis (not available on the Cloud Service subset). | Connect Transactions External and personal card feed matched into Navan; retrieved read-only and coded with custom-field values through the transaction update endpoint. | Carts / quotes is specific to Magento and Connect Transactions to Navan — each maps to any object or custom field on the other side. | |
| Products Catalog items keyed by SKU; carry created_at/updated_at for incremental polling and are written two-way from a PIM or ERP into the storefront. | Manual Transactions Out-of-pocket reimbursements and payroll submissions; synced for approval and reimbursement, then GL-coded back into Navan. | Products is specific to Magento and Manual Transactions to Navan — each maps to any object or custom field on the other side. | |
| Configurable / variant products Parent configurable products link to simple product variants by attribute; synced so size/color SKUs and their prices stay aligned with source systems. | Bookings Flight, hotel, rail, and car reservations from the Booking API; pulled read-only by createdFrom/createdTo date range for trip and travel-spend reporting. | Configurable / variant products is specific to Magento and Bookings to Navan — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionMagento notifies Stacksync of record changes through webhook events. Polling with searchCriteria filters on updated_at (catalog, sales, and customer entities carry created_at/updated_at).
DeliveryEach detected change is written to Navan through its API, with automatic retries and rate-limit backoff.
DetectionNavan notifies Stacksync of record changes through webhook events. Navan's Expense API supports webhooks for transaction and expense events.
DeliveryEach detected change is written to Magento through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Magento–Navan connection.
Changes in Magento or Navan instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Magento or Navan data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Magento or Navan record.
Track your Magento ⇄ Navan sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Magento and Navan.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Magento and Navan with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Magento and Navan objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 459 integrations available for Magento and Navan.