Two-way sync
Changes in Brightpearl or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Keep Brightpearl and Nutshell in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Nutshell holds the customer relationship; Brightpearl runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.
Stacksync syncs Tags, Users, Leads, People in Nutshell 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; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Owners, territories, and org structure informed by Brightpearl stay current in Nutshell.
A deal won in Nutshell creates or updates the customer in Brightpearl with clean data, so fulfillment and invoicing start without re-entry.
Invoice and payment state from Brightpearl shows on the account in Nutshell, so reps see balances before promising the next order.
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 | Nutshell objects | How this pairing syncs | |
|---|---|---|---|
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Products Line items attached to leads, used to sync sold products into billing | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Contacts Customers and suppliers in one contact model, matched to CRM records by email or reference. | People Individual contacts, kept consistent with marketing and outreach tools | Contacts is specific to Brightpearl and People to Nutshell — 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. | Companies Account records that group people and leads for account-level syncs | Inventory and warehouses is specific to Brightpearl and Companies to Nutshell — 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. | Activities Logged calls, meetings, and emails used for engagement reporting | Goods-out notes is specific to Brightpearl and Activities to Nutshell — each maps to any object or custom field on the other side. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Tasks Rep to-dos mirrored into external work-management or reporting systems | Invoices and payments is specific to Brightpearl and Tasks to Nutshell — each maps to any object or custom field on the other side. | |
| Custom fields Per-object custom attributes included in field mappings. | Notes Free-text history attached to leads and contacts, replicated for a full timeline | Custom fields is specific to Brightpearl and Notes to Nutshell — each maps to any object or custom field on the other side. |
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.
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 Nutshell through its API, with automatic retries and rate-limit backoff.
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
DeliveryEach detected change is written to Brightpearl through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Nutshell connection.
Changes in Brightpearl or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Brightpearl or Nutshell data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Brightpearl or Nutshell record.
Track your Brightpearl ⇄ Nutshell sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Brightpearl and Nutshell.
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.
Authenticate Brightpearl and Nutshell with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Brightpearl and Nutshell 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Nutshell: authenticate both systems, choose the objects to sync (such as Brightpearl's Products and Contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Brightpearl: Webhooks for object created/updated events, with resource search polling as a fallback. On Nutshell: Webhook subscriptions for record events, with polling as fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Nutshell side: Tags, Users, Leads, People, plus custom fields where Nutshell exposes them. On the Brightpearl side: Invoices and payments, Custom fields, Products, Sales orders. 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 Nutshell: Where Brightpearl manages people and org data: keep Nutshell aligned; Where Brightpearl handles order-to-cash: closed-won flows through; Where Brightpearl is the finance system of record: money status on the account. Owners, territories, and org structure informed by Brightpearl stay current in Nutshell.
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. Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 421 integrations available for Brightpearl and Nutshell.