Skip to content
ERP ⇄ Marketing

DEAR Inventory to Iterable integration — real-time, two-way sync

Keep DEAR Inventory and Iterable 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 DEAR Inventory and Iterable

Feed the real customer, order, and revenue records from DEAR Inventory into Iterable so campaigns run on who actually bought what, and let contact and consent changes flow back in real time.

Marketing runs on lists of people, but the list rarely knows which of those people are paying customers, what they ordered, or what they are worth. DEAR Inventory holds exactly that: Suppliers, Stock adjustments and transfers, Assemblies / Production, Locations that record who the customer is, what they bought, and what they owe. When the two are joined only by a periodic export, campaigns go out against stale audiences, existing customers get prospecting emails, high-value accounts look the same as cold leads, and a canceled order still counts toward a segment.

Stacksync syncs Suppliers, Stock adjustments and transfers, Assemblies / Production, Locations in DEAR Inventory with Commerce / Purchases, Export data, Users, Events in Iterable in real time, and where both sides accept writes, in both directions. Customer, order, and invoice data maps field by field onto the contacts, audiences, or accounts Iterable works with, so segmentation and personalization run on current purchase history instead of a month-old snapshot. Contact details and consent changes that originate in Iterable flow back onto the record in DEAR Inventory.

The strongest bridge between the two is identity and purchase history, who the customer is and what they have bought, so that is where most of the value sits. Because the sync is field-level, each system keeps the attributes the other has no use for; only the shared records are held in agreement.

Common use cases

  • 01 Sync stock levels and product data to e-commerce storefronts and a CRM so sales quotes reflect real availability.
  • 02 Push sale orders from a storefront or CRM into DEAR for fulfillment without manual re-entry.
  • 03 Stream Iterable System Webhook events into a database in near real time so opens, clicks, bounces, and unsubscribes land alongside CRM contact records.
  • 04 Write list subscribe/unsubscribe changes from a CRM back into Iterable Lists so suppression and opt-in state stay current before the next send.

Common sync patterns

Suppress or target existing customers

Because DEAR Inventory knows who is already a paying customer, Iterable can exclude them from acquisition campaigns or single them out for renewal and cross-sell.

One customer identity across both systems

A person or company's contact details corrected in either system update the other, so marketing and the back office stop maintaining separate versions of the same record.

Lifecycle triggers from back-office events

A first order, a renewal, or a lapsed account recorded in DEAR Inventory appears in Iterable within seconds, ready to start or stop a lifecycle campaign.

What you can sync between DEAR Inventory and Iterable

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.

DEAR Inventory objects Iterable objects How this pairing syncs
Purchase orders Supplier orders and receiving records synced with accounting and planning tools. Templates Reusable email/SMS/push/in-app message templates with handlebars fields; read via /api/templates and per-channel get endpoints, written via /api/templates/email/upsert and the other channel upserts. Purchase orders is specific to DEAR Inventory and Templates to Iterable — each maps to any object or custom field on the other side.
Customers Buyer records aligned with CRM and accounting counterparts. Lists Static subscriber lists; read via GET /api/lists and /api/lists/getUsers, with users added or removed via /api/lists/subscribe and /api/lists/unsubscribe to control who receives a send. Customers is specific to DEAR Inventory and Lists to Iterable — each maps to any object or custom field on the other side.
Suppliers Vendor records referenced on purchase orders. Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. Suppliers is specific to DEAR Inventory and Catalogs to Iterable — each maps to any object or custom field on the other side.
Stock adjustments and transfers Inventory movement transactions that explain changes in availability. Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. Stock adjustments and transfers is specific to DEAR Inventory and Commerce / Purchases to Iterable — each maps to any object or custom field on the other side.
Assemblies / Production Bill-of-material and production records for light manufacturing workflows. Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. Assemblies / Production is specific to DEAR Inventory and Export data to Iterable — each maps to any object or custom field on the other side.
Locations Warehouses and bins that scope stock levels and fulfillment. Users User profiles keyed by email or userId with custom data fields; upserted via POST /api/users/update, read via GET /api/users/{email} or getByUserId, bulk-written via /api/users/bulkUpdate (up to 1000 users per call), and deleted or GDPR-forgotten. Locations is specific to DEAR Inventory and Users to Iterable — each maps to any object or custom field on the other side.

How changes propagate between DEAR Inventory and Iterable

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.

DEAR Inventory Iterable Sub-second propagation

DetectionDEAR Inventory notifies Stacksync of record changes through webhook events. Polling with modified-since filters.

DeliveryEach detected change is written to Iterable through its API, with automatic retries and rate-limit backoff.

Iterable DEAR Inventory Sub-second propagation

DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time.

DeliveryEach detected change is written to DEAR Inventory through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • DEAR Inventory: Subject to the platform's per-account API rate limits.
  • Iterable: Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
What ships with DEAR Inventory ⇄ Iterable

Connect DEAR Inventory and Iterable for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DEAR Inventory–Iterable connection.

Real-time

Two-way sync

Changes in DEAR Inventory or Iterable instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever DEAR Inventory or Iterable 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 DEAR Inventory or Iterable record.

Observability

Monitoring

Track your DEAR Inventory ⇄ Iterable sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between DEAR Inventory and Iterable.

How the DEAR Inventory and Iterable connectors work

DEAR Inventory

Integration surface
REST API
Authentication
Account ID plus application key sent as request headers
Change detection
Polling with modified-since filters; webhook notifications for sale and purchase events are available on subscriptions that include the Automation module
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's per-account API rate limits

Iterable

Integration surface
Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data
Authentication
API key sent in the Api-Key HTTP header (also accepted as Api_Key; the name is case-insensitive). Keys are scoped by type - Server-side, JavaScript (Web SDK), or Mobile - with optional JWT-enabled keys. US projects use api.iterable.com; EU projects use api.eu.iterable.com.
Change detection
System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time; historical backfill and incremental catch-up run through the Export API over a date range.
Capabilities
read · write · webhooks
Rate limits
Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
How it works

How to connect DEAR Inventory to Iterable — 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 DEAR Inventory and Iterable 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
    DEAR Inventory connected
    Iterable connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the DEAR Inventory and Iterable 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 · DEAR Inventory ⇄ Iterable
    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
    DEAR Inventory Iterable
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

DEAR Inventory and Iterable 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 368 integrations available for DEAR Inventory and Iterable.

Popular · 8 of 368
All DEAR Inventory integrations All Iterable integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own