Skip to content
E-commerce ⇄ Accounting and finance

Magento to Navan integration — real-time, two-way sync

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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Magento and Navan

Turn every Magento order into clean revenue: Navan and Magento keep customers, orders, and payment status aligned in real time, in both directions.

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.

Common use cases

  • 01 Sync Card Transactions and Manual Transactions into Postgres or a warehouse so finance analyzes corporate spend in SQL without manual CSV exports.
  • 02 Push coded expense transactions into an accounting system, then set their ERP sync status in Navan so the same records are not exported twice.
  • 03 Sync Orders, invoices, and shipments from Magento into Postgres or a warehouse for revenue, margin, and fulfillment-SLA reporting.
  • 04 Master Products, prices, and Category assignments in an ERP or PIM and write them into Magento's catalog by SKU.

Common sync patterns

Where Magento originates orders: sales flow into the books

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.

Where Navan is the money system of record: payment status on the order

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.

One customer master

Where both systems keep customer or buyer records, an edit in either propagates to the other, ending duplicate accounts and mismatched contact details.

What you can sync between Magento and Navan

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.

How changes propagate between Magento and Navan

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.

Magento Navan Sub-second propagation

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.

Navan Magento Sub-second propagation

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.

Rate-limit considerations

  • Magento: No fixed request-per-minute cap on PaaS/on-prem; responses page via searchCriteria pageSize/currentPage under a default maximum page size of 300 (Web API Input Limits), with /async/bulk endpoints for large writes.
  • Navan: Requests are throttled with HTTP 429 and Navan recommends retrying with exponential backoff; the Expense/Public API must first be enabled per account by Navan.
What ships with Magento ⇄ Navan

Connect Magento and Navan for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Magento–Navan connection.

Real-time

Two-way sync

Changes in Magento or Navan instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Magento or Navan data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Magento or Navan record.

Observability

Monitoring

Track your Magento ⇄ Navan sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Magento and Navan.

How the Magento and Navan connectors work

Magento

Integration surface
REST and GraphQL Web APIs (SOAP also available)
Authentication
Token-based OAuth: an integration's access token (consumer key/secret + access token/secret) or a Bearer admin token (default 4-hour expiry); Adobe Commerce as a Cloud Service authenticates via Adobe IMS (OAuth 2)
Change detection
Polling with searchCriteria filters on updated_at (catalog, sales, and customer entities carry created_at/updated_at); optional near-real-time via the Adobe Commerce Webhooks / Adobe I/O Events modules (order/created, product/updated, customer/created)
Capabilities
read · write · webhooks
Rate limits
No fixed request-per-minute cap on PaaS/on-prem; responses page via searchCriteria pageSize/currentPage under a default maximum page size of 300 (Web API Input Limits), with /async/bulk endpoints for large writes.

Navan

Integration surface
REST (Expense API and Booking API)
Authentication
OAuth 2.0 client-credentials flow; an admin creates a client_id and client_secret under Settings > Integrations and exchanges them at Navan's OAuth token endpoint for a short-lived bearer token that is refreshed on expiry (separate US and EU regional hosts)
Change detection
Navan's Expense API supports webhooks for transaction and expense events; sync engines also poll GET endpoints with date-range and updatedAt filters (createdFrom/createdTo for bookings) to backfill history and reconcile. There is no database-level CDC.
Capabilities
read · write · webhooks
Rate limits
Requests are throttled with HTTP 429 and Navan recommends retrying with exponential backoff; the Expense/Public API must first be enabled per account by Navan.
How it works

How to connect Magento to Navan — three steps, no code

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.

  1. 01

    Connect your apps

    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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Magento connected
    Navan connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Magento ⇄ Navan
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Magento Navan
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Magento and Navan integration FAQ

SECURITY

Security teams trust Stacksync

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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 459 integrations available for Magento and Navan.

Popular · 8 of 459
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.