Real-time
Two-way sync
Changes in Brightpearl or Gatekeeper instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Business productivity
Brightpearl to Gatekeeper integration — real-time, two-way sync
Keep Brightpearl and Gatekeeper 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 Gatekeeper
Bridge the tools people work in and the system the business runs on: real-time, two-way sync between Gatekeeper and Brightpearl.
The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Gatekeeper is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.
Stacksync syncs Custom data groups, Users, Categories, Contracts in Gatekeeper with Inventory and warehouses, Goods-out notes, Invoices and payments, Custom fields in Brightpearl bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.
Common use cases
- 01 Two-way sync Contracts between Gatekeeper and an ERP or warehouse so value, renewal dates, owner, and status stay current without manual re-keying.
- 02 Sync Vendors (Suppliers) with a CRM or ERP so counterparty, compliance, contact, and spend records match across the VCLM and the systems of record.
- 03 Push invoices and payments into an accounting platform for reconciliation.
- 04 Keep the product catalog aligned between Brightpearl and e-commerce channels, including price list changes.
Common sync patterns
Where Brightpearl is the HR or people system of record
Worker and organization data from Brightpearl stays current in Gatekeeper, so the tools people use daily reflect the org as it actually is.
Master data corrections travel
A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.
Where Gatekeeper faces customers and Brightpearl carries account records
Order, invoice, or account status from Brightpearl appears alongside the customer in Gatekeeper, so front-line teams answer from live data.
What you can sync between Brightpearl and Gatekeeper
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 | Gatekeeper objects | How this pairing syncs | |
|---|---|---|---|
| Custom fields Per-object custom attributes included in field mappings. | Custom data groups Customer-configured custom fields and data groups; because the JSON:API and its docs are dynamic, any custom data added in Configuration exposes the same read/write endpoints as the standard objects and syncs the same way. | Custom fields is specific to Brightpearl and Custom data groups to Gatekeeper — each maps to any object or custom field on the other side. | |
| Products SKU records with variants and price lists, synced with e-commerce and ERP catalogs. | Users Gatekeeper user and team records governed by role-based access; read to map contract and vendor owners, approvers, and internal contacts to CRM or HR records. | Products is specific to Brightpearl and Users to Gatekeeper — 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. | Categories The classification taxonomy applied to contracts and vendors (type, department, business unit); synced so categorization stays consistent between Gatekeeper and downstream reporting or ERP dimensions. | Sales orders is specific to Brightpearl and Categories to Gatekeeper — each maps to any object or custom field on the other side. | |
| Purchase orders Supplier orders synced with procurement or accounting systems. | Contracts The core contract records holding value, key dates, renewal terms, status, type, owner, and the linked vendor; created, read, updated, and deleted so contract data moves two-way between Gatekeeper and a database, ERP, or CRM. | Purchase orders is specific to Brightpearl and Contracts to Gatekeeper — 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. | Vendors (Suppliers) Company records for counterparties and suppliers with onboarding status, compliance, risk, contacts, and spend; read and written to keep vendor master data aligned with a CRM or ERP. | Contacts is specific to Brightpearl and Vendors (Suppliers) to Gatekeeper — 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. | Files Document files attached to contracts and vendors - executed PDFs, certificates, and compliance evidence; read to pull signed files and evidence out, or written to push generated documents in. | Inventory and warehouses is specific to Brightpearl and Files to Gatekeeper — each maps to any object or custom field on the other side. |
How changes propagate between Brightpearl and Gatekeeper
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 Gatekeeper 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 Gatekeeper through its API, with automatic retries and rate-limit backoff.
Gatekeeper Brightpearl Interval-based propagation
DetectionStacksync polls Gatekeeper for changes on an incremental schedule, reading only records changed since the previous pass. No native developer webhook subscription API and no database change-data-capture log.
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.
- Gatekeeper: Gatekeeper publishes no fixed public per-minute request quota; throughput is governed per key by its endpoint permissions, and every call is recorded (parameters, payload, response) under API Logs for monitoring. Pace bulk writes and use JSON:API pagination on list endpoints.
What ships with Brightpearl ⇄ Gatekeeper
Connect Brightpearl and Gatekeeper for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Brightpearl–Gatekeeper connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Brightpearl or Gatekeeper 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 Gatekeeper record.
Observability
Monitoring
Track your Brightpearl ⇄ Gatekeeper 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 Gatekeeper.
How the Brightpearl and Gatekeeper 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
Gatekeeper
- Integration surface
- RESTful API following the JSON:API specification, tenant-scoped with interactive docs at {tenant}.gatekeeperhq.com/api_docs and a published Postman collection. The API is dynamic: it exposes the standard Contract and Vendor objects plus any custom data groups and workflow-form data configured in the tenant.
- Authentication
- API keys created and managed under Configuration > API Keys and passed as a token; each key carries granular per-endpoint permissions set to read-only or write, so access is scoped per object. Multiple keys can be issued and revoked independently.
- Change detection
- No native developer webhook subscription API and no database change-data-capture log; detect changes by polling the JSON:API list endpoints filtered and sorted on updated-at timestamps. Gatekeeper's own event automation - Workflow Engine phase transitions and Interconnect process orchestration - runs inside the platform rather than as a subscribable webhook stream.
- Capabilities
- read · write
- Rate limits
- Gatekeeper publishes no fixed public per-minute request quota; throughput is governed per key by its endpoint permissions, and every call is recorded (parameters, payload, response) under API Logs for monitoring. Pace bulk writes and use JSON:API pagination on list endpoints.
How it works
How to connect Brightpearl to Gatekeeper — 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 Gatekeeper 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
Gatekeeper
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Brightpearl and Gatekeeper 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 ⇄ GatekeeperCustomers 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 GatekeeperCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Brightpearl and Gatekeeper integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Brightpearl and Gatekeeper: authenticate both systems, choose the objects to sync (such as Brightpearl's Custom fields and Products), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Brightpearl and Gatekeeper records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Brightpearl and Gatekeeper connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Brightpearl–Gatekeeper integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Brightpearl and Gatekeeper. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Brightpearl: Webhooks for object created/updated events, with resource search polling as a fallback. On Gatekeeper: No native developer webhook subscription API and no database change-data-capture log; detect changes by polling the JSON:API list endpoints filtered and sorted on updated-at timestamps. Gatekeeper's own event automation - Workflow Engine phase transitions and Interconnect process orchestration - runs inside the platform rather than as a subscribable webhook stream. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Gatekeeper side: Custom data groups, Users, Categories, Contracts, plus custom fields where Gatekeeper exposes them. On the Brightpearl side: Inventory and warehouses, Goods-out notes, Invoices and payments, Custom fields. Stacksync auto-detects both schemas and converts types between the two systems.
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
CSA STAR
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 408 integrations available for Brightpearl and Gatekeeper.
Popular · 4 of 408
-
Brightpearl ⇄ Customer.io -
Brightpearl ⇄ Google Sheets -
Gatekeeper ⇄ NetSuite -
Gatekeeper ⇄ Dynamics 365 Business Central
No integrations match .
