Skip to content
ERP ⇄ E-commerce

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

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

Keep the storefront in step with the back office: Magento and Brightpearl share products, inventory, and orders in real time, in both directions.

Magento runs the storefront and takes the orders; Brightpearl owns the item master, the stock on hand, and the finance behind every transaction. The two overlap wherever the same products, customers, and sales matter to both — and when re-keying or an overnight batch is what connects them, the store oversells items it can't ship, quotes prices finance never set, or leaves buyers waiting on status that already changed.

Stacksync syncs Configurable / variant products, Categories, Orders, Customers in Magento with Invoices and payments, Custom fields, Products, Sales orders in Brightpearl field by field, in real time, and in both directions. You decide which system owns which fields — stock and pricing from Brightpearl, order and customer detail from Magento — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync Orders, invoices, and shipments from Magento into Postgres or a warehouse for revenue, margin, and fulfillment-SLA reporting.
  • 02 Master Products, prices, and Category assignments in an ERP or PIM and write them into Magento's catalog by SKU.
  • 03 Mirror inventory levels from Brightpearl into a database that feeds availability to storefronts and marketplaces.
  • 04 Push invoices and payments into an accounting platform for reconciliation.

Common sync patterns

One customer master

Where both systems keep customer records, a correction in either propagates to the other, ending dual maintenance.

Where Brightpearl is the inventory system of record: stock stays accurate

Available quantities from Brightpearl publish to Magento, so the store shows what can actually ship and stops overselling.

New orders reach the back office

An order captured in Magento creates the matching record in Brightpearl with customer, line items, and totals, so fulfillment and invoicing start without re-entry.

What you can sync between Brightpearl and Magento

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 Magento objects How this pairing syncs
Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. Products Catalog items keyed by SKU; carry created_at/updated_at for incremental polling and are written two-way from a PIM or ERP into the storefront. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Purchase orders Supplier orders synced with procurement or accounting systems. Inventory source items (MSI) Per-source stock quantities under Multi-Source Inventory; written from a WMS/ERP so storefront stock matches the warehouse. Purchase orders is specific to Brightpearl and Inventory source items (MSI) to Magento — 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. Invoices Invoice documents tied to orders; read out for finance and revenue recognition, or created via the sales API when billing downstream. Contacts is specific to Brightpearl and Invoices to Magento — 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. Shipments Shipment and tracking records against orders; created or read to drive fulfillment status between Magento and a 3PL/WMS. Inventory and warehouses is specific to Brightpearl and Shipments to Magento — 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. Carts / quotes Active and guest carts (quotes) with items and totals; read for abandoned-cart analysis (not available on the Cloud Service subset). Goods-out notes is specific to Brightpearl and Carts / quotes to Magento — each maps to any object or custom field on the other side.
Invoices and payments Financial documents synced to accounting platforms for reconciliation. Configurable / variant products Parent configurable products link to simple product variants by attribute; synced so size/color SKUs and their prices stay aligned with source systems. Invoices and payments is specific to Brightpearl and Configurable / variant products to Magento — each maps to any object or custom field on the other side.

How changes propagate between Brightpearl and Magento

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

Magento Brightpearl Sub-second propagation

DetectionMagento notifies Stacksync of record changes through webhook events. Polling with searchCriteria filters on updated_at (catalog, sales, and customer entities carry created_at/updated_at).

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.
  • Magento: No fixed request-per-minute cap on PaaS/on-prem; responses page via searchCriteria pageSize/currentPage under a default maximum page size of 300 (Web API Input Limits), with /async/bulk endpoints for large writes.
What ships with Brightpearl ⇄ Magento

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Magento

Integration surface
REST and GraphQL Web APIs (SOAP also available)
Authentication
Token-based OAuth: an integration's access token (consumer key/secret + access token/secret) or a Bearer admin token (default 4-hour expiry); Adobe Commerce as a Cloud Service authenticates via Adobe IMS (OAuth 2)
Change detection
Polling with searchCriteria filters on updated_at (catalog, sales, and customer entities carry created_at/updated_at); optional near-real-time via the Adobe Commerce Webhooks / Adobe I/O Events modules (order/created, product/updated, customer/created)
Capabilities
read · write · webhooks
Rate limits
No fixed request-per-minute cap on PaaS/on-prem; responses page via searchCriteria pageSize/currentPage under a default maximum page size of 300 (Web API Input Limits), with /async/bulk endpoints for large writes.
How it works

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

    Choose tables

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

Brightpearl and Magento 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
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 465 integrations available for Brightpearl and Magento.

Popular · 8 of 465
All Brightpearl integrations All Magento 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