Real-time
Two-way sync
Changes in Brightpearl or Supabase instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Database
Brightpearl to Supabase integration — real-time, two-way sync
Keep Brightpearl and Supabase 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 Supabase
Give your engineers Brightpearl's data in Supabase: 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 Contacts, Inventory and warehouses, Goods-out notes, Invoices and payments from Brightpearl into Supabase 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 Supabase sync back into Brightpearl with its validations respected.
Common use cases
- Reflect auth.users state into support and CRM systems so teams see account status without querying the database
- Push product events captured in Supabase Postgres to marketing tools for lifecycle campaigns
- Keep the product catalog aligned between Brightpearl and e-commerce channels, including price list changes.
- Land order and margin data in a warehouse for retail performance reporting.
Controlled write-back
Choose exactly which tables and fields may flow from Supabase back into Brightpearl, keeping the ERP authoritative.
Read ERP records with a query
Records from Brightpearl live in Supabase 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 Brightpearl and Supabase
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 | Supabase objects | |
|---|---|---|
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | auth.users Managed authentication users, often mirrored into CRM or support systems. | |
| Custom fields Per-object custom attributes included in field mappings. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Database Functions Postgres functions that can transform or validate synced rows. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Storage Object Metadata File metadata rows that can be joined to synced application data. | |
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | Tables Standard Postgres tables; the primary two-way sync target. |
What ships with Brightpearl ⇄ Supabase
Connect Brightpearl and Supabase for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Supabase connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Supabase 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 Supabase record.
Observability
Monitoring
Track your Brightpearl ⇄ Supabase 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 Supabase.
How the Brightpearl and Supabase 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
Supabase
- Integration surface
- Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST)
- Authentication
- Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer
- Change detection
- Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits
How it works
How to connect Brightpearl to Supabase — 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 Supabase 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
Supabase
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Supabase 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 ⇄ SupabaseCustomers 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 SupabaseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Supabase integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Supabase: authenticate both systems, choose the objects to sync (such as Brightpearl's Invoices and payments and Custom fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Supabase: PostgREST auto-generates a REST endpoint per table, with Row Level Security policies gating access at the row level. Brightpearl: The API is split into functional services (order-service, product-service, contact-service, warehouse-service, accounting-service), each with its own resource paths. Stacksync's field mapping accounts for these differences between Brightpearl and Supabase without custom code.
-
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 Supabase records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Brightpearl and Supabase connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Brightpearl–Supabase integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Brightpearl and Supabase. 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 Supabase: Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 Brightpearl and Supabase.
Popular · 8 of 386
-
Brightpearl ⇄ SAP ASE (Sybase) -
Brightpearl ⇄ Scaleway Postgres -
Brightpearl ⇄ TiDB -
Brightpearl ⇄ TimescaleDB -
Supabase ⇄ Manhattan Associates WMS -
Supabase ⇄ Microsoft Dynamics GP - Supabase ⇄ Microsoft Dynamics NAV
-
Supabase ⇄ Plex ERP
No integrations match .
