Two-way sync
Changes in DEAR Inventory or JobBOSS² instantly reflect in both systems. No stale data, no manual imports.
Keep DEAR Inventory and JobBOSS² in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Companies run two ERPs for structural reasons: a two-tier setup with subsidiaries on lighter systems, an acquisition that brought its own stack, a split by function or region, or a migration that will take quarters. In all of these, some of the same organizations, people, and transactions exist in both systems, and keeping them aligned by hand is a standing tax on the back office.
Stacksync syncs Products, Stock levels, Sale orders, Purchase orders in DEAR Inventory with Routings & Operations, Materials & Inventory, Purchase Orders, Vendors in JobBOSS² bi-directionally and in real time, with field-level mapping across the two data models and conflict rules you define. A record changed in either system is reflected in the other within seconds, not at the next interface run.
Where both systems keep records of the same customers, suppliers, or organizations, a correction in either updates the other.
Where one system is the people or finance suite and the other runs operations, the records both sides depend on, such as organizations, cost centers, and reference data, stay in agreement.
Where subsidiaries run one system and headquarters runs the other, shared records and transactions flow up continuously, so consolidation starts from live data.
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 | JobBOSS² objects | How this pairing syncs | |
|---|---|---|---|
| Purchase orders Supplier orders and receiving records synced with accounting and planning tools. | Purchase Orders PO data syncs outward for spend and receiving visibility. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Customers Buyer records aligned with CRM and accounting counterparts. | Customers Customer records sync with CRM accounts so sales and the shop share one file. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Products SKU records with pricing, suppliers, and bill-of-material links; the master data most syncs start from. | Jobs / Work Orders Job records carry production status back to sales and customer-facing tools. | Products is specific to DEAR Inventory and Jobs / Work Orders to JobBOSS² — 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. | Routings & Operations Operation steps support scheduling and costing data in external reporting. | Stock levels is specific to DEAR Inventory and Routings & Operations to JobBOSS² — 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. | Materials & Inventory Material and stock data feed purchasing and availability checks. | Sale orders is specific to DEAR Inventory and Materials & Inventory to JobBOSS² — each maps to any object or custom field on the other side. | |
| Suppliers Vendor records referenced on purchase orders. | Vendors Vendor records keep procurement and accounting tools consistent. | Suppliers is specific to DEAR Inventory and Vendors to JobBOSS² — 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.
DetectionDEAR Inventory notifies Stacksync of record changes through webhook events. Polling with modified-since filters.
DeliveryEach detected change is written to JobBOSS² through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls JobBOSS² for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
DeliveryEach detected change is written to DEAR Inventory through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DEAR Inventory–JobBOSS² connection.
Changes in DEAR Inventory or JobBOSS² instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DEAR Inventory or JobBOSS² data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single DEAR Inventory or JobBOSS² record.
Track your DEAR Inventory ⇄ JobBOSS² sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DEAR Inventory and JobBOSS².
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 DEAR Inventory and JobBOSS² 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 DEAR Inventory and JobBOSS² 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.
Yes. Stacksync provides a managed, real-time two-way integration between DEAR Inventory and JobBOSS²: authenticate both systems, choose the objects to sync (such as DEAR Inventory's Purchase orders and Customers), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both DEAR Inventory and JobBOSS². The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on DEAR Inventory: Polling with modified-since filters; webhook notifications for sale and purchase events are available on subscriptions that include the Automation module. On JobBOSS²: Polling. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the DEAR Inventory side: Products, Stock levels, Sale orders, Purchase orders, plus custom fields where DEAR Inventory exposes them. On the JobBOSS² side: Routings & Operations, Materials & Inventory, Purchase Orders, Vendors. 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 JobBOSS²: Shared master data; Split by function; Two-tier roll-up. Where both systems keep records of the same customers, suppliers, or organizations, a correction in either updates the other.
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 162 integrations available for DEAR Inventory and JobBOSS².