Real-time
Two-way sync
Changes in Azure Cosmos DB or Brightpearl instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ ERP
Azure Cosmos DB to Brightpearl integration — real-time, two-way sync
Keep Azure Cosmos DB 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 Azure Cosmos DB and Brightpearl
Give your engineers Brightpearl's data in Azure Cosmos DB: read it with normal queries, write back through the sync, and skip the ERP API entirely.
ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.
Stacksync mirrors Inventory and warehouses, Goods-out notes, Invoices and payments, Custom fields from Brightpearl into Azure Cosmos DB and keeps both sides consistent in real time. Whatever Brightpearl is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Azure Cosmos DB sync back into Brightpearl with its validations respected.
Common use cases
- Mirror Cosmos DB items into Postgres so teams can query operational data with standard SQL.
- Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.
- Mirror inventory levels from Brightpearl into a database that feeds availability to storefronts and marketplaces.
- Push invoices and payments into an accounting platform for reconciliation.
Controlled write-back
Choose exactly which tables and fields may flow from Azure Cosmos DB back into Brightpearl, keeping the ERP authoritative.
Read ERP records with a query
Records from Brightpearl live in Azure Cosmos DB as ordinary tables or collections, joinable with the rest of your data.
Internal tools and automations without API code
Scripts and services read and write the synced tables; Stacksync handles the Brightpearl interface, limits, and retries.
What you can sync between Azure Cosmos DB 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.
| Azure Cosmos DB objects | Brightpearl objects | |
|---|---|---|
| Containers The unit of partitioning and throughput; each container maps to a synced collection. | Custom fields Per-object custom attributes included in field mappings. | |
| Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. | Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | |
| Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. | Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | |
| Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. | Purchase orders Supplier orders synced with procurement or accounting systems. | |
| Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. | Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | |
| Databases Top-level namespaces that scope containers and throughput provisioning. | Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. |
What ships with Azure Cosmos DB ⇄ Brightpearl
Connect Azure Cosmos DB and Brightpearl for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Brightpearl connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Cosmos DB 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 Azure Cosmos DB or Brightpearl record.
Observability
Monitoring
Track your Azure Cosmos DB ⇄ Brightpearl sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Brightpearl.
How the Azure Cosmos DB and Brightpearl connectors work
Azure Cosmos DB
- Integration surface
- REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
- Authentication
- Account keys, resource tokens, or Microsoft Entra ID role-based access
- Change detection
- Built-in change feed exposing inserts and updates in order within each partition key range
- Capabilities
- read · write · CDC
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 Azure Cosmos DB 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 Azure Cosmos DB 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.
Azure Cosmos DB
connected
Brightpearl
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Cosmos DB 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 · Azure Cosmos DB ⇄ 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.
Azure Cosmos DB BrightpearlCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Cosmos DB and Brightpearl integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Cosmos DB and Brightpearl: authenticate both systems, choose the objects to sync (such as Azure Cosmos DB's Containers and Items (JSON documents)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Azure Cosmos DB and Brightpearl. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Azure Cosmos DB: Built-in change feed exposing inserts and updates in order within each partition key range. 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 Azure Cosmos DB side: Partition keys, Change feed entries, Stored procedures and triggers, Databases, plus custom fields where Azure Cosmos DB exposes them. On the Brightpearl side: Inventory and warehouses, Goods-out notes, Invoices and payments, Custom fields. 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 Azure Cosmos DB and Brightpearl: Controlled write-back; Read ERP records with a query; Internal tools and automations without API code. Choose exactly which tables and fields may flow from Azure Cosmos DB back into Brightpearl, keeping the ERP authoritative.
SECURITY
Security teams love 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
CSA STAR
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 386 integrations available for Azure Cosmos DB and Brightpearl.
Popular · 8 of 386
-
Azure Cosmos DB ⇄ Dynamics 365 F&O -
Azure Cosmos DB ⇄ SuiteAnalytics -
Azure Cosmos DB ⇄ Dynamics 365 Business Central -
Azure Cosmos DB ⇄ SAP Business ByDesign -
Brightpearl ⇄ Google AlloyDB -
Brightpearl ⇄ Dynamo DB -
Brightpearl ⇄ IBM Db2 -
Brightpearl ⇄ Firebase
No integrations match .
