Real-time
Real-time sync
Changes in Brightpearl or E2 Shop System instantly reflect in both systems. No stale data, no manual imports.
ERP
Brightpearl to E2 Shop System integration — real-time data sync
Keep Brightpearl and E2 Shop System 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 E2 Shop System
Two ERPs, one set of facts: Stacksync keeps Brightpearl and E2 Shop System consistent in real time, whether they split the business or one is replacing the other.
E2 Shop System is a read-only source: Stacksync reads its data in real time and delivers it into Brightpearl, so Brightpearl always reflects the current state of E2 Shop System — without exports, scripts, or schedulers.
Companies run two ERPs for structural reasons: a two-tier setup with subsidiaries on lighter systems, an acquisition that brought its own stack, a split by function or region, or a migration that will take quarters. In all of these, some of the same organizations, people, and transactions exist in both systems, and keeping them aligned by hand is a standing tax on the back office.
Common use cases
- 01 Push invoices and payments into an accounting platform for reconciliation.
- 02 Keep the product catalog aligned between Brightpearl and e-commerce channels, including price list changes.
- 03 Sync customer and invoice data to accounting or CRM so the front office is not re-keying from the ERP.
- 04 Land quote, job cost, and time-ticket data in a warehouse for margin analysis across jobs.
Common sync patterns
Split by function
Where one system is the people or finance suite and the other runs operations, the records both sides depend on, such as organizations, cost centers, and reference data, stay in agreement.
Two-tier roll-up
Where subsidiaries run one system and headquarters runs the other, shared records and transactions flow up continuously, so consolidation starts from live data.
Migration in parallel
When one system is replacing the other, run both fully live during the transition and cut over without a data freeze.
What you can sync between Brightpearl and E2 Shop System
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 | E2 Shop System objects | How this pairing syncs | |
|---|---|---|---|
| Purchase orders Supplier orders synced with procurement or accounting systems. | Purchase orders Outside material and service purchases tied to jobs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in the writable direction. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Customers Buyer records synced to CRM or accounting counterparts. | Products is specific to Brightpearl and Customers to E2 Shop System — 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. | Vendors Supplier records referenced on purchasing documents. | Sales orders is specific to Brightpearl and Vendors to E2 Shop System — 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. | Parts Part masters with routings and material definitions specific to each shop. | Contacts is specific to Brightpearl and Parts to E2 Shop System — 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. | Routings / Operations Per-part operation sequences that carry estimated and actual times. | Inventory and warehouses is specific to Brightpearl and Routings / Operations to E2 Shop System — 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. | Time tickets Labor collection records used for job costing. | Goods-out notes is specific to Brightpearl and Time tickets to E2 Shop System — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and E2 Shop System
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 E2 Shop System 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.
DeliveryE2 Shop System does not accept inbound record writes, so this direction carries requests rather than records: E2 Shop System's output flows back as field updates on the originating Brightpearl records.
E2 Shop System Brightpearl Interval-based propagation
DetectionStacksync polls E2 Shop System for changes on an incremental schedule, reading only records changed since the previous pass. Polling database tables or scheduled exports.
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.
- E2 Shop System: Not API-bound; constrained by on-premises database access windows.
What ships with Brightpearl ⇄ E2 Shop System
Connect Brightpearl and E2 Shop System for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–E2 Shop System connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or E2 Shop System 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 E2 Shop System record.
Observability
Monitoring
Track your Brightpearl ⇄ E2 Shop System 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 E2 Shop System.
How the Brightpearl and E2 Shop System 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
E2 Shop System
- Integration surface
- No broadly documented public web API; integration typically works through the underlying database or application import/export, depending on deployment
- Authentication
- Database credentials or application-level export access on the on-premises installation
- Change detection
- Polling database tables or scheduled exports
- Capabilities
- read
- Rate limits
- Not API-bound; constrained by on-premises database access windows
How it works
How to connect Brightpearl to E2 Shop System — 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 E2 Shop System 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
E2 Shop System
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and E2 Shop System 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 ⇄ E2 Shop SystemCustomers 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 E2 Shop SystemCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and E2 Shop System integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Brightpearl and E2 Shop System — E2 Shop System is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
On the Brightpearl side: Invoices and payments, Custom fields, Products, Sales orders, plus custom fields where Brightpearl exposes them. On the E2 Shop System side: Time tickets, Invoices, Quotes / Estimates, Jobs / Work orders. Stacksync auto-detects both schemas and converts types between the two systems.
-
E2 Shop System is a read-only source, so this integration runs one-way: Stacksync reads from E2 Shop System in real time and delivers into Brightpearl. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for Brightpearl and E2 Shop System: Split by function; Two-tier roll-up; Migration in parallel. Where one system is the people or finance suite and the other runs operations, the records both sides depend on, such as organizations, cost centers, and reference data, stay in agreement.
-
Brightpearl: 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. E2 Shop System: No broadly documented public web API; integration typically works through the underlying database or application import/export, depending on deployment. Authentication: Database credentials or application-level export access on the on-premises installation. Stacksync manages authentication, retries, and rate limits on both sides.
-
Brightpearl: Resource search endpoints return column-oriented result sets with filter parameters, which is the efficient way to poll for changed records. E2 Shop System: E2 is a Windows-based job shop ERP from Shoptech, now part of ECI Software Solutions, where it has been rebranded as JobBOSS²; most installations run on premises. Stacksync's field mapping accounts for these differences between Brightpearl and E2 Shop System without custom code.
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
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 264 integrations available for Brightpearl and E2 Shop System.
Popular · 3 of 264
No integrations match .
