Real-time
Two-way sync
Changes in Brightpearl or Google Cloud Spanner instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Database
Brightpearl to Google Cloud Spanner integration — real-time, two-way sync
Keep Brightpearl and Google Cloud Spanner 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 Brightpearl and Google Cloud Spanner
Give your engineers Brightpearl's data in Google Cloud Spanner: 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 Goods-out notes, Invoices and payments, Custom fields, Products from Brightpearl into Google Cloud Spanner 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 Google Cloud Spanner sync back into Brightpearl with its validations respected.
Common use cases
- 01 Run a two-way sync between Spanner and a SaaS tool so edits made by ops teams land back in the application database.
- 02 Consolidate data from a globally distributed Spanner deployment into regional business systems.
- 03 Land order and margin data in a warehouse for retail performance reporting.
- 04 Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.
Common sync patterns
Where Brightpearl is the HR system of record: people data for internal systems
Worker and org records stay current in Google Cloud Spanner for provisioning, access, and reporting systems that read from the database.
Controlled write-back
Choose exactly which tables and fields may flow from Google Cloud Spanner back into Brightpearl, keeping the ERP authoritative.
Read ERP records with a query
Records from Brightpearl live in Google Cloud Spanner as ordinary tables or collections, joinable with the rest of your data.
What you can sync between Brightpearl and Google Cloud Spanner
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.
| Brightpearl objects | Google Cloud Spanner objects | How this pairing syncs | |
|---|---|---|---|
| Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. | Tables Relational tables mapped one-to-one to sync targets. | Goods-out notes is specific to Brightpearl and Tables to Google Cloud Spanner — each maps to any object or custom field on the other side. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Rows The unit of read and write in each sync cycle, keyed by primary key. | Invoices and payments is specific to Brightpearl and Rows to Google Cloud Spanner — each maps to any object or custom field on the other side. | |
| Custom fields Per-object custom attributes included in field mappings. | Interleaved tables Child rows physically co-located with parents; synced as related records. | Custom fields is specific to Brightpearl and Interleaved tables to Google Cloud Spanner — each maps to any object or custom field on the other side. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Secondary indexes Used to make incremental read queries efficient on non-key columns. | Products is specific to Brightpearl and Secondary indexes to Google Cloud Spanner — each maps to any object or custom field on the other side. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Change streams Capture inserts, updates, and deletes for log-style change data capture. | Sales orders is specific to Brightpearl and Change streams to Google Cloud Spanner — each maps to any object or custom field on the other side. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Views Read-only projections useful for shaping data before it leaves Spanner. | Purchase orders is specific to Brightpearl and Views to Google Cloud Spanner — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and Google Cloud Spanner
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.
Brightpearl Google Cloud Spanner 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 applied to Google Cloud Spanner as a row-level write, with types converted between the two schemas.
Google Cloud Spanner Brightpearl Sub-second propagation
DetectionChanges in Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.
DeliveryEach detected change is written to Brightpearl through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Brightpearl: Requests are throttled per account under Brightpearl's API usage policies; bulk operations should use batch endpoints.
- Google Cloud Spanner: Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
What ships with Brightpearl ⇄ Google Cloud Spanner
Connect Brightpearl and Google Cloud Spanner for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Google Cloud Spanner connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Google Cloud Spanner 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 Brightpearl or Google Cloud Spanner record.
Observability
Monitoring
Track your Brightpearl ⇄ Google Cloud Spanner sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Brightpearl and Google Cloud Spanner.
How the Brightpearl and Google Cloud Spanner connectors work
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
Google Cloud Spanner
- Integration surface
- gRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects)
- Authentication
- Google Cloud IAM (service accounts)
- Change detection
- Change streams (log-style CDC), or timestamp-based polling queries
- Capabilities
- read · write · CDC
- Rate limits
- Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
How it works
How to connect Brightpearl to Google Cloud Spanner — 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 Brightpearl and Google Cloud Spanner with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Brightpearl
connected
Google Cloud Spanner
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Google Cloud Spanner 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 · Brightpearl ⇄ Google Cloud SpannerCustomers 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.
Brightpearl Google Cloud SpannerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Google Cloud Spanner integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Google Cloud Spanner: authenticate both systems, choose the objects to sync (such as Brightpearl's Goods-out notes and Invoices and payments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Brightpearl and Google Cloud Spanner records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Brightpearl and Google Cloud Spanner connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Brightpearl–Google Cloud Spanner integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Brightpearl and Google Cloud Spanner. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Brightpearl: Webhooks for object created/updated events, with resource search polling as a fallback. On Google Cloud Spanner: Change streams (log-style CDC), or timestamp-based polling queries. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Google Cloud Spanner side: Rows, Interleaved tables, Secondary indexes, Change streams, plus custom fields where Google Cloud Spanner exposes them. On the Brightpearl side: Goods-out notes, Invoices and payments, Custom fields, Products. Stacksync auto-detects both schemas and converts types between the two systems.
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 428 integrations available for Brightpearl and Google Cloud Spanner.
Popular · 5 of 428
-
Brightpearl ⇄ AWS Aurora PostgreSQL -
Brightpearl ⇄ MongoDB -
Brightpearl ⇄ CockroachDB -
Brightpearl ⇄ Google AlloyDB -
Google Cloud Spanner ⇄ Cin7
No integrations match .
