Skip to content
ERP ⇄ CRM

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

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

Close the gap between front office and back office: Shopify and Brightpearl share customers and status in real time, in both directions.

Shopify holds the customer relationship; Brightpearl runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.

Stacksync syncs Products, ProductMedias, ProductVariants, Orders in Shopify with Sales orders, Purchase orders, Contacts, Inventory and warehouses in Brightpearl field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync orders, customers, and inventory into Postgres for operational reporting across stores.
  • 02 Keep customer records aligned between Shopify and a CRM for segmentation and lifetime-value analysis.
  • 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 handles order-to-cash: closed-won flows through

A deal won in Shopify creates or updates the customer in Brightpearl with clean data, so fulfillment and invoicing start without re-entry.

Where Brightpearl is the finance system of record: money status on the account

Invoice and payment state from Brightpearl shows on the account in Shopify, so reps see balances before promising the next order.

One customer master

Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.

What you can sync between Brightpearl and Shopify

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 Shopify objects How this pairing syncs
Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. Products Catalog entries; often mastered in a PIM or ERP and written into Shopify. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Invoices and payments Financial documents synced to accounting platforms for reconciliation. Orders Purchase transactions; pushed to ERPs for fulfillment and billing, and read into databases for reporting. Invoices and payments is specific to Brightpearl and Orders to Shopify — each maps to any object or custom field on the other side.
Custom fields Per-object custom attributes included in field mappings. Customers Buyer records; matched to CRM contacts for marketing and lifetime-value analysis. Custom fields is specific to Brightpearl and Customers to Shopify — 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. Abandoned Checkouts Synced with incremental and full sync per the Stacksync docs. Sales orders is specific to Brightpearl and Abandoned Checkouts to Shopify — each maps to any object or custom field on the other side.
Purchase orders Supplier orders synced with procurement or accounting systems. ProductMedias Synced with incremental and full sync per the Stacksync docs. Purchase orders is specific to Brightpearl and ProductMedias to Shopify — 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. ProductVariants Synced with incremental and full sync per the Stacksync docs. Contacts is specific to Brightpearl and ProductVariants to Shopify — each maps to any object or custom field on the other side.

How changes propagate between Brightpearl and Shopify

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

Shopify Brightpearl Sub-second propagation

DetectionShopify notifies Stacksync of record changes through webhook events. Webhook topics per resource, with polling on updated_at as a fallback.

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.
  • Shopify: GraphQL uses a calculated query-cost budget; the REST API uses a leaky-bucket model.
What ships with Brightpearl ⇄ Shopify

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Shopify

Integration surface
GraphQL Admin API (primary) and REST Admin API (legacy)
Authentication
OAuth via a custom Shopify app: admin creates an app in the Shopify Dev Dashboard, enables required API scopes, sets the Stacksync redirect URL, then supplies shop name + Client ID and Client Secret to Stacksync
Change detection
Webhook topics per resource, with polling on updated_at as a fallback
Capabilities
read · write · webhooks
Rate limits
GraphQL uses a calculated query-cost budget; the REST API uses a leaky-bucket model.
Shopify setup guide
How it works

How to connect Brightpearl to Shopify — 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 Shopify 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
    Shopify connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Brightpearl and Shopify 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 ⇄ Shopify
    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 Shopify
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Brightpearl and Shopify 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.

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 390 integrations available for Brightpearl and Shopify.

Popular · 8 of 390
Coworkers laughing in front of a laptop in a casual office setting

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