Real-time
Two-way sync
Changes in Box or DEAR Inventory instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ ERP
Box to DEAR Inventory integration — real-time, two-way sync
Keep Box and DEAR Inventory 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 Box and DEAR Inventory
Move the documents and data that DEAR Inventory produces into Box as files, and let files stored in Box update the records they belong to in DEAR Inventory, continuously and without exports or manual filing.
DEAR Inventory runs the business on structured records: Products, Stock levels, Sale orders, Purchase orders. Box holds files and the metadata that describes them: Metadata, Collaborations, Users, Groups. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record DEAR Inventory touches produces a file that belongs in storage, whether an invoice, a purchase order, a statement, or a shipping doc, and many files that land in Box, from signed contracts to vendor bills to receipts, describe a transaction DEAR Inventory needs to record. Left unconnected, that link is maintained by hand: someone exports a PDF and drags it into a folder, or downloads a file and keys its details into a record.
Stacksync keeps Products, Stock levels, Sale orders, Purchase orders in DEAR Inventory and Metadata, Collaborations, Users, Groups in Box in sync, bi-directionally and in real time. A document and its details, the customer, the type, the date, an amount, an order or invoice number, are mapped field by field, so a file arrives in Box already labeled and filed, and metadata captured against a stored file can create or update the matching record in DEAR Inventory. Changes on either side show up within seconds, with conflict resolution in place of nightly exports and manual filing.
The result is that a transaction and the document that backs it stay together. Finance, operations, and audit teams find the file behind a record without digging through folders, and the record in DEAR Inventory and the file in Box never describe two different versions of the same document.
Common use cases
- 01 Push sale orders from a storefront or CRM into DEAR for fulfillment without manual re-entry.
- 02 Land orders, costs, and inventory movements in a warehouse for margin and stock-turn reporting.
- 03 Mirror Metadata template instances on Files into database columns so contracts and assets are searchable and reportable alongside other business data.
- 04 Provision and deprovision Users, Groups, and Collaborations from an HR system or IdP so Box access follows onboarding and offboarding.
Common sync patterns
Audit-ready retention
Every transaction's supporting file lives in Box beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in DEAR Inventory.
Documents filed with their context
Files that DEAR Inventory produces land in Box labeled with the customer, document type, and reference number they belong to, so the right copy is one search away instead of buried in a folder.
Metadata that files itself
Record fields from DEAR Inventory, like customer, date, amount, type, and reference number, become the metadata and tags on the stored file in Box, so storage stays organized without anyone tagging by hand.
What you can sync between Box and DEAR Inventory
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.
| Box objects | DEAR Inventory objects | How this pairing syncs | |
|---|---|---|---|
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Products SKU records with pricing, suppliers, and bill-of-material links; the master data most syncs start from. | Users is specific to Box and Products to DEAR Inventory — each maps to any object or custom field on the other side. | |
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | Stock levels Per-location availability derived from inventory transactions; read-heavy in storefront syncs. | Groups is specific to Box and Stock levels to DEAR Inventory — each maps to any object or custom field on the other side. | |
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Sale orders Customer orders through their pick/pack/ship lifecycle; synced with storefronts and CRMs. | Tasks is specific to Box and Sale orders to DEAR Inventory — each maps to any object or custom field on the other side. | |
| Events Enterprise admin event stream, an audit log of uploads, deletes, logins, and shares across the account; read-only, consumed for reporting or change feeds. | Purchase orders Supplier orders and receiving records synced with accounting and planning tools. | Events is specific to Box and Purchase orders to DEAR Inventory — each maps to any object or custom field on the other side. | |
| Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. | Customers Buyer records aligned with CRM and accounting counterparts. | Files is specific to Box and Customers to DEAR Inventory — each maps to any object or custom field on the other side. | |
| Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. | Suppliers Vendor records referenced on purchase orders. | Folders is specific to Box and Suppliers to DEAR Inventory — each maps to any object or custom field on the other side. |
How changes propagate between Box and DEAR Inventory
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.
Box DEAR Inventory Sub-second propagation
DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.
DeliveryEach detected change is written to DEAR Inventory through its API, with automatic retries and rate-limit backoff.
DEAR Inventory Box Sub-second propagation
DetectionDEAR Inventory notifies Stacksync of record changes through webhook events. Polling with modified-since filters.
DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
- DEAR Inventory: Subject to the platform's per-account API rate limits.
What ships with Box ⇄ DEAR Inventory
Connect Box and DEAR Inventory for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–DEAR Inventory connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or DEAR Inventory 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 Box or DEAR Inventory record.
Observability
Monitoring
Track your Box ⇄ DEAR Inventory sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Box and DEAR Inventory.
How the Box and DEAR Inventory connectors work
Box
- Integration surface
- REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
- Authentication
- OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
- Change detection
- V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
- Capabilities
- read · write · webhooks
- Rate limits
- Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
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
How it works
How to connect Box to DEAR Inventory — 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 Box and DEAR Inventory with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Box
connected
DEAR Inventory
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and DEAR Inventory 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 · Box ⇄ DEAR InventoryCustomers 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.
Box DEAR InventoryCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and DEAR Inventory integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and DEAR Inventory: authenticate both systems, choose the objects to sync (such as Box's Users and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Box: V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed. On DEAR Inventory: Polling with modified-since filters; webhook notifications for sale and purchase events are available on subscriptions that include the Automation module. 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 Box side: Metadata, Collaborations, Users, Groups. 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 Box and DEAR Inventory: Audit-ready retention; Documents filed with their context; Metadata that files itself. Every transaction's supporting file lives in Box beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in DEAR Inventory.
-
Box: REST API (api.box.com/2.0), plus the Events API and V2 Webhooks. Authentication: OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing. DEAR Inventory: REST API. Authentication: Account ID plus application key sent as request headers. Stacksync manages authentication, retries, and rate limits on both sides.
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 399 integrations available for Box and DEAR Inventory.
Popular · 7 of 399
-
Box ⇄ Infor CloudSuite - Box ⇄ Infor LN
- Box ⇄ Infor M3
- Box ⇄ Infor WMS
-
DEAR Inventory ⇄ Sharepoint -
DEAR Inventory ⇄ Egnyte -
DEAR Inventory ⇄ Amazon S3
No integrations match .
