Can you integrate Brightpearl with Shopware?

Explore a Brightpearl and Shopware integration with a Stacksync engineer. Stacksync support for Brightpearl and Shopware is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

Can Brightpearl and Shopware sync in both directions?

Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.

What should be ready before the Brightpearl and Shopware initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Brightpearl account, edition, environment, and business objects the integration must access. Identify the Shopware account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the Brightpearl to Shopware sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.

How do I map Brightpearl fields to Shopware?

Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.

What should I do if a record fails to sync?

Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.

What does a Brightpearl and Shopware integration cost?

Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.

Which records should the Brightpearl and Shopware pilot start with?

Start by reviewing Sales orders in Brightpearl and Orders in Shopware. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.

ERP / E-commerce · Two-way sync platform

Brightpearl and Shopware integration

Plan how Brightpearl and Shopware should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

Brightpearl

Shopware

Review the integration scope

Built for teams where self-serve, reliability and scale matter

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

Proposed workflow

Sales order sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving Brightpearl Sales orders or Shopware Orders needs a defined result in the other system.

Start with Brightpearl Sales orders and Shopware Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.

Review records and field ownership

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between Brightpearl and Shopware
Brightpearl record	Shopware record	Record matching	Field ownership
Sales ordersProposed record; confirm Stacksync object support.Record matching	OrdersProposed record; confirm Stacksync object support.	Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.	Decide which system approves the order and which can cancel or amend it after fulfillment begins.
ContactsProposed record; confirm Stacksync object support.Customer identity assessment	CustomersProposed record; confirm Stacksync object support.	Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.	Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
ProductsProposed record; confirm Stacksync object support.Record matching	ProductsProposed record; confirm Stacksync object support.	Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.	Assign ownership for catalog content, price, and stock separately.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

Brightpearl

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Products Sales orders Purchase orders Contacts Inventory and warehouses Goods-out notes	Confirm support for this record type and the direction you need.

Discuss Brightpearl requirements

Shopware

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Products Categories Customers Orders Order Line Items Order Deliveries	Confirm support for this record type and the direction you need.

Discuss Shopware requirements

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits

Connection requirement	Brightpearl	Shopware
Integration interface	REST API, organized into services (order, product, contact, warehouse, accounting)	Admin API (REST / JSON:API) with a bulk POST /api/_action/sync endpoint
Authentication	Confirm the credentials, API plan, and permissions required for Brightpearl.	Confirm the credentials, API plan, and permissions required for Shopware.
Change detection	Confirm how Stacksync detects changes for this connector and the objects you need.	Confirm how Stacksync detects changes for this connector and the objects you need.
Read access	Confirm with Stacksync	Confirm with Stacksync
Write access	Confirm with Stacksync	Confirm with Stacksync

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

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

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:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

Brightpearl

Integration interface: REST API, organized into services (order, product, contact, warehouse, accounting)
Authentication: Confirm the credentials, API plan, and permissions required for Brightpearl.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the Brightpearl account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Brightpearl, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for Brightpearl and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Shopware

Integration interface: Admin API (REST / JSON:API) with a bulk POST /api/_action/sync endpoint
Authentication: Confirm the credentials, API plan, and permissions required for Shopware.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the Shopware account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Shopware, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for Shopware and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare Brightpearl and Shopware access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

Brightpearl setup checklist

Identify the Brightpearl account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Brightpearl, including read/write support, authentication, and initial-load limits.

Shopware setup checklist

Identify the Shopware account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Shopware, including read/write support, authentication, and initial-load limits.

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the Brightpearl and Shopware planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Record matching

Sales orders / Orders

Compare whether Brightpearl Sales orders and Shopware Orders describe the same sales order in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Brightpearl: Object support to establish
Shopware: Object support to establish
Record identity: Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
Field ownership: Decide which system approves the order and which can cancel or amend it after fulfillment begins.

Fields to include

Source order ID
Customer reference
Line references and quantities
Order status
Currency

Record dependencies: Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation: Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Recovery: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Customer identity

Contacts / Customers

Before linking Brightpearl Contacts to Shopware Customers, check whether the customer is an individual or a company. Match the correct record type in each system.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Brightpearl: Object support to establish
Shopware: Object support to establish
Record identity: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership: Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

Source customer ID
Person/company classification
Legal entity or business unit
Destination identity reference

Record dependencies: Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Record matching

Products / Products

Compare whether Brightpearl Products and Shopware Products describe the same product or catalog item in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Brightpearl: Object support to establish
Shopware: Object support to establish
Record identity: Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
Field ownership: Assign ownership for catalog content, price, and stock separately.

Fields to include

Source product ID
SKU or variant reference
Description
Unit of measure
Price-list reference

Record dependencies: Resolve units, variants, categories, and applicable price lists before order lines.
Validation: Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
Recovery: Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Sales orders / Orders to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your Brightpearl and Shopware record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Sales orders / Orders, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider when Brightpearl and Shopware need a transformation, approval, or action outside a direct record sync.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit: Consider for a one-time Brightpearl / Shopware migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Sales order sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Sales orders or Orders record needs a defined result in the other system.

Start with Brightpearl Sales orders and Shopware Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.

If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Customer sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Contacts or Customers record needs a defined result in the other system.

Start with Brightpearl Contacts and Shopware Customers. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Product or catalog item sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Products or Products record needs a defined result in the other system.

Start with Brightpearl Products and Shopware Products. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve units, variants, categories, and applicable price lists before order lines.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.

If it fails: Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.

Reconcile Brightpearl business records with Shopware

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A finance-owned record in Brightpearl needs operational visibility through Products or Customers.

Select Products or Sales orders with the correct legal entity, period, and currency.
Define a reporting relationship in Shopware; do not equate customer records, ledger accounts, and posted transactions.
Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated sales order change

Investigate

Inspect Brightpearl Sales orders and Shopware Orders, their IDs, and the destination error.

Next action

Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Rejected or repeated customer change

Investigate

Inspect Brightpearl Contacts and Shopware Customers, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Rejected or repeated product or catalog item change

Investigate

Inspect Brightpearl Products and Shopware Products, their IDs, and the destination error.

Next action

Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.

A record type or update is unavailable

Investigate

Check the Brightpearl and Shopware connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between Brightpearl and Shopware

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

Brightpearl Shopware Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Shopware.

Shopware Brightpearl Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Brightpearl.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Review write-back, deletion handling, update timing, and account limits with the integration team.
Review write-back, deletion handling, update timing, and account limits with the integration team.

FAQ