Real-time
Two-way sync
Changes in Brightpearl or Shipwire instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ E-commerce
Brightpearl to Shipwire integration — real-time, two-way sync
Keep Brightpearl and Shipwire 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 Shipwire
Keep the storefront in step with the back office: Shipwire and Brightpearl share products, inventory, and orders in real time, in both directions.
Shipwire 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 Products, Stock, Receivings, Returns in Shipwire with Purchase orders, Contacts, Inventory and warehouses, Goods-out notes 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 Shipwire — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Two-way sync Orders between a storefront or ERP database and Shipwire so new orders create fulfillment requests and Stacksync writes Trackings and status (processed, submitted, delivered) back.
- 02 Push Products, kits, and their dimensions and pricing from a PIM or ERP into the Shipwire catalog and keep SKUs aligned.
- 03 Sync Brightpearl sales orders and fulfillment status with a CRM so sales and support see order state without switching tools.
- 04 Mirror inventory levels from Brightpearl into a database that feeds availability to storefronts and marketplaces.
Common sync patterns
Where Brightpearl is the inventory system of record: stock stays accurate
Available quantities from Brightpearl publish to Shipwire, so the store shows what can actually ship and stops overselling.
New orders reach the back office
An order captured in Shipwire creates the matching record in Brightpearl with customer, line items, and totals, so fulfillment and invoicing start without re-entry.
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.
What you can sync between Brightpearl and Shipwire
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 | Shipwire objects | How this pairing syncs | |
|---|---|---|---|
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Products Catalog SKUs including kits, virtual kits, and marketplace products; created and edited via API, commonly mastered in a PIM or ERP and pushed into Shipwire with dimensions and pricing. | 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. | Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Orders B2C fulfillment orders (create, update, cancel, get) with item, hold, routing, and tracking subresources; typically written from a storefront or ERP and synced back with status and trackings. | Sales orders is specific to Brightpearl and Orders to Shipwire — 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. | Stock Real-time per-warehouse inventory levels; read-only, pulled into a database or storefront so availability reflects on-hand and backordered quantities. | Contacts is specific to Brightpearl and Stock to Shipwire — 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. | Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. | Inventory and warehouses is specific to Brightpearl and Receivings to Shipwire — 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. | Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. | Goods-out notes is specific to Brightpearl and Returns to Shipwire — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and Shipwire
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 Shipwire 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 Shipwire through its API, with automatic retries and rate-limit backoff.
Shipwire Brightpearl Sub-second propagation
DetectionShipwire notifies Stacksync of record changes through webhook events. Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics.
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.
- Shipwire: No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
What ships with Brightpearl ⇄ Shipwire
Connect Brightpearl and Shipwire for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Shipwire connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Shipwire 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 Shipwire record.
Observability
Monitoring
Track your Brightpearl ⇄ Shipwire 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 Shipwire.
How the Brightpearl and Shipwire 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
Shipwire
- Integration surface
- REST API (v3)
- Authentication
- Bearer token sent as `Authorization: ShipwireKey <token>`; up to two keys are generated per account on the Users and Roles page, refreshable/expirable, over HTTPS only (separate sandbox at api.beta.shipwire.com)
- Change detection
- Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics; polling the list endpoints as a fallback (no CDC/log stream)
- Capabilities
- read · write · webhooks
- Rate limits
- No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
How it works
How to connect Brightpearl to Shipwire — 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 Shipwire 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
Shipwire
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Shipwire 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 ⇄ ShipwireCustomers 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 ShipwireCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Shipwire integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Shipwire: authenticate both systems, choose the objects to sync (such as Brightpearl's Products and Purchase orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Shipwire side: Products, Stock, Receivings, Returns, plus custom fields where Shipwire exposes them. On the Brightpearl side: Purchase orders, Contacts, Inventory and warehouses, Goods-out notes. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Brightpearl and Shipwire: Where Brightpearl is the inventory system of record: stock stays accurate; New orders reach the back office; One product catalog. Available quantities from Brightpearl publish to Shipwire, so the store shows what can actually ship and stops overselling.
-
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. Shipwire: REST API (v3). Authentication: Bearer token sent as `Authorization: ShipwireKey <token>`; up to two keys are generated per account on the Users and Roles page, refreshable/expirable, over HTTPS only (separate sandbox at api.beta.shipwire.com). Stacksync manages authentication, retries, and rate limits on both sides.
-
Shipwire: Webhook endpoints must return a 200 within 5 seconds over HTTPS; Shipwire retries up to ~10 times over roughly 5.5 hours and deregisters endpoints that keep failing. Brightpearl: The API is split into functional services (order-service, product-service, contact-service, warehouse-service, accounting-service), each with its own resource paths. Stacksync's field mapping accounts for these differences between Brightpearl and Shipwire 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 465 integrations available for Brightpearl and Shipwire.
Popular · 7 of 465
-
Brightpearl ⇄ Easypost -
Brightpearl ⇄ Magento -
Brightpearl ⇄ Nuorder -
Brightpearl ⇄ Shopware -
Shipwire ⇄ Syspro -
Shipwire ⇄ TikTok Shop -
Shipwire ⇄ Unleashed Software
No integrations match .
