Real-time
Two-way sync
Changes in Box or Brightpearl instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ ERP
Box to Brightpearl integration — real-time, two-way sync
Keep Box and Brightpearl 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 Brightpearl
Move the documents and data that Brightpearl produces into Box as files, and let files stored in Box update the records they belong to in Brightpearl, continuously and without exports or manual filing.
Brightpearl runs the business on structured records: Custom fields, Products, Sales orders, Purchase orders. Box holds files and the metadata that describes them: Groups, Tasks, Events, Files. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Brightpearl 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 Brightpearl 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 Custom fields, Products, Sales orders, Purchase orders in Brightpearl and Groups, Tasks, Events, Files 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 Brightpearl. 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 Brightpearl and the file in Box never describe two different versions of the same document.
Common use cases
- 01 Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.
- 02 Mirror inventory levels from Brightpearl into a database that feeds availability to storefronts and marketplaces.
- 03 Provision and deprovision Users, Groups, and Collaborations from an HR system or IdP so Box access follows onboarding and offboarding.
- 04 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.
Common sync patterns
Metadata that files itself
Record fields from Brightpearl, 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.
Where Box captures inbound files: details reach the record
A contract, vendor bill, or receipt added to Box with its details can create or update the matching record in Brightpearl, so a document captured outside the finance system still reaches the books.
An archive that stays current
As records change in Brightpearl, the corresponding files and metadata in Box are kept in step, so a stored document reflects the latest version rather than a stale one-time export.
What you can sync between Box and Brightpearl
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 | Brightpearl objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Folders is specific to Box and Products to Brightpearl — each maps to any object or custom field on the other side. | |
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Metadata is specific to Box and Sales orders to Brightpearl — each maps to any object or custom field on the other side. | |
| Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. | Purchase orders Supplier orders synced with procurement or accounting systems. | Collaborations is specific to Box and Purchase orders to Brightpearl — each maps to any object or custom field on the other side. | |
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | Users is specific to Box and Contacts to Brightpearl — 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. | Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. | Groups is specific to Box and Inventory and warehouses to Brightpearl — 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. | Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. | Tasks is specific to Box and Goods-out notes to Brightpearl — each maps to any object or custom field on the other side. |
How changes propagate between Box and Brightpearl
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 Brightpearl 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 Brightpearl through its API, with automatic retries and rate-limit backoff.
Brightpearl Box Sub-second propagation
DetectionBrightpearl notifies Stacksync of record changes through webhook events. Webhooks for object created/updated events, with resource search polling as a fallback.
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.
- Brightpearl: Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints.
What ships with Box ⇄ Brightpearl
Connect Box and Brightpearl for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Brightpearl connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Brightpearl 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 Brightpearl record.
Observability
Monitoring
Track your Box ⇄ Brightpearl 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 Brightpearl.
How the Box and Brightpearl 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.
Brightpearl
- Integration surface
- REST API, organized into services (order, product, contact, warehouse, accounting)
- Authentication
- OAuth 2.0 (authorization code grant) for current apps; legacy private and public apps authenticate with app reference and account token headers
- Change detection
- Webhooks for object created/updated events, with resource search polling as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints
How it works
How to connect Box to Brightpearl — 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 Brightpearl 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
Brightpearl
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Brightpearl 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 ⇄ BrightpearlCustomers 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 BrightpearlCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Brightpearl integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Brightpearl: authenticate both systems, choose the objects to sync (such as Box's Folders and Metadata), 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 Brightpearl: Webhooks for object created/updated events, with resource search polling as a fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Brightpearl side: Custom fields, Products, Sales orders, Purchase orders, plus custom fields where Brightpearl exposes them. On the Box side: Groups, Tasks, Events, Files. 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 Brightpearl: Metadata that files itself; Where Box captures inbound files: details reach the record; An archive that stays current. Record fields from Brightpearl, 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.
-
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. Brightpearl: REST API, organized into services (order, product, contact, warehouse, accounting). Authentication: OAuth 2.0 (authorization code grant) for current apps; legacy private and public apps authenticate with app reference and account token 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 498 integrations available for Box and Brightpearl.
Popular · 6 of 498
-
Box ⇄ Epicor ERP -
Box ⇄ Extensiv (3PL Central) -
Box ⇄ Fishbowl Manufacturing -
Brightpearl ⇄ Amazon S3 -
Brightpearl ⇄ Sharepoint -
Brightpearl ⇄ Egnyte
No integrations match .
