Real-time
Two-way sync
Changes in Brightpearl or Namely instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Human resources
Brightpearl to Namely integration — real-time, two-way sync
Keep Brightpearl and Namely 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 Namely
Sync the workers, org structure, and cost centers that Brightpearl and Namely share in real time, so the people Namely manages stay current in the system that runs finance and operations.
Namely is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Brightpearl runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.
Stacksync syncs Inventory and warehouses, Goods-out notes, Invoices and payments, Custom fields in Brightpearl with Reports, Profile Fields, Events, Profiles in Namely field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Brightpearl keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.
Common use cases
- 01 Keep the product catalog aligned between Brightpearl and e-commerce channels, including price list changes.
- 02 Land order and margin data in a warehouse for retail performance reporting.
- 03 Feed Namely Reports as JSON into a database on a schedule for roster, turnover, and diversity dashboards without manual CSV exports.
- 04 Provision or deprovision accounts in an IdP or directory when a Profile's user_status or start_date changes, and write the resulting user ID and email back onto the Profile.
Common sync patterns
Where Namely runs payroll: labor cost in the books
Pay and compensation data from Namely posts into Brightpearl as labor cost, so finance sees workforce spend without re-entering it by hand.
Where Namely is the worker system of record: one employee master
When a worker is hired, moved, or offboarded in Namely, the matching employee record in Brightpearl is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
New hires ready to transact in Brightpearl
A new person set up in Namely becomes an employee record in Brightpearl in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.
What you can sync between Brightpearl and Namely
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 | Namely objects | How this pairing syncs | |
|---|---|---|---|
| Sales orders Orders from all channels; the central object for fulfillment and revenue syncs. | Teams Teams and team categories a Profile belongs to; read and written for org-chart and provisioning workflows. | Sales orders is specific to Brightpearl and Teams to Namely — each maps to any object or custom field on the other side. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Reports Saved Namely reports returned as JSON snapshots that update instantly; read-only feeds for headcount and roster analytics. | Purchase orders is specific to Brightpearl and Reports to Namely — 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. | Profile Fields Metadata describing standard and company-defined custom field sections; read to discover schema and generate mappings. | Contacts is specific to Brightpearl and Profile Fields to Namely — 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. | Events Home-feed items such as announcements, birthdays, anniversaries, and new arrivals; typically read-only into comms tools. | Inventory and warehouses is specific to Brightpearl and Events to Namely — 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. | Profiles The core employee record (personal, job, contact, and compensation fields); synced two-way via GET/POST/PUT with updated_at driving incremental polling. | Goods-out notes is specific to Brightpearl and Profiles to Namely — each maps to any object or custom field on the other side. | |
| Invoices and payments Financial documents synced to accounting platforms for reconciliation. | Job Titles Job title definitions; read and written so titles stay aligned with an HRIS, directory, or reporting dimension. | Invoices and payments is specific to Brightpearl and Job Titles to Namely — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and Namely
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 Namely 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 Namely through its API, with automatic retries and rate-limit backoff.
Namely Brightpearl Interval-based propagation
DetectionStacksync polls Namely for changes on an incremental schedule, reading only records changed since the previous pass. No webhooks.
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.
- Namely: Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.
What ships with Brightpearl ⇄ Namely
Connect Brightpearl and Namely for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Namely connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Namely 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 Namely record.
Observability
Monitoring
Track your Brightpearl ⇄ Namely 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 Namely.
How the Brightpearl and Namely 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
Namely
- Integration surface
- REST API (JSON over HTTPS)
- Authentication
- OAuth 2.0 authorization-code grant, or a personal access token sent as a Bearer token; all calls run over HTTPS against https://{subdomain}.namely.com/api/v1
- Change detection
- No webhooks; integrations poll GET endpoints and compare the updated_at / created_at timestamps on Profiles and related objects to detect changes
- Capabilities
- read · write
- Rate limits
- Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.
How it works
How to connect Brightpearl to Namely — 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 Namely 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
Namely
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Namely 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 ⇄ NamelyCustomers 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 NamelyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Namely integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Namely: authenticate both systems, choose the objects to sync (such as Brightpearl's Sales orders and Purchase orders), 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 Namely: No webhooks; integrations poll GET endpoints and compare the updated_at / created_at timestamps on Profiles and related objects to detect changes. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Brightpearl side: Inventory and warehouses, Goods-out notes, Invoices and payments, Custom fields, plus custom fields where Brightpearl exposes them. On the Namely side: Reports, Profile Fields, Events, Profiles. 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 Namely: Where Namely runs payroll: labor cost in the books; Where Namely is the worker system of record: one employee master; New hires ready to transact in Brightpearl. Pay and compensation data from Namely posts into Brightpearl as labor cost, so finance sees workforce spend without re-entering it by hand.
-
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. Namely: REST API (JSON over HTTPS). Authentication: OAuth 2.0 authorization-code grant, or a personal access token sent as a Bearer token; all calls run over HTTPS against https://{subdomain}.namely.com/api/v1. Stacksync manages authentication, retries, and rate limits on both sides.
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 404 integrations available for Brightpearl and Namely.
Popular · 5 of 404
-
Brightpearl ⇄ Ukg Ready -
Brightpearl ⇄ Success Factors -
Brightpearl ⇄ Hibob -
Namely ⇄ Microsoft Dynamics GP - Namely ⇄ Microsoft Dynamics NAV
No integrations match .
