Real-time
Two-way sync
Changes in DEAR Inventory or Salesforce instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ CRM
DEAR Inventory to Salesforce integration — real-time, two-way sync
Keep DEAR Inventory and Salesforce 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 Salesforce
Close the gap between front office and back office: Salesforce and DEAR Inventory share customers and status in real time, in both directions.
Salesforce holds the customer relationship; DEAR Inventory runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Stacksync syncs Leads, Opportunities, Cases, Campaigns in Salesforce with Assemblies / Production, Locations, Products, Stock levels in DEAR Inventory field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
- 02 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
- 03 Sync stock levels and product data to e-commerce storefronts and a CRM so sales quotes reflect real availability.
- 04 Push sale orders from a storefront or CRM into DEAR for fulfillment without manual re-entry.
Common sync patterns
Where DEAR Inventory manages people and org data: keep Salesforce aligned
Owners, territories, and org structure informed by DEAR Inventory stay current in Salesforce.
Where DEAR Inventory handles order-to-cash: closed-won flows through
A deal won in Salesforce creates or updates the customer in DEAR Inventory with clean data, so fulfillment and invoicing start without re-entry.
Where DEAR Inventory is the finance system of record: money status on the account
Invoice and payment state from DEAR Inventory shows on the account in Salesforce, so reps see balances before promising the next order.
What you can sync between DEAR Inventory and Salesforce
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 | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| Locations Warehouses and bins that scope stock levels and fulfillment. | Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. | Locations is specific to DEAR Inventory and Custom Objects to Salesforce — each maps to any object or custom field on the other side. | |
| Products SKU records with pricing, suppliers, and bill-of-material links; the master data most syncs start from. | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | Products is specific to DEAR Inventory and Accounts to Salesforce — each maps to any object or custom field on the other side. | |
| Stock levels Per-location availability derived from inventory transactions; read-heavy in storefront syncs. | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Stock levels is specific to DEAR Inventory and Contacts to Salesforce — each maps to any object or custom field on the other side. | |
| Sale orders Customer orders through their pick/pack/ship lifecycle; synced with storefronts and CRMs. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Sale orders is specific to DEAR Inventory and Leads to Salesforce — each maps to any object or custom field on the other side. | |
| Purchase orders Supplier orders and receiving records synced with accounting and planning tools. | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Purchase orders is specific to DEAR Inventory and Opportunities to Salesforce — each maps to any object or custom field on the other side. | |
| Customers Buyer records aligned with CRM and accounting counterparts. | Cases Support records; synced with help desk tools or internal databases for escalation workflows. | Customers is specific to DEAR Inventory and Cases to Salesforce — each maps to any object or custom field on the other side. |
How changes propagate between DEAR Inventory and Salesforce
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 Salesforce Sub-second propagation
DetectionDEAR Inventory notifies Stacksync of record changes through webhook events. Polling with modified-since filters.
DeliveryEach detected change is written to Salesforce through its API, with automatic retries and rate-limit backoff.
Salesforce DEAR Inventory Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
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.
- Salesforce: Daily API request allocations vary by edition and license count.
What ships with DEAR Inventory ⇄ Salesforce
Connect DEAR Inventory and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DEAR Inventory–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever DEAR Inventory or Salesforce 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 Salesforce record.
Observability
Monitoring
Track your DEAR Inventory ⇄ Salesforce 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 Salesforce.
How the DEAR Inventory and Salesforce 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
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
How it works
How to connect DEAR Inventory to Salesforce — 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.
- 01
Connect your apps
Authenticate DEAR Inventory and Salesforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
DEAR Inventory
connected
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the DEAR Inventory and Salesforce 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.
objects · DEAR Inventory ⇄ SalesforceCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
DEAR Inventory SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
DEAR Inventory and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between DEAR Inventory and Salesforce: authenticate both systems, choose the objects to sync (such as DEAR Inventory's Locations and Products), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Salesforce side: Leads, Opportunities, Cases, Campaigns, plus custom fields where Salesforce exposes them. On the DEAR Inventory side: Assemblies / Production, Locations, Products, Stock levels. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for DEAR Inventory and Salesforce: Where DEAR Inventory manages people and org data: keep Salesforce aligned; Where DEAR Inventory handles order-to-cash: closed-won flows through; Where DEAR Inventory is the finance system of record: money status on the account. Owners, territories, and org structure informed by DEAR Inventory stay current in Salesforce.
-
DEAR Inventory: REST API. Authentication: Account ID plus application key sent as request headers. Salesforce: REST, SOAP, and Bulk APIs. Authentication: OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode. Stacksync manages authentication, retries, and rate limits on both sides.
-
Salesforce: Salesforce org must have API access enabled — Group and Essentials editions cannot use Stacksync; Professional requires the API add-on. DEAR Inventory: DEAR Systems was acquired by Cin7 and the product now operates as Cin7 Core; the API and data model carried over from DEAR. Stacksync's field mapping accounts for these differences between DEAR Inventory and Salesforce without custom code.
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 439 integrations available for DEAR Inventory and Salesforce.
Popular · 7 of 439
-
DEAR Inventory ⇄ Attio -
DEAR Inventory ⇄ Pipedrive -
DEAR Inventory ⇄ Zoho CRM -
Salesforce ⇄ IQMS (DELMIAworks) -
Salesforce ⇄ JobBOSS² -
Salesforce ⇄ Körber WMS -
Salesforce ⇄ Linnworks
No integrations match .
