Skip to content
ERP ⇄ Business productivity

Brightpearl to Notion integration — real-time, two-way sync

Keep Brightpearl and Notion 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 Notion

Bridge the tools people work in and the system the business runs on: real-time, two-way sync between Notion and Brightpearl.

The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Notion is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.

Stacksync syncs Users, Comments, Files and attachments, Pages in Notion with Custom fields, Products, Sales orders, Purchase orders in Brightpearl bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.

Common use cases

  • 01 Sync a Notion content-calendar database with Jira or Linear by mapping status and date properties both directions.
  • 02 Read Notion wiki Pages and their Blocks into a database or search index for internal knowledge retrieval.
  • 03 Keep the product catalog aligned between Brightpearl and e-commerce channels, including price list changes.
  • 04 Land order and margin data in a warehouse for retail performance reporting.

Common sync patterns

Where Brightpearl is the HR or people system of record

Worker and organization data from Brightpearl stays current in Notion, so the tools people use daily reflect the org as it actually is.

Master data corrections travel

A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.

Where Notion faces customers and Brightpearl carries account records

Order, invoice, or account status from Brightpearl appears alongside the customer in Notion, so front-line teams answer from live data.

What you can sync between Brightpearl and Notion

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 Notion objects How this pairing syncs
Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. Pages The core content unit and also every row of a database; synced two-way as records, with typed properties mapping to table columns. Sales orders is specific to Brightpearl and Pages to Notion — each maps to any object or custom field on the other side.
Purchase orders Supplier orders synced with procurement or accounting systems. Databases / Data sources Collections of pages with a typed property schema. Since the 2025-09-03 API a database is a container holding one or more data sources; syncs target a specific data_source_id. Purchase orders is specific to Brightpearl and Databases / Data sources to Notion — each maps to any object or custom field on the other side.
Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. Properties Typed columns on a page — title, rich_text, number, select, multi_select, date, people, relation, status, checkbox, URL. Read and written both ways. Contacts is specific to Brightpearl and Properties to Notion — each maps to any object or custom field on the other side.
Inventory and warehouses On-hand and allocated stock by warehouse, read for availability publishing. Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. Inventory and warehouses is specific to Brightpearl and Blocks to Notion — each maps to any object or custom field on the other side.
Goods-out notes Fulfillment documents that carry picking and shipping status back to order sources. Formula and Rollup properties Values computed by Notion from other fields; read-only, so they are pulled out for reporting but never written back. Goods-out notes is specific to Brightpearl and Formula and Rollup properties to Notion — each maps to any object or custom field on the other side.
Invoices and payments Financial documents synced to accounting platforms for reconciliation. Users Workspace members and bots referenced by people properties; read-only — users cannot be created or invited through the API. Invoices and payments is specific to Brightpearl and Users to Notion — each maps to any object or custom field on the other side.

How changes propagate between Brightpearl and Notion

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 Notion 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 Notion through its API, with automatic retries and rate-limit backoff.

Notion Brightpearl Sub-second propagation

DetectionNotion notifies Stacksync of record changes through webhook events. Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created.

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.
  • Notion: Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
What ships with Brightpearl ⇄ Notion

Connect Brightpearl and Notion for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Notion connection.

Real-time

Two-way sync

Changes in Brightpearl or Notion instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Brightpearl or Notion 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 Notion record.

Observability

Monitoring

Track your Brightpearl ⇄ Notion 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 Notion.

How the Brightpearl and Notion 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

Notion

Integration surface
REST API (api.notion.com/v1)
Authentication
OAuth 2.0 for public integrations, or an internal integration secret (bearer token); every request must send a Notion-Version header
Change detection
Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created; HMAC-SHA256 signed) plus polling on each page's last_edited_time
Capabilities
read · write · webhooks
Rate limits
Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
How it works

How to connect Brightpearl to Notion — 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.

  1. 01

    Connect your apps

    Authenticate Brightpearl and Notion with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Brightpearl connected
    Notion connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Brightpearl and Notion 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Brightpearl ⇄ Notion
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Brightpearl Notion
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Brightpearl and Notion integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 512 integrations available for Brightpearl and Notion.

Popular · 7 of 512
All Brightpearl integrations All Notion integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own