Skip to content
ERP ⇄ E-commerce

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

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

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

Channelengine 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 Cancellations, Backorders, Order documents, Orders in Channelengine 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 Channelengine — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Pull new marketplace orders with GET /v2/orders/new into an ERP or OMS and acknowledge them so fulfillment runs from the system of record.
  • 02 Write Shipments with tracking back to ChannelEngine when the warehouse or ERP marks an order shipped, so each marketplace notifies the buyer.
  • 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

One product catalog

Where both systems keep item records, SKUs, descriptions, and attributes stay aligned so the store and the back office describe the same product.

Fulfillment and shipment status close the loop

As orders are picked, shipped, or invoiced in Brightpearl, tracking and status flow back to Channelengine so buyers see accurate updates.

One customer master

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

What you can sync between Brightpearl and Channelengine

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 Channelengine objects How this pairing syncs
Custom fields Per-object custom attributes included in field mappings. Shipments Fulfillment records; write with POST /v2/shipments to mark an order shipped with tracking, read with GET /v2/shipments. Pushed back from a warehouse or ERP so marketplaces update the buyer. Custom fields is specific to Brightpearl and Shipments to Channelengine — 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. Returns Marketplace- and merchant-initiated returns; read via GET /v2/returns and created with POST /v2/returns. Synced two-way so customer-service and finance systems reconcile with the ERP. Products is specific to Brightpearl and Returns to Channelengine — 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. Cancellations Order cancellations; create with POST /v2/cancellations and read with GET /v2/cancellations. Written when stock is unavailable and read back for reconciliation. Sales orders is specific to Brightpearl and Cancellations to Channelengine — each maps to any object or custom field on the other side.
Purchase orders Supplier orders synced with procurement or accounting systems. Backorders Records marking part of an order as temporarily out of stock; create with POST /v2/backorders and read with GET /v2/backorders by merchant reference or since a date. Purchase orders is specific to Brightpearl and Backorders to Channelengine — 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. Order documents Invoices and other order documents; retrieved as a paginated, filterable list via GET /v2/orders/documents for finance and archiving systems. Read-only. Contacts is specific to Brightpearl and Order documents to Channelengine — 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. Orders Marketplace and merchant-fulfilled orders; read via GET /v2/orders and GET /v2/orders/new (status NEW), then acknowledged with POST /v2/orders/acknowledge so later shipment, return, and cancellation calls can reference them. Inventory and warehouses is specific to Brightpearl and Orders to Channelengine — each maps to any object or custom field on the other side.

How changes propagate between Brightpearl and Channelengine

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

Channelengine Brightpearl Sub-second propagation

DetectionChannelengine notifies Stacksync of record changes through webhook events. Webhooks fire on order creation and on return and shipment/cancellation changes.

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.
  • Channelengine: Rate limits are per endpoint and returned in headers: x-rate-limit-limit (interval length in minutes), x-rate-limit-remaining, and retry-after (seconds to wait); e.g. POST /v2/supportorder allows 3 calls per minute.
What ships with Brightpearl ⇄ Channelengine

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Channelengine

Integration surface
REST API (Merchant API v2); per-tenant base URL https://{tenant}.channelengine.net/api
Authentication
API key passed as the 'apikey' parameter; ChannelEngine recommends sending it in a request header rather than the URL because some webservers log full URLs
Change detection
Webhooks fire on order creation and on return and shipment/cancellation changes; product content and offers use change-tracking endpoints (GET /v2/products/data and /v2/products/offers) with an acknowledge pattern that returns only changed records, plus polling GET /v2/orders/new
Capabilities
read · write · webhooks
Rate limits
Rate limits are per endpoint and returned in headers: x-rate-limit-limit (interval length in minutes), x-rate-limit-remaining, and retry-after (seconds to wait); e.g. POST /v2/supportorder allows 3 calls per minute.
How it works

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

    Choose tables

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

Brightpearl and Channelengine 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 370 integrations available for Brightpearl and Channelengine.

Popular · 5 of 370
All Brightpearl integrations All Channelengine 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